• The doctor would like reports from the lab and radiologists to print directly to a printer at his practice.
  
  This is a very simple and inexpensive process and is the most popular use case for the HIP. The CIP_SA agent is configured and installed at the practice and, if necessary, at the host facility. This process requires about an hour of the practice administrators time to install and less than five minutes per day on average to support.
  
  
• A practice or clinic uses an Electronic Medical Records package. They wish to place orders with the Lab through their system, and have the results returned and attached to the original order in the patient's medical record.
  
  The EMR software must support these functions and have an external communications or interface package available. In addition, the diagnostic or data provider facility must be a HIP node with HL7 support, or be willing to join HIP. If these requirements are met HIP engineers, the facility and the practice determine which interface package option is correct for the practices' situation. HIP engineers then configure the interface. If translation services are required HIP engineers work with the practice to create the code maps. The practice downloads the CIP_CS interface agent from the internet and installs it. HIP engineers then coordinate acceptance testing with the data provider and the practice.
  
  This process normally requires eight to sixteen hours of time on the practice IT staff or administrators time over a two week period to install. Note that if a new HL7 interface installation is needed from the EMR vendor time requirements for the practice can at times be greatly increased. Time requirements for data providers are variable depending on the interface models being used between them and the HIP.
  
  The HIP can support either network based transaction models or file based transfer methods (import/export interfaces) for the EMR software.

• A reference lab wishes to have the ability to remote print results to their practice when the results are finalized. The HIP and CIP_CS software are very flexible and can accommodate a number of different report production and delivery scenarios. In all cases, a simple CIP_CS secure agent is installed on a PC or existing server. The CIP_CS can connect to the source system using socket interfaces (one socket per site, or one socket to support all sites) or file transfers.
  
  
  • Scenario 1: The LIS software can produce the results as individual .pdf files. These files are sent to the CIP_CS secure agent. The CIP_CS agent processes encrypts the files and sends them to the HIP data facility which in turn forwards them to the CIP_CS correct destination. The destination node software prints the files locally and then can either archive them on site (encrypted or decrypted) or destroy them as appropriate.
  
  
  
  • Scenario 2: The LIS sends an HL7 result message to the CIP_CS agent. This message is converted from HL7 to a .pdf document at the HIP server and is then forwarded and printed as described above.
  
  Print formats can be customized, and the use of multiple formats for a single facility is supports. All formats can be branded to the diagnostic facility and can also be formatted for specific provider requirements if needed.
  

Intechgra engineers can work with interested parties to design a specialized version of the HIP tailored to your specific needs. Solutions can be hosted, purchased or in some cases licensed. Please contact an Intechgra sales representative to discuss your organizations specific requirements.