1 / 9

National Trauma Data Standard: CDA

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?

saeran
Download Presentation

National Trauma Data Standard: CDA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. National Trauma Data Standard: CDA 23 January 2014

  2. 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

  3. 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]”

  4. 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

  5. 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

  6. Our DSTU Process : Issue Resolution

  7. 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

  8. Our DSTU Process: Publication

  9. 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

More Related