Sector examplesHealthcare
Demo Clinic
A patient assistant that books appointments, answers policy questions and screens urgency safely, without ever diagnosing.
The problem it solves
Clinics want patients to book and get answers at any hour, but an assistant must never diagnose, must send emergencies to emergency care immediately, must keep each patient's data private, and must let partner organisations send referrals without exposing patient records.
- Red-flag symptoms trigger emergency guidance and a clear notice, never a diagnosis
- Bookings and cancellations wait for the patient's confirmation and can't be made for someone else
- Patients can see a pseudonymous log of every access to their data
Run it on your computer
git clone https://github.com/karawash-projects/amoxi.gitcd amoxinpm installnpm run buildnpm run dev -w clinic-assistantThen open http://localhost:8082. The tests run with npm test -w clinic-assistant.
Amoxi features in this example
| Feature | Why it matters here |
|---|---|
| Safety checks on answers | A wrapper around the model holds back any sentence that diagnoses or recommends a medicine, so it is never shown or saved. |
| Tools with approval | The patient confirms each booking and cancellation; double bookings are refused. |
| Guardrails | Booking for another patient is refused before the patient is ever asked to confirm. |
| Generative UI | Clinician cards, a time-slot picker, confirmations and an emergency notice the patient can act on. |
| Knowledge base (RAG) | Cancellation, vaccination, prescription and privacy questions are answered from clinic policies, with the section cited. |
| Memory with consent | Only preferences such as a preferred clinician or language are remembered, never clinical details. |
| A2A for partners | Pharmacies and hospitals send referrals agent to agent, and the clinic can tell partner requests apart from patients. |