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

EMS Run Report CDA Meeting 110804

From HL7Wiki
Jump to navigation Jump to search

HL7 project team meeting, 4 August, 2011, 12:00 PM ET

Dial-in

Back to EMS DAM

Attendees

  • Jay Lyle, project manager
  • Sarah Ryan, terminology facilitator
  • Jaci Phillips, MS RN, Regenstrief Institute
  • Clay Mann, NEMSIS
  • Peter Gilbert, Covisint

Agenda

  1. Agenda check
  2. Code approach
  3. Code finalization
  4. Code publication
  5. ballot reponse
  6. San Diego

Minutes

  • Added San Diego plans to agenda
  • Codes: keep the two-tier approach, where LOINC codes are assigned according to semantics of label (one 'abdominal bleeding' code) and NEMSIS keeps all ten. This is not a problem for LOINC. It might be confusing to those assessing NEMSIS; Clay will consider a) documenting the reason for the 1:many relationship and b) adding metadata to the code repository to clarify the actual semantics of the codes.
    • Items from other systems (ICD-10, RxNorm, or GNIS) are not to be enumerated.
  • Delivery: Jaci can continue with the current list of labels. The codes will change (e.g., there are codes that are reused). NEMSIS will assess criteria for the splitting/lumping practice, regenerate codes where necessary, and have the final list ready next week.
  • Publishing: via LOINC, via NEMSIS web site, via a DSTU site for implementer info (either NEMSIS or GForge), hopefully via PHIN VADS
    • Clay to follow up with Sundak
  • Ballot response: NEMSIS and Ockham both to review and respond; Clay to include items from V3 change log in review.
  • San Diego: out of time

Action Items

Action Responsible Description Timeline Status
SD questions Jay See issues 2/10 Closed
update vocabulary approach document Sarah vocabulary principles, approach priorities, preferred systems 2/17 open
PHIN VADS Sarah Contact Sundak 2/24 closed

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 URN: make one up, per B Dolin. OIDs: request a 'root' document OID and write our extensions, for later import into the repository. closed
SD question 2 harmonizing sections with IHE, HITSP, etc. Use CCD as appropriate, or downstream templates as necessary. No registry or process exists. closed
MDHT question 1 approach for many questions: model question as separate template, create new association, use Type to assign template confirmed by Sean closed
Coding strength Are all RR codes CNE, except, presumably, ICD/RxNorm sets? open