EMS Run Report CDA Meeting 110210
Contents
HL7 project team meeting, 10 February, 2011, 12:00 PM ET
Back to EMS Run Report CDA Meetings
Attendees
- Jay Lyle, project manager, Ockham Information Services
- Sarah Ryan, vocabulary facilitator, Ockham Information Services
- Abdul Malik Shakir, Shakir Consulting
- Rob Hausam, OntoReason
- one more--did anyone catch the name?
Agenda
- Agenda check
- Vocabulary approach
- Action Items and Issues
- Other business
Minutes
while waiting, we discussed some non-vocabulary questions
- OIDs: vocabulary OIDs have a process; work with Ted
- section OIDs do, too; work with Rob
- extensions: let's bring it to SD
Sarah shared a slide deck on vocabulary approaches
frequency tables: we determined that the best way to handle, e.g., medications, is to bind the whole system. A short list may be provided to the designer of the application user interface, but the interoperability constraint is the system.
post-coordination: not a great idea unless we plan on building tools that can read it. For codes not in systems already: make Nemsis the registrar. Avoid burdening HL7 with curation. NEMSIS can submit these codes to NLM for inclusion in SNOMED CT US extension later, if desired.
Looking for existing OIDs: CDATools.org, and HL7 registry
If a NEMSIS procedure includes a method, and there is a SNOMED code but without the method, put the method in the model, or use a NEMSIS code?
Document principles. We think they are this order:
- Balance interoperability with ease of transition
- Consistency with some other specification, viz, CDA
- Analytical detail
Document preferred systems (clinical questions: LOINC, clinical answers and procedures: SNOMED. medicine: RxNorm. demographics: HL7. . . .)
update vocabulary approach with priority of approaches
- code in preferred system
- make a NEMSIS code
- put the qualifier in the model
- post-coordinate
- (I think we won't get past 2)
Action Items
Action | Responsible | Description | Timeline | Status |
SD questions | Jay | See issues | 2/10 | open |
update vocabulary approach document | Sarah | vocabulary principles, approach priorities, preferred systems | 2/17 | open |
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 | |
Coding strength | Are all RR codes CNE, except, presumably, ICD/RxNorm sets? | open |