Clinical work begins with an exact encounter and carries context forward.
Reception, Vitals, consultation, prescription, investigation, referral and follow-up are separate steps joined by the same encounter context.
See how the clinician receives the work.
Click the tabs. The preview is synthetic, but its fields and workflow states are derived from the product source and blueprint.
Control room
Today’s activity stays connected to the encounter context.
Longitudinal record
Identity, continuity history and current encounter sit together.
Demo Patient
EPV-260921-0142 · 43 years · Male
History
Current encounter
Continuity
Vitals and encounter intake
The clinician gets the same encounter, not a newly inferred one.
Structured prescription
Diagnosis, medicines, dosing, follow-up and verification form one clinical output.
RX-260921-00483
Diagnosis: Type 2 diabetes mellitus · ICD-10 E11.9
| Medicine | Dose | Frequency | Route | Duration |
|---|---|---|---|---|
| Demo medicine | 500 mg | BD | PO | 30 days |
| Demo pediatric-ready syrup | 5 mL | OD | PO | 7 days |
Lab lifecycle
Order, collection, result, verification and release remain distinct states.
Financial handoff
Consultation payment stays separate from later laboratory and pharmacy charges.
Staff and governance
Position, system role, credentials, training and capability remain separate.
tenant
System role
Credential & training
Access and audit
Authorization, permission changes, activity and verification create the trust layer.
Clinical intake has more depth than a five-card dashboard.
The production source includes the following fields and the blueprint protects exact handoff into the consultation stage.
No hidden encounter should appear because another module was opened.
The blueprint explicitly requires the same exact encounter to propagate through the clinical workflow.
Create the visit
Attach clinical intake
Assess and treat
Order evidence
Continue care
A prescription is a structured record, not a text blob.
Medicine lines, dose, frequency, duration, route, timing, advice, follow-up and verification are structured into the prescription workflow. Pediatric metadata can include age, weight, dose type, concentration and maximum-dose fields.
Explore the medicine model →