QDX5.5 Possible Bug in OM1-OM6 Segment Definitions

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf QDX5.5 Possible Bug in OM1-OM6 Segment Definitions

  • Creator
    Topic
  • #49343
    Michael Lacriola
    Participant

      I’m working in AIX and I noticed that in 2.2 HL7 versions for the OM1 through OM6 segments, the definition starts off with “segment type id” for a length of 3. All of the other “basic” segments such as PID, OBR, NTE, OBX start with a sequence number field. I noticed when doing a MFN^M03 xlate and it is throwing everything off by 1. Interesting that when I use HL7 test tool for the variants, that works, but when using test tool for xlate using a basic BULKCOPY, the OM1 segment is off by 1, meaning OM1.#1 shows a field length of 3 instead of 4, OM1.#2 has a field length of 4 instead of 200. I plan on removing field number 585 from these segments to see if that makes a difference.

      Anyone else noticed this?

    Viewing 0 reply threads
    • Author
      Replies
      • #61579
        Jim Kosloskey
        Participant

          Michael,

          I think that is an error.

          Were it me, I would remove the 00585 (Segment ID) field from the segment definition for these segments.

          I do not have the 2.2 HL/7 document but I suspect it might be a flaw with the provided base definition provided by Cloverleaf(R). So you might want to change that at the root level – however, if that error gets replicated with each release of Cloverleaf(R) you would need to remember to make the same change with each upgrade.

          Better to make the change to your variant rather than the root version I think.

          Jim Kosloskey

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

      Viewing 0 reply threads
      • The forum ‘Cloverleaf’ is closed to new topics and replies.