2018-09-26 SGB Conference Call

From HL7Wiki
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-09-26
Time: 10:00 AM Eastern
Facilitator Paul/Lorraine Note taker(s) Anne
Attendee Name


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

Agenda

  • Agenda review
  • Approve Minutes of 2018-09-19_SGB_Conference_Call
  • 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
    • Austin to craft slides with questions for the board
  • Discussion Topics
    • Continued discussion on Calvin's continuous maintenance document
    • 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

Minutes

  • Agenda review
  • Approve Minutes of 2018-09-19_SGB_Conference_Call
    • MOTION to approve: Austin/Calvin
    • 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
    • Austin to craft slides with questions for the board
      • Austin comments that our questions from last week were perhaps too broad for the board. Also going back to the board about their motion for TSC to streamline standards; intention is unclear.
    • Calvin: When we look at the existing base of standards, they’re trying to figure out what we put money into for tooling to support the standards. Paul: So we’re talking about the machinery to support the development, management, publication of the standards. Discussion over quota solution. Austin: If they want to see fewer standards, I don’t see how to do that other than throttling in some fashion, whether because of a quota system, or we say your project will move forward when the membership selects the project to move forward in a ballot cycle. If it’s about the technical artifacts, there is going to be a massive fight.
    • Paul: Trying to understand the cost that’s incurred by having artifacts that we are unaware that people are using. Calvin: If we’re going to plan, we need to understand the intent of reduction. It’s really about where to you apply limited resources. Austin: If we’re going to reduce, we’ve got to stop doing so many projects – and how do you choose?
    • Paul: There’s a notion of limited resources, but not hearing anyone say that we have more work to do than we can afford to do. Calvin: That’s pretty clear, though, looking at the budget of the tooling plan. Paul: So the board needs to better articulate what the value is that we as an SDO provide to the membership. Need to be cautious on how we frame the question so they don’t end up making methodological questions.
    • Calvin: We have a challenge of key people not understanding the basic behavior or the industry and how it works, and the message that would send to the market. But we are a very limited resource group. There is going to have to be some rationalization.
    • Discussion over V3 issues. Could compel people into funding things to prevent them from going away. Paul: How much money will we save if we lose members because of that? Calvin: So what is the range of costs we’re trying to reduce is something we need to determine.
    • Austin: HL7 as a financial organization has been bleeding to death. It’s not massive bleeding, but it’s a slow trickle of money just leaving. Calvin: Our cost of living increase is almost compensating for the bleed. Austin: Increases could also drive members to drop.
    • Calvin: So is the board asking for a plan that determines where resources go, a pruning of what are considered unused standard – or whole families? Paul: A fallow field doesn’t cost anything. Need to have some understanding of the stuff vs. the costs.
    • Austin departs
    • Management groups have been analyzing their catalog of standards.
  • Carry forward:
    • Continued discussion on Calvin's continuous maintenance document
    • 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

Meeting Outcomes

Actions
Next Meeting/Preliminary Agenda Items

© 2018 Health Level Seven® International. All rights reserved