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

Difference between revisions of "2017-09-06 FMG concall"

From HL7Wiki
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  
 
| width="0%" colspan="2" align="left" style="background:#f0f0f0;"|'''HL7 TSC FMG Meeting Minutes''' <br/>
 
| width="0%" colspan="2" align="left" style="background:#f0f0f0;"|'''HL7 TSC FMG Meeting Minutes''' <br/>
 
'''Location: <br>https://global.gotomeeting.com/join/279790597''' <br/>(voice and screen)
 
'''Location: <br>https://global.gotomeeting.com/join/279790597''' <br/>(voice and screen)
| width="0%" colspan="1" align="left" style="background:#f0f0f0;"|'''Date: 2017-08-30 '''<br/> '''Time: 4:00 PM U.S. Eastern'''
+
| width="0%" colspan="1" align="left" style="background:#f0f0f0;"|'''Date: 2017-09-06 '''<br/> '''Time: 4:00 PM U.S. Eastern'''
 
|-
 
|-
 
| width="0%" colspan="2" align="right"|'''Chair''':  
 
| width="0%" colspan="2" align="right"|'''Chair''':  
Line 22: Line 21:
 
| colspan="2"| Members ||colspan="2"|Members||colspan="2"|Members ||colspan="2"|Observers/Guests
 
| colspan="2"| Members ||colspan="2"|Members||colspan="2"|Members ||colspan="2"|Observers/Guests
 
|-
 
|-
|x || Hans Buitendijk||x ||Brian Postlethwaite  ||x ||Paul Knapp || x || Anne W., scribe
+
| || Hans Buitendijk|| x||Brian Postlethwaite  || ||Paul Knapp ||x || Anne W., scribe
 
|-
 
|-
| x||Josh Mandel  || ||John Moehrke||x ||Brian Pech || ||  
+
|x ||Josh Mandel  || x||John Moehrke|| ||Brian Pech || ||  
 
|-
 
|-
|x ||Grahame Grieve  || || || || ||.||eric Haas, Richard Ettema  
+
| ||Grahame Grieve  || || || || ||x|| Richard Ettema, Chris Johnson
 
|-
 
|-
 
|}
 
|}
Line 33: Line 32:
 
*Roll Call
 
*Roll Call
 
*Agenda Check
 
*Agenda Check
*Minutes from [[2017-08-09_FMG_concall]]  
+
*Minutes from [[2017-08-30_FMG_concall]]  
*Administrative
 
 
*Action items
 
*Action items
**Lloyd to put together a draft template for IG proposals and clean up some of the profile proposal template  
+
**Lloyd to put together a draft template for IG proposals and clean up some of the profile proposal template
 
**Lloyd to update on turning QA spreadsheet and corresponding wiki pages into WG assessment/reporting tool
 
**Lloyd to update on turning QA spreadsheet and corresponding wiki pages into WG assessment/reporting tool
 
**Josh and Grahame to determine requirements for proposal to manage balloting on Github
 
**Josh and Grahame to determine requirements for proposal to manage balloting on Github
**Paul to check with TSC regarding agenda time in San Diego regarding publishing ballot content on Github/other tools
+
**Paul to take proposal on publishing ballot content on Github/other tools to TSC when available
**David to send out reminder regarding Connectathon registration before early bird deadline
 
 
**Eric to nudge Lorraine/Claude to come to 2017-08-30 meeting for update on CatalogEntry
 
**Eric to nudge Lorraine/Claude to come to 2017-08-30 meeting for update on CatalogEntry
**John to follow up with CBCC on ConsentRequest
+
**Anne to add FMG notes section proposal templates
**Anne to add add FMG notes section to proposals we have issues with
+
***Complete
**Delete DecisionSupportServiceModule
 
 
**Lloyd to discuss ServiceDefinition issues with Bryn
 
**Lloyd to discuss ServiceDefinition issues with Bryn
**Lloyd to nudge FHIR-I regarding completing TestReport proposal
+
**John to complete TestReport proposal
 
*Discussion Topics
 
*Discussion Topics
**Publishing ballot content on Github (continued from last call)
+
**San Diego Agenda
 
*Reports
 
*Reports
 
**Connectathon management (David/Brian)
 
**Connectathon management (David/Brian)
Line 64: Line 60:
 
**Ballot content review and QA process [[FHIR QA Guidelines]]
 
**Ballot content review and QA process [[FHIR QA Guidelines]]
 
*AOB (Any Other Business)
 
*AOB (Any Other Business)
*Parking Lot
 
**Paul to review STU FMM rationale and discuss with SGB
 
  
 
==Minutes==
 
==Minutes==
 +
 
*Roll Call
 
*Roll Call
 
*Agenda Check
 
*Agenda Check
**MOTION to accept: Hans/Paul
+
**MOTION to accept: Josh/Brian Post
 +
*Minutes from [[2017-08-30_FMG_concall]]
 +
**MOTION to accept: John/Brian Post
 
**VOTE: All in favor
 
**VOTE: All in favor
*Minutes from [[2017-08-09_FMG_concall]]
 
**MOTION to accept: John/Paul
 
**VOTE: Hans abstains. Remaining in favor.
 
*Administrative
 
 
*Action items
 
*Action items
**Lloyd to put together a draft template for IG proposals and clean up some of the profile proposal template  
+
**Lloyd to put together a draft template for IG proposals and clean up some of the profile proposal template
 
***Add for next week
 
***Add for next week
 
**Lloyd to update on turning QA spreadsheet and corresponding wiki pages into WG assessment/reporting tool
 
**Lloyd to update on turning QA spreadsheet and corresponding wiki pages into WG assessment/reporting tool
Line 83: Line 76:
 
**Josh and Grahame to determine requirements for proposal to manage balloting on Github
 
**Josh and Grahame to determine requirements for proposal to manage balloting on Github
 
***Add for next week
 
***Add for next week
**Paul to check with TSC regarding agenda time in San Diego regarding publishing ballot content on Github/other tools
+
**Paul to take proposal on publishing ballot content on Github/other tools to TSC when available
***Paul will take to TSC when we have proposal is available
+
***Add for next week
**David to send out reminder regarding Connectathon registration before early bird deadline
 
*** 6 days ago we had a total of 146 registered with 17 observers. Paul reports that some regular financial track people may not be there.
 
 
**Eric to nudge Lorraine/Claude to come to 2017-08-30 meeting for update on CatalogEntry
 
**Eric to nudge Lorraine/Claude to come to 2017-08-30 meeting for update on CatalogEntry
 
***Add for next week
 
***Add for next week
**John to follow up with CBCC on ConsentRequest
+
**Anne to add FMG notes section proposal templates
***Complete. They have withdrawn the proposal. Discussion over adding "retracted" category to the top of the resource proposal page. Added pages on the wiki for retracted resources and profiles.
+
***Complete
**Anne to add FMG notes section to proposals we have issues with
 
***Anne to add to template and we'll do it as we go.
 
**Delete DecisionSupportServiceModule
 
***Added to retracted proposal page
 
 
**Lloyd to discuss ServiceDefinition issues with Bryn
 
**Lloyd to discuss ServiceDefinition issues with Bryn
***Add for next week
+
***Complete. They are looking at getting rid of it.
**Lloyd to nudge FHIR-I regarding completing TestReport proposal
+
**Richard to complete TestReport proposal
***John volunteers to complete the proposal
+
***Richard made updates. Group Reviews. Still needs FHIR-I approval before FMG can approve it.
 +
****FHIR-I to review and bring back to FMG.
 
*Discussion Topics
 
*Discussion Topics
**Publishing ballot content on Github (continued from last call)
+
**San Diego Agenda
***Nothing more to report this week.
+
*FMG
*Reports
+
**Plan for draft for comment ballot in December
 +
**Connectathon recap
 +
**Github balloting proposal - brainstorm requirements, next steps. Lloyd notes that Jira may meet the intended outcome of this idea. Josh says it may do so. Josh asks if there is a list of requirements for Jira? Lloyd will be taking time at WG to talk to Karen/Mark regarding changes to fundamental ballot processes, like how block votes are handled, etc. to better allow voting directly using a tracker with no spreadsheets. Most obvious challenge with voting directly inside Github is it wouldn't be tied to HL7's membership database, and the right to vote is what you're paying for. TSC has been clear they want any voting solution to be the solution for all content, and all content won't live on Git. If we can come up with a pleasant way of linking pull requests to ballot items that are also change requests, then we might be able to meet the objective behind this proposal. Brian: One request is to use Github issues for tracking and the other is to use Github source control for the build. David: If we use Jira and Github, the comments could end up in two places. Lloyd: The desire of HL7 is that we use one mechanism for commenting, and they will likely want total control over that mechanism. Question is really - for the content that lives in Github, how easy is it to point people to Jira for comment submission, still integrating with the pull request mechanism of Git.  Josh asks, from a governance perspective, what our balloting needs to accomplish. Lloyd: Our desire is to get read of spreadsheets. Will be writing up requirements prior to WGM. Could add integrating with pull request mechanism of Git.  Josh: We want to know what it would take to do a small ballot in Github. Lloyd: The TSC's directive is that there is one balloting mechanism for everything for everyone. Decision to continue the discussion in person.
 +
**Jira evaluation/requirements
 
**Connectathon management (David/Brian)
 
**Connectathon management (David/Brian)
***David won' t be there; Ewout will facilitate. Wayne is keen to make sure that the wrap up presentations are linked back into the track proposals so that they can be found. Richard asks if he should plan to do the usual intro to FHIR morning presentation; David suggests he talk to email about it. Also notes that he will be publishing the latest test scripts out to the Github platform - Patient, Patch, Terminology, FHIR Genomics,ProviderDirectory, GraphQL, LastN. Paul asks if it's on the HL7 Github? Richard states it is at https://github.com/FHIR/documents. David asks if we should go out to track leads to have them work with Richard to develop  test scripts? Richard will send out an email to the track leads. John asks if we have a common way we have the tracks utilizing Zulip? Hasn't noted a pattern. His track could use some kind of discussion forum. Paul notes  people have used Con_track name under Connectathon Management stream. Discussion over going out to track leads with the advice that there should be a communication vehicle and suggest that they use Zulip.
+
***ACTION: David to create/post signup spreadsheet for Connectathon
****ACTION: David and Richard will work on an email re: chat during the event and how to upload the report afterwards
 
 
**[[FHIR Governance Board|FGB]] –  
 
**[[FHIR Governance Board|FGB]] –  
***Met and discussed/approved principles for product life cycle. There is a role there for FMG in executing the principles. Paul sees this as a change management strategy. Came up on SGB today as well. Seems to be a mixture of things which are management and things which are methodology. Grahame agrees with that assessment. Paul: Should we discuss at the joint meeting in San Diego? Wondering about timeline for advancement. Grahame: Hard to know timeline. Will try to have ready for San Diego.
+
***Didn't meet this week
 
**MnM –  
 
**MnM –  
***Has not met.
+
***Didn't meet this week
 
**[[FMG Liaisons]] –
 
**[[FMG Liaisons]] –
***John updated profiles from other organizations with profiles from IHE. Still probably two more to come. David notes there should be a link from the main wiki page. John states that the goal is to get into the eventual registry on FHIR.org. David asks how you get added to the "organizations implementing FHIR" page on FHIR.org? Grahame states that, for the time being, they can email him.
+
***No report
<!--
+
*Adjourned at 4:50 pm
*Precepts
+
 
**
+
 
-->
 
*Process management
 
**Ballot Planning
 
<!--**Developing FMG Management Methodology - see [[FHIR Methodology Process]] and [[FHIR Guide to Designing Resources]]
 
**FHIR Design patterns - see [[FHIR Design Patterns]] -->
 
**Ballot content review and QA process [[FHIR QA Guidelines]]
 
*AOB (Any Other Business)
 
*Parking Lot
 
**Paul to review STU FMM rationale and discuss with SGB
 
*Adjourned at 4:52 pm Eastern
 
  
 
===Next Steps===
 
===Next Steps===
Line 134: Line 114:
 
|-
 
|-
 
|colspan="4" |'''Next Meeting/Preliminary Agenda Items'''<br/>
 
|colspan="4" |'''Next Meeting/Preliminary Agenda Items'''<br/>
[[2017-09-06 FMG concall]]
+
[[2017-09-20 FMG concall]]
  
 
|}
 
|}

Latest revision as of 20:59, 6 September 2017

HL7 TSC FMG Meeting Minutes

Location:
https://global.gotomeeting.com/join/279790597

(voice and screen)

Date: 2017-09-06
Time: 4:00 PM U.S. Eastern
Chair: Note taker(s): Anne W.
Quorum = chair + 4 yes/no
Co chairs x David Hay x Lloyd McKenzie
ex-officio Lorraine Constable,
Dave Shaver
FGB Co-chairs
. Wayne Kubick, CTO
Members Members Members Observers/Guests
Hans Buitendijk x Brian Postlethwaite Paul Knapp x Anne W., scribe
x Josh Mandel x John Moehrke Brian Pech
Grahame Grieve x Richard Ettema, Chris Johnson

Agenda

  • Roll Call
  • Agenda Check
  • Minutes from 2017-08-30_FMG_concall
  • Action items
    • Lloyd to put together a draft template for IG proposals and clean up some of the profile proposal template
    • Lloyd to update on turning QA spreadsheet and corresponding wiki pages into WG assessment/reporting tool
    • Josh and Grahame to determine requirements for proposal to manage balloting on Github
    • Paul to take proposal on publishing ballot content on Github/other tools to TSC when available
    • Eric to nudge Lorraine/Claude to come to 2017-08-30 meeting for update on CatalogEntry
    • Anne to add FMG notes section proposal templates
      • Complete
    • Lloyd to discuss ServiceDefinition issues with Bryn
    • John to complete TestReport proposal
  • Discussion Topics
    • San Diego Agenda
  • Reports
  • Process management
  • AOB (Any Other Business)

Minutes

  • Roll Call
  • Agenda Check
    • MOTION to accept: Josh/Brian Post
  • Minutes from 2017-08-30_FMG_concall
    • MOTION to accept: John/Brian Post
    • VOTE: All in favor
  • Action items
    • Lloyd to put together a draft template for IG proposals and clean up some of the profile proposal template
      • Add for next week
    • Lloyd to update on turning QA spreadsheet and corresponding wiki pages into WG assessment/reporting tool
      • Add for next week
    • Josh and Grahame to determine requirements for proposal to manage balloting on Github
      • Add for next week
    • Paul to take proposal on publishing ballot content on Github/other tools to TSC when available
      • Add for next week
    • Eric to nudge Lorraine/Claude to come to 2017-08-30 meeting for update on CatalogEntry
      • Add for next week
    • Anne to add FMG notes section proposal templates
      • Complete
    • Lloyd to discuss ServiceDefinition issues with Bryn
      • Complete. They are looking at getting rid of it.
    • Richard to complete TestReport proposal
      • Richard made updates. Group Reviews. Still needs FHIR-I approval before FMG can approve it.
        • FHIR-I to review and bring back to FMG.
  • Discussion Topics
    • San Diego Agenda
  • FMG
    • Plan for draft for comment ballot in December
    • Connectathon recap
    • Github balloting proposal - brainstorm requirements, next steps. Lloyd notes that Jira may meet the intended outcome of this idea. Josh says it may do so. Josh asks if there is a list of requirements for Jira? Lloyd will be taking time at WG to talk to Karen/Mark regarding changes to fundamental ballot processes, like how block votes are handled, etc. to better allow voting directly using a tracker with no spreadsheets. Most obvious challenge with voting directly inside Github is it wouldn't be tied to HL7's membership database, and the right to vote is what you're paying for. TSC has been clear they want any voting solution to be the solution for all content, and all content won't live on Git. If we can come up with a pleasant way of linking pull requests to ballot items that are also change requests, then we might be able to meet the objective behind this proposal. Brian: One request is to use Github issues for tracking and the other is to use Github source control for the build. David: If we use Jira and Github, the comments could end up in two places. Lloyd: The desire of HL7 is that we use one mechanism for commenting, and they will likely want total control over that mechanism. Question is really - for the content that lives in Github, how easy is it to point people to Jira for comment submission, still integrating with the pull request mechanism of Git. Josh asks, from a governance perspective, what our balloting needs to accomplish. Lloyd: Our desire is to get read of spreadsheets. Will be writing up requirements prior to WGM. Could add integrating with pull request mechanism of Git. Josh: We want to know what it would take to do a small ballot in Github. Lloyd: The TSC's directive is that there is one balloting mechanism for everything for everyone. Decision to continue the discussion in person.
    • Jira evaluation/requirements
    • Connectathon management (David/Brian)
      • ACTION: David to create/post signup spreadsheet for Connectathon
    • FGB
      • Didn't meet this week
    • MnM –
      • Didn't meet this week
    • FMG Liaisons
      • No report
  • Adjourned at 4:50 pm


Next Steps

Actions (Include Owner, Action Item, and due date)
Next Meeting/Preliminary Agenda Items

2017-09-20 FMG concall


Back to FHIR_Management_Group

© 2017 Health Level Seven® International