Tag Archives: ORM

Important HL7 Segement

======= MSH =======
3 – Sending Application
4 – Sending facility
5 – Receiving App
6 – Receiving Facility
7 – Date time of msg
9.1 – Msg Type
92. – Msg Event
10 – Msg Control Id
11 – Msg Processing Id
12- HL7 Version

======= PID =======
3.1 – InternalId
5.1 – Patient Last Name
5.2 – First Name
8.1 – M/F
11.1 – 11.5 – Pat Address
18.1 – Pat Acc Number
19.1 – Pat SSN

======= GT1=======
3.1 – Insured Last Name
3.2 – First Name
81. – DOB

======= DG1 =======
3.1 – ICD Code

======= OBR =======
2.1 – Placer Order No. (Accession Id)
3.1 – Filler Order No. (Accession Id)
4.1 – Claim Order Code
4.2 – Claim Or Cod desc
7.1 – Requested Dt
10.1 – Run By
14.1 – Sampel received dt
16.1 – Extrnl Phy Id (NPI)
22.1 – Result date time
25.1 – Status

======= OBX =======
3.1 Result Code
3.2 Result description
5.1 Result Value
6.1 Res Unit
11.1 – Res Status
14.1 – Rest date time

======= IN1 =======
3.2 – Payer id
4.1 – Payer Name
5.1 – 5.5 – Payer Add
8.1 – Grp No.
15.1 – Payer Type
16.1 – Insured Last Name
17.1 – Relation
36.1 – Policy No.

Quest and Mirth – 1

Using Mirth for Quest lab, I felt the most difficult thing in Mirth. It took me long to finalize the things. Basically we have been given two works for Quest:
1. Sending an order file (HL7-ORM) to Quest lab
2. Receving the result file (HL7-ORU) from Quest lab.

I will be dealing them into two different posts.
This post is for sending the order file to Quest lab.
 
Mirth Version : 1.8 ( Mirth 2.0 will have a slight different approach)

To note here :
Note#1. Quest expected the order file using WSDL. Hence you need to use SOAP sender as destination to send the ORM file to Quest.
Note#2. Quest expects an encoded message. [Dont send a plain HL7 message]

Lets create a channel in Mirth:
1. Channel Name : Quest-Order
2. Configuring Source : Source can be anything which provides a ORM to Mirth engine. Say its a file reader from D:/Quest/Orders/In
  Because of Note#2, we must use a transformer to encode the message.
  Use a JavaScript transformer at source level with below code to it:
 

  var encodedMsg = FileUtil.encode(messageObject.getRawData().getBytes());
  channelMap.put("EncodedMsg", encodedMsg);

    
3. Configuring Destination : Destionation
    Connector Type : SOAP Sender

    While implementing, Quest will be sending you the WSDL URL (or just a web url) and you may get an implementation guide as well. Its huge and will take a lot time to understand and crack the things according to your need. If they dont send you need to ask them.
   
    Irrespective what you get the URL you need to modify it in below manner to fit right with Mirth. Once you choose SOAP Sender under destination fill the things as below:
   
    a) WSDL Path : https://<UserName>:<Password>@cert.hub.care360.com/orders/service?wsdl
    b) Service Endpoint URI : https://<UserName>:<Password>@cert.hub.care360.com:443/orders/service [This will be filled automatically – But I think modify it as I mentioned here]
        SOAP Action URI : Leave blank
    c) Click on “Get Methods” – this should show you all the methods defined in above WSDL
        Select the “SubmitOrder”
    d) Select YES for Generate Envelope
    e) Modify the generated XML as below – Just one change I did under tag  <hl7Order>${EncodedMsg}</hl7Order> – Putting your endcoded variable

<?xml version="1.0" encoding="utf-16"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
  <submitOrder xmlns="http://medplus.com/orders">
    <order xmlns="java:com.medplus.serviceHub.orders.webservice">
      <hl7Order>${EncodedMsg}</hl7Order>
    </order>
  </submitOrder>
</soap:Body>
</soap:Envelope>