Versions Compared

Key

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


Item

Who

Notes

Roll CallMP
  •  Wayne Kubick
  •  David Johnson
  •  Lorraine Constable
  •  Tony Julian
  •  Lloyd McKenzie
  •  Ted Klein
  •  Jean Duteau
  •  Josh Procious
  •  Marc Duteau
  •  Andrew Statler
  •  Dave Hamill
  •  Jessica Snell
  •  Patrick Loyd
  •  Melva Peters
  •  Austin Kreisler 
  •  Lynn Laakso
Ballot ProjectLM/MP
  • FHIR Specification Feedback project - Josh has identified code that is FHIR specific.
    • change from id to name has been completed 
    • looks like once Lloyd fixes FHIR specific code and one additional review, can begin copying out for other product families
    • hope that this will be done in the next two weeks
Webmaster's ReportDJ/JP
  • no updates

JIRACon Project

JP
  • Gforge License
    • working with Bryn to create server that can export Gforge stuff - historical data but not sure how it will be used going forward
    • will move active things to SVN - EA Cloud
    • need to do analysis before we decide what needs to be moved
    • will renew Gforge license for one more year
    • Lynn - on an old release so may have to upgrade to new release
    • can we get stats on usage
    • do we have to upgrade in order to renew our licence?  Will investigate
  • Confluence calendar - there have been issues reported about timezones
    • variable by user
    • Josh is still looking at the issue
  • 3 short JIRA webinar tutorials have been created
    • how to create issues
    • how to edit and comment
    • how to search
  • Archiving old how to documents
    • need to determine what to do with them
    • Melva is working to review documents on website
  • SGB precepts - creating a form in Confluence
STU Comment Jira MigrationMP
  • waiting on project
  • set up with CDA and V2 Management Groups - to discuss specifications 
  • CDS has comments on STU page
  • Melva will review STU Comment page
Gforge Tracker Jira MigrationMP
  • Have archived some JIRA projects and will archive Gforge projects
  • Decision Tree for what tool to use
  • Process for JIRA projects
  • Have default JIRA workflow and HL7 extended workflow - which one we create will depend on the project
    • Decision tree for HL7 tools - only make the extended workflow available
  • Doesn't include all tools
  • Need to look at communication tools
    • Use of Google Documents/google sheets - not everyone can use
      • need to have the link from Confluence
    • Use of Dropbox
    • Call Calendars - problems with projects not setting calls up in Conference Center
      • looking at allowing non-co-chairs to be able to set up calls
UTG ProjectTK
  • Congrats Ted! Published this week!
    • Thanks to DJ for all of the help with server side work
    • new release planned for next week
  • Working on UTG workflow with Josh over next couple of weeks
    • okay to move forward with the pilot
    • some edge case work to be done and changes to custom fields
    • simplify screens
    • Need to look at scripting - want to automate some parts of the workflow - creation of new OIDS for V3
    • history tracking - need to produce history automatically in workflow
  • Link to JIRA ticketing system was put on bottom - already seeing reported issues
    • Ted thinking how best capture issues in the terminology - may use Confluence instead
      • report a problem and perhaps document a solution
  • Ready to proceed with pilot - to be started May 19th
    • have several who have agreed to participate in pilot
    • will wait to determine if more participants are needed for the pilot
  • Working on scripts to do some clean up
  • Need documentation to be created
    • need to look at where operational support documentation should be created and maintained
Parking LotWK/JP
  • Ballot bound vocabulary - want to identify when something is ballot bound and doesn't go through UTC consensus process
    • use ballot decision and approval tracking and reconciliation processes - run in parallel with UTG consensus processtoo early at this stage - will discuss once live
    • Ted has had a discussion with Lloyd about this topic - each product line has vocabulary
      • only things that are ballot bound in V3 - are those that are in the schemas that are generated by changes to the RIM or datatypes
      • FHIR - if required and published in normative spec and tied to code - will call ballot bound
        • if things are extensible - some issues with calling ballot bound - still under discussion
      • everything that is non-ballot bound - have been brought into UTG
        • will remove from FHIR and just point to UTG
      • still discussion around external vocabulary in FHIR - manually maintained in build
        • Jira workflow change for updates of this in UTG - Ted will work with Josh - transfer to HTA for external terminology
  • 508 Compliance - in IG templates - should we do this in the templates we publish
Announcements / AdministrationMP


Adjournment

...