MEDICINES

The medicine model carries enough detail to support the prescription workflow without turning clinical judgement into automation.

Brand/generic data, route, frequency, timing, instructions and pediatric metadata are part of the current source model. Hospital-specific visibility remains configurable.

EPIOVIADemo workspace
Demo Hospital · OPD
Prescription

Structured prescription

Diagnosis, medicines, dosing, follow-up and verification form one clinical output.

SOURCE-ALIGNED PREVIEW
Prescription

RX-260921-00483

Diagnosis: Type 2 diabetes mellitus · ICD-10 E11.9

QR / UUID ready
MedicineDoseFrequencyRouteDuration
Demo medicine500 mgBDPO30 days
Demo pediatric-ready syrup5 mLODPO7 days
Follow-up: 7 daysReferral: NoneAdvice: Stored with Rx
DEMO DATA Interface previews are intentionally synthetic. Labels, relationships and workflow states are derived from EPIOVIA's current source and blueprint, not patient data.
MEDICINE MASTER

Structured medication data has a purpose.

The master supports prescribing detail, display consistency and pediatric-specific fields.

Identity

Generic name, brand name, category

Clinical use

Indication and medicine context

Standard dosing

Dose, frequency, duration, route, timing

Instructions

Prescription instruction text and patient-facing guidance

Pediatric

Enable/disable, age range, weight range, dose type and value

Concentration

Concentration amount and volume for liquid formulations

Safety limits

Maximum single dose and maximum daily dose

Hospital visibility

Per-hospital visibility without changing the global record

PEDIATRIC STRUCTURE

Age, weight and concentration belong in the data model.

That means a syrup can carry concentration context and pediatric rule metadata rather than relying on a doctor to infer everything from a free-text medicine name.

Age6 years
Weight21 kg
Concentration125 mg / 5 mL
Dose ruleSource-defined
Maximum singleSource-defined
Maximum dailySource-defined