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

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. MFN interfaces aren’t incredibly common, but the setup is site specific and not based on the EHR vendor, so 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 synced 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 and applications would call a queryable endpoint to receive up-to-date provider details.