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

2018-04-11 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: 2017-MM-DD
Time: 10:00 AM Eastern
Facilitator Lorraine Note taker(s) Anne
Attendee Name


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

Agenda

  • Agenda review
  • Approve Minutes of 2018-04-04_SGB_Conference_Call
  • Action Items
    • Paul waiting to hear back from Vocab and PA re: approval of items balloting at STU in FHIR R3
      • Will then verify with Karen that the documentation on the FHIR R3 ballot STU approvals is sufficient
    • Tony to put ISM information Confluence/Calvin to make some examples of how to use the ISM using CDA
    • Anne to work on adding links on precepts page to approval minutes for each precept
      • Ongoing
    • Anne to add "role of architecture in standards development process" to TSC agenda in Cologne
    • Anne to send out V2MG M&C to TSC e-vote with any needed discussion on Monday
      • Complete. TSC requested that SGB review the boilerplate for necessary adjustments
    • Anne to draft V2MG invitation email and send to SGB for review
      • Complete
  • Discussion Topics
    • Look at definitions of each activity in step 1 of the BAM and boil them down into a task list
    • Normative balloting/continuous balloting in FHIR
    • Review FHIR artifact governance process
    • Review of project 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?
    • Precepts We Need to Develop
  • Parking Lot
    • 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
    • Add Cologne planning
  • Approve Minutes of 2018-04-04_SGB_Conference_Call
    • MOTION to approve: Wayne/Thom
    • VOTE: All in favor
  • Action Items
    • Paul waiting to hear back from Vocab and PA re: approval of items balloting at STU in FHIR R3
      • Will then verify with Karen that the documentation on the FHIR R3 ballot STU approvals is sufficient
        • Carry forward
    • Tony to put ISM information on Confluence/Calvin to make some examples of how to use the ISM using CDA
      • Complete
    • Anne to work on adding links on precepts page to approval minutes for each precept
      • Ongoing
    • Anne to add "role of architecture in standards development process" to TSC agenda in Cologne
    • Anne to send out V2MG M&C to TSC e-vote with any needed discussion on Monday
      • Complete. TSC requested that SGB review the boilerplate for necessary adjustments
        • ACTION: Anne to clean up using Tony's comments and send back for review
    • Anne to draft V2MG invitation email and send to SGB for review
      • Reviewed draft and made edits.
        • MOTION to approve: Wayne/Thom
          • Anne to send to Andrea/Pat for distribution and check on schedule - due date 3 weeks from send date (no later than the 10th of May)
      • VOTE: All in favor
      • Complete
  • Discussion Topics
    • Look at definitions of each activity in step 1 of the BAM and boil them down into a task list
      • Reviewed 1.1.8, Create Product Concept Proposal. Who is the "HL7" referenced in "For the initial evaluation by HL7?" Discussion over when this would be applied. Intent was for this to be used for new product families, and it might be appropriate to apply to new methodology. Anything large and new, such as big cross cutting models. Will have to come up with criteria for when it's applied. For things that are cross-cutting or huge, what other players need to be involved? Lorraine notes some things are now going through product family management groups; perhaps the product family management council will be where these things are first considered. Group agrees that would be a good place for initial discussion and recommendation, although that is management not methodology. Need to get at it before too much work has been done.
      • 1.1.9: Review Product Concept Proposal. Product director could mean Wayne if there is not one. Calvin notes that, at one time, we had a strategy for innovation (predated FHIR).
      • Discussion over lack of consistency in datatypes. Are these assessments going to be plugged into our vocabulary standards or datatype mapping? Lorraine notes that should be part of 1.1.11, organizational readiness assessment.
      • Next step would be to create a simpler checklist. Could use the RDAM as something to use to create the steps.
      • Discussion over the three large projects currently coming in and conflicting priorities. Need to develop decision making process to avoid areas of division. Need to justify the business case of "why?"
      • The difficulties around this are strategic, tactical, and cultural. What is our focus? Do we want to allow anybody to come in to HL7 and do anything they want, or do we want to maintain our focus on our stated vision? How many models do we need? What about external work that people are trying to bring under the tent?
      • Calvin: If we could formulate 3-5 questions that are tough questions for us to tackle as an organization for a conversation with the Board, that could help spur some initial high-level conversation. Wayne: We need to articulate a clear problem statement for the board.
        • ACTION: Lorraine to add an SGB page to Confluence where SGB can work on this task
      • Calvin: Perhaps each of these initiatives should have its own page on Confluence for organizational review. Thom notes that so many groups don't know the processes and rules, and we need someone with knowledge to go in and educate as Lorraine often does.
  • Carry forward:
    • Normative balloting/continuous balloting in FHIR
    • Review FHIR artifact governance process
    • Review of project 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?
    • Precepts We Need to Develop
  • Adjourned at 11:03 am Eastern

Meeting Outcomes

Actions
Next Meeting/Preliminary Agenda Items

© 2018 Health Level Seven® International. All rights reserved