HL7 project team meeting, 1 December, 2011, 12:00 PM ET

Back to EMS DAM

Attendees

Lat and long: LOINC QN supports string, so a regex for degree/minute/second (as used in NEMSIS) is kosher (it does not have to be a floating point number)
1. question remains: should we convert this to a floating point and make it a PQ, or keep it a text string and let people parse it? NEMSIS offers a regex for it.
'diversion/failure' is a distinct concept; the other 3 'diversion' instances are one concept
'extrication' is sufficient; '>20 min' is too constrictive
LOINCs may be published in January, if we can QA them by next week
CDA Guide ballot changes (accepted in November) to be applied by next week
Jay will ask CIC (today) what to do to get it published as DSTU
open issue: what to do about the agreement to use FDA route codes

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?	Per NEMSIS spec	closed
update vocabulary approach document			open
PHIN VADS	reassess plan to publish via PHIN VADS in light of LOINC/NLM/SCT approach		open