[Karen May]

Thanks Jim..

The only way to do filtering (I’ve already got a tps proc working) is based on the SectionID in OBR.24 which at present, comes in blank.. hence the other proc move to the preXlate stack.  I’ll play with this more and see what I can come up with.

Karen

[Karen May]

Thanks Jim.. The reason I’ve gone the tps route is to avoid overhead in the engine.  I originally set it up as a tcl frag inside the xlate and that worked out just fine untl we realized that Meditech is sending in three different formats requiring three different translations.  I could still do it that way… It would be a whole lot quicker as I know I’ve got the 2.5.1 iterations working as expected via the xlate.

We’ve asked Meditech to modify their output to include the section ID in OBR.24 but it takes a while for them to do anything.  Thought it might be a little cleaner to stack a couple of procs pre-xlate to 1.  Determine section ID and then 2. A second proc using an ARG to Continue or Kill based on that.  Then once Meditech does their thing… the first proc can be removed/retired.  Another wrinkle that just got thrown at us is that a fair number of the OBX’s have to be turned into NTE’s based on the data type in OBX1.  Yeesshh.. They’re makin me nuts..!

Hope that helps..  Based on the above.. how would you attack it.?

Still futzing with the lvarpop syntax.. Haven’t used it before..  

Thanks again.. Karen

[Karen May]

Thanks for your reply Robert.  I had found that last brace item.  Given that I have to replace OBR.24 in ALL OBR segs, your suggestion to set a counter to keep track of where the proc is at each encounter is a prudent one.. I’ll give it a try.

[Karen May]

Hi Mike..

Typically per the HL7 2.3 standard;  A01, A04, A05, A08, A13, A14 have the same structure.  A09, A10 & A11 use a slightly different structure, as do the A02, A03.

The format is structured according to the type of transaction being processed.  ie; IN1 segments are not needed to transfer a patient from one bed to another with an A02.  They are needed when changing a patient type from Out to IN or vice versa.  

Of course, the standard is just that.  A standard.  Every vendor has their own interpretation and will structure accordingly.  That’s why Cloverleaf gives you the ability to create multiple variants with custom modifications.

Hope that helps..

[Author]

Replies