2019 September WGM - Atlanta Agenda

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.

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?

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