90 likes | 228 Views
National Trauma Data Standard: CDA. 23 January 2014. Trauma - WGM Agenda 1: Guide. CDA implementation guide Changes applied from ballot comments Ask for withdrawal of negatives Publish as DSTU Coding approach AAAM (under ACS OID) Answer codes Leave as LOINC, or temporarily as NTDS?
E N D
National Trauma Data Standard: CDA 23 January 2014
Trauma - WGM Agenda 1: Guide • CDA implementation guide • Changes applied from ballot comments • Ask for withdrawal of negatives • Publish as DSTU • Coding approach • AAAM (under ACS OID) • Answer codes • Leave as LOINC, or temporarily as NTDS? • Project period for DSTU: 1 year (ballot Jan 2015) • DSTU data scenarios • DSTU criteria: one successful send & import
Example • Invent ACS question codes with same semantics • IS_01: pre-dot; IS_02: severity; IS_03: region; IS_04: AIS version; IS_05: ISS • Specified • Code: “IS_01”; System: “aCS-NTDB”; OID: “2.16.840.1.113883.3.2898.12.1”; text: “injury code” • Or “pre-dot code”? • Value: from System: “AIS”; OID: “2.16.840.1.113883.3.2898.12.2” • Annotation: licensed AIS users may use the pre-dot code, the NTDS OID for the AIS system, and some resolution of the text presentation; see AAAM.org for more information • Not specified (instance example) • Value: “711001”; System: “AIS”; OID: “2.16.840.1.113883.3.2898.12.2”; text: “Amputation [traumatic] partial or complete, at shoulder [unilateral]”
Trauma - WGM Agenda 2: DSTU • DSTU period • Rationale & transition assumptions for implementers • Training Friday, 1/24/14 • Criteria (including test data) • Target date to finish • Wiki • Biweekly meetings • Use Gforge to track change requests & issues • WGM meetings • Process • Slides in Training presentation
Trauma - WGM Agenda 3: DSTU • Implementers implement the specification • Modify application code to generate a document when needed • Validate document against xsd • Send document to NTDS to confirm it can be validated & imported correctly • NTDS (DI) develops receipt capability
Our DSTU Process: Issue Resolution • You identify issue and create Bug (“New”) • I triage and put it on the agenda • Priority, grouping similar items • We discuss at biweekly project meeting • Resolve or reject • I modify the guide if necessary • Changes also published on Wiki
Our DSTU Process: Publication • Determine need for new version • Determine scope and date for new version • Generate document • Post to GForge • If appropriate, forward to HL7 for publication on DSTU site