Copy/Convert A34 to A31, Send Both Through

[Greg Tataryn]

We converted to a new registration, HIS, and pharmacy system last summer.  We have recently begun running into issues with patient merges due to improper registrations.  Patients who may have had an old MRN with us and have been back since the conversion have not always been registered under the old MRN.  Many have ended up with new MRN’s.  Of course these flow downstream no problem.  When HIM goes to merge however it causes an issue because the newer downstream systems do not have the old MRN.

Now we have been given a suggestion to take the A34 merge message, make a copy to convert to an A31.  We would then send through the A31 before the A34.  I understand the concept but am a bit unclear on the coding.  Any help would be greatly appreciated.

Thank you,

Greg

Topic

[Nick Stainback]

Now assuming that the messages are standard A31 and A34 messages you will only have the PID and possibly the PD1.   Will the HIM system be able to make the necessary updates with just this information is the A31?

You Can Read it the message twice

set msgA34 [msgget $mh]

               set msgA31 [msgget $mh]

Take the fields and segments needed for the A31 and keep them in var msgA31 and once you have both messages just continue the A31 first and then the A34

[Greg Tataryn]

That makes sense.  I suppose I could do all of my translations via TCL rather than using an xlate file.  Have to brush up on my TCL.  The registration, pharmacy and clinical systems are all McKesson and for the most part all messages between them go through the engine relatively un-altered so I would guess that assuming an A34 has all the information an A31 would need I can strip out anything unnessicary.

Greg Tataryn

St. Francis Hospital

Columbus, GA

tataryng@sfhga.com

[Scott Folley]

You can also do this in the translate.

[Nick Stainback]

I can tell you this,

The standard A34 is only going to have the PID and PD1 fields that match up the the A31.

The PD1 is optionsal so it will not be and issues, however the A31 by default will require a PV1 for most of the Mckesson Products.  In Order to add the person record to the recieving system.

You may have to copy the account # to PV1 18 from the PID based on where the app is going to be looking for it.

Good luck, hope this helps,

[David Barr]

If you do this in TCL, you’ll need to call “msgcopy” to make a copy of the message, call “msgset” to update the contents of one of the messages with the new message type, and return a disposition list that has a “CONTINUE” disposition for each message.

[James Cobane]

If you do this in the xlate, just understand the difference between the SEND vs. CONTINUE action.  Using SEND will put the message straight to the OB data queue (skipping any post-xlate procs), where CONTINUE will continue the message on its normal route through the engine.  So, if there is no post-xlate, or OB data procs, then SEND & CONTINUE essentially do the same thing.  But, if you have any procs in the post-xlate or OB Data context, then you may want to CONTINUE so the messages process through those procs.

Jim Cobane

Henry Ford Health

[Author]

Replies