Relocate only one case

[Steve_Borland]

We need a method to relocate a single case from the source to the target MPI/MRN. Results from testing an A35 have been unsatisfactory. We are looking for a message that is NOT and A08 or A18.      A44 per HL7.org looks correct. There is no pre-configured template. Will OnBase process an A44?

[Aaron_Truskot]

Hi Steven, 

OnBase is capable of processing event types that are not available by default. You can add a new HL7 Message Template for the ADT^A44 (or any other event) and then add HL7 Import Processors that will rely on the new message template when processing incoming messages. 

As for merging in OnBase, the simplest way to think of it is that OnBase will attempt to merge, move, or change the ID of any source identifier that it finds in the MRG segment. You can include any target identifiers or demographic data that you wish to include. Those values will be used to update records as part of the processing of the message. 

If you want to strictly follow the HL7 specification when building your messages in the external system, just be sure not to map any patient identifiers from the MRG segment or you will end up attempting a patient merge in addition to your case-level move.  (Again, in your situation, you only want to map the "case" Keyword Type or Data Field to your MRG segment or OnBase might attempt to perform additional merges based on mapped values that it finds.)

Recall that OnBase knows to process a move operation when it finds the same value for the source (i.e. MRG) and target (ex: PID) segments. You will need to include the target's parent identifiers (ex: MRN, MPI, or any identifiers that live "above" case in your identification hierarchy) so we know where to move the record to.

[Aaron_Truskot]

Hi Steven, 

I wanted to take a moment to clarify my original response. 

In OnBase Foundation EP3 and later, Chart move requests can be processed via the Medical Records Chart Merge processor. In this case, you have a source Chart Id (in the MRG segment) and a target Chart Id, MRN, and MPI (in PID and PV1, normally). If the source and target Chart Id are the same then OnBase will move the Chart from whatever original MRN/MPI it was on to the MRN/MPI specified in the message. 

Prior to OnBase Foundation, OnBase could only move a Chart when the request was processed as an update rather than a merge. You'd see the following error when attempting to process the request as a merge: "duplicate data in MRG segment"

Processing a move request as an update means that OnBase will not validate the source Chart Id found in the MRG segment prior to performing the move. In an effort to allow for improved validation of move requests, we have introduced the ability to process moves only after validating that the request is an explicit move request (i.e. contains a source identifier in the MRG segment). We will not remove the ability to process Chart moves as updates to avoid upgrade complications. 

In the configuration client, Foundation allows any of the three options to be used to process a merge. Older versions of OnBase only allow Update Chart or Create Or Update Chart options to be utilized. These three options are highlighted below for reference.