OBX segment based on NTE value for ORU message type.

This topic has 3 replies, 2 voices, and was last updated 10 years, 1 month ago by Hina Siddiqui.

Creator

Topic
November 7, 2014 at 6:32 pm #54456
Hina Siddiqui
Participant
So the logic in the spec doc goes as follows:

OBX segment [These are mapped based on NTE-3 values NTEs following OBXs]

For all NTE segments if there is an NTE segment with NTE-2-SourceofComment =
Creator

Topic

Viewing 2 reply threads

Author

Replies
- November 7, 2014 at 7:44 pm #81568
  Tom Rioux
  Participant
  If I understand you correctly, you are creating additional OBX segments for the output message. I’m not sure what your output looks like or is supposed to look like (some examples might help).
  
  Are you using your OBX counter to keep the order of OBX Set ID’s? If so, you may need to do something with your iteration counter on the destination side. Otherwise you run the risk of overwriting the OBX segment you previously created with the next iteration of the OBX from the source.
  
  Hope this helps…
  
  Tom Rioux
- November 7, 2014 at 8:00 pm #81569
  Hina Siddiqui
  Participant
  yes that is correct, I am trying to create a new OBX. The output should look like as follows
  
  MSH|
  
  PID|
  
  PV1|
  
  ‘
  
  ‘
  
  ‘
  
  ‘
  
  OBX|1
  
  OBX|2
  
  OBX|3
  
  OBX|4
  
  OBX|5|will have value of OBX 4
  
  OBX|6
  
  OBX|7
  
  OBX|8|will have value of OBX 6 fields
  
  Hope i made more sense
- November 7, 2014 at 9:02 pm #81570
  Hina Siddiqui
  Participant
  Just another quick info. My output looks like the image i have attached. As you can see, the 3 new OBXs that were created, were placed in the end and all those 3 new OBXs dont have the values from the OBX preceding to NTE but have values from the 1st OBX in the group 🙁
  
  I tried to debug a lot but just stuck here and not able to move forward.
Author

Replies

Viewing 2 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.