ITDX History & Industry Transition

The ITDX (International Trauma Data Exchange) is a FREE industry standard for supporting the flow of standardized trauma registry data to state, regional, system, and national registries.

ITDX is a continuation of the vendor-designed XML format that has been in place in the industry since the inception of NTDS. ITDX is the “new name” for the “same format” that has been designed and used by the vendors to support ACS initiatives. 2018 marks the first year that the ACS designed an NTDS XML format that is not designed by the majority of hospital registry vendors who must develop the needed export and mapping software. Due to this divergence, both XML standards now play important and distinct roles:

  • ITDX XML Role – An Industry Technical Standard – To allow continuity of vendor, hospital, and state system investments, to support standardized exports, and preserve backwards compatibility of data
  • NTDS XML Role – An NTDB & ACS TQIP® Technical Standard – To provide the precise formats required for data submission to these proprietary fee-based repositories.

 

 

ITDX General Overview

The ITDX provides a data transmission format that is harmonized to national standards, such as those used by ACS NTDB® and ACS TQIP®. The general uses of the ITDX are:

  • To serve as a foundation for states to build NTDB-based data submission protocols
  • For hospital systems and other registries to establish custom data standards that could be supported by multiple vendors
  • As a data transmission format that can allow a local registry system to connect to centralized integration points, such as the Trauma Cloud™, or other aggregator implementations for meeting national, state, and other compliance initiatives. In this context ITDX functions as a “buffer” that allows the central database to evolve in a manner that is best for it while minimizing the impact and costs to other information systems that also need to share and integrate trauma data.

 

See the Anatomy of Compliance video for one helpful explanation of ITDX’s important role. (Click Here)

 

The ITDX and NTDS XML formats work together as illustrated in the diagram below. They are both important.

* As is evident from the above diagram, use of the ITDX XML provides reduced initial and ongoing impact to hospital, hospital vendors, State Vendors, and States, for meeting ACS compliance requirements. This is because ITDX is a continuation of the existing vendor instructure used for State and National data submission.

 

ITDX Key Features & Benefits

Key features of ITDX include:

  • 100% ACS Clinical Compatibility – with ACS national standards defined in the NTDS Data Dictionary
  • Vendor Solutions Continuity (e.g, software features & functionality integration, registry mappings, export software)
  • Backwards Compatibility of Data (e.g., landing spots for prior definitions, minimizing impact of change to existing systems)
    As a data transmission format that can allow a local registry system to connect to centralized integration points, such as the Trauma Cloud(TM), State registries, or other aggregators for meeting national, state, and system data submission requirements. In this context ITDX functions as a “buffer” that allows the central database to evolve in a technical manner that is best for its developer/vendor, while minimizing the impact and costs to other information systems and vendors that also need to share and integrate trauma data.
  • Industry Support & Funding (ITDX is the ONLY technical standard that has the FREE export support of all the major vendors — ACS, in contrast, is NOT providing any funding to CDM, DI, or Lancet for implementation of their NTDS XML technical standard)
  • EMS Linkage Support – to help facilitate the electronic integration and linking of trauma outcomes data to pre-hospital run reports and NEMSIS
  • Time Saving Innovations – such as Explicit Negatives Support (which can meet coming ACS requirements for Complications and Comorbidities). Important for minimizing work for registrars and for avoiding impacts on queries and reports, and system change order costs.