I have heard that the NHTSA 2.2.1 database shares common XSDs with the National Trauma Data Standard (NTDS). Why is this?
The National Trauma Data Standard (NTDS) data dictionary contains a number of variables that are to be obtained from the pre-hospital record. The programming language that defines variables in NTDS and NHTSA 2.1.1 were designed to exactly match. This was done so that “next generation” trauma registry software and pre-hospital software could exchange data. Thus, in the future, trauma registrars may open a new record on a patient, only to find that all of the pre-hospital variables have “auto-populated” the record. Similarly, when an abstractor finishes a trauma registry record, ED and hospital outcome data could “back-populate” the EMS record, allowing EMS to evaluate QA topics for transported patients. For a detailed description of the overlap between the two data bases, click on this link. In the linked document, green variables demonstrate direct XML and XSD compatability when moving from NEMSIS to NTDS. Yellow indicates variables in NEMSIS that could “inform” trauma registry abstrac
Related Questions
- The NHTSA 2.2 Data Dictionary indicates that a number of demographic elements are required National Elements. Why doesn’t my XML validate when I include all of the National demographic elements?
- I have heard that the NHTSA 2.2.1 database shares common XSDs with the National Trauma Data Standard (NTDS). Why is this?
- Can I use vendor software to send Fire Department and incident data to the State of Maine and the National Database?
