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

UTG Agendas and Minutes

From HL7Wiki
Jump to navigation Jump to search

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

March 14, 2017

  • Note that North America has gone onto Summer Time (Daylight Saving Time); ET is now UTC-4.

Attendees: Ted (chair), Susan Barber, Rob Hausam,
call began at 1:05PM EDT; quorum reached.
Agenda:

  1. Review of Status
    1. Actions:
      1. V8 of document in Dropbox
      2. Voting Strawman Analysis document in Dropbox
        1. We looked at the use case, and talked about just what would be "pro-forma" and what would not be for FHIR use cases.
        2. We agreed that even pro-forma vocabulary should go through the new governance process - as long as the process is lightweight and effective and productive.
        3. Continue working through FHIR allergy-verifcation-status example for the new process. This is an internally defined code system, and a value set built on 'all codes'.
        4. It is unclear exactly the constituents and role of the management groups. It was noted that FMG is not the same kind of group as the other Product Line overnight groups. Should it be FHIR-I instead?
        5. Susan asked if it is reasonable to assume that such a large number of participants can be expected to be engaged in the process to review proposals and cast a vote.
      3. Updated diagrams loaded to Dropbox
    2. PSS has been approved, it is still waiting on TSC
  2. Discussion of relationship of this project and the Vocabulary Tooling Project #??? (with Russ)
  3. Review of voting strawman continue on Use Case
  4. Actions
    1. Rob H will take the question about the oversight group to FHIR-I
  5. Next call scheduled for 1:00PM March 28 (two weeks hence)
  6. Call adjourned at ...

February 28, 2017

Note this is the new time, being tried to see if we can get enhanced attendance Attendees: Ted (chair), Rob Hausam, Rob McClure, Frank Oemig, Susan Barber call began at 1:04PM ET after quorum reached Agenda:

  1. Review of Status
    1. PSS is in the process of being approved by TSC
    2. Document is at version 7 right now
  2. Review of voting strawman
    1. Example analysis document
      1. We spent nearly the entire call discussing the proposed example, and realized that we have not yet specified what kinds of vocabulary maintenance operations will be in scope for the new process vs. those that will be out of scope i.e. part of the model design/decision/voting/QA processes, whether that model is a FHIR Resource, a RIM class or attribute, a new V2 message element, or a new CIMI template.
      2. We seem to have decided that new value sets whose CLD is 'all codes from underlying code system' should be treated as pro-forma, and not subject this rigorous maintenance process.
  3. Review of updates to diagrams based on call notes
    1. Overall Process Diagram page 5
    2. Updated color-coded State Machine page 6
      1. Folks would like to see Submitter and Terminology Curator shown the same way Community is shown
    3. Small updates to the 5 diagrams in Annex A
  4. Next Steps
  5. Actions
    1. Ted will update the Overall Process Diagram and integrated into a new v8 of the document
    2. Ted will update the example strawman and the new v8 of the document into DropBox.
  6. Next call scheduled in two weeks on March 14 at 1:00PM ET for one hour.
  7. Call adjourned at 2:01PM ET.

February 23, 2017

Attendees: Ted (chair), Carmela, Rob Hausam, Frank Oemig, Rob McClure call began at 3:35PM ET after quorum reached

Agenda:

  1. Review of Status
    1. PSS is in the process of being approved by TSC
    2. Document is at version 6 right now
  2. New schedule for calls discussion
    1. Some key folks such as Lloyd cannot make it at this time, which also conflicts with much upcoming travel for Ted. New day/time proposed: every other Tuesday 13:00ET or 15:00ET. beginning next Tuesday 2/28/2017
      1. We discussed the time change, there are many HL7 calls on Tuesdays as well. If we had this call at 13:00 ET, it could only be 1 hour, since the binding semantics call is at 14:00. But Lloyd and Frank would have a conflict if the call ran longer than 1 hour, as there are other calls at 16:00 ET on Tuesdays.
      2. We agreed that we would try next Tuesday every other week 13:00 ET for one hour duration.
      3. If this doesn't work, we'll move it again.
  3. Review document v6
    1. State Machine
      1. Missing state and transitions when approved proposal is applied, if errors or problems cannot be validated or applied, need to report and reinject into the process somewhere.
      2. If proposal voting expires (failure to meet quorum), then it may go back to Editing state, or may go archive
      3. Out of manual resolution process, the states are likely ok, but we need to identify somehow that the state transitions may be managed through the tooling or through the manual processes.
      4. Ted notes that we may need to limit the controversial transition so that it cannot be an endless loop
      5. Make it very clear that "Editing" state is creation of a proposal - NOT the terminology store content
    2. Overall Diagrams
      1. "Change Needed" should be "Change to HL7 Terminology Needed"
      2. Make it clear that any submitted proposal is a COMPLETE proposal
      3. It may be very useful to show a very high level picture of 3 phases: construct a proposal, decide on a proposal, apply a proposal to update the HL7 Terminology. Perhaps make three different colors, and use these to color key the States to illustrate which part(s) of the overall process each State belongs to
    3. Voting Strawman
  4. Next Steps
  5. Actions
    1. Ted to update the call calendar and put in the new schedule.
    2. Ted to update the State Machine as per the decisions above
    3. Next call scheduled at the new day/time Tuesday February 28, 2017 at 1:30PM ET.
      1. Note that Ted will be attending the Clinical LOINC meeting in Salt Lake City and may be unable to run or even join the call

February 9, 2017

call had to be cancelled due to inability to attain quorum as of 4:00PM EST (30 minutes into the 60 minute call) We will try again in two weeks on February 23

Attendees: Ted (chair), Susan Barber

Agenda:

  1. Review of Status
    1. All 3 actions from last call completed
    2. State machine diagram for proposals added to document
    3. PSS is in e-vote at FTSD, and will pass (enough yes votes already, but not yet closed)
    4. SGB requested to be added as a co-sponsor to confirm and give the organizational imprimatur to the principles
    5. DropBox folder created for documents
      1. Everyone with the link on the main page can view the documents
      2. Folks shared for edit permissions so far: Susan
  • Email Ted for a share to be able to Edit them; permissions should be set so anyone can view them
  1. Review current document
    1. Review proposal state machine
    2. Review voting strawman - needs enhancements and work
  2. Next Steps
    1. Need a comprehensive overall constructive critique of document
    2. Need to review schedule and project plan for completion
  3. Actions

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. We began reviewing the proposed voting strawman in the Google process doc in some detail and made some tweaks. It needs more work and clarification, and needs to be put into the main process document
    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
    3. Ted to put the voting strawman as updated in the process document and release v5 to the site asap

We are out of time, call adjourned at 5:00PM EST. Next call in 2 weeks on February 9 same time same channel.

General Information

Retrieved from "https://wiki.hl7.org/w/index.php?title=UTG_Agendas_and_Minutes&oldid=135690"