Overview

The FutureNet iSeries system can be interfaced with many different healthcare information systems for voice, text, and image importing and exporting.  FutureNet interfacing software supports standard interface formats, such as HL7 and DICOM.  In addition, FutureNet's software engineers can customize text-based or XML-based interface formats to meet any hospital's specifications.

HL7

FutureNet's iSeries software supports the Health Level Seven (HL7) standard protocol to interface with existing healthcare communication environments.

HL7 interfaces facilitate communication in healthcare settings.  The primary goal is to provide standards for the exchange of data among healthcare computer applications.  The HL7 standard for electronic data exchange in healthcare environments currently addresses the interfaces among various systems that send or receive patient Admissions/registration, Discharge, or Transfer (ADT) data, queries, resource and patient scheduling, orders, results, clinical observations, billing, master file updating information, medical records, scheduling, patient referral, and patient care.

In the past two decades, health care institutions have begun to automate aspects of their information management.  HL7 standards have been instrumental in reducing paper processing, improving cash flow, and improving management decision-making.  HL7 standards have also allowed for the stream-lining and improving of clinical and ancillary services and the ability to integrate all information related to the delivery of healthcare to a patient over his or her lifetime (i.e., an electronic medical record).

DICOM

FutureNet's iSeries software supports the Digital Imaging and Communications in Medicine (DICOM) standard protocol to interface with an existing healthcare communication environment.

The DICOM standard addresses the exchange of digital information between medical imaging equipment.

The DICOM Standard facilitates interoperability of devices claiming conformance.  In particular, it:

• Addresses the semantics of commands and associated data.  For devices to interact, there must be standards on how devices are expected to react to commands and associated data, not just to the information, which is to be moved between devices.
• Is explicit in defining the conformance requirements of implementations of the standard.  In particular, a conformance statement must specify enough information to determine the functions for which interoperability can be expected with another device claiming conformance.
• Facilitates operation in a networked environment, without the requirement for network interface units.
• Is structured to accommodate the introduction of new services, thus facilitating support for future medical imaging applications.
• akes use of existing international standards wherever applicable, and conforms itself to established documentation guidelines for international standards.

Even though the DICOM standard has the potential to facilitate implementations of Picture Archiving and Communication System (PACS) solutions, use of the standard alone does not guarantee that all the goals of a PACS will be met.  This standard facilitates interoperability of systems claiming conformance in a multi-vendor environment, but does not, by itself, guarantee interoperability.

The DICOM standard has been developed with an emphasis on diagnostic medical imaging as practiced in radiology and related disciplines.  However, it is thought to be applicable to a wide range of image-related information exchanged in a clinical environment.