Understanding the Redox Medications Model

When do I need to use the medications data model?

The medications data model is for applications looking 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 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, primarily this model is used to transmit prescription notifications in realtime as meds 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 if I need to receive medication administrations?

If you need data on medications that are administered within a healthcare setting, then the visit ClinicalSummary is the best model and event type to use. See our FAQ on the ClinicalSummary model for more information on visit summaries and medication administrations. Eventually we are planning on adding an administration event to the medications model as well.

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 will fire as prescription orders are dispensed and filled and statement events will be transmitted as patient-reported medications are added 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 OMP or RDE HL7v2 interface
  • MedicationOrder FHIR resource
  • Medication orders API