Skip to end of metadata
Go to start of metadata

WGM Information - September 14-20, 2019, Atlanta

Attendance EST 2019 September Atlanta

Day

Date

AM/PM

Session

Icon

Event

Chair

Scribe

Room

Sunday

9/15
PM

Q5


5:00-6:00PM

  • Confluence Tips & Tricks
  • STU Comments Migration Project
  • Additional use of Forms
  • Tools Catalog Project
Andrew
M109

Monday

9/16 

AM

Q1






AM

Q2






PM

Q3






PM

Q4

















AM

Q0


7:00-8:00AMAndrew
M109

Tuesday

9/17
AM

Q1

 

 WGM Agenda / Project Updates / Work Group Health

  • Michael's Items
  • Josh's Items
  • Housekeeping
    • Workgroup Health
      • Mission & Charter
      • DMP
      • SWOT
    • Liaisons Review
      • Review for gaps
      • Communications plan
    • Steering Division Update
      • Updates from SD meeting
      • F/U - Next Steps
  • Merger of EST and Publishing
    • Next Steps
    • GOM process to start with.
      • Mission and Charter
      • Co-chairs
  • Survey Creation
    • Review Questions
    • Identify gaps
    • timeline
    • frequency
    • process for survey data review?
    • Prep/Next steps
Andrew<Need>L501
AM

Q2






PM

Q3






PM

Q4















Wednesday

9/18
AM

Q1

Hosting: V2 Management Group

L506
AM

Q2






PM
Luncheon
Luncheon Meeting

M103
PM

Q3





Parlor 1104
PM

Q4















Thursday

9/19
AM

Q1

Project Review:

  • Tooling Catalog Process Review
  • Call center follow-up for OO
  • RFP response for new C-CDA publishing tool
  • Merger of Publishing and EST Next Steps
    • GOM documents
  • Other Projects
    • JIRA queues for other GForge migrations?
      • Is it far enough along that we can set up the queue for CDA and I can work on the CDA queue migrations?
      • It was suggested that we might be able to take a cut once they were in testing in June/July?
    • As was heard in the co-chairs meeting, the other groups in GForge are interested in getting their errata queues off of GForge as well. I am working on it for CDA Management Group. I can't necessarily speak for the V2 Management Group or any other groups that might still be on GForge but we are already preparing data to migrate.

September WGM Housekeeping

  • Room Assignments
  • Agenda Planning
  • EST Meeting Schedule


L506
AM

Q2

Liaisons Meeting

  • Tools Update for Liaisons
  • Workgroup Survey
  • Liaisons Q&A
<Andrew>
L506
PM

Q3






PM

Q4















Friday

9/20
AM

Q1






AM

Q2






PM

Q3






PM

Q4






Legend

Business
Ballot Reconciliation
Technical

Joint Session

Session with representatives of

Normal Business

User/Community Help Sessions

Luncheon Meeting

Hosting

Unable to render {include} The included page could not be found.

3 Comments

  1. Lloyd didn't punt migration to Jira to the management groups.  Timeline for migrating FHIR is October.  We can look at turning on CDA and CIMI in January-ish.  (No plans to 'migrate' as their source doesn't contain enough metadata).  All work group trackers that are for specifications (i.e. things that could potentially be balloted) need to be based off the same Jira template, so adhoc migration can't work.  It needs to be carefully coordinated & managed.

  2. Lloyd McKenzie , my apologies for the word choice in the agenda. That was absolutely a misrepresentation of the situation. It was I that had been inquiring about moving forward with a migration of STU comments for CDA and then other areas were lumped into that request as well. It had nothing to do with any decisions on your part.

    When we compare the STU comments to what is currently in place for the FHIR JIRA work, there are definitely gaps, as the STU comments include places for current language and proposed language and there does not seem to be fields in the FHIR JIRA that would work for those today, so we would need to look at adding some of those. 

    We also need to answer questions about how we'd set up projects for the non-FHIR areas. Would we do it by product families (CDA, V2, etc?) or would we look at workgroup alignments?

  3. The expectation is that "current language", "proposed language", "issue" all goes in the "details" area in Jira.  That's how trackers typically function.  If you choose to import from your existing tracker structure, you can put labeled versions of those things into the one space, just as FHIR does when importing ballot content.

    All of the "specification tracker" projects will have to work identically in order for ballot processing to work, so "Extra fields" isn't an option.  What there will be is variations in the lists of artifacts and pages that can be pointed to and potentially how those elements are "named" in the CDA and V2 projects.

    There will be a separate tracker for FHIR, CDA, V2 and presumably CIMI.  Discussion will be needed about how we want to handle the other product families - my guess is they'll all get handled in a single tracker.  Items within each tracker can be assigned to the full breadth of HL7 workgroups.  I.e. CDA IG items could be assigned to Pharmacy or even FM.

    I'm happy to come chat with SD and/or the CDA management group to walk through how the tracker functions and how we can/can't adapt it for use by CDA