Difference between revisions of "2013-04-17 TRAC"
Jump to navigation
Jump to search
m |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
==TSC Risk Assessment Committee (TRAC) Agenda/Minutes == | ==TSC Risk Assessment Committee (TRAC) Agenda/Minutes == | ||
back to [[TRAC|TRAC page]] | back to [[TRAC|TRAC page]] | ||
| Line 23: | Line 22: | ||
|colspan="2"|Chair/CTO ||colspan="2"|Members ||colspan="2"|Members | |colspan="2"|Chair/CTO ||colspan="2"|Members ||colspan="2"|Members | ||
|- | |- | ||
| − | | ||Pat Van Dyke|| | + | |x ||Pat Van Dyke||x||Rick Haddorff||regrets ||Melva Peters |
|- | |- | ||
| − | | | + | |x||John Quinn ||x ||Austin Kreisler||.||| |
|- | |- | ||
| Line 33: | Line 32: | ||
*Agenda review and approval - Pat Van Dyke | *Agenda review and approval - Pat Van Dyke | ||
*Review minutes of [[2013-04-10 TRAC]] | *Review minutes of [[2013-04-10 TRAC]] | ||
| − | * | + | *Continue [http://gforge.hl7.org/gf/download/docmanfileversion/7284/10311/ConsolidatedRiskAssessment20130410.xlsx risk assessment review] (GOM) |
| − | **What areas where review | + | **What areas where review have not been submitted or reviewed |
***Set review schedule for known sources of risk | ***Set review schedule for known sources of risk | ||
***Plan for review of GOM on regular basis | ***Plan for review of GOM on regular basis | ||
| Line 40: | Line 39: | ||
*Areas submitted where review still needs to occur | *Areas submitted where review still needs to occur | ||
**Check with Jane on GOM Section 16 Risks | **Check with Jane on GOM Section 16 Risks | ||
| − | ** T3F Strategic Initiative TSC Self Assessment [http://lists.hl7.org/read/attachment/223431/2/T3F_Assessment_survey_results20121024.pdf results] (See [http://gforge.hl7.org/gf/download/docmanfileversion/7262/10203/Survey_30497710.pdf Original survey]) - review red and yellow against existing risk items; if there isn't one then develop new risk items. | + | ** T3F Strategic Initiative TSC Self Assessment [http://lists.hl7.org/read/attachment/223431/2/T3F_Assessment_survey_results20121024.pdf results] (See [http://gforge.hl7.org/gf/download/docmanfileversion/7262/10203/Survey_30497710.pdf Original survey]) - review red and yellow against existing risk items; if there isn't one then develop new risk items. |
| − | |||
| − | |||
*How to address "issues" | *How to address "issues" | ||
| Line 49: | Line 46: | ||
===Minutes=== | ===Minutes=== | ||
'''Minutes/Conclusions Reached:'''<br/> | '''Minutes/Conclusions Reached:'''<br/> | ||
| + | *Continue [http://gforge.hl7.org/gf/download/docmanfileversion/7284/10311/ConsolidatedRiskAssessment20130410.xlsx risk assessment review] (GOM) | ||
| + | **Pat notes that with the ANSI/GOM Review Task Force meeting yesterday she identified that a GOM risk review would need to be conducted on changes to the GOM. | ||
| + | **One year reconciliation deadline for informatives discussed. It is not addressed by AAWI0005 which is for normative only. May require GOM change to have review ballots on same timelines as normative. May need to incorporate into a governance point or a precept that internal processes should be consistent. | ||
| + | **Do we look at mitigation for critical first or serious ones next. Un-filtering reveals additional critical impact but less than high likelihood. Look at remaining critical risks next week and then collect a report of issues for TSC. | ||
| + | **John will be at ISO meeting next week but will join as connectivity permits. | ||
| + | Adjourned 11:00 AM | ||
===Next Steps=== | ===Next Steps=== | ||
| Line 55: | Line 58: | ||
|- | |- | ||
|colspan="4" |'''Actions''' ''(Include Owner, Action Item, and due date)''<br/> | |colspan="4" |'''Actions''' ''(Include Owner, Action Item, and due date)''<br/> | ||
| − | * . | + | *Austin will look in the ECCF for the correct wording on risk id 43. |
|- | |- | ||
|colspan="4" |'''Next Meeting/Preliminary Agenda Items'''<br/> | |colspan="4" |'''Next Meeting/Preliminary Agenda Items'''<br/> | ||
*[[2013-04-24 TRAC]]. | *[[2013-04-24 TRAC]]. | ||
| + | *continue [http://gforge.hl7.org/gf/download/docmanfileversion/7292/10340/ConsolidatedRiskAssessment20130417.xlsx risk assessment] | ||
|} | |} | ||
Latest revision as of 15:28, 17 April 2013
Contents
TSC Risk Assessment Committee (TRAC) Agenda/Minutes
back to TRAC page
Meeting Info/Attendees
| TRAC Meeting Minutes Location: call 770-657-9270 using code 985371# |
Date: 2013-04-17 Time: 10:00 AM U.S. Eastern | |
| Facilitator: Pat Van Dyke | Note taker(s): Lynn Laakso | |
| Quorum ?? | yes/no | ||||
| Chair/CTO | Members | Members | |||
| x | Pat Van Dyke | x | Rick Haddorff | regrets | Melva Peters |
| x | John Quinn | x | Austin Kreisler | . | |
Agenda
- Agenda review and approval - Pat Van Dyke
- Review minutes of 2013-04-10 TRAC
- Continue risk assessment review (GOM)
- What areas where review have not been submitted or reviewed
- Set review schedule for known sources of risk
- Plan for review of GOM on regular basis
- Describe feedback loop
- What areas where review have not been submitted or reviewed
- Areas submitted where review still needs to occur
- Check with Jane on GOM Section 16 Risks
- T3F Strategic Initiative TSC Self Assessment results (See Original survey) - review red and yellow against existing risk items; if there isn't one then develop new risk items.
- How to address "issues"
Minutes
Minutes/Conclusions Reached:
- Continue risk assessment review (GOM)
- Pat notes that with the ANSI/GOM Review Task Force meeting yesterday she identified that a GOM risk review would need to be conducted on changes to the GOM.
- One year reconciliation deadline for informatives discussed. It is not addressed by AAWI0005 which is for normative only. May require GOM change to have review ballots on same timelines as normative. May need to incorporate into a governance point or a precept that internal processes should be consistent.
- Do we look at mitigation for critical first or serious ones next. Un-filtering reveals additional critical impact but less than high likelihood. Look at remaining critical risks next week and then collect a report of issues for TSC.
- John will be at ISO meeting next week but will join as connectivity permits.
Adjourned 11:00 AM
Next Steps
Actions (Include Owner, Action Item, and due date)
| |||
Next Meeting/Preliminary Agenda Items
|
