Difference between revisions of "20121114 TSC Risk Assessment call"

From HL7 TSC
Jump to navigation Jump to search
(Created page with '{{subst::20121107 TSC Risk Assessment call}}')
 
 
(One intermediate revision by the same user not shown)
Line 7: Line 7:
 
| width="0%" colspan="2" align="left" style="background:#f0f0f0;"|'''HL7 TSC Meeting Minutes''' <br/>
 
| width="0%" colspan="2" align="left" style="background:#f0f0f0;"|'''HL7 TSC Meeting Minutes''' <br/>
 
'''Location: call 770-657-9270 using code 985371#'''<br/> GoToMeeting ID: [https://www2.gotomeeting.com/join/998903490 998-903-490]
 
'''Location: call 770-657-9270 using code 985371#'''<br/> GoToMeeting ID: [https://www2.gotomeeting.com/join/998903490 998-903-490]
| width="0%" colspan="1" align="left" style="background:#f0f0f0;"|'''Date: 2012-11-07 '''<br/> '''Time: 9:00 AM U.S. Eastern'''
+
| width="0%" colspan="1" align="left" style="background:#f0f0f0;"|'''Date: 2012-11-14 '''<br/> '''Time: 9:00 AM U.S. Eastern'''
 
|-
 
|-
 
| width="0%" colspan="2" align="right"|'''Facilitator''': Austin Kreisler
 
| width="0%" colspan="2" align="right"|'''Facilitator''': Austin Kreisler
Line 20: Line 20:
 
|colspan="2"|Facilitators ||colspan="2"|ArB ||colspan="2"|Members||colspan="2"|Members
 
|colspan="2"|Facilitators ||colspan="2"|ArB ||colspan="2"|Members||colspan="2"|Members
 
|-
 
|-
|x||Austin Kreisler||resigned||Charlie Mead||regrets||Calvin Beebe||x||Pat van Dyke
+
|x ||Austin Kreisler||x|| Calvin Beebe || || Pat van Dyke
 
|-
 
|-
|x||Jane Curry ||resigned||Ron Parker||x||Ed Tripp||
+
|x ||Jane Curry ||x || Ed Tripp || || ||
 
|}
 
|}
 
===Agenda===
 
===Agenda===
*Review the [http://gforge.hl7.org/gf/download/docmanfileversion/7056/9840/BallotRisks_Strengths.xlsx Ballot risks spreadsheet] from Pat, on Chapter 13 of the GOM.
+
*Review the Ballot risks spreadsheet from Pat, on Chapter 14-16 of the GOM.
*Review the [http://gforge.hl7.org/gf/download/docmanfileversion/7053/9836/GOMSectionsforRiskAnalysis.xls GOM sections spreadsheet]
+
*Continue Review [http://gforge.hl7.org/gf/download/docmanfileversion/7054/9837/ConsolidatedRiskAssessment.xlsx Consolidated risk assessment spreadsheet]
*Review [http://gforge.hl7.org/gf/download/docmanfileversion/7054/9837/ConsolidatedRiskAssessment.xlsx Consolidated risk assessment spreadsheet]
 
  
  
Line 33: Line 32:
 
*See links
 
*See links
 
===Minutes===
 
===Minutes===
'''Minutes/Conclusions Reached:'''<br/>
+
*Review the Ballot risks spreadsheet from Pat, on Chapter 14-16 of the GOM. - Pat is not available.
*Review the [http://gforge.hl7.org/gf/download/docmanfileversion/7056/9840/BallotRisks_Strengths.xlsx Ballot risks spreadsheet]
+
*Continue Review [http://gforge.hl7.org/gf/download/docmanfileversion/7054/9837/ConsolidatedRiskAssessment.xlsx Consolidated risk assessment spreadsheet]
**Pat reviews risks from Chapter 13 of the GOM. She still is planning to review sections 14 and 15.
+
**Review of where left off last week
**No comments on the ANSI technical report registration process
+
**TSC Policy, Project Approval Process, Poor communication with ANSI addressed last week
**Mitigation of risks related to lack of US Affiliate
+
**SI2.1.3 Global adoption increased split into two - that version is not available; will update
**May want to capture the reason for the GOM in the first place, to separate out procedural details from the bylaws. Allows incremental change without full membership ballot. Risk also that lack of update results in actual procedures differing from those documented in bylaws. Key risk is the ANSI audit that finds we are not following our processes. Now we've created a bureaucratic framework that is slow when we need to be nimble.
+
**Next is SI2.1.5 Key stakeholder groups - two sets: members, internal to HL7; and stakeholders outside of HL7 who are not members are an external problem. It's not as critical as Austin feels our focus needs to be on providing value to our members. Value of HL7 membership is to get members' requirements into the HL7 standards. Divide this one into two. Mitigation for nonmembers is to communicate to them that their membership would allow their requirements to take priority within standards development.
*Review the [http://gforge.hl7.org/gf/download/docmanfileversion/7053/9836/GOMSectionsforRiskAnalysis.xls GOM sections spreadsheet]
+
**SI 2.2 streamline process, speed to develop. Jane notes that not everyone understands what the process is. Using too stringent a reconciliation process is one problem they face. Others feel their negative comments are steamrolled in the reconciliation process as declared not persuasive, as a Social-Political type. Austin suggests we have the technology to run the steamroller. Do we need to tease this into other entries? Three dimensions, including education which is under Resources. V3 artifact development and publication/balloting process is a technical exercise understood by a handful of people, and resource intensive. Technical development of the standard break out as resource type. Balloting is second item as social political type
**Austin reviewed which sections are not under the TSC purview and solicited volunteers for other sections
+
**Continued discussion resulted in identifying internal risks as those of focus and may have to group all the external risks to address their impact on the organization. Set impact to low.
*Review [http://gforge.hl7.org/gf/download/docmanfileversion/7054/9837/ConsolidatedRiskAssessment.xlsx Consolidated risk assessment spreadsheet]
 
**Focus on those risks deemed critical and high likelihood. Five of the 10 in focus are resource-related.
 
**Communication with ANSI regarding standards under development - both communications and process related. Should be documented as two different risks. One can be Policy and Process differences between HL7 and ANSI.
 
**Need to understand the rationale for why we have a process in place. We're trying to recover the documentation of the rationale but need to keep in mind the big picture level as we consider requirements, notes Jane.  
 
**Austin views the charge of this task force is to identify and surface the risks but not to begin addressing the mitigation directly.
 
**Risk to global adoption: inability to simplify implementation prevents global adoption (SI 2.1.3, 2.3.2). 2.x space isn't so much the risk of adoption but standardization in implementation. V2 was syntactic interoperability rather than semantic. CDA is much more successful. May not be solely a technology problem. FHIR is addressing it as a technology problem, rather than requirements. CDA uses an engineering model to break problem into smaller pieces. FHIR keeps simple things, simple; reduces problem space. Is the mitigation through technology?
 
  
 +
Being at time, adjourned at 9:59 AM
  
Adjounred 10:07 AM EST
 
 
===Next Steps===
 
===Next Steps===
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  
Line 57: Line 50:
 
|-
 
|-
 
|colspan="4" |'''Next Meeting/Preliminary Agenda Items'''<br/>
 
|colspan="4" |'''Next Meeting/Preliminary Agenda Items'''<br/>
*[[20121114 TSC Risk Assessment call]].
+
*[[20121121 TSC Risk Assessment call]].
 +
*Continue reviewing critical impact risks from updated spreadsheet at http://gforge.hl7.org/gf/download/docmanfileversion/7069/9859/ConsolidatedRiskAssessment20121114.xlsx
 +
 
 
|}
 
|}
  
  
 
© 2012 Health Level Seven® International.  All rights reserved.
 
© 2012 Health Level Seven® International.  All rights reserved.

Latest revision as of 15:05, 14 November 2012

TSC Risk Assessment Task Force Agenda/Minutes

HL7 TSC Meeting Minutes

Location: call 770-657-9270 using code 985371#
GoToMeeting ID: 998-903-490

Date: 2012-11-14
Time: 9:00 AM U.S. Eastern
Facilitator: Austin Kreisler Note taker(s): Lynn Laakso
Quorum n/a
Facilitators ArB Members Members
x Austin Kreisler x Calvin Beebe Pat van Dyke
x Jane Curry x Ed Tripp

Agenda


Supporting Documents

  • See links

Minutes

  • Review the Ballot risks spreadsheet from Pat, on Chapter 14-16 of the GOM. - Pat is not available.
  • Continue Review Consolidated risk assessment spreadsheet
    • Review of where left off last week
    • TSC Policy, Project Approval Process, Poor communication with ANSI addressed last week
    • SI2.1.3 Global adoption increased split into two - that version is not available; will update
    • Next is SI2.1.5 Key stakeholder groups - two sets: members, internal to HL7; and stakeholders outside of HL7 who are not members are an external problem. It's not as critical as Austin feels our focus needs to be on providing value to our members. Value of HL7 membership is to get members' requirements into the HL7 standards. Divide this one into two. Mitigation for nonmembers is to communicate to them that their membership would allow their requirements to take priority within standards development.
    • SI 2.2 streamline process, speed to develop. Jane notes that not everyone understands what the process is. Using too stringent a reconciliation process is one problem they face. Others feel their negative comments are steamrolled in the reconciliation process as declared not persuasive, as a Social-Political type. Austin suggests we have the technology to run the steamroller. Do we need to tease this into other entries? Three dimensions, including education which is under Resources. V3 artifact development and publication/balloting process is a technical exercise understood by a handful of people, and resource intensive. Technical development of the standard break out as resource type. Balloting is second item as social political type
    • Continued discussion resulted in identifying internal risks as those of focus and may have to group all the external risks to address their impact on the organization. Set impact to low.

Being at time, adjourned at 9:59 AM

Next Steps

Actions (Include Owner, Action Item, and due date)
  • .
Next Meeting/Preliminary Agenda Items


© 2012 Health Level Seven® International. All rights reserved.