PatientKeeper Retorno

PatientKeeper Retorno turns unresolved clinic follow-up into an accountable next administrative step. Inspired by daily work supporting medical practices, it combines eight fictional return cases with a doctor workspace for an illustrative bunion and bunionette episode. The doctor assigns ownership, a next action and an administrative due date, reviews exact sources and messages, and records a simulated reply or refusal before human closure. Changed sources invalidate earlier reviews; conflicts and clinical questions require handoff. A secretary is not required to operate the new workspace. On October 16, the local app called an Evolus workflow connected to Gemma through AMD Token Factory, with a read-only knowledge library. One run returned pure JSON in 8.149 seconds with two literal citations, mandatory human review and unchanged case state. Configuration was verified; execution metadata does not independently report model identity or hardware. The source includes the optional API integration, disabled by default, and a validated Linux/arm64 container. Earlier direct Gemma attempts and the separate Qwen AMD GPU pilot remain documented. The public demo is static: recorded proof, no live inference or WhatsApp sending. Consultation notes extract selected transcript segments with references. PT/EN audio transcription runs only in the configured local CPU version. No signed medical record or clinical protocol is generated. EN/PT/ES, dark mode and a fictional read-only doctor calendar support exploration. October 5 scaffolding and event work from October 12-16 are disclosed. Illustrative scenario: six records/day at fifteen reported manual minutes versus ten assumed assisted minutes would free thirty minutes/day, including preparation, review and corrections. Savings are unmeasured. All cases are fictional; no patient data is used.