Changing Multiple OBRs to OBXs

[Sandi Meyers]

I have a site that will not allow repeating multiple OBR segments and want me to change them to OBX segments.  I even tried the CONTINUE but the result is not acceptable to the physician practice.  This is above my expertise as of yet.  Would this be done in a tcl?  Would anyone have anything that I would be able to use and possibly be able to modify (easily)?  I would greatly appreciate it.  I am a quick study and will try anything.  I am getting desperate.

Topic

[Max Drown (Infor)]

Sandi, are there any conditions on the conversion to OBX? Can you post a sample inbound and a converted outbound?

-- Max Drown (Infor)

[Sandi Meyers]

none that I know of yet.  I am getting all other messages/results across.  But the big problem seems to be micro messages when cultures have multiple organisms with susceptibilites.  My concern was when changing to OBX will the susceptility stay with the proper organism since all these will now be OBX segments.  The message for these come with OBR for the first organism and then mulitple OBX for susceptiblity results, then another OBR with more OBX results for that organism susceptibilty.  Sorry, I am a clinical person recruited to do interfacing.  Traing keeps getting postponed because I keep making it work but this has me stymied.

[Max Drown (Infor)]

Please post a sample inbound and an example of how it should look outbound.

-- Max Drown (Infor)

[Chris Williams]

I haven’t seen their specifications, but I’m thinking they probably don’t want what they are asking for. They may want the results simplified by skipping the initial OBR/OBX organism identification group and then using the individual organism OBR/OBX susceptibility groups to create a separate message for each group. That would eliminate this conversion of OBR to OBX nonsense.

[Sandi Meyers]

I tried a separate message for each group with the CONTINUE option in an XLATE.  But it makes for very confusing group of messages.  In the clinical aspect it looks like there are more then one specimen being analyzed.

[Gordon Koch]

I see that this is an old posting, but I am dealing with the same situation where the repeating ORC/OBR/OBX groups in the micro message are not supported. Has anyone else resolved this problem (other than by creating multiple messages)?

Thank you.

[Jim Kosloskey]

What does the receiving system want then?

The only other thing I can think of is to regroup all of the OBX segments within a single ORC/OBR group in a single message.

If that is acceptable to the receiving system that can be done easilly within an Xlate.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Terry Kellum]

We had a similar situation where the receiving system couldn’t handle the OBR/OBX structure of micro results.  We had to go to the lab vendor and get both OBR/OBX AND a OBR/OBX/NTE ASCII “report” style format.

We then had to pick the format that the receiving system wanted and send one set of results or the other set.

I would get the formal specs from each side.  No detailed specs, no interface.

[Gordon Koch]

Hello Jim. Yes, that would be the desired output (to have all the information in one ORC/OBR series with the multiple OBX’s). Two important concerns for me would to include the information in the OBR into an OBX, and to not change the order of the segments. The OBR segments contain the bacteria/isolate information that acts as a header for the antibiotic/sensitivity information in the OBX’s that follow.

The output could not contain the subsequent ORC/OBR segments. The gist of it is that I am not sure how to “convert” an the OBR into an OBX. The information in the subsequent ORC’s is not needed. Any thoughts?

Thank you.

[Jim Kosloskey]

Well hopefully the number of OBR fields needed to be in the OBX is small (maybe one or two). The receiving system should be able to tell you which fields they want.

The next step is to find out where in the OBX the receiving system wants the OBR data.

Some accomodation needs to be reached if the target OBX fields already contain OBX data.

You really need get to get some cooperation from the receiving system.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Gordon Koch]

Hello Jim. Yes, I know what the receiving system requires, my question was more at the Xlate level. If I do not iterate on the ORC and OBR segments, they will not be in the output. I am not sure how to create new OBX segments (to be filled with the values in the subsequent OBR’s) in the same position. I hoped to not CONCAT the data in existing OBX’s.

Thank you.

[Jim Kosloskey]

Gordon,

Email me and I will work with you on this offline (my email is in my post).

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Gordon Koch]

Thanks Jim. I just sent an email out to you.

Thank you,

[Gordon Koch]

Jim, thanks again for the offline help. As you suggested, the solution is also posted here:

The first task is to identify the instances where there are multiple ORC/OBR/OBX groups. This is done by using an IF/ELSE action to interrogate the group iterate: IF $%g1 eq =0

The ELSE action repeats translation actions for the subsequent iterates.

The next point involved using the % functionality outside of the ITERATE action. It is first initialized in a COPY action: =0  COPY  $%g99

This variable is used in the Destination side of the Pathcopy and Copy actions:

1(0).1(%g1).3(0).0(%g2).OBX(0)  COPY  1(0).1(0).3(0).0(%g99).OBX(0)

The part that I was previously not understanding involved changing the OBR to an OBX. This is simply done per the following:

1(0).1(%g1).0(0).OBR(0).#26(0)  COPY  1(0).1(0).3(0).0(%g99).OBX(0).#5(0)

for each field that is needed form the OBR segment.

Again, Thank you…

[Author]

Replies