Trauma Registry

Trauma Registry Standardization Projects

DAM project

• Project Scope Statement
• High-Level Plan
• DAM (Enterprise Architect)
• Schedule
  • Compose DAM in fall of 2012 - complete
  • Meet in Phoenix to review DAM - complete
  • Draft constrained model in winter and spring - complete
  • Ballot DAM in May 2013 - complete

CDA project

• Project Scope Statement
• CIM
• Complete IG in summer - complete
• Ballot IG in September 2013 - complete
• Reconcile ballot comments - complete
• Publish - in process
• DSTU is 2014
• Ballot to normative status in January 2015

DSTU Process

Goal: Achieve validation by receiver of at least one document submitted by a sender. Validation level: DI has 4; let's choose the right one.

Gforge site for issues

Trauma_Registry_Terminology_Questions

current implementation guide

Trauma Registry Project FAQ

Meeting coordinates: 10 am ET alternate Mondays beginning 9 February 2014; calls to be posted on the HL7 call site and URL here

Terminology

• All questions have been encoded in LOINC, with the exception of the AAAM Abbreviated Injury Score, which has declined to allow LOINC to reference their property without a fee. This question is encoded in a system developed by ACS for the express purpose of providing a conformant code value for these questions.
• For many properties, answers are encoded in existing systems (ICD, HL7). For the rest, answers have been encoded in LOINC.
• ACS has secured the OID 2.16.840.1.113883.3.2898. Under this root,
  • ".10" values are templates
  • ".11" values are value sets
  • ".12" values are terminologies
  • ".12.1" is the ACS terminology that supports the AIS code mentioned above
  • ".12.2" is the AIS system, which, due to licensing restrictions, is not further specified.

Sources

NTDS

• 2013 Data Dictionary

• schema

Meetings

• Updates will be presented to CIC at monthly meetings. EC, SD, and PC are invited to these and to WGM working meetings.

23 January 2014

20 November 2012