Merge Scenarios - HL7 Module - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Essential - Standard - Premier

The HL7 module supports the following merge scenarios:

• MPI merging —The old MPI is deleted and replaced with the new value. Any MRNs or charts using the old MPI are re-indexed with the new MPI. Any cases¹ or appointments associated with the old MPI are moved to the new MPI.

• MRN merging —The old MRN is deleted and replaced with the new value. Any charts assigned to it are re-indexed to the new MRN.

  Note:

  Multiple MRNs for a given MPI can be created when processing a merge request.

• MRN moving —The MRN is moved to a different MPI. Any charts assigned to the MRN are re-indexed to the new MPI. The original MPI remains in the database. See Moving an MRN to a Different MPI.

• Chart ID merging —The chart in OnBase with the old value is re-indexed with the new value. If a chart already exists in OnBase with the new Chart ID value, then the re-indexed charts are flagged for review.

For each scenario, the HL7 message must contain the MRG segment to be used for merging. The MRG segment always contains the old values that will be removed from the database. The new values are in their normal segments in the message.

If the Listener receives a request to merge two records that do not exist, it will attempt to create the target. However, if it cannot create the target, the message is rejected. This is most likely to occur if the customer is sending one of the following:

• MRN merge messages with a target MPI

• Chart merge messages without an MRN or MPI

Customers that always send target MPI, MRN, and Chart messages do not run the risk of having a merge request rejected.

If the MPI, MRN, or chart specified in the PID segment of the HL7 message does not exist in the database, this configuration would be an error unless you are merging Chart IDs or renaming the MPI or MRN.