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

EMS Run Report CDA Meeting 120614

From HL7Wiki
Revision as of 17:54, 14 June 2012 by Jlyle (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

HL7 project team meeting, 14 June 2012, 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

Agenda

  1. licensing
  2. guide progress
  3. training
  4. plan for scoping up: defer to July

Minutes

  • Note: Meetings have been held since January, but we'll need to reconstruct them, as they were not recorded here. For the May WGM, see the CIC minutes.
  1. licensing
    1. Jay has not yet determined whether DSTU participants must be members (or purchase the specification). It seems a comment profile should be sufficient: tbd.
    2. Still working on a meeting with HL7 regarding Umbrella membership. It seems from the GOM that it's a discount mechanism for benefactors, not, as previously thought, a way to purchase a bundle of memberships.
  2. Guide is substantively complete and should be published by the end of June
    1. working on integrating intro material into DITA
    2. QA and rationalization of patterns
    3. importing value sets
  3. DSTU Implementer Training
    1. On continuum of Powerpoint-to-on site training, sponsor leans toward on-site.
    2. Team to outline course, bringing in a technical resource to assist
    3. Aiming for August, optimistically
  4. Scope
    1. Structured Documents is OK with the one large document serving many use cases with lots of optional content approach.
    2. We'll get the current guide implemented and nailed down before expanding scope
    3. At that point we can plan to flesh out the full data set
      1. DSTU extensions (one) are permitted (GOM 13.02.06.02 Extending the Trial Use Period)
      2. We'd want to stage that process; i.e., build out interaction #2 (outcomes) and begin testing it before tackling #3, etc.