Two A02 messages into One A17

Shelbi,

I’ve had to deal with the inverse situation (take an A17 and create two A02’s), as many systems can’t handle an A17.  But I haven’t encountered a situation where the receiving system requires an A17.  It seems that the McKesson system should be able to handle the separate A02’s.

Jim Cobane

Henry Ford Health

The problem here is getting the two A02 messages at the same time.

The solution would be to store the first one in a sqlite database and when the second one comes in combine to a single A17.  The code is simple, the hard part is getting the two messages.

You need to add code that says if an A02 is in the DB and a time has expired without the matching one, error it out.  Remeber Murphy was the biggest optimist that ever lived  😀

The problem may be that the receiving system may not allow cohabitation, that is, 2 people in the same bed at the same time.  If 2 A02’s are used for a bed swap, the first A02 transfers a patient into a bed that’s already occupied.  Now, if the sending system could transfer the first  patient  into a temporary or virtual bed, the 2nd A02 takes the 2nd patient and places it into the bed now vacated by the 1st patient, then the 3rd A02 takes the 1st patient out of the temp/virtual bed and into the bed now vacated by the 2nd patient.

I’m with Charlie, it  will  be a can of worms to get the engine to do it, unless you can guarentee that the 2 A02’s will follow each other.  Even so, there’s  needs to be some  sort of key to let the engine to know that these A02’s are paired together instead of just 2 consecutive A02’s.