Roadmap & status
What works today, what's in progress, and where temetro is headed.
temetro is open source and under active development. This page is the honest summary of where things stand.
What works today
| Area | Status |
|---|---|
| Accounts & sign-in (email or username, password reset) | ✅ Working |
| Multi-clinic workspaces with invitations and roles | ✅ Working |
| Department roles & dashboards (Pharmacy dispensing queue, Lab work queue + result entry) | ✅ Working |
| Pharmacy inventory (medication stock & availability) | ✅ Working |
| Patient records (demographics, allergies, medications, problems, labs, encounters, vitals with trends) | ✅ Working |
/patient <fileNumber> lookup with record cards in chat | ✅ Working |
| AI chat agent (bring your own OpenAI / Anthropic / Gemini key, or local Ollama) with record cards, lab charts & database import | ✅ Working |
| Veil PHI de-identification + approval gate for AI writes | ✅ Working |
| Appointments, prescriptions, tasks (personal + department queues) | ✅ Working |
| Real-time staff messaging & notifications | ✅ Working |
| Activity log (audit trail) & analytics dashboard | ✅ Working |
| Per-user settings (notification preferences) & account deletion | ✅ Working |
| Self-hosting with Docker Compose | ✅ Working |
Mobile apps
Native clinician apps are in the works alongside the web app:
| App | Status |
|---|---|
| iOS app | 🚧 In progress — actively being built |
| Android app | 🚧 In development — runs as a separate effort on its own track and timeline |
Both will talk to the same backend API as the web app. The patient companion app (for approving record changes) is a separate, later project.
The AI chat is now live: free-form messages run a tool-using agent that looks up records and replies with cards and lab charts. You bring your own model — an OpenAI, Anthropic, or Gemini API key, or a local Ollama model — configured under Settings → AI. Patient data is protected by Veil (de-identification before any external call) and an approval gate for writes. See AI setup & safeguards.
In progress / planned
Deeper AI workflows
The agent reads records, charts labs, and imports databases today. Planned next: richer clinical reasoning, summarization across encounters, and tighter free-text PHI scrubbing in Veil.
Patient-owned records & signing
The defining long-term vision (explained in Core concepts):
- Records stored on the patient's own device, not only in the clinic database.
- Every clinician change cryptographically signed, blockchain-style.
- Changes stay pending until the patient approves them in a companion app.
- A patient companion app for reviewing and approving changes.
None of this is built yet. Today, accountability is provided by the activity log, which records every change with who made it and when.
Hospital ledger (blockchain)
A future, hospital-side blockchain-style ledger: every clinical change hash-chained to the previous one and signed by the clinic, so the hospital's own record history is tamper-evident and verifiable end-to-end. This is the on-prem counterpart to — and a stepping stone toward — the patient-owned signing above. Today it's approximated by the plain activity log; the chained-and-signed version is planned.
Email verification enforcement
Verification emails are already sent (and the /verify-email page exists), but
sign-in currently does not require a verified address. Enforcement is wired and can
be switched on; it will be enabled by default once email delivery setup is documented
for production.
Catching up with established EHRs
temetro focuses on the AI-chat + patient-owned-records core first. Features that established clinic systems offer and temetro doesn't yet — all planned for later:
| Feature | Status |
|---|---|
| Billing & invoicing (incl. insurance claims) | 📋 Planned |
| e-Prescribing to pharmacies | 📋 Planned |
| Lab system integrations (HL7 / FHIR) | 📋 Planned |
| Internal video visits (doctor ↔ hospital-staff consults, not patient-facing) | 📋 Planned |
| Patient portal (self-service booking, results) | 📋 Planned |
| Document & imaging attachments on the chart | 📋 Planned |
| Multi-language UI (i18n plumbing exists; English only today) | 📋 Planned |
Contributing
temetro is open source — if any of the above sounds like something you'd like to help build, see the contributing guide. Wiring the real LLM into the chat is a particularly good place to start.