EM-HCP-06 · Subject model · W-IND
Prescription and medication administration
A medication order or prescription, its dispensing and each recorded administration or omitted dose. Medicinal product definitions belong to referenced world models, and dosing decisions belong to clinicians.
Partially published; research continues
Claude: initial-industry-contour-and-card-supplement; Grok: not-started.
Published results
The independent second-provider study, fixtures and the full research protocol remain open. Runtime promotion is governed by the package allocation holds.
Subject boundary and candidate types
- MedicationRequest
- Prescription
- MedicationDispense
- MedicationAdministration
- OmissionReason
Deep research questions
- How is a prescription linked to dispenses and administrations without copying its content?
- How are changes of dose recorded as new orders rather than edits?
- How is an omitted dose recorded with its reason?
Verifiable invariants
- An administration references the order it fulfils, unless it is recorded as an emergency without an order
- A change of dose creates a new order linked to the previous one
- Each administration records who gave it and when
End-to-end acceptance scenario
For a synthetic inpatient stay, prescribe a medication, change the dose by a new order, record three administrations and one omission with its reason, and reconcile the medication list at discharge.
Negative case
A prescription record is edited in place to change the dose, so earlier administrations appear to follow the new dose.
Approaches to compare
- HL7 FHIR: MedicationRequest, MedicationDispense and MedicationAdministration resources
- ISO IDMP: identification of medicinal products
- Medication reconciliation practice at transitions of care
Candidates in the live catalogue
- WM-ACT-048 · Medication Order / Administration · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-OBJ-005 · Medicinal Product · 0.1.0-reviewable-draft · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.