When do I need to use the Medications Data Model?
Applications use the Medications Data model to receive prescription notifications and fill requests in realtime. This includes new medication orders as well as updates and cancellations.
What if I want to receive all the medications the patient is currently taking?
If you’re not looking for prescription order updates but rather the patient’s list of current medications, then ClinicalSummary Data Model is the best model to use. See our FAQ on the ClinicalSummary model for more information.
Does the medications model allow my application to e-prescribe medication orders?
Nope, applications primarily use this model to transmit prescription notifications in realtime as medications are ordered between an EHR and a connecting application. If your application wants to update a patient’s medication list with a medication that has already been ordered and prescribed or that has been reported by the patient, then we recommend leveraging the ClinicalSummary model to send the patient’s updated medication list inbound to the EHR where it will be reconciled by a clinician.
What other use cases will the medications model support in the future?
In addition to administration, we also plan on adding dispense and statement event types in the future. Dispense events fire as users dispense or fill prescription orders. Systems transmit statement events as users add patient-reported medications to the patient’s chart.
What are the EHR requirements to support the medications model?
The current supported events require one of the following:
- Active ORM or RDE HL7v2 interface
- MedicationOrder FHIR resource
- Medication orders API