Announcement

Collapse

NextGen (Mirth) Connect 3.9.1 Released!

NextGen (Mirth) Connect 3.9.1 is now available as an appliance update and on our GitHub page. This release contains bug fixes and adds support for eHealth Exchange UDDI providers in the Interoperability plugin. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

Encoding not supported error for a sample ORU message

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Encoding not supported error for a sample ORU message

    I have few ORU sample messages for LAB, RADIOLOGY, and TRANSCRIPTION. Mirth "HL7 Message Template" recognizes all LAB, RADIOLOGY and some TRANSCRIPTION messages and displays the HL Tree. But not all ORU messages for TRANSCRIPTION are getting recognized.

    when I paste the following message in "HL7 Message Template" and hit "HL7 Tree" in the Mirth Administrator, I get the following warning message:

    =============
    Warning: Encoding not supported. Please check the syntax of your message and try again.

    ============= SAMPLE MESSAGE =========

    MSH|^~\&|TESTCONNECT|TESTSENDER|||200011251556||OR U|17531813|P|2.2
    PID|||N000123456^^^TST||Patient^Test^T||19800819|F |||123 TEST STREET APT 1^^TestCity^TT^12345||||||||111221234
    PV1||I|||||Doctor^Test^M^^^^MD^TST
    OBR|1||TCSV2000112500^TRANSCRIPTION|ECHO2D^2-D Echocardiogram 4800807 ... more||200012271555|20001224|||||||20001224||Doctor ^Test^M^^^^MD^TST||||TCSV|CARD||||F|||TESTDA^Docto r2^Test^T^^^MD^TST
    NTE|1||Site: CARDIOLOGY\.br\Unit #: N000308048\.br\Location: BN4T\.br\Account #: 123\.br\Req #: 0112233; 00-0118139\.br\Order #: TestOrder; CARD20001224-0021; CARD20001224-0022\.br\Procedure: 2-D Echocardiogram 4800807; Cardiac Doppler Study 4800809; Cardiac Color Flow 4800813\.br\Exam Date/Time: 11/25/00 \.br\Admitting Diagnosis: DIABETES,DEHYDRATION\.br\Reason for exam: \.br\\.br\\.br\
    NTE|2
    NTE|3||Dictated by: Test M.D. Doctor3 \.br\D: 11/25/00 \.br\T: 12/27/00 1553 JB\.br\\.br\This is a test document.
    OBX|1||||\.br\Technologist: Test, TEST\.br\\.br\2-D MEASUREMENTS:\.br\\.br\Test1: 3.1\.br\\.br\Test2\.br\\.br\RV Dimension Test: --\.br\\.br\LV Test\.br\\.br\LV Posterior Wall Thickness Test: 1.1\.br\\.br\\.br\Test note.\.br\\.br\\.br\\.br\\.br\\.br\
    =============

    I played with it a bit trying to remove the \.br\ as part of the transcript text but that didn't help. Any help to resolve this would be appreciated.

    Thanks in advance

  • #2
    Re: Encoding not supported error for a sample ORU message

    OBX.2 is lost, I'm not sure for 2.2, but for >2.31 it's a requiered data. And the type of the message must be ORU^R01, not ORU

    You can try this one:
    Code:
    MSH|^~\&|TESTCONNECT|TESTSENDER|||200011251||ORU^R01|17531813|P|2.2
    PID|||N000123456^^^TST||Patient^Test^T||19800819|F|||123 TEST STREET APT 1^^TestCity^TT^12345||||||||111221234
    PV1||I|||||Doctor^Test^M^^^^MD^TST
    OBR|1||TCSV2000112500^TRANSCRIPTION|ECHO2D^2-D Echocardiogram 4800807 ... more||200012271555|20001224|||||||20001224||Doctor^Test^M^^^^MD^TST||||TCSV|CARD||||F|||TESTDA^Doctor2^Test^T^^^MD^TSTCardiac Color Flow 4800813\.br\Exam Date/Time: 11/25/00 \.br\Admitting Diagnosis: DIABETES,DEHYDRATION\.br\Reason for exam:\.br\\.br\\.br\
    NTE|2
    NTE|3||Dictated by:  Test M.D. Doctor3 \.br\D:  11/25/00 \.br\T:  12/27/00 1553   JB\.br\\.br\This is a test document.
    OBX|1|FT|||\Technologist:  Test, TEST\.br\\.br\2-D MEASUREMENTS:\.br\\.br\Test1: 3.1 \.br\\.br\Test2\.br\\.br\RV Dimension Test: --\.br\\.br\LVTest\.br\\.br\LV Posterior Wall Thickness Test: 1.1\.br\\.br\\.br\Test note.\.br\\.br\\.br\\.br\\.br\\.br\
    The changes can be made at the preprocessor

    Comment


    • #3
      Re: Encoding not supported error for a sample ORU message

      albertosaez,

      Thank you very much! That worked!

      I tried your corrected message and fixed the following segments in another error sample and both worked fine:

      ORU^R01 in MSH

      and

      FT in OBX (OBX|1|FT| for Formatted Text)

      Thanks for your help!

      Comment


      • #4
        Re: Encoding not supported error for a sample ORU message

        The encoding not supported is usually caused by the message type: ORU vs ORU^R01 as alberto stated.

        -Chris
        Chris Lang

        Comment

        Working...
        X