Questions and Answers > Understanding the Redox Medications Data Model
Questions and Answers

Understanding the Redox Medications Data Model

When do I need to use the Medications Data Model?

Applications use the Medications Data model to receive real time updates about individual medications. This currently includes new medication orders, updates, cancellations, and administrations.

What triggers are currently supported by the Medications Data Model?

The “New” and “Update” events on the Medications Data Model are usually triggered by a new/updated prescription in the outpatient context or pharmacy verification of a new/updated order in the inpatient context. The “Cancel” event represents an order being discontinued.

The “Administration” event is triggered by a medication being given to a patient by a clinician at the hospital or clinic.  

Redox does not currently support Dispense events, which fire as users dispense or fill prescription orders, Statement events, which fire as users add patient-reported medications to the patient’s chart, or Renewal events, which fire when a patient requests a renewal of a prescription. If you have a use case involving these actions, reach out to your Redox representative.

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 Data 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.

Can I use the Medications Data Model to send information inbound to the EHR?

Most EHRs don’t accept inbound Medication orders or cancellations. These systems are designed to have closed-loop medication ordering, dispensing, and administration, and therefore don’t open up integrations for that information coming from an external application. However, if it’s supported by the EHR, the Medications Data Model can be used to send that information.

The “Administration” event can sometimes be sent inbound to the EHR, but the resulting information tends to display read-only once saved in the chart.

What variations should I expect in the information sent via the Medications Data Model?

Lots. Medication integrations tend to have more variation in the information/fields sent and the workflows for when the information is triggered across EHRs than other data types. Redox will do what we can to normalize these differences for you, but you may see that some information is available in more or less specificity at certain sites. You should be prepared to be flexible in the face of these differences, as well as to do extensive testing of your workflow to verify that there aren’t any issues.

What are the EHR requirements to support the Medications Data Model?

The currently supported events require one of the following feeds.

New/Update/Cancel:

  • Active ORM, OMP, or RDE HL7v2 interface
  • MedicationOrder FHIR resource
  • Medication orders API

Administration:

  • Active RAS HL7v2 interface
  • MedicationAdministration FHIR resource
  • Medication administration API