This problem affects the following products:
- HealthShare Unified Care Record® version, all versions up to and including 2024.1:
2019.1 • 2019.2 • 2020.1 • 2020.2 • 2021.1 • 2021.2 • 2022.1 • 2022.2 • 2023.1 • 2023.2 • 2024.1
Requirements:
- Inbound data that includes an MPIID
The Unified Care Record patient registry processes updates from upstream systems based on inbound data. A patient registry update can either:
- add a new record to the patient registry.
- update an existing entry in the patient registry with new information from inbound data.
In most cases, when an existing patient registry entry is updated, the update request does not contain an MPIID. This is because upstream systems are typically unaware of MPIID values, since these systems identify patients using an MRN. If an update request does contain an MPIID value, the value typically matches the MPIID stored in the existing patient registry entry.
In the rare circumstance when a patient registry update request includes an MPIID, but that MPIID value that does not match the existing patient registry entry, Unified Care Record was incorrectly processing the update request by overwriting the MPIID in the existing patient registry entry with the new MPIID.
The correct behavior in the case of an MPIID mismatch should be to throw an error, since the correct action to take is undefined in this case. By throwing an error, a system operator is alerted, who can then manually resolve the mismatch by reconciling the provided MPIID with MPIID indicated in the enterprise master person index (EMPI) solution that is used with Unified Care Record, such as Patient Index or InterSystems EMPI. Possible corrective actions include updating the data source feed or correcting the EMPI.
The correction for this defect is identified as HSIEO-10679, which is included in version 2024.2 and all future product releases. It is also available for older versions via ad hoc change file (patch) or full kit distribution by contacting the Worldwide Response Center (WRC).
With the correction in place, when an MPIID mismatch is detected, an error is thrown in the interoperability production log for the HS.Hub.MPI.Manager component, and the patient registry is not updated.