Understanding the Redox Provider Data Model

When do I need to use the Provider Data Model?

The Redox Provider┬áData Model should be used if your application is looking to maintain a synchronized provider database with an EHR. Health systems that support this model generate messages when provider records are created, updated or inactivated, allowing applications receiving them to update their own application’s provider database accordingly.

What’s the difference between the Provider Data Model and other Data Models that use providers?

Almost all patient centric data models have data elements that are providers. For example, PatientAdmin may have a referring provider, Scheduling may have a scheduled provider, and Order may have ordering provider. The Provider Data Model is different in that it is not patient-centric. It tells who the provider is, not what role the provider plays in regards to a certain patient.

Which EHRs support the Provider Data Model?

Right now this model would leverage either a vendor API or an MFN HL7v2 feed on the EHR side. In general, MFN interfaces aren’t incredibly common; however, the setup is site specific and not based on the EHR vendor. It is always worth asking if this is something a specific health system has live.

What are the future plans for the Provider Data Model?

We do have a future project planned to build support for leveraging ADT or SIU HL7v2 interfaces to maintain a synchronized provider database, which would allow applications to use the Provider model at sites that don’t have available APIs or MFN interfaces. After pulling provider objects from the ADT or SIU messages, Redox would maintain them in our Data Chateau infrastructure. Applications could then call a queryable endpoint to receive up-to-date provider details.