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

2018-10-17 SGB Conference Call

From HL7Wiki
Revision as of 15:08, 23 October 2018 by Annewiz (talk | contribs)
Jump to navigation Jump to search

back to Standards Governance Board main page

HL7 SGB Minutes

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

Date: 2018-10-17
Time: 10:00 AM Eastern
Facilitator Paul/Lorraine Note taker(s) Anne
Attendee Name


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

Agenda

  • Agenda review
  • Approve Minutes of 2018-09-26_SGB_Conference_Call
  • Approve Minutes of 2018-09-30_SGB_WGM_Agenda
  • Approve Minutes of 2018-10-05_SGB_WGM_Agenda
  • Action Items
    • Paul to contact Vocab/PA re: approval items balloting at STU in FHIR R3
      • Will then verify with Karen that the documentation on the FHIR R3 ballot STU approvals is sufficient
    • Paul to ask PH for clarification on the status of items taken out of tracker and then reconciled on spreadsheet/ask for a plan for addressing the issue
    • Paul to draft precept on artifact governance
    • Ask US Realm to consider recommending to Project Services another realm category for items that are US Realm but intended to be universal in the future
    • Wayne to reach out to Argonaut project leads re: Argonaut diagnostic report development
    • Paul to write up our current continuous maintenance process for review
    • Forward Karen our list of continuous maintenance questions
    • Talk with FMG regarding what they want to accomplish with continuous maintenance to see if it fits
    • Anne to work with Josh to set up SGB page to communicate decisions/precepts by January
    • Anne to add TSC proposed actions around tooling to upcoming call
    • Anne to add link to ARB Confluence page with SGB content to SGB page
    • Anne to research if product management life cycle spec was approved by TSC and add to agenda to discuss dissemination
  • Discussion Topics
    • Currency of Value Set Content - from HTA
    • Continued discussion: Tasks in step 1 of the BAM
    • SGB Communication Plan
    • Large architectures coming in:
      • Evaluate PSS process to potentially provide earlier visibility
      • How should a product family-type project be documented and reviewed - is PSS enough?
      • When it affects cross-organizational methodology, PFMGs need to have a review/say - potential precept
    • Updates that we do to newer versions of FHIR that are also applicable to older versions
    • Precepts We Need to Develop
  • Parking Lot
    • Mapping coordination
    • Add link to Confluence page from ARB page
    • Review of product management life cycle spec to see if it talks about project and ballot scope
    • Review of MG responses to SGB query on substantive change
    • Need to make sure that SGB is accurately reflected in the GOM, and figure out what precepts should appear in the GOM
    • Review Mission and Charter
    • Drafting Shared Product Management Responsibilities
    • Technical Alignments Between Product Families
    • How groups are to interact with publishing, EST, Vocabulary, etc.
    • Precept on bringing in large projects
    • Vocabulary - review HTA material for precepts
    • Precept for adding new tools (include that WGs with a specific mandate must be involved, such as EST, Publishing, Vocabulary, etc.) - was this covered by the tooling precept we created in New Orleans?
    • BAM guidance on process for product adoption
    • Create PRECEPTS that require that it be articulated in the standards how the value sets specified within the standards respond to changes in regulation, licensing, time, etc.- to do in April/before Cologne
    • FHIR Product Director Position Description: we should 1) review further and draft feedback, then 2) map back the description to the role of FGB
    • Ownership of content
    • What precepts do we need to address PSS/profile approval processes of balloting and publishing potentially thousands of CIMI model?

Minutes

  • Agenda review
  • Approve Minutes of 2018-09-26_SGB_Conference_Call
    • MOTION to approve: Lorraine/Thom
    • VOTE: All in favor
  • Approve Minutes of [2018-09-30_SGB_WGM_Agenda]]
    • MOTION to approve: Lorraine/Austin
    • VOTE: All in favor
  • Approve Minutes of 2018-10-05_SGB_WGM_Agenda
    • MOTION to approve: Lorraine/Thom
    • VOTE: All in favor
  • Action Items
    • Paul to contact Vocab/PA re: approval items balloting at STU in FHIR R3
      • Will then verify with Karen that the documentation on the FHIR R3 ballot STU approvals is sufficient
    • Paul to ask PH for clarification on the status of items taken out of tracker and then reconciled on spreadsheet/ask for a plan for addressing the issue
    • Paul to draft precept on artifact governance
    • Ask US Realm to consider recommending to Project Services another realm category for items that are US Realm but intended to be universal in the future
    • Wayne to reach out to Argonaut project leads re: Argonaut diagnostic report development
    • Paul to write up our current continuous maintenance process for review
    • Forward Karen our list of continuous maintenance questions
    • Talk with FMG regarding what they want to accomplish with continuous maintenance to see if it fits
    • Anne to work with Josh to set up SGB page to communicate decisions/precepts by January
    • Anne to add TSC proposed actions around tooling to upcoming call
    • Anne to add link to ARB Confluence page with SGB content to SGB page
    • Anne to research if product management life cycle spec was approved by TSC and add to agenda to discuss dissemination
  • Discussion Topics
    • Austin: The board is not going to give us clear direction on creating a set of agile standards. It’s in our hands to figure out what we’re going to do without damaging the organization.
    • Currency of Value Set Content - from HTA
      • Couple of problems. Almost entirely focused on SNOMED and only seems to apply to normative documents. HTA asked for TSC review and approval, and TSC sent review to us. Needs clarity on how it applies to other value sets and non-normative content.
      • Thom: It seems reasonable but needs some minor tweaks. When we publish expansions they could be marked as informative. Wayne: This came up because the SNOMED agreement expressly instructs us to use the latest version when we ballot standards. But this needs to be simplified and implies we’re going to reballot every five years as opposed to reaffirm. Need to get clear guidance out to work groups.
      • Added questions from SGB to the document
    • Continued discussion: Tasks in step 1 of the BAM
      • Complete
    • SGB Communication Plan
    • Large architectures coming in:
      • Evaluate PSS process to potentially provide earlier visibility
      • How should a product family-type project be documented and reviewed - is PSS enough?
      • When it affects cross-organizational methodology, PFMGs need to have a review/say - potential precept
        • Complete
    • Updates that we do to newer versions of FHIR that are also applicable to older versions
      • Carry forward
    • Precepts We Need to Develop
      • Carry forward
  • Adjourned at 11:02 am Eastern


Meeting Outcomes

Actions
Next Meeting/Preliminary Agenda Items

© 2018 Health Level Seven® International. All rights reserved