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

Difference between revisions of "2017-10-25 SGB Conference Call"

From HL7Wiki
Jump to navigation Jump to search
Line 76: Line 76:
 
===Agenda===
 
===Agenda===
 
*Agenda review
 
*Agenda review
−
*Approve Minutes of [[2017-MM-DD_SGB_Conference_Call]]
+
*Approve Minutes of [[2017-10-18_SGB_Conference_Call]]
 
*Action Items
 
*Action Items
 +
**Review GOM with respect to where SGB and precepts should be reflected
 +
**Recommend to TSC to work with CTO on architecture and tooling strategy to support the work of the committees in following the precepts
 +
**Ask Vocab to approve a motion that it was the WG’s intention in R3 for the Expansion profile to be balloted as STU. If PA has not documented approval, send them the same message
 +
**Paul to verify with Karen that the documentation on the FHIR R3 ballot STU approvals is sufficient
 
*Discussion Topics
 
*Discussion Topics
 +
**Conversation with EST regarding precepts around adding new tools.
 +
**Finish review of mixed ballot content precept
 +
**Precept implementation strategy
 +
**Backwards compatibility consistency and definition across families
 +
*Precepts to Develop:
 +
**SGB to produce a precept requiring that, in order to publish a specification, it has to be conformant to any harmonization patterns that HL7 has published
 +
**State Machine Alignment
 +
**How groups are to interact with Publishing, EST, Vocabulary, etc. WGs
 +
**Engaging the implementer community in the consideration of changes as artifacts mature
 +
**Engagement in large cross-organizational projects
 +
**How management groups document, enforce, and manage the precepts regarding inter-WG participation in artifact creation
 +
**Management groups must establish in writing a refinement of examples that adhere to the definition of substantive change that apply to their product family. Must monitor, audit, and measure conformance to the definition of substantive change.
 +
**The addition of new tools (with EST)
 +
**Managing unresponsive parties in PSS approval process
 +
**Vocabulary
 +
**Training WGs in CDA methodology and management principles
 +
**Vitality Assessment
 
*Parking Lot
 
*Parking Lot
 +
**Review Publishing M&C updates regarding dual roles
 +
**How do we deal with making sure that WGs involve those whose content domain they’re touching? (CIMI and Pharmacy and Lab models)
 +
**Review Mission and Charter
 +
**Handling situations where two documents come out of one project
 +
**[http://wiki.hl7.org/index.php?title=FHIR_Product_Director_Page FHIR Product Director Position Description]: we should 1) review further and draft feedback, then 2) map back the description to the role of FGB
 +
**Drafting Shared Product Management Responsibilities
 +
**Levels of standards
 +
**Separation of concerns
 +
**Ownership of content
 +
**ISM
 +
**Ask methodology groups to define how the definition of substantive change applies to their product family; management groups must then operationalize
  
 
===Minutes===
 
===Minutes===
Line 113: Line 145:
  
 
|width="100%" |'''Next Meeting/Preliminary Agenda Items'''<br/>
 
|width="100%" |'''Next Meeting/Preliminary Agenda Items'''<br/>
−
*[[2017mmdd SGB Conference Call]]
+
*[[2017-11-01 SGB Conference Call]]
  
 
|}
 
|}
  
 
© 2017 Health Level Seven® International.  All rights reserved
 
© 2017 Health Level Seven® International.  All rights reserved

Revision as of 18:21, 24 October 2017

back to Standards Governance Board main page

HL7 SGB Minutes

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

Date: 2017-MM-DD
Time: 10:00 AM Eastern
Facilitator Paul/Calvin Note taker(s) Anne
Attendee Name


Calvin Beebe
Lorraine Constable
Russ Hamm
Tony Julian
Paul Knapp
Austin Kreisler
Wayne Kubick
Thom Kuhn
Ken McCaslin
Rik Smithies
Sandy Stuart
Quorum: Chair + 4

Agenda

  • Agenda review
  • Approve Minutes of 2017-10-18_SGB_Conference_Call
  • Action Items
    • Review GOM with respect to where SGB and precepts should be reflected
    • Recommend to TSC to work with CTO on architecture and tooling strategy to support the work of the committees in following the precepts
    • Ask Vocab to approve a motion that it was the WG’s intention in R3 for the Expansion profile to be balloted as STU. If PA has not documented approval, send them the same message
    • Paul to verify with Karen that the documentation on the FHIR R3 ballot STU approvals is sufficient
  • Discussion Topics
    • Conversation with EST regarding precepts around adding new tools.
    • Finish review of mixed ballot content precept
    • Precept implementation strategy
    • Backwards compatibility consistency and definition across families
  • Precepts to Develop:
    • SGB to produce a precept requiring that, in order to publish a specification, it has to be conformant to any harmonization patterns that HL7 has published
    • State Machine Alignment
    • How groups are to interact with Publishing, EST, Vocabulary, etc. WGs
    • Engaging the implementer community in the consideration of changes as artifacts mature
    • Engagement in large cross-organizational projects
    • How management groups document, enforce, and manage the precepts regarding inter-WG participation in artifact creation
    • Management groups must establish in writing a refinement of examples that adhere to the definition of substantive change that apply to their product family. Must monitor, audit, and measure conformance to the definition of substantive change.
    • The addition of new tools (with EST)
    • Managing unresponsive parties in PSS approval process
    • Vocabulary
    • Training WGs in CDA methodology and management principles
    • Vitality Assessment
  • Parking Lot
    • Review Publishing M&C updates regarding dual roles
    • How do we deal with making sure that WGs involve those whose content domain they’re touching? (CIMI and Pharmacy and Lab models)
    • Review Mission and Charter
    • Handling situations where two documents come out of one project
    • FHIR Product Director Position Description: we should 1) review further and draft feedback, then 2) map back the description to the role of FGB
    • Drafting Shared Product Management Responsibilities
    • Levels of standards
    • Separation of concerns
    • Ownership of content
    • ISM
    • Ask methodology groups to define how the definition of substantive change applies to their product family; management groups must then operationalize

Minutes

Meeting Outcomes

Actions
Next Meeting/Preliminary Agenda Items

© 2017 Health Level Seven® International. All rights reserved

Retrieved from "https://wiki.hl7.org/w/index.php?title=2017-10-25_SGB_Conference_Call&oldid=148073"