What can I do with this functionality.
Scenario 1: Laboratory Orders
The Situation: Our customer's system produces HL7 Laboratory Orders and receives back HL7 Laboratory Results. However, when trying to do business with a new laboratory they find that while the lab can return lab results in HL7 format, they cannot receive laboratory orders in HL7 format.
The Solution: Since the customer's system could already produce the Lab order in HL7 format, we just created a "Laboratory Order" template and directed the Lab Order HL7 feed to an HL7 Document Publisher (like the UltraPort HL7 Document Engine). The template produced a standard Lab Order document in PDF format and populated a folder connected to the customer's Fax-Server which then faxed those documents out to the Laboratory automatically.
Total time from concept to implementation: 1 day.
Estimated New Cost to the Customer: US$700.00.
Scenario 2: Discharge Summaries
The Situation: The customer (a hospital in the USA southwest). Our customer's billing system produces HL7 ADT messages whenever a patient is discharged for delivery to their EMR system. They needed the ability to automatically create and print discharge summary documents both for the patient and for the hard file.
The Solution: The customer's system was already producing 1 HL7 feed to the EMR whenever a patient was discharged, so they created a "Discharge Summary" document template. Since having the customer's billing system create an additional HL7 feed was prohibitively expensive they used the UltraPort HL7 Postmaster
to intercept the single HL7 feed directed to the EMR and split it into 2 feeds. One for the EMR and one which only included "Discharge" events to an HL7 Document Publisher (like the UltraPort HL7 Document Engine). The template produced a standard Discharge Summary document in PDF format and populated a folder managed by a simple print-server software.
Total time from concept to implementation: 4 days.
Estimated New Cost to the Customer: US$800.00 including the print-server software.
Scenario 3: Extracting Binary Data From HL7 Messages
The Situation: The customer (an EMR software developer) receives HL7 messages with embedded Pathology and Radiology reports (PDF and MS Word documents) which are embedded in OBX segments.
The Solution: Creating a HL7 Document Template designed specifically to ONLY extract embedded binary documents from HL7 messages and spool them out to the file system (see Embedded Binary Data) with a flag in the Publisher Settings to indicate that the Template would ONLY export binary data (see Publisher Settings {Advanced}).