HTTP Archives - File transfer tool from Limagito

12 Nov
How to skip a path in http as source method 2
How to skip a path in http as source method 2
Q: There are times when downloads are no longer needed for a couple months, is there something I can place in front of the URL to that they are skipped? I tried a semicolon and that did not work 🙂
A: Option added in version v2023.11.10.0
When the URL starts with a ! (exclamation mark) then it will be skipped, example: !https://limagito.com/helpxfm/IntroXFM.pdf
#filetransfer #filemanagement
If you need any help with this ‘skip a path in http’ option, please let us know.
Best Regards,
Limagito Team
By Limagito-Team HTTP skip a path
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
Please add two destinations. Important, the first destination should be HTTP and the second destination WIN
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
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).
RunTime Log Result:
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 ABN, getOrderDocument, HL7
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:
submitOrder
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.
Endpoint
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
{“TVNIfF5+XCZ8Q1RGV3w5NzUwMjg0MHx8TkVMfDIwMT…”}
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):
MSH|^~\&|INSTPROG|50203311|1111|MET|19980630080040||ORM^O01|MSG00001|P|2.3| PID|1||28514753||Joan^Howard^J||196303241225|F SAC|991912376^EXTLAB|01039421^THISLAB|092321A^LAS|092321^LAS||SER|19980620080037|R^PROCESS COMPLETED ORC|RE|5212498721A|||||^^^^^R OBR|1|5212498721A||2951-2^SODIUM^LN|||199807240826||||||||SER OBX|1|NM|2951-2^SODIUM^LN||24.3|ug/g||N
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).
As Destination we selected HTTP:
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)
Content of the Example1.hl7 file:
RunTime Log Result:
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 Base64, HL7, submitorder