This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

EMS Run Report CDA Meeting 110203

From HL7Wiki
Jump to navigation Jump to search

HL7 project team meeting, 3 February, 2011, 12:00 PM ET

Dial-in

Back to EMS Run Report CDA Meetings

Attendees

  • Jay Lyle, project manager, Ockham Information Services
  • Sarah Ryan, vocabulary facilitator, Ockham Information Services
  • Clay Mann, director, NEMSIS
  • Jim McClay, MD, University of Nebraska Medical Center

Agenda

  1. Agenda check
  2. DAM and DIM status
  3. Review of scope
  4. Approach
    1. Mapping DAM to DIM; DIM to CDA
    2. Tools: MDHT, Wiki
    3. Namespace: OIDs, URI
    4. Vocabularies
    5. Outreach
    6. Meeting topics
  5. Other business

Minutes

Jay reviewed the agenda

Jim narrated the flow of EMS data at Nebraska

  • EMS Agency brings in patient
  • EMS Agency delivers some form of run report on paper
    • One tried an electronic interface, but they didn't last
  • Run report is scanned or keyed into the patient's record in the EHR
  • Trauma registry can pull some information from EHR; some must be keyed

Regarding the question of the scope of the CDA

  • There is information in the Event side of the DAM that requires hospital input
  • This information is out of scope for the run report
  • There are various ways to fill it in--CODES uses run reports + discharges + probablistic matching. For future reference.

Our meeting time coincides with EC: we may ask to share once a month

Next week:

  • review LOINC question submission format
  • review vocabulary process details
  • review CWE code sets (drugs, procedures, etc.)

Action Items

Action Description Timeline Status
SD questions See issues 2/10 open
text text text text

Issues

Issue Description Resolution Status
Run Report Scope Event model contains hospital information: is this 'run report' information? No, per Clay, 2/3/11 Closed
SD question 1 Need OIDs, URN open
SD question 2 harmonizing sections with IHE, HITSP, etc. open
MDHT question 1 approach for many questions: model question as separate template, create new association, use Type to assign template open