Clovertech

When XLTing between HL7 formats, segment number definitions have to match?

› Clovertech Forums › Cloverleaf › When XLTing between HL7 formats, segment number definitions have to match?

  • Creator
    Topic
  • January 26, 2022 at 3:45 pm #119524
    Jason
    Participant

      So I’m trying to XLT between two different DFT message versions (2.3 -> 2.4).

      I’m doing a simple pathcopy on the FT1 but I’m missing the FT1:26 even though that segment is defined in both HL7 configurations. The only difference is the HL7 field number (in HL7 configuration) is different… I tried removing the FT1:26 and re-adding it with a new field definition (with a matching field # definition) as the 2.3 and now it flows through..

      Does the field # (in HL7 configurator) have to always match?

      When I say field # in this context, it’s the field number in HL7 configurator

      thanks!

    • Creator
      Topic
    Viewing 0 reply threads
    • Author
      Replies
      • January 26, 2022 at 9:29 pm #119525
        Charlie Bursell
        Participant

          There must be an exact match of segments for PATHCOPY to work.  it is always problematic when doing a bulk copy between different versions.

          Why can’t you simply do the  PATHCOPY followed by a COPY statement for FT1:26?

      • Author
        Replies
      Viewing 0 reply threads
      • You must be logged in to reply to this topic.