Home >

Development Tools
05-May-2016

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 05/05/2016. Previous versions of the NTDS SDK may be found in the website archive.

(05/05/2016) Hi Everyone,

The link below is for a Validator update to address a relatively minor issue which is entirely discretionary to download and install for your users. It mostly concerns Rules 6208 and 6209 which were introduced for the 2016 Admissions year and incorrectly referred to ‘DeathInEd’ instead of ‘SignsOfLife’ in their Rule descriptions. Other minor updates can be reviewed in the readme enclosed in the zip.

https://transfer.dicorp.com/download/ntdsdk/NtdsSdkv2016.1.5.zip

We have installed this update on the NTDB Data Center, which will always give the most up to date validation responses.

As always, feel free to contact me to review any questions or concerns you might have.

Thanks, Grant

*****************************

(01/20/2016) Hi Everyone,

As we all collectively gain experience with the ICD-10-CM system of coding, our understanding of how Trauma fits within that system will similarly improve. In these relatively early days of using ICD-10 within the NTDS standard we therefore expect to be making somewhat frequent updates to the NTDS Validator so that we don’t unwittingly prevent our trauma users from sending NTDB the records that should be there. The update link included with this email is an example of the need to improve the NTDS Validator with experience gained in the field.

https://www.dicorp.com/download/NtdsSdkV2016.1.4.zip

In certain cases of External Cause coding, it is not possible to describe the mechanism using just the standard set of External Causes within ICD-10. So some experts have recommended adding diagnosis codes from the ‘T’ range to mechanism picklists. While the actual subset of ‘T’ codes where this should be permitted is still being hammered out we didn’t want to prevent valid NTDB submissions being received using ‘T’ codes as External Causes. We have therefore modified the pattern for External Cause and Additional External Causes to allow ‘T’ codes to be used in this release of the Validator.

While we have always strived to keep NTDB Data Center and local Validators in sync, during this fast-paced time of change the same objective might not always be possible. Any software change requires effort to make available within our software products so we want to ensure that the NTDB Data Center will always have the most recent updates in place. If there are any perceived differences in validation results the NTDB Data Center should always be considered as the most up-to-date validation possible. We will make these updates available for you to download at the same time as the NTDB Data Center gets them.

Lastly, if any of your users’ experiences have demonstrated valid records not being accepted by the NTDB Data Center then the specific scenarios generating the result should be brought to the attention of the NTDB folks at ACS so that appropriate modifications to the Validator can be made.

As always, feel free to contact me to review any questions or concerns you might have.

Thanks-- Grant

Grant Dittmer

Project Manager, NTDS Validator

Digital Innovation, Inc.

Contact Information regarding use of the Software Developer’s Toolkit:
Grant Dittmer
Project Manager, NTDS SDK
Digital Innovation
e-mail: NtdsSdkSupport@dicorp.com

 

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