• 28 Mar

    HL7 getOrderDocument Request ABN using Limagito File Mover

    Q: HL7 getOrderDocument Request ABN using Limagito File Mover. I would like to resume if possible the sending to ‘MyDomain’ with the ABN option. From my understanding we will use the same wrapper which is working well to send to a new url with a document type of ABN. ‘MyDomain’ will review the codes within the HL7 message and determine the patient needs to sign an ABN form. If they do not ‘MyDomain’ will process the order message and result back using the current download. If the patient has to sign ABN form ‘MyDomain’ will kick back the ACK with a code, we will need to download the ABN form and place on the local server for the staff to get the patient to sign. The order will be processed and resulted, the signed ABN form will be placed with the pickup order.

    A: We added this option in version v2021.3.28.0. FYI, we are using REST/JSON (not SOAP).

    We added some screenshots to get you started. This is how we tested this new option.

    • Use WIN as Source. Put your HL7 files needed for the getOrderDocument ABN request

    Limagito File Mover HL7 Source Folder

    • Please add two destinations. Important, the first destination should be HTTP and the second destination WIN

    Limagito File Mover HL7 as Destination

    • HTTP as Destination setup:
      • Be sure to select the ‘Result Directory’ Folder. Here we’ll put the ABN pdf files if required
      • Select ‘Content File as HL7 getOrderDocument ABN’ as Content Selection
      • ‘Content File’ option should stay: %SFP%SFN.
        • This way we’ll use the content of the source HL7 files for the getOrderDocument Request

    Limagito File Mover HL7 getOrderDocument

    • Add a second Destination, use WIN as Destination.
      • This is where we’ll move the source .dat HL7 files to when HTTP POST is successful.


    • Set Function Setup as in the following screenshot:
      • We enabled the ‘Exit Cyclus on Error’ option so if the HTTP Destination fails (which is the first one), we’ll leave it in the source folder and try again during the next scan.
      • So when we get a HTTP error we’ll not move it to the second Destination (WIN).

    Limagito File Mover Function Setup

    • RunTime Log Result:

    Limagito File Mover HL7 ABN is Required

    If you need any help with this ‘HL7 getOrderDocument Request ABN’ issue, please let us know.

    Best Regards,

    Limagito Team

    By Limagito-Team HL7 HTTP , ,
  • 22 Nov

    Submit a Base64-encoded order HL7 message with Limagito File Mover

    A while ago we received the following question from William: “Is it possible to submit a Base64-encoded order HL7 message”. Since we already had HTTP as Destination, we decided to add this as an extra feature. Available in version v2020.11.21.0

    We recieved the following information from the user:

    The submitOrder method allows you to submit a Base64-encoded order HL7 message to the Data Exchange. The order can be either a Basic Lab Order or a Patient Service Center (PSC) Hold Order.

    You must use the HTTP POST method to submit orders to the endpoint shown below, where domain specifies the Data Exchange environment. 

    POST https://domain/rest/orders/v1/submission

    Request: The Base64-encoded order HL7 message as text/plain format


    Response: The Base64-encoded order acknowledgment (ACK) HL7 message as text/plain format

    As Source we’ll have HL7 order file (not encoded yet) which looks like (it’s just an example):

    SAC|991912376^EXTLAB|01039421^THISLAB|092321A^LAS|092321^LAS||SER|19980620080037|R^PROCESS COMPLETED

    What this new ‘Content File as HL7 order’ option will do is:

    • Strip the Message Control ID from the source HL7 file which is MSH.10 (i.e. MSG00001)
    • Base64-Encode the complete content of the file
    • Place the Base64-Encoded content between JSON quotes like {“Base64-encoded content”}
      • i.e. {“TVNIfF5+XCZ8Q1RGV3w5NzUwMjg0MHx8TkVMfDIwMT…”}
    • Post the result as text/plain format to the domain
    • Check the Response, Result Code = 200 => OK
    • Base64-Decode the content of the Response and check MSH and MSA
    22/11/2020 9:16:14 Check Result Code: 200, True
    22/11/2020 9:16:14 PostHTTP, ContentFileAsHL7order Response Data Decoded as HL7 MSH: MSH|^~\&|1111|MET|INSTPROG|50203311|20201122081613||OOR^O02|MSG00001|P|2.3|||||
    22/11/2020 9:16:14 PostHTTP, ContentFileAsHL7order Response Data Decoded as HL7 MSA: MSA|AA|MSG00001|2916c40402e141b9b07d701671c5019d||
    • Compare the Message Control ID from the Request with the Message Control ID from the Response
      • Both should be the same => OK
      • When different: Error
    • Check the Acknowledgment Code MAS.01
      • AA: Application Acknowledgment: Accept => OK
      • AE: Application Acknowledgment: Error

    Interesting link

    Some screenshot to get you started:

    In our example we have a WIN as Source. The source file will be a HL7 order file (Example1.hl7).

    Limagito File Mover WIN as Source

    As Destination we selected HTTP:

    Limagito File Mover HTTP as Destination

    HTTP Setup:

    • Set Request to POST
    • Set Content Selecton to: Content File as HL7 order
    • Set %SFP%SFN as Content File
      • %SFP: Source File Path (i.e. C:\Test\IN_HL7\)
      • %SFN: Source File Name (i.e. Example1.hl7)
    • Leave Content-Type empty (default = text/plain)

    Limagito File Mover HTTP as Destination Setup

    Content of the Example1.hl7 file:

    Limagito File Mover HL7 example file

    RunTime Log Result:

    Limagito File Mover Submit HL7 order RunTime Log

    If you need any help with our ‘submit Base64-encoded order HL7 message’ option, please let us know. Also, other HL7 related feature requests are welcome.

    Best Regards,

    Limagito Team

    By Limagito-Team HL7 HTTP REST , ,
  • 20 Jan

    Using HTTP Server RunTime Log option as Interface

    Dear Users,

    On request we expanded the built in HTTP server to except some extra parameters of the log URL (i.e. )

    • Before we go further, please check if the HTTP Server is Enabled (Menu item: Server\HTTP Server)

    • Also the RunTime Log option must be enabled to use these extra parameters

    What parameters were already available:

    • ruleid
      • Show the RunTime Log of RuleID 4
    • exe
      • Execute RuleID4

    Since v2019.1.20.0 we’ve added the following extra parameters:

    • status
      • Get the Status of RuleID 4 as HTML Status Code
      • We are using unassigned Status codes as Rule Status (RFC7231: 227-299 Unassigned)
        • 250 = Hold Mode
        • 251 = Move Enabled
        • 252 = Copy Enabled
        • 253 = Delete Enabled
        • 254 = Move enabled, Check RunTime Log
        • 255 = Copy enabled, Check RunTime Log
        • 256 = Delete enabled, Check RunTime Log
        • 257 = Move Disabled
        • 258 = Copy Disabled
        • 259 = Delete Disabled
        • 261 = Move Running
        • 262 = Copy Running
        • 263 = Delete Running
        • 264 = Move Terminating
        • 265 = Copy Terminating
        • 266 = Delete Terminating
        • 270 = Scanning Disabled
    • report
      • Get the Report of RuleID 4

    Quite some customers use a command line tool called curl to execute a rule from an external application. This command line tool (curl) uses the built in HTTP server options/parameters we explained before.

    Some examples:

    • Execute RuleID4 using curl
      • curl
    • Get Status Code of RuleID as HTML Status Code using curl
      • curl -sL -w “%{http_code}” -I “” -o /dev/null
    • Get Report of RuleID 4 in your browser

    Please let us know if you have any questions about these new parameters. Don’t hesitate to contact us.

    Limagito Team

    By Limagito-Team HTTP , ,
1 2