Support — for the clinic with no IT staff and no vendor within a day’s travel
The feature set that makes a one-clinician clinic stay on the software when there is nobody else to ask.
ITEM 8PlannedNo patient data
Answers “how do I do this in blueHealthcare?”
Answers how-to questions about the software itself from our own manuals, citing the exact page — never from or about a clinic’s patient data.
Synthetic example walkthrough
Who
Dr. Aisha Rahman (synthetic example), a solo-practice physician who just switched to blueHealthcare.
Situation
She needs to void an order she placed by mistake but cannot find the control.
Blue shows
“To void an order: open it from the patient’s chart, select ‘Void’, and enter a reason — see Orders Manual, page 14, ‘Correcting a placed order.’”
They do
Dr. Rahman follows the steps, or opens the linked manual page to read the full procedure herself.
Design mockup · not built Shown inside blueHealthcare's real shell (top bar, left rail, product tokens) with synthetic data, composed from the platform's own components — not a live feature, and not a real screenshot of a shipped screen.
What it never does
Never answers a question about a specific patient’s data — only how the software itself works.
Never invents a workflow the manual does not describe.
ITEM 9PlannedNo patient data
Answers from the runbook, citing the page
For operational and technical issues, answers from the clinic’s own runbook and a diagnostic bundle built to carry no patient data, citing the exact runbook page.
Synthetic example walkthrough
Who
James Okafor (synthetic example), the one IT-literate staff member at a rural clinic, hours from the nearest vendor visit.
Situation
The interface to the lab analyzer stopped sending results overnight.
Blue shows
“Runbook page 22 describes this exact symptom. The diagnostic bundle shows the analyzer’s last heartbeat was 6 hours ago, consistent with the analyzer being powered off or its network cable disconnected.”
They do
James checks the analyzer, finds the cable unplugged, reconnects it, and confirms messages resume.
Design mockup · not built Shown inside blueHealthcare's real shell (top bar, left rail, product tokens) with synthetic data, composed from the platform's own components — not a live feature, and not a real screenshot of a shipped screen.
What it never does
Never reads or reasons about patient data — the diagnostic bundle excludes it by construction.
Never changes any configuration itself — a person acts on what it says.
ITEM 10PlannedNo patient data
Tutors a new user in a sandbox
Lets a brand-new clinician practice the software on synthetic patients in a sandbox, with Blue suggesting what to try next and answering questions — nothing done there ever touches a real record.
Synthetic example walkthrough
Who
Ngozi Chukwu (synthetic example), a newly hired nurse at a clinic with no training budget.
Situation
It is her first day and nobody is free to train her one-on-one.
Blue shows
In the sandbox only: “Try placing an order for the synthetic patient ‘Test Patient A’ — open their chart and select ‘New order.’”
They do
Ngozi practices as long as she needs, asking Blue questions about what each screen does.
Design mockup · not built Shown inside blueHealthcare's real shell (top bar, left rail, product tokens) with synthetic data, composed from the platform's own components — not a live feature, and not a real screenshot of a shipped screen.
What it never does
Never operates outside the sandbox.
Never touches a real patient record during a training session.
Never migrates anything a trainee does into production data.
