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

2016 ARB Baltimore WGM

From HL7Wiki
Jump to navigation Jump to search
DRAFT - this agenda will be finalized on teleconferences

Agenda Sunday Q4 Joint with SGB

  1. Call to order
  2. Roll Call
  3. Approval of Agenda and Minutes
  4. Management
  5. Governance
  6. Methodology (60 minutes)
  7. Other business and planning
  8. Adjournment

Agenda Thursday Q3

  1. Call to order
  2. Roll Call
  3. Approval of Agenda and September 13, 2016 Minutes
  4. Management
  5. Governance
  6. Methodology (60 minutes)
  7. Other business and planning
  8. Adjournment

Report of Decisions made last cycle

  1. Decisions:
    • 20160531:
      • CIMI Proof of concept
        • Motion ARB be co-sponsor of the project, with periodic reports on progress what they are doing and where they are going.
        • Zoran: On this PSS only? Need to clarify "• Demonstrate relationship between information models and logically computable expressions"
        • Motion to table (Paul/Lorraine)
        • Vote' 7-0-0
    • 20160607:
      • CIMI Proof of concept
        • Motion ARB be co-sponsor of the project, with periodic reports on progress what they are doing and where they are going. To develop a better understanding how the CIMI artifacts integrate with the current products and families. (Lorraine/Paul)
        • Andy B: Need to look at how we integrate new work groups - need to discuss with TSC, PLA, and PIC.
        • Vote (4-0-0)
    • 20160614:
      • Discussed the ISM
    • 20160621:
      • Discussed the ISM
    • 20160628:
      • Discussed the ISM
    • 20160705:
    1. Discussed the ISM
      • Prepared PPT
    • 20160712:
    • 20160719:
      • Refined ISM
    • 20160726:
    • 20160802:
      • DAF Pss external content
        • DAF should belong to another committee.
        • Motion Arb agrees that the external content is appropriate. (Wayne/Paul)
        • Vote 3-0-0
    • 20160830:
      1. Mission and Charter Review
    1. Methodology
      • Definition of "Guidance" product
  2. A Guidance is a type of informative document that describes principles, best practices, and general advice but is not directly related to implementation of one or more specifications.
  3. MOTION to accept definition: Tony/Andy
  4. Discussion: Calvin asks if it's a sense that the definition precludes referencing any implementations or complete implementations? Tony: the idea is that it's not an implementation guide. Calvin: Could a guidance document apply to the writing of the standard? Or how you implement an aspect of a standard? Decision that these aspects don't change the definition. Discussion over whether past products would fall under this type.
    • 20160906:
      • Definition:
        • A Guidance document is a type of informative document that describes principles, best practices, and general advice but is not sufficient to achieve the conformant implementation of one or more standards.
        • Motion to accept the above(Andy S/Lorraine)
        • Vote (5-0-0)
    • 20160913: