The HL7 Comm server is a software solution that enables secure and efficient communication between various healthcare systems, including electronic health records (EHRs) and medical devices. It facilitates the exchange of patient information, streamlines workflows, and reduces errors, improving the overall quality of care.
HL7 Comm Multi, also known as HCM, is a server version of HL7 Comm. It allows users to operate their HL7 Comm configurations through a web browser, providing a secure and easily controlled environment. For those seeking a quick and efficient way to perform integration testing or create a single interface on a console access machine, the normal HL7 Comm is more than capable.
However, for those requiring HL7 Comm to function as a server, HCM provides a few key benefits. By running on top of a Java servlet container like Tomcat 6, HCM enables its users to take full advantage of a process run as a service or daemon on their platform. Instead of starting numerous HL7 Comm instances, the HCM ensures that multiple interfaces coexist within a single process that's far easier to manage.
With HCM, users can simultaneously run any number of HL7 Comm "processor agents." All of these processor agents utilize the same code as HL7 Comm. Meaning, if your configuration works using HL7 Comm, it'll work flawlessly inside of HCM. From your web browser, you can monitor and manage processor agents as well as view recent logs using the overview page that shows the status report of all components.
Soon, upcoming versions of HCM will feature the capability to manage configurations and logic scripts directly in a user's browser. Currently, it's recommended to use normal HL7 Comm for creating and editing configurations and for testing and developing logic scripts. Once completed, these results can then be saved in a location accessible by HCM. It's worth mentioning that a queuing service will soon be added to HCM, including basic queue management. For now, a pair of file clients, such as FileOutByDir and FileInByDir, is recommended to transfer data between two processor agents. Alternatively, a set of HL7 network clients (HL7Client and HL7ThreadServer) can also be used.
However, for those requiring HL7 Comm to function as a server, HCM provides a few key benefits. By running on top of a Java servlet container like Tomcat 6, HCM enables its users to take full advantage of a process run as a service or daemon on their platform. Instead of starting numerous HL7 Comm instances, the HCM ensures that multiple interfaces coexist within a single process that's far easier to manage.
With HCM, users can simultaneously run any number of HL7 Comm "processor agents." All of these processor agents utilize the same code as HL7 Comm. Meaning, if your configuration works using HL7 Comm, it'll work flawlessly inside of HCM. From your web browser, you can monitor and manage processor agents as well as view recent logs using the overview page that shows the status report of all components.
Soon, upcoming versions of HCM will feature the capability to manage configurations and logic scripts directly in a user's browser. Currently, it's recommended to use normal HL7 Comm for creating and editing configurations and for testing and developing logic scripts. Once completed, these results can then be saved in a location accessible by HCM. It's worth mentioning that a queuing service will soon be added to HCM, including basic queue management. For now, a pair of file clients, such as FileOutByDir and FileInByDir, is recommended to transfer data between two processor agents. Alternatively, a set of HL7 network clients (HL7Client and HL7ThreadServer) can also be used.
What's New
Version 0.2: N/A