An investigation is a lifecycle, not a checkbox.
EPIOVIA's blueprint separates ordering, billing, collection, processing, result entry, verification and release so each fact can remain auditable.
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.
The lab knows where an order is.
The public site is intentionally explicit about state because “ordered” is not “resulted” and “resulted” is not “verified.”
The final report carries provenance.
Blueprint requirements include patient demographics, accession/order, investigation, specimen, result, unit, reference range, flags, verifier, timestamps and a report identifier.
Diagnostic Report
| Investigation | Result | Unit | Reference | Flag |
|---|---|---|---|---|
| HbA1c | 7.1 | % | 4.0–5.6 | High |
| Creatinine | 1.0 | mg/dL | Lab configured | Normal |