Submitting OLIS messages in production

Cho Yin Yong 6/28/2018 3:27:50 PM

What exactly should I use to digitally sign my hl7 request? In the above link, it says "Digitally sign the Request message using a PKCS#7 format signature using a cryptographic toolkit.", but no specifics on which PKCS signature I should use to sign. Thanks in advance.

I have tried a few ways to sign the message. I have tried to use OpenSSL to sign the request message (datafile) with a combination of my private key and the certificate.pem (keyandcertfile) with the following command:

openssl cms -in datafile -sign -signer keyandcertfile -nodetach -outform pem|der

I then used the output of that file, base64 encode that and then send the request to the endpoint with no luck.

EDIT: The server is now responding with Unsupported Message Type (HL7 Error #200) with this HL7 message:

MSH|^~\&|^2.16.840.1.113883.3.59.1:4004^ISO|194cd1ca-da5f-4c23-a324-87a44f67c6a0|^OLIS^X500||200506 01134500-0400||SPQ^Z01^SPQQ08|5b6046b3-54e9-4f24-8e8d-f784d283d41b|P|2.3.1||||||8859/1 ZSH|123976456|John Henry Everyman SPR|QRYTAG123|R|ZQryLabInfoForPatientID^^HL70471|@OBR.22^20020101000000-0400~@PID.3.1^6948425589~@PID.8^F~@PID.7^19940115~@ZRP.1.1^926279~@ZRP.1.13^MDL~@ZRP.1.22.1^ON~@ZRP.1.22.3^HL70347~@ZRP.1.2^Richards~@ZRP.1.3^Reed~@ZRP.1.4

Last Edited 6/28/2018 4:26:52 PM

0 Vote Up 0 Vote Down

6 Comment Details

Order By Standard | Newest | Votes | All
Arthur Krughkov 6/29/2018 11:00:45 AM

Hi Cho,

First of all I want to make sure that you are using the FULL OLIS Specifications documentation that has been published. The summary that is published on innovation-lab is enough to get you started with LITE services, but once you move on to the FULL services I STRONGLY recommend to go to the complete documentation that is published on our standards site (the link can be found under each EHR Service under resources on the right hand side) For example for OLIS, if you go to "EHR Services -> Ontario Laboratories Information System", then scroll to the bottom and on the right hand side you will see "Resources" section, click on the "OLIS Standard" and it will take you to the latest OLIS Standards.

Once you have the complete OLISInterfaceSpecifications guide, it will most likely make it a LOT easier for you to develop and troubleshoot FULL services.

In your specific case, looking at page 258 of OLISInterfaceSpecifications, the error indicates that the message type that you are indicating in MSH.9 field is not a valid message type.

If you need us to take a closer look at the message you are sending, please attach here the message before you sign it, and then the SOAP message that you are sending.

Hope this helps

0 Vote Up 0 Vote Down
Cho Yin Yong 6/29/2018 3:16:47 PM

I have looked at the specifications document prior to posting this and know that it is saying the MSH.9 field is not supported by OLIS.

My unsigned message request: My full soap message:

Thanks in advance.

I've also tried these things in MSH.9





Last Edited 6/29/2018 3:53:41 PM

0 Vote Up 0 Vote Down
Arthur Krughkov 6/29/2018 3:54:14 PM

Hi Cho,

I took a very quick look at your message (thanks for sending it). Lets look at the second line: MSH|^~\&|^2.16.840.1.113883.3.59.1:4004^ISO|194cd1ca-da5f-4c23-a324-87a44f67c6a0|^OLIS^X500||200506 01134500-0400||SPQ^Z01^SPQQ08|5b6046b3-54e9-4f24-8e8d-f784d283d41b|P|2.3.1||||||8859/1

Looking at MSH.9 you have the following:


Looking at the OLIS Specifications (pg 152, section: MSH.9 Message Type) the valid options for Z01 are any one of the following: SPQ^Znn^SPQ_Q08

Summary: You are missing the "_" between the "QQ". MSH.9 should like like this:


0 Vote Up 0 Vote Down
Cho Yin Yong 6/29/2018 4:01:00 PM

Yes, I have tried a variety of things in the MSH.9 field, but they all return unsupported message type for some reason.





0 Vote Up 0 Vote Down
Vlad Lev 7/3/2018 11:03:53 AM

Hello Cho,

Based on standard (page 152, paragraph we use the date time value for MSH.7 without space (Format: CCYYMMDDHHMMSS-ZZZZ). In your original message you have a space between 6 and 0. 200506 01134500-0400 Could you please try to change the date/time value?

Thank you

0 Vote Up 0 Vote Down
Cho Yin Yong 7/3/2018 11:13:23 AM

Seems to work now, thank you

0 Vote Up 0 Vote Down

Stay Up To Date

Published four times a year, the Blueprint Bulletin provides readers with regular insight into the elements, services and new developments associated with the Ontario eHealth blueprint.