Call Us Today! 1-800-279-6726
ONBASE HL7 - (HEALTH LEVEL SEVEN)
Health Level Seven (HL7) is an international healthcare messaging standard widely used to enable disparate healthcare applications to exchange key sets of clinical and administrative data. The OnBase HL7 interface is capable of listening for all HL7 messages, including user-defined messages. The Information within the HL7 message can be used to automate the indexing of documents by utilizing the content of HL7 messages, which can be stored in OnBase as an identifiable set. The content can also be stored and presented in an intuitive, customizable format for viewing purposes. The OnBase HL7 interface is unlike most hospital systems and equipment, which only deal with specific HL7 messages. The OnBase HL7 functionality can listen for any type of message. It is also not tied to a specific version of HL7 (e.g. 2.3 or 2.4).
There is no limit to the number of values assigned to a message that OnBase can store for document indexing purposes. The OnBase HL7 interface attaches actions to each message as soon as the message enters the system. Examples include the automatically storing the values that facilitate automating indexing or the formatting of the information for retrieval and display.
The OnBase HL7 interface is capable of sending HL7 messages and is integrated with the OnBase input modules such as COLD, DIP, Document Imaging, etc. When these modules are utilized in order to process a document, HL7 messages are generated and sent to one or more destination applications. HL7 adopts PPP (Point-to-Point Protocol), therefore ensuring the network is not flooded with broadcast information.
Application
An example of an application in which the HL7 module functionality would be valuable is to make payment posting (unless that is a department in a hospital) faster and more efficient.
In this instance, thousands of Explanations of Benefits (EOBs) EOBs are generated each day. Periodically, an HL7 message would be sent to the HL7 listener from the main medical application side. The HL7 message populates the correct data set to enable the automation of much of the indexing process. This will enable a person to scan in a paper EOB and have all subsequent data fields populated automatically simply by entering a single index value.
835 Processor
The OnBase 835 processor can be used to not only import and index data delivered in that format automatically, but can also separate all EOBs into individual claims. Individual EOBs can then be retrieved from the OnBase repository via claim number. A PCL version of the EOBs is an optional format which can be created using EDI data. This process can be scheduled in the exact same way as a COLD or DIP process.
837 Processor
When the 837 processor is executed, it will produce an XML version of the data with the data parsed by claim. This will allow for the presentation of the data in a document format with only one patient per claim. The entire 837 file stored as an XML file so that research and data mining can be performed on that entire data set.
Integration of Healthcare Applications with OnBase
When the 837 processor is executed, it will produce an XML version of the data with the data parsed by claim. This will allow for the presentation of the data in a document format with only one patient per claim. The entire 837 file stored as an XML file so that research and data mining can be performed on that entire data set.
Core Features
