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 on11/5/2013. Previous versions of the NTDS SDK may be found in the website archive.
I wanted to let you all know that a second release of the Validator and SDK for the 2014 Data Dictionary is now available for download at:
This release addresses a change to the ICD-10 inclusion criteria described in an update to the 2014 Data Dictionary (that will be located at http://www.ntdsdictionary.org/ shortly). Rule 8703 has been modified to conform to the new inclusion criteria. Also Rule 5302 has been removed.
- XSDs – these have been reworked to simplify the former XSDs. Both the NTDS and TQIP versions now have a common datatypes.xsd that they refer to. Data types that are common to many elements (e.g. Sbp, Gcs, etc) are now declared only once in the datatypes xsd and all elements using that type refer to it. The shorthand identifiers from the data dictionary (e.g. D_03) have been added to the XSD as well to make cross-referencing easier.
- Some of you have noticed that the data dictionary no longer carries the XSD table that previously headed up the description of each data element. Contained within the SDK is a version of the dictionary document that has it back (called 2014 NTDS Data Dictionary (tech version).pdf). This is not a full version of the dictionary document but rather just a description of the elements with the XSD table included. If you need the Appendices and preamble please continue to use the primary data dictionary document. The XSD table has been amended to provide you with more information than it contained previously. The format and definition of the table is as follows:
- XSD Element Name – this is the name of the element within the XSD. Simple enough.
- XSD Schema Datatype – formerly known as XSD Data Type this is the primitive data type defined by the XSD standard like string, integer, date, etc. This is a list of all of them: http://www.w3.org/TR/xmlschema-2/#built-in-primitive-datatypes
- XSD ComplexType – this one is new. It is the data type defined internally within the datatypes XSD.
- Multiple Entry Configuration – same as previous
- Required in XSD – same as previous
- Accepts Null Value – same as previous
- The last line(s) don’t always appear but they do they can have different things in it:
- Constraint: Enumerated List – this means that there is a specific set of values that are valid for this element. These are defined below in Field Values. But in the XSD they are spelled out as well and only valid numbers in the list can be used.
- Minimum/Maximum Length – if a code has certain length constraints like an ICD9 code then you will see these headings pop up.
- Minimum/Maximum Value – if a number has range limits then these will show here – e.g. SBP
- RegEx Pattern – this is a new one and only shows up in the second column of this row when it’s used. These are mostly present in the ICD9 and 10 elements now. The RegEx patterns in the XSD are really intended as a guideline for format. In ICD10 there are many nuances regarding when variations in format are permitted and the Validator follows these differences more faithfully. The Rules added for ICD10 elements describe these in more detail.
- The items that were discussed last week between Chris at ACS and the vendor community (for minor Rule and definition changes) are included in this release.
- The rest of the contents of the zip file should be familiar to you by now. Please note that this is a channel only release and is additive to previous Validator installs. If you need a full version of all channels for the Validator, please let me know so we can put something together for you.
Please let me know if you have any issues or concerns with this updated release for 2014.
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