Announcement

Collapse
No announcement yet.

Different Parsing Options

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

  • Different Parsing Options

    Hi All,

    I'm having an issue with the parsing options.
    I use the strict parser option so it's possible to loop through results.

    For example to retrieve the patient ID I would use:
    msg['ORU_R01.RESPONSE']['ORU_R01.PATIENT']['PID']['PID.2']['CX.1'].toString();

    However in a new channel I have created I'm getting the following from my message definition template:
    msg['ORU_R01.PIDPD1NK1NTEPV1PV2ORCOBRNTEOBXNTECTI']['ORU_R01.PIDPD1NK1NTEPV1PV2']['PID']['PID.2']['CX.1'].toString()

    Why are these being seen differently? What can I do to make them like the 1st messages?

    Cheers
    Simon
    Last edited by simidau; 03-07-2011, 07:28 PM.

  • #2
    Attached is a sample of the message that gives me the problem in my new channel.
    Attached Files

    Comment


    • #3
      After a little playing it seems changing the version of the message from 2.3.1 to 2.2 changes the way it's parsed and it then comes up the way I'm used to.

      Is the best way to just change in on the inbound section of the channel?
      Will there be any repercussions I should be aware of by changing the message version?

      Comment


      • #4
        Just tried a few more things
        Changing the version (in the message) from 2.3.1 to 2.3 changes it parse how I want it.
        Changing it to 2.3.0 and mirth says it's not a valid HL7 message.

        Looking at the differences between 2.3 and 2.3.1 in the standard show very changes - just confirming now that none of the changes will have an effect on the message contents I'm dealing with.

        Comment

        Working...
        X