This is a question we are asked periodically: how can I process a non-HL7 batch file, such as a CSV, into individual HL7 messages for delivery via the interface engine?
Recently, we helped a local hospital on one of our free Ask a Trainer sessions with setting up such a process for handling COVID testing results.
This site has a mass sampling site for COVID-19 testing. The tests are currently sent out for processing which can take 1-4 days for the result to return. A local company has an analyzer that can process the tests which therefore could be done in-house. The company’s analyzer does not have an interface/integration but they can drop the batch results as a CSV file. With this CSV>HL7 conversion, the hospital can then route these results into Meditech through the POC Results interface.
Some other use cases that could fit this process are:
- Re-processing large batches of messages stored in a log file
- Scheduling upcoming appointments taken from another system via file batch
- Registering patient lists
- Processing test cases to test upgrades (orders, results)
With Summit Exchange, one would use the PLAIN TEXT format to feed in non HL7 messages, with a batch file delimiter defined, and a MAP to populate the data in the batch file into the “shell” of a true HL7 message to deliver. Then a regular delivery SENDER.
With Summit Express Connect – one would use The Summit Scripting Toolkit, our Robotic Process Automation technology, to parse the batch file into individual text files for consumption, then the same process as above. We have posted a KB and sample map on our client area to give some guidance on how this may be accomplished.
Learn more here:
For additional information on Product Use Cases, Downloads, and Resources, check out the Customer Care Center.