ZYVORA
Talk to us

Modules

Everything a day on the ward needs.

The modules share one patient record, one sign-in and one audit trail. Each card says what exists; the limits are listed at the bottom of the page.

Dashboard

Today's timeline, the waiting room, trends and ward bed maps, tuned to the signed-in role.

Patients

Registry, allergies and history, problems and immunisations, with restricted records that open only through break-glass.

Appointments

Scheduling with no double-booking enforced in the database, check-in and a waiting room; a missed visit opens a rebooking task.

Encounters and prescribing

SOAP notes, orders, prescribing with an honest safety report, signing and amendments.

Consultation assistant

With the patient's consent, a transcript becomes a draft whose every statement points to the lines it came from; a named clinician accepts, edits or rejects each one and signs.

Templates and chart forms

Skeleton note text and structured forms (a per-tooth map, right and left pairs, choices) that the hospital writes for its specialties. Nothing clinical ships in the software.

Emergency

A tracking board with triage decision support (a trained classifier plus safety rules) and treatment-to-admission flow.

Beds, discharge and theatre

Admissions and transfers with a bed map; discharge plans whose milestones are tasks with owners; theatre scheduling the database will not let overlap.

Laboratory

Separate result entry and verification, critical alerts, turnaround against the lab's own targets, home sample collection with a printable round.

Imaging

Orders with a wrong-patient guard and radiologist-only reports.

Pharmacy and medication review

An expiry-first stock ledger, dispensing and returns; before-admission, in-hospital and discharge lists compared by fixed rules. Interaction and dose checks report “unavailable” until a drug database is connected.

Billing, finance and claims

Exact money, tax rules as data, idempotent payments, refunds; events that never reached an invoice; collections; claim cases with checklists and frozen packets. Payment links are a labelled simulator.

Follow-up and care programmes

Reminders and questionnaires using wording a doctor approved, with the patient's consent and quiet hours checked at send time; long-term programmes whose ranges the hospital sets, with a coach queue.

Assistants

Discharge, claims, handover and reply-draft assistants that only propose: a person accepts or dismisses each suggestion. Off until an administrator turns them on.

Protocols

The hospital's own protocols, approved by a second person and immutable once approved; answers only from approved passages, with citations.

Integration hub

HL7 results and lab analyser messages (ASTM), matched to patients by identifier only, with quarantine and replay. Tested with simulated instruments.

Insights

Eleven operational metrics from a closed catalogue, a patient-journey funnel; there is no generated SQL.

Audit and setup

Audit viewer with chain verification and break-glass review; facilities, wards, formulary, tax rates, payers and switches.

Also included

Around the modules.

Patient portal

A linked patient sees their own appointments, medicines, released results and visit summaries, home sample collection visits (without the address), follow-up and care programmes, and can join a video visit.

FHIR R4 (read-only)

Patient, Encounter, Observation, AllergyIntolerance, MedicationRequest, Appointment and $everything.

Offline drafts

A note typed without a connection is kept encrypted on the device and syncs when the connection returns.

Assistants, with review

Off by default. Drafts never write to the record without a named reviewer; the propose-only assistants can only create suggestions that a person accepts. No model is clinically validated.

Not built yet: automated backups, critical-result paging, e-prescription, a real payment gateway (payment links are a simulator), WhatsApp and ABDM, patient self-booking, other languages and a native mobile app.