Request Scoring Matrix |
|
Patient Safety Definition: Current workflow and build is having a negative impact on Patient Safety, by completing this particular optimization item Patient Care will be improved |
|
|
Patient Safety |
4 |
Severe Impact |
Immediate HIGH RISK patient safety issue with NO WORKAROUND |
|
3 |
High Impact |
Immediate HIGH RISK patient safety issue with AVAILABLE WORKAROUND |
|
2 |
Medium Impact |
Potential LOW RISK patient safety issue with NO WORKAROUND |
|
1 |
Low Impact |
Potential LOW RISK patient safety issue with AVAILABLE WORKAROUND |
|
0 |
No Impact |
|
|
|
|
Productivity / Efficiency Definition: The amount of time a particular user can save or become more efficient by implementing a particular optimization item |
|
|
Productivity / Efficiency |
4 |
Severe Impact |
Affecting MULTIPLE USERS in a HIGH VOLUME area |
|
3 |
High Impact |
Affecting SMALL USER GROUP in a HIGH VOLUME area |
|
2 |
Medium Impact |
Affecting MULTIPLE USERS in a LOW VOLUME area |
|
1 |
Low Impact |
Affecting SMALL USER GROUP in a LOW VOLUME area |
|
0 |
No Impact |
|
|
|
|
Compliance / Regulatory Definition: This particular optimization request will address a lack of a Compliance/Regulatory need with the system |
|
|
Compliance / Regulatory |
4 |
Severe Impact |
CMS or Joint Commission Mandate w/ No Exceptions |
|
3 |
High Impact |
YNHHS / YMG / NEMG - Policy Standard |
|
2 |
Medium Impact |
YNHHS / YMG / NEMG - Standard of Care |
|
1 |
Low Impact |
YNHHS / YMG / NEMG - Nice to Have |
|
0 |
No Impact |
|
|
|
|
Revenue Definition: The amount of money that is currently not being captured or money that an optimization item if built can save the organization |
|
|
Revenue |
4 |
Severe Impact |
Greater than $1M |
|
3 |
High Impact |
Between $500K and $1M |
|
2 |
Medium Impact |
Between $100K and $500K |
|
1 |
Low Impact |
Less than $100K |
|
0 |
No Impact |
|
|
|
|
Organizational Impact Definition: The number of Users that a particular optimization item is currently affecting and by completing it will positively affect |
|
|
Organizational Impact |
3 |
High Impact |
YNHH System Wide / All Users |
|
2 |
Medium Impact |
Multiple Departments / Many Users |
|
1 |
Low Impact |
Single Department / A Few Users |
|
0 |
No Impact |
|
|
|
|
Resources Definition: The amount of work it will take the Analyst(s) / Application Team(s) to Design / Build / Implement a particular item |
|
|
Resources |
-3 |
High Impact |
YNHH System Wide / Multiple Analysts / Multiple Application Teams / Leadership Decisions |
|
-2 |
Medium Impact |
Moderate Amount of Work for Multiple Analysts and/or Multiple Application Teams |
|
-1 |
Low Impact |
Moderate Amount of Work for an Analyst |
|
0 |
No Impact |
Minimal Amount of Work for a single Analyst |
|
|
|
Negative Impact Definition: If an optimization item is to be built and released, will it have an adverse negative effect to Users / Departments or System Wide, if so on what scale |
|
|
Negative
Impact |
-3 |
High Impact |
YNHHS Wide will notice Negative Impact |
|
-2 |
Medium Impact |
Department(s) will notice a Negative Impact |
|
-1 |
Low Impact |
Small Negative Impact on a few Users |
|
0 |
No Impact |
|
|