Home >

Development Tools
29-Jan-2013

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

 

My apologies but we are needing to make this latest release available after the admission year that it relates to has already commenced. However, for TQIP Centers this update is an important one that clarifies and improves upon many of the Rules affecting the use of null values when those are necessary – i.e. this update only affects channel 205. I trust that it doesn’t cause any of you any significant concern in making it available to your clients. Please review the enclosed Release Notes for specific details about the changed Rules.

http://ftp.dicorp.com/download/NtdsSdkV2013.1.7_205_only.zip

------------------------------------------------------------------------------------------------------------------------------------------------

It was recently realized that the 2013 Data Dictionary and NTDS dataset contained an inconsistency which needed to be addressed right away. This email is to announce the update which we would recommend you download as soon as possible to include alongside your applications. The download can be found here:

http://ftp.dicorp.com/download/NtdsSdkV2013.1.3_205_only.zip

The inconsistency this update addresses is in the area of Process Measures – Hemorrhage Control Surgery. The data dictionary shows that HemorrhageControlSurgeryType allows multiple items to be collected. The Date and Time associated with that surgery also indicates multiple entries are possible but has a description that talks about the first surgery that occurred. After revisiting this area of the data dictionary it was determined that the date and time for the Surgery should only be captured for the first surgery and so only single occurrences of the date/time fields are needed. So the XSD has been updated along with the Validator rules that deal with this amended structure. The update only affects channel 205 and so the above zip file only contains the changed files. If anyone needs a full version of the Validator that includes this update, please let me know.

Thanks-

Grant

 

Contained in the files below are the final 2013 NTDS Validator packages. These versions contain all the additional Rules for handling the submission of ICD10 data in 2013 submissions. Only channels 105 and 205 have been updated so if you only need those then choose the “channel-only” zip file and unzip the contents over the top of your existing Validator. If you need a complete set of everything to date then choose the “full” zip package.

In the TQIP Release Notes you’ll see that the element Embolization is highlighted in yellow. Previous communication of this element showed it as a single element when it is in fact a list. Note also in the NTDS Release Notes that the new ICD10 Rules (in light blue highlighting) apply to both channels.

Over the two releases there is a lot of new stuff to absorb so please let me know if anyone has any questions about the new Validator. Also note that there is a new version of the Data Dictionary document as well since this version of the Validator necessitated some small changes there too – so be sure to grab a copy of that when it is released very soon.

Here are the links:

http://ftp.dicorp.com/download/NtdsSdkV2013.1.2_channel_only.zip

http://ftp.dicorp.com/download/NtdsSdkV2013.1.2_full.zip

Documentation of all the changes you can expect to find is included within the zip files.

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