Data Exchange
DSI offers multiple options to exchange information from our system to yours. These options are based on your specific requirements and offer flexibility and scalability; your choice of Exchange options expands as you grow. Data Exchange in divided into 3 categories:

• Remote Document Delivery
  
  • Automatic fax delivery of test results
    
  • Automatic report printing of test results
    
  • Automatic file delivery of test results
    
    
• Internet Ordering and Results Viewing
  
  • ePathlink
    
    
• HL7 Interfaces
  
  • Results
    
  • Orders & Results

Remote Document Delivery
Remote Document Delivery offers DSI clients the option of receiving test results directly to their office.

• Auto Fax
  Delivers test results at appointed (scheduled) times automatically to clients fax machine.
  
  
• Auto Print
  Delivers test results at appointed (scheduled) times automatically to a printer located at the customer's office.
  
  
• File Delivery
  Delivers test results via a secure internet link directly to a folder located on a client's computer.

Internet Ordering and Results Viewing

• ePathlink
  ePathLink provides Web-based patient registration, order entry, and result inquiry capabilities. The tool provides a real-time link to DSI's PathNet Laboratory Information System (LIS) through a secure corporate Internet connection. The solution provides the physician connectivity and ability to register patients and place laboratory orders from clinics or offices via a clinician-friendly graphical user interface. Patients already present in the PathNet database are immediately accessible through online searches or location-based selection lists. New patients can be registered online, with optional prompts for insurance and diagnostic coding information.
  
  
• Script Link - Demographic Upload for ePathlink
  A demographic upload is used for clients using ePathlink for ordering. A historic list of patient demographics from each client's Patient Management System (PMS) is uploaded into ePathlink, capturing all existing patient information. As new patients are added, the script will capture this new information and transport it to ePathlink. This eliminates the need to re-enter patient information.

HL7 Interface
HL7 is a standard for information exchange between medical applications. It is an abbreviation of "Health Level Seven", 7th OSI layer protocol for the health environment. HL7 is a protocol for data exchange. It defines the format and the content of the messages that applications must use when exchanging data with one another in various circumstances. The following descriptions provide an outline for the protocol (computer term for a formal, well defined standard for exchanging information between computer programs):

• Event Driven
  Real world events, such as the admission of a patient, cause messages to flow between applications. In other words, an application that encounters a real world event sends a message to other applications that need to be aware of this event.
  
  
• Application to Application Protocol
  It defines a communication between two independent applications, rather than between closely coupled, client-server type applications. The scope of interest for HL7 is the message exchange between the applications, rather than the specific role of each application in the health care delivery process.
  
  
• OSI level 7 Protocol
  This means that HL7's scope is the format and content of the data exchanged between the applications, not how it's passed between computers or networks. HL7 does not specify how messages will be delivered between the applications. Usually a TCP/IP connection or FTP file transfer is used to deliver a message. However, within local area networks, the de facto standard is the Lower Layer Protocol.
  
  
• Exchange Protocol
  HL7 specifies the way data exchange between applications will be accomplished. It does not specify how applications store or process this data. It is nice for an application developer if their application's database structure coincides with HL7 message definitions, but it's not mandatory.
  
  
• A Standard Protocol
  When you create a proprietary, non-standard link between two systems, a message exchange that better suits your personal needs and better fits the data structure of your application can be created. Although this can be done, the efforts invested in this link are useless when considering a connection to other 3rd party systems. Using HL7 means that your initial development effort can be reused again and again.

Results Only Interface
This is used for clients requesting test results be sent back to their system for viewing and reporting.
Use:

• Results integration into client's system.
  

Requirements:

• Client's system must be a cooperative system, i.e. a system that supports the exchange of HL7 formatted messages.
  
• Client's commitment to and establishment of a formal change control process.
  
• Robust client infrastructure - Network, Operations, and Security (DSI IT Site Survey will determine).
  
• Robust client IT technical skills.

Orders & Results Interface
This is an option for clients using a fully functional practice management or hospital information system.
Use:

• ADT, orders and results integration into client's native system.
  

Requirements:

• Client's system must be a cooperative system, i.e. a system that supports the exchange of HL7 formatted messages.
  
• Client's commitment to and establishment of a formal change control process.
  
• Robust client infrastructure - Network, Operations, and Security (DSI IT Site Survey will determine).
  
• Robust client IT technical skills.