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

Difference between revisions of "UTG Agendas and Minutes"

From HL7Wiki
Jump to navigation Jump to search
Line 20: Line 20:
 
#Key topics to be reviewed and confirmed
 
#Key topics to be reviewed and confirmed
 
##Voting strategy
 
##Voting strategy
 +
###Rob questioned if it should be FMG or FHIR-I for FHIR since FMG is not really a workgroup and is not like the other product oversight groups.  Or is it that the other product lines (V2, V3, CDA, CIMI) do not yet have formal management groups?
 
##Coordination with ballots
 
##Coordination with ballots
 
##Integration of External Terminologies Requests
 
##Integration of External Terminologies Requests

Revision as of 21:43, 26 January 2017

Agendas and Minutes

The agendas and minutes will be reverse chronological order. Current scheduled is every other Thursday at 3:30PM US EST. We will use the HL7 conference service:

+1 770-657-9270 Participant Passcode: 598745

and the screen share will be Ted's join.me account, accessible by clicking: https://join.me/tedsnewsessions

You will have to click on 'Knock to Enter' and be recognized to join - so please enter your name when you get to the entry screen

January 26, 2017

call began 3:37PM EST

Attendees: Ted (chair), Rob Hausam, Susan Barber

  1. Overview of Project, Goals, Schedule
  2. Review of PSS
  3. Review of UTG document draft
    1. Available for download at http://www.hl7.org/documentcenter/public/wg/vocab/UTGPdocument_v4.docx
  4. Review of updated intro diagram
  5. Key topics to be reviewed and confirmed
    1. Voting strategy
      1. Rob questioned if it should be FMG or FHIR-I for FHIR since FMG is not really a workgroup and is not like the other product oversight groups. Or is it that the other product lines (V2, V3, CDA, CIMI) do not yet have formal management groups?
    2. Coordination with ballots
    3. Integration of External Terminologies Requests
    4. ??
  6. List of items that need improvement/clarification on the document
    1. Path/process for the 'structural vocabulary'
    2. Coordination and engagement of consensus pool
      1. Do we need a subprocess for consensus pool formation, signup, notification, tracking, etc.?
  7. List of items to be defined
    1. Concordance/index for interest groups
    2. Knowledge set for voting levels
    3. Major tool components needed
    4. Exploration of federated Terminology Store architecture
    5. State machine for proposals
    6. State machine for terminology objects
    7. QA process to discover errors or software bug issues after proposals are applied before they are released
    8. Other ??
  8. Actions
    1. Add submit queue to consensus process
    2. Rename Endorsement Acquisition process to Consensus Process

General Information