National Trauma Data Bank - www.ntdsdictionary.org
Software Developer’s Toolkit
The NTDB would like to offer the latest version of the Software Developer’s Toolkit to states and developers to implement the NTDS XML into their product. This SDK update was posted on 10/10/2016. Previous versions of the NTDS SDK may be found in the website archive.
I wanted to let you all know that the Validator / SDK for the 2017 Data Dictionary is now available for download
The zip file contains the usual assortment of artifacts including:
· The “Technical” version of the Data Dictionary containing extra information from the XSD for each data element
· The XSDs (one for NTDS and the other for NTDS+Process Measures aka TQIP)
· XSD change logs
· NTDS Programmers Guide
· Test harness for command line validation
· And of course this year’s new NTDSSDK.DLL and channel folders.
There are a lot of changes to the NTDS in 2017 so please review the materials closely. This release is the “channel only” version of the SDK which means you must add it to your existing working Validator in order for it to work correctly. If you need a full version with all channels going back over the years, please let me know. If you are looking for the 2017 Data Dictionary please refer to
And as always, please let me know if you have any issues or concerns.
Project Manager, NTDS Validator
Digital Innovation, Inc.
Contact Information regarding use of the Software Developer’s Toolkit:
Project Manager, NTDS SDK
The NTDS and NHTSA 2.2.1 Connection
The XML associated with NTDS is similar to the NHTSA 2.2.1 XML, characterizing standardized pre-hospital variables. The XSDs associated with pre-hospital variables in the NTDS exactly match the same variables in the NHTSA 2.2.1 data standard. This compatibility was designed to promote data exchange. The following link provides a document in which green variables demonstrate direct XML and XSD compatability when moving from NEMSIS to NTDS. Yellow indicates variables in NEMSIS that could “inform” trauma registry abstractors, but no direct data transfer is possible (i.e., there is non-matching XML and XSDs).
Linked document developed by: David James Harden, JD; Trauma Program Coordinator; Arizona Department of Health Services