Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Time

Item

Who

Notes

Time

Item

Who

Notes

1mRoll call and agenda check

Ted

  • Call started at 12:06PM EST with quorum reached.  
5mReview of status Ted/Jess
  1. Still trying to get a time coordinated with Grahame
  2. Working on design of the publishing of releases workflow and operations
  3. TSC demo went OK yesterday; we are now instructed to sprint to go-live by San Antonio
    1. New requirements came out of the comments
    2. Demo and workflow details setup with Rob McClure for Thursday
    3. First live use will actually be a final beta test and will be those terminology changes critically needed for the opening of the May demo.  We will reach out in Sydney and announce this and make sure that those that will have these proposals will have th training an access to the development team that they will need.
  4. Dave T updates for the versioning and the text blob extensions?
    1. content has not been updated with the new versions yet
    2. unknown states on the text blob extensions; definition needs to be added to the extensions google doc and it needs to get on Dave's plate
  5. Dave T updates for the v2 content
    1. status unknown but it looks like content has not been refreshed
  6. Frank and Ted need to figure out the V2 database and where we will go with the support for older (before v2.9) versions of the tables and their content
  7. Josh is working on finagling and fixing some items noticed during the demo
20mImplementation Of The Versioning SolutionCarol/Jess

The design for versioning was decided on previous calls and the main Vocabulary WG calls (see older minutes for details).  We now have to dtetemine the implementation of the design vis a vis the obects having existing versions from the 3 product families (V2, V3, and FHIR) 

  1. We will implement a 3 part versioning identifier: major versions, minor version, error patch/technical correction.   Confluence discussion of this can be found here 
  2. Each of the 3 clauses will be an integer (e.g. 2.1.0)
  3. Classification of UTG versioning changes by resource (major, minor or technical correction) and by product family as specified in #2 in the UTG versioning discussion page
  4. Value Set Refinements continued from last call
    1. Any meaningful change to definitional elements means a new Value Set Definition (not version). This includes scope and immutable.  Also any change to the Defining URI and OID both.
    2. Major number increment with change to URI or OID without changing the other, ... TBD
    3. The UML model of the VSD and the UTG value set resource design and fully understand the impact on versioning of change in <compose> or other header metadata.
  5. Decisions:
    1. For all non-definitional items in VSD that the VSD spec is silent, changes to these will cause an increment to the minor number.  This may not be workable though.  
    2. Next step:  Ted will list all of the Class.attribute items and we will walk through them one by one on the next.  
  6. Code System version implementation
    1. FHIR and FHIR servers have chosen their own means of version assignment in the past years.  We have to discuss impact of UTG version assignment during the Sydney joint Vocab/FHIR-I session
      1. It appears that FHIR sets the version when it generates a release of the spec; e.g. all of the code systems that are FHIR internal have their versions set to "4.0.1" in the R4 spec.    "Current" has a them set to "4.1.0" (all of them), and we assume this will be changed to "5.0.10" when R5 is released.   This indicates that the <version> in <CodeSystem> holds a publishing release, not a content version update, and thus is confusing.
      2. Should we just keep the FHIR versions, or change them to 2.0.0 for UTG? (as Lloyd has suggested)
    2. The V2 code systems will have their versions set to 2.nn.0 where 'nn' is the version number of the code system published in the v2.9 chapter 2c.
    3. The imported v3 code systems will have their versions set to 2.0.0
  7. All of the v3 value sets imported will be set to 2.0.0
  8. All fo the V2 value sets imported will be set to 2.0.0
  9. At the current time, all the imported FHIR value sets are set to 4.1.0
  10. We will set the versions of the Naming System Resource instances to 2.0.0
  11. No decisions yet for versioning of Concept Maps (which are not yet in UTG)
  12. Versioning of Releases will be also the same kind of 3 part version identifier.   Full publication is an increment of the major number, significant changes are increments of the minor number (but maybe not finalized).   Each new commit/push of approved proposals to the GitHub trunk forcing a new ci build will be an increment of the patch number.
20mImmediate prioritiesJess
  1. Plan the details for the upcoming demos
    1. Plan the Sydney dog-and-pony show, both Matt and Steve will be there
  2. Plan the message for the cochair dinner in Sydney (Tuesday night)
    1. Reminder we will no longer do 'old' harmonization for terminology maintenance; we will start using the new process after Sydney as soon as we can for the May ballot open content
    2. We are working to go live with the new process prior to San Antonio WGM
    3. Education and rollout materials are being developed
    4. We have been focussed on everything we are able to address, but recognize that there are many additional desires that will have to be addressed post-San Antonio
    5. Jess should put ONE slide together that Ted will include - 'old world' vs. 'new world' focus on what cochairs need to pay attention to in order to do their work in 2020 and prepare for the 'new world'
    6. Mention on cochair slides we NEED QA OF CONTENT!!!
    7. Continue the debugging and development and content cleanup, critical that Dave T has any Ted blockers cleared
    8. Iron out the extensions questions with Grahame
    9. Iron out the properties display questions for IGPublisher
    10. Mention that we are aware that the FHIR iG value set development in the Accelerator projects is currently not part of the initial UTG release, and initial discussion on when it will be brought in will be during the Vocabulary WG/FHIR-I session on Thursday Q1
  3. Improve verbiage and documentation for rendered pages. Folks to help are being solicited. 
  4. Follow up with CDA Mgt group on review/examination of the content being rendered
  5. Work with Josh on the publishing workflow implementation and the bug fixes for the proposal completion
20mSpring 2020 PlanningTed/Jess
  1. Testing
    1. "Beta" final test post Sydney for go-live prep
      1. Testing content
      2. Testing workflow
      3. Solicit requests in Sydney for terminology changes that may be used for the final testing prior to go-live
    2. Note that AT THE CURRENT TIME the FHIR value sets being developed for the Accelerator projects are NOT part of UTG.
      1. Absolutely needs discussion in FHIR-I session in Sydney with Vocabulary
    3. Implementation and generation of the initial published release
      1. Must be linked into the main entry page
      2. MUST be done prior to San Antonio WGM
  2. Sydney lunchtime demo Wednesday 2/5/2020; likely only 30m 
    1. Solicit Matt as to what he wants to see since he was not at the TSC demo
  3. Figure out what the go-live process needs to look like
    1. We must have this documented as a first draft to go over with TSC and Wayne in Sydney
    2. Document on a new Confluence page under 'Execution'
  4. Put list of what will be needed in Sydney together for the go/no-go decision the first week of January by the project team
    1. Final TSC decision on go-live date is likely not to occur until after the Sydney TSC meeting (when 'ready')
    2. What does the team need to have ready for the Sydney meeting (to be completed prior to 1/31/2020
10mOther longer term itemsTed
  1. We need major QA on the content
    1. Cleanup the V2 and V3 content for the initial live rollout
    2. Complete the cleanup of the CDA content
    3. Figure out what needs to be done for the FHIR content (ie the stuff being cleaned up on the FHIR 'Internal' tab)
      1. To be discussed in the joint vocab/FHIR-I session in Sydney
    4. Ask the product line management groups to look at the content in UTG and let us know if there seem to be obvious errors and what those errors are so we can fix them.  Ask in Sydney.
  2. Need to setup the list for the immediate items that must be addressed as soon as we go live
    1. Editing of manifests
      1. May be later; may be done manually for some time after go-live
    2. Editing of naming systems
      1. Grahame said it is in the latest editor, but we cannot seem to get it working
    3. We have a running list on Confluence of these.  Update it! Open Issues and Deficiencies in UTG Tooling
  3. VSAC issues
    1. Publication and maintenance for the VSAC value sets which are actually HL7 V3 value sets which have historically been maintained through harmonization and published in the coremif
    2. Convenience copies of content that is not IP protected by the code system owners
    3. Access to or documentation about the rest of the value sets
  4. CIMI/SOLOR (Keith Campbell)
    1. Confirm in Sydney with Keith if we can make the SOLOR interface look like the loinc.org interface stuff for browsing
  5. LOINC value set definitions interface for IGs
  6. IG terminology access in generatl
    1. V2 IGs
    2. V3 IGs
    3. FHIR IGs

Call adjournedTedCall adjourned at 1:01PM EST when quorum was lost.   Next call will be scheduled at the Sydney WGM.

...

  •  Jessica Snellsetup the confluence page for the new requirements that came out of the TSC demo on 1/20/2020
  •  Ted Klein must put cochair slides tougher THIS WEEK for review with Jess, Carol, and Wayne
  •  Ted Klein reach out AGAIN to the marketing folks on logos and colors, and text for the main pages for Sydney
  •  Ted Klein reach out AGAIN to Lisa Nelson on telling us what is missing or wrong in the CDA rendered UTG page
  •  Jessica Snell reach out to Dave H and Matt on what they wish to see at the lunch demo in Sydney (cannot do everything)
  •  Ted Klein see if the OSX version of the FHIR toolkit is updated to 0.0.59 in the GitHub repo (it is not on the GG FHIR tools page)
  •   
  •   
  •   
  •