HL7 project team meeting, 28 April, 2011, 12:00 PM ET

Back to EMS DAM

Attendees

Lumping is OK. NEMSIS elements that are conceptually splittable, but lumped for the purpose of the domain, are acceptable for LOINC question codes.
LOINC names may differ in point of clarification. NEMSIS may or may not use these clarifications in the NEMSIS publication; likewise the HL7 specifications.
LOINC Example answers do not exclusively constitute the range of the question. Questions with different answer sets may be used as long as the conceptual space is the same.
- If the answers are different, the conceptual spaces constituted by those answers will never be identical. There is some level of judgement here.
- The name and axes of the code are constitutive. The examples can be taken to define the minimum conceptual space.
- Open question: whether our codes should be added to the LOINC answer set for existing codes (and for new ones as well).
HL7 "getting out of the business of terminology maintenance": need to define what this means procedurally for value set definition and harmonization
Many domain-specific sets cannot be represented in SCT or other standard terminologies; NEMSIS will become the steward of the NEMSIS code system to support these sets until such time as it is practical and advisable to submit them for inclusion in some other system.

Action	Responsible	Description	Timeline	Status
provide codes to CDC for evaluation	Jay		5/30	open
provide codes to Clay for NEMSIS code assignment	Jay		5/30	open
confirm 'assertion' vs clinical statement pattern	Jay		5/20	open
provide question list to Jaci	Sarah		5/30	open
update vocabulary approach document	Sarah	vocabulary principles, approach priorities, preferred systems	2/17	open
provide trauma criteria	Clay		5/13	closed
SD questions	Jay	See issues	2/10	Closed
PHIN VADS	Sarah	Contact Sundak	2/24	closed

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