20121003 TSC Risk Assessment call

From HL7 TSC
Revision as of 14:00, 3 October 2012 by Llaakso (talk | contribs) (→‎Next Steps)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

TSC Risk Assessment Task Force Agenda/Minutes

HL7 TSC TaskForce Meeting Minutes

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

Date: 2012-10-03
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 Charlie Mead x Calvin Beebe regrets Pat van Dyke
regrets Jane Curry x Ron Parker x Ed Tripp

Agenda

members to look at existing documents to evaluate risk.

  • Pat: GOM and balloting;
  • Ron on org process of GOM;
  • Calvin at SWOTs;
  • Austin at TSC P&P; Ed at SI;
  • Jane the harmonization process.

Supporting Documents

Minutes

Minutes/Conclusions Reached:

Convened by Austin at 9:07 AM EDT
members to look at existing documents to evaluate risk.

  • Pat: GOM and balloting;
  • Ron on org process of GOM;
  • Calvin at SWOTs;
  • Austin at TSC P&P;
  • Ed at SI;
  • Jane the harmonization process.

The group reviews Charlie's document. He reiterates you must review a risk profile on a regular basis, such as every (other) week, looking for trends. Trending implies you've tracked history of the risk items. Austin proposes we adopt this and start applying this to risk.

  • Calvin's document on SWOTs reveal need for facilitators; pulled text from SWOT's, codified, dated, internal or external, and then graphed. Concerns on facilitators, domain experts, time, etc.
    • Calvin cannot be on Monday's TSC call as he's teaching, but he'll clean up the graphic a bit for use in the TSC discussion.
  • Ed took the SI and used sub-bullets to identify risk areas in his document. He has not evaluated likelihood yet. How we implement SI may expose new risk in addition to the risk for which the SI are mitigation strategies already.
    • Austin thinks we need additional definition of the principal risk these SI were trying to mitigate. He notes he'll need to look again at his risks to identify implementation risks. Both lenses of perception are valuable.
  • Practice exercise in scoring assigned sets of risks during identification, and review as a group.
  • Austin created this document by grabbing process or policy ideas from the main page of the TSC wiki, of which many are repeated in the GOM. For example, he addressed each section of the Project Scope Statement to identify risks to be mitigated by the information requested.
    • Calvin notes that Work Group surveys, staff support surveys, WGM Effectiveness surveys that could be included in terms of the risks they are trying to mitigate.
    • Austin notes that Work Group Health measures as risk mitigation have several common risks and may reveal opportunities to consolidate them into one measure.
    • Austin will also take another pass at the risks in implementation of these processes/policies.
  • Ron's measures are not ready, Pat and Jane not available.
  • If we spend time on the TSC call Monday to address stepping through items already identified, maybe skip next week's meeting.
  • Each assignee start assessment in priority and criticality for review in two weeks.

Adjourned 9:49 AM EDT

Next Steps

Actions (Include Owner, Action Item, and due date)

members to look at existing documents to identify risks in their assigned areas, and draft evaluation of risk according to the Risk Management document.

  • Pat: GOM and balloting;
  • Ron on org process of GOM;
  • Calvin at SWOTs;
  • Austin at TSC P&P;
  • Ed at SI;
  • Jane the harmonization process.
Next Meeting/Preliminary Agenda Items


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