When do I need to use the PatientAdmin data model?
PatientAdmin is the most common feed used across Redox customers and is something we would recommend you require if you persist patient data in your application. Over 90% of our installs use PatientAdmin in some form. This is the primary method for you to stay in sync with the health care organization regarding the patient’s documented demographics, insurance information, and the health system’s patient identifier (usually called a medical record number or MRN). PatientAdmin is the only webhook-based feed that communicates changes to this type of patient information, usually through a push notification generated from health system’s ADT HL7v2 interface.
What is a PatientMerge event?
A PatientMerge event occurs when the health system identifies duplicate patients in their EHR system and merges their charts together. This usually is an uncommon event that occurs a few times per month at a health system, but it’s critical for you to know the correct patient identifier and to help you identify if you have duplicate patients from the health system in your application. If you persist patient information in your application, we strongly recommend that you plan to receive PatientMerge events from the health system. Most Redox application partners develop to accept the PatientMerge event and leverage a notification process such as an email or page to either someone on their team or someone at the health system with access to the application to manually review duplicate patients identified for merge. If duplicates exist that need to be merged, the process of merging the records is also usually handled manually on the backend in the application.
If I can get VisitUpdate information from PatientAdmin, why do I need a Scheduling feed?
The biggest piece of scheduling related content that you can’t get on a PatientAdmin feed is the appointment status.
Will the IDType for the patient identifier always be MR?
Redox sample messages use MR as the value for Patient.Identifiers.IDType, but this is a value that is defined by the health system. Some EHRs and health systems have different names for their IDTypes and require those same IDType values be sent back for any updates that you need to push into the EHR.
But, I only have to worry about the main identifier, right?
Not always – some health systems will have multiple identifiers that are used for different reasons so you should plan to be able to handle multiple identifiers in the Patient.Identifiers array.