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. MR should not be assumed or hardcoded as the expected ID type.
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.
What is the difference between a visit/case number and an encounter number?
You may hear these two terms used during conversations with the health system. The importance of each really will depend on your workflow and your goals for tracking data. A visit/case number represents a single, specific appointment or surgical case. An encounter number can represent a single appointment but is more often used to bundle together a set of appointments related to a single event. In the case of a surgery, a patient’s pre-op evaluation, surgical case, and post-op visit could all have the same encounter number but different visit numbers. For some EHRs, the encounter number is preferred for them to be able to file information in a specific place in the patient charts.
Cool – the visit/case number sounds like what I need. Will the appointment always have the same visit/case number if it’s been rescheduled?
This depends on the EHR workflow for handling appointment rescheduling. If the EHR uses a true reschedule workflow, the visit or case number is usually retained. If the EHR uses a cancel/new workflow where the old appointment is canceled and then a new one is made, the visit number may change.
On all of the location fields (Visit.Location, Order.Location, etc) is it possible to receive the ID of the location in the EMR?
Whenever you’re receiving location details (ie. Facility, Location, Department, Unit, etc…), you should be prepared to receive either an identifier for the location or the actual name of the location. This is something that we see vary between EHRs and sites that are using the same EHR, so we recommend that you prepare for receiving either. We typically see groups handle this by building location tables on their end that map location IDs to location names and potentially backfilling this during the implementation with a facility structure export.