Announcement

Collapse
No announcement yet.

MSH parsing error

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

  • MSH parsing error

    Hi,

    As a first step in connecting to a production ADT system I'm tryiing to simply store a message to a file. I basically am using the example LLP 2 file example and storing the HL7 message. It works fine when I use some sample messages. When I use a message from the production system I get MSH parsing errors indication that '|' is incorrect.

    The exception is below. If you need the HL7 file I can send that.

    Thanks in advance.

    INFO com.webreach.mirth.server.Mirth: starting mirth server...
    Mirth 1.1.0 (August 28, 2006) server successfully started: Wed Oct 18 16:24:56 E
    DT 2006
    Running Java 1.5.0_08 on Windows XP (5.1, x86)
    INFO com.webreach.mirth.server.mule.util.ER7Util: Unable to convert message to
    XML (Possibly already in XML or Invalid HL7)
    ERROR com.webreach.mirth.server.mule.filters.JavaScriptF ilter: org.mozilla.javas
    cript.EcmaError: TypeError: error: Unexpected character encountered (lex state 3
    ): &#039;|&#039; (<cmd>#2)
    ca.uhn.hl7v2.HL7Exception: Couldn&#039;t create MSH for version 2.1 (does your class
    path include this version?) ...
    at ca.uhn.hl7v2.parser.Parser.makeControlMSH(Parser.j ava:299)
    at ca.uhn.hl7v2.parser.PipeParser.getCriticalResponse Data(PipeParser.jav
    a:635)
    at com.webreach.mirth.util.ACKGenerator.generateAckRe sponse(ACKGenerator
    .java:37)
    at org.mule.providers.tcp.TcpMessageReceiver$TcpWorke r.generateACK(TcpMe
    ssageReceiver.java:285)
    at org.mule.providers.tcp.TcpMessageReceiver$TcpWorke r.processData(TcpMe
    ssageReceiver.java:275)
    at org.mule.providers.tcp.TcpMessageReceiver$TcpWorke r.run(TcpMessageRec
    eiver.java:250)
    at org.mule.impl.work.WorkerContext.run(WorkerContext .java:290)
    at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Wor
    ker.runTask(ThreadPoolExecutor.java:650)
    at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Wor
    ker.run(ThreadPoolExecutor.java:675)
    at java.lang.Thread.run(Unknown Source)
    Caused by: java.lang.IllegalArgumentException: The version 2.1 is not recognize
    d
    at ca.uhn.hl7v2.model.GenericMessage.getGenericMessag eClass(GenericMessa
    ge.java:38)
    at ca.uhn.hl7v2.parser.Parser.makeControlMSH(Parser.j ava:289)
    ... 9 more
    ERROR org.mule.impl.DefaultExceptionStrategy: Caught exception in Exception Stra
    tegy: Can&#039;t parse critical fields from MSH segment (ca.uhn.hl7v2.HL7Exception: C
    ouldn&#039;t create MSH for version 2.1 (does your classpath include this version?)
    ... ): MSH|^~\&|ADL|LHH|EAD|BEN|200609260920||ADT^A01|200 60926092025|T|2.1
    ca.uhn.hl7v2.HL7Exception: Can&#039;t parse critical fields from MSH segment (ca.uhn.
    hl7v2.HL7Exception: Couldn&#039;t create MSH for version 2.1 (does your classpath in
    clude this version?) ... ): MSH|^~\&|ADL|LHH|EAD|BEN|200609260920||ADT^A01|200 60
    926092025|T|2.1
    at ca.uhn.hl7v2.parser.PipeParser.getCriticalResponse Data(PipeParser.jav
    a:643)
    at com.webreach.mirth.util.ACKGenerator.generateAckRe sponse(ACKGenerator
    .java:37)
    at org.mule.providers.tcp.TcpMessageReceiver$TcpWorke r.generateACK(TcpMe
    ssageReceiver.java:285)
    at org.mule.providers.tcp.TcpMessageReceiver$TcpWorke r.processData(TcpMe
    ssageReceiver.java:275)
    at org.mule.providers.tcp.TcpMessageReceiver$TcpWorke r.run(TcpMessageRec
    eiver.java:250)
    at org.mule.impl.work.WorkerContext.run(WorkerContext .java:290)
    at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Wor
    ker.runTask(ThreadPoolExecutor.java:650)
    at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Wor
    ker.run(ThreadPoolExecutor.java:675)
    at java.lang.Thread.run(Unknown Source)
    WARN org.mule.config.ExceptionHelper: Failed to load error mappings from: META-
    INF/services/org/mule/config/tcp-exception-mappings.properties. This may be beca
    use there are no error code mappings for protocol: tcp

  • #2
    Re: MSH parsing error

    Ah, this is a bug - can you add it to the tracker? (www.mirthproject.org/jira)
    Chris Lang

    Comment

    Working...
    X