Interface

Software Linkages and Interfaces

Complex systems are comprised of many parts, making system interfacing skills paramount. DI has developed system interfaces with a wide array of capabilities to allow our clients to seamlessly integrate a variety of information systems and tools. DI’s system architecture supports a number of interface types and provides the flexibility to enable the “joining” of disparate systems. This flexibility stems from DI’s object-oriented approach, which allows DI to take the programming code that lies “under the hood” of our applications and make it available for use with a range of additional systems and user interfaces, including those connected via the Internet and/or using industry standard formats

DI has developed a number of application program interfaces (or APIs) to allow for data import, export and transfer between applications. One such example of a DI created API is the interface developed for the American College Surgeons for use with their National Trauma Data Bank (NTDB). The NTDB API collects data from an existing Collector Trauma Registry product and passes the data to NTDB. The API reads data records and strips PHI-related fields as well as all non-NTDB related fields. The API “maps” the data into the format expected by the NTDB import function so that the data can be easily passed without a great deal of user intervention. Thus, DI builds APIs to specifically provide a “conduit” between applications. Furthermore, DI maintains the NTDB API to ensure that users stay current with NTDB format changes without direct involvement or interaction.

Complex systems are comprised of many parts, making system interfacing skills paramount. Also paramount is having a system architecture that can support a variety of interfaces. DI is able to develop system interfaces to the many capabilities of its data management solutions, allowing them to integrate with a variety of information systems and tools. This flexibility stems from DI’s object-oriented approach, which allows DI to take the programming code that lies “under the hood” of our applications and make it available for use with a variety of additional systems and user interfaces, including those connected via the Internet and/or using industry standard formats.

Several of DI’s solutions entail system interfaces and examples of those interfaces are as follows:

  • Numerous trauma registry systems entail interfacing between user and central-sites
  • The PA Trauma Systems Foundation (PTSF) central-site trauma system interfaces with the PTSF Site Survey system to implement an electronic medical records review system to support PA trauma center accreditation
  • The QANET system integrates databases for certification, hospital and trauma center resource status, EMS bypass status, mass casualty patient management, EMS data collection, medical command, and PDA upload capability for the County of San Diego’s EMS system
  • Numerous Collector users have developed interfaces between Collector and internal hospital systems, such as ED, Med-Flite, billing, and admission systems.
  • Collector trauma registry systems interface seamlessly with Tri-Code; an automated injury coding product for coding injury narratives into AIS-98 and ICD9.
  • Interfaces are available that allow our applications to interface with specialized analytical, statistical and other third party packages in a variety of medical disciplines.
  • Central-site Collector has components that can be accessed over the WEB via a simple browser interface, and Collector’s components can as well by utilizing CITRIX via a browser

The goal of our interfaces is to allow data to be garnered from other systems, reducing the amount of time spent for duplicate data entry. For example, ADT information can be “pulled” from a hospital’s primary HIS system and interfaces to Pre-hospital solutions like MEMSIS can significantly reduce data entry requirements. Collector’s API for trauma allows data to be entered or updated electronically, while ensuring that the data remains subject to all of Collector’s data integrity and audit trail management functions.

  • All Collector trauma registry systems interface seamlessly with TriCode; an automated injury coding product for coding injury narratives into AIS-98 and ICD9.
  • Our PK pharmaceutical applications interface with specialized analytical and statistical packages, such NONMEM and WinNonLin.
  • Central-site Collector has components that can be accessed over the WEB via a simple browser interface, and Collector’s components can as well by utilizing CITRIX via a browser.

DI engineers can readily adapt to a variety of systems to satisfy specific client requirements. These capabilities have been used to develop numerous interfaces between our products and other information systems, and to extend the functionality of our products. For example, DI developed a sophisticated record linking system for the Maryland Cancer Registry, interfacing numerous information systems to build a comprehensive central history of a cancer diagnosis and the associated follow up treatment. Many other similar examples can be cited.

Collector provides application program interfaces (API) to allow data to be garnered from other systems, reducing the amount of time spent for duplicate data entry. For example, ADT information can be “pulled” from a hospital’s primary HIS system and interfaces to Pre-hospital solutions like MEMSIS can significantly reduce trauma data entry requirements. The included API allows for automated functions to be developed. The API inter-operates with the Collector application, allowing data to be entered or updated electronically, while remaining subject to all of Collector’s data integrity and audit trail management functions. The specific programming aspects of each usage of the API are done on a case-by-case basis. The bid includes such services for MEMSIS and PINS. Others can be developed as well, by DI or others, using the API.

DI’s API will support the use of custom HL7 records as well as ODBC, XML and comma delimited ASCII for the purpose of importing data into the Collector system. The API allows for electronic entry/update of patient records, utilizing Collector’s full management features for ensuring data consistency, integrity, data dictionary compliance, and audit trail logging. In addition, the Collector product has built-in features for importing data in various pre-specified formats (e.g., XML, CSV, etc.)