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

Difference between revisions of "2016 ARB Baltimore WGM"

From HL7Wiki
Jump to navigation Jump to search
Line 18: Line 18:
 
#Roll Call
 
#Roll Call
 
#Approval of Agenda and [[20160913_arb_minutes| September 13, 2016 Minutes]]
 
#Approval of Agenda and [[20160913_arb_minutes| September 13, 2016 Minutes]]
 +
#Methodology (60 minutes)
 +
#*[http://gforge.hl7.org/gf/project/arbgeneral/scmsvn/?action=browse&path=%2F%2Acheckout%2A%2Ftrunk%2FHL7%2520PSS%2520ODH%2520Elements%2520in%2520v2%2520and%2520FHIR%2520091316.docx Occupational Data for Health Elements and Structure in HL7 V2 Messaging and FHIR]
 
#Management
 
#Management
 
#*Decision review:
 
#*Decision review:
Line 25: Line 27:
 
#*Wrap-up from WGM
 
#*Wrap-up from WGM
 
#Governance
 
#Governance
#Methodology (60 minutes)
+
 
#*[http://gforge.hl7.org/gf/project/arbgeneral/scmsvn/?action=browse&path=%2F%2Acheckout%2A%2Ftrunk%2FHL7%2520PSS%2520ODH%2520Elements%2520in%2520v2%2520and%2520FHIR%2520091316.docx Occupational Data for Health Elements and Structure in HL7 V2 Messaging and FHIR]
 
#*TBD
 
#*TBD
 
 
#Other business and planning
 
#Other business and planning
 
#Adjournment
 
#Adjournment
 +
 
==Report of Decisions made last cycle==
 
==Report of Decisions made last cycle==
 
#*[[20160531_arb_minutes | May 31, 2016]]
 
#*[[20160531_arb_minutes | May 31, 2016]]

Revision as of 18:01, 14 September 2016

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. Methodology (60 minutes)
  5. Management
  6. Governance
  1. Other business and planning
  2. Adjournment

Report of Decisions made last cycle

    • May 31, 2016
      • 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
    • June 7, 2016
      • 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)
    • June 14, 2016,June 21, 2016, June 28, 2016,July 5, 2016
      • Discussed the ISM
      • Prepared ISM PPT
    • July 12, 2016
    • July 19,2016
      • Refined ISM
    • July 26, 2016
    • August 2, 2016
      • 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
    • August 16, 2016
      • ARB suggested the following draft definition for “Guidance” Product Type: - Tony
        • 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.
          • MOTION to accept definition: Tony/Andy
          • 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.
          • MOTION to table the motion until next week: Lorraine/Paul
    • August 23, 2016
      • Reviewed Mission and charter
      • Review Technical Architecture
    • August 30, 2016
      • Mission and Charter Review
      • Definition of "Guidance" product
        • 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.
      • MOTION to accept definition: Tony/Andy
      • 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.
      • Tabled due to exhaustion
    • September 6, 2016
    • Guidance Document 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)
    • September 13, 2016

Works in progress

  1. Mission and Charter
    • Review after discussing goals
  2. Decision Making practices
    • Second vote as required by the DMP for revisions
  3. Substantivity
  4. BAM
    • Where do we go from here?
    • We started sunset, were going to review with PIC, but circumstances overcame