Example Technology Rollout
Impact analysis
Calculated from the submitted answers by fixed rules.
42/ 100
Contained enough to be decided close to the work.
- Recommended review route
- Department / Site Manager
- Highest individual impact identified
- Moderate
- What drove this score
- How severely those areas are affected · Implementation complexity · Departments affected
Where the points came from
- How many areas are affected5.5 / 15
4 of the 11 listed areas were rated above N/A.
- How severely those areas are affected8.8 / 15
Across the 4 areas that were rated, the average is 1.8 on the Minor-to-Major scale. Areas marked N/A are excluded here — they are counted in the breadth dimension above.
- Departments affected6.0 / 15
2 of 5 departments were selected.
- Operational categories affected3.8 / 10
3 of the 8 operational categories were answered Yes.
- How many stakeholder groups are affected5.0 / 10
4 of the 8 stakeholder groups were rated above N/A.
- How severely those groups are affected5.0 / 10
Across the 4 groups that were rated, the average is 1.5 on the Minor-to-Major scale.
- Compliance and risk position0.0 / 10
Compliance review: no. Risk assessment: yes. A completed risk assessment scores zero here — the points reflect what is outstanding.
- Implementation complexity8.0 / 15
Training yes, pilot yes, rollback plan yes, 2 communication methods, go-live in 32 days.
This score reflects the breadth and severity of the structured impacts identified in the request. Written descriptions provide review context but do not directly change the score.
One row is rated Moderate, above this request’s overall classification
The classification above is the request’s official one: it weighs how far the change spreads as well as how hard it lands, and this change is narrow. The Moderate rating is worth a second look all the same — it is the kind of detail a breadth-aware score is least likely to surface on its own.
How this was calculated
Each dimension is scored against its own maximum and the eight are added together. Grid questions are read twice, once for breadth and once for severity, because those are different questions with different denominators:
- Breadth counts rows marked N/A in the denominator. That is what makes a change touching one of eleven areas read as narrow, and a change touching eight read as wide.
- Severity excludes them. One area hit as hard as possible is fully severe; it should not read as mild merely because the form lists eleven areas.
The highest individual impact identified above is a fact about the answers, not a second classification. Its role in the calculation is to trigger the escalation floors below.
- Weighted total
- 42.0 / 100
- After escalation floors
- 42.0 → displayed as 42
- Classification bands
- Minor below 50 · Moderate 50–74 · Major 75 and above
- Scoring version
- change-impact-score-v1
These weights are a draft. They were proposed for review and have not been approved as IDEL policy. Changing them produces a new scoring version, so past scores keep meaning what they meant when they were calculated.
Overview
- Organization
- Test Community Health
- Requestor
- Test Submitter Two
- Role
- Manager / Supervisor
- Executive sponsor
- Sample Operations Leader
- Date submitted
- Jul 16, 2026
- Target go-live
- Aug 17, 2026in 11 days
- Departments impacted
- Clinical Staff, Administration
- Rationale
- Operational Efficiencies, Technology Initiative
- Assigned reviewer
- Test Reviewer Two
Description of change
Fictional demonstration record. Replaces a manual step with a supported tool, with a defined fallback for the first thirty days.
Affected areas
- Clinical CareModerate
- Patient ServicesModerate
- TechnologyModerate
- FinanceMinor
Description of impact
A supported tool replaces the manual step; the fallback stays available for thirty days.
Compliance and risk
- Is a regulatory or compliance review required?
- No
- Has a Risk Assessment been completed?
- Yes
Operational impact
- Clinical CareYes
- IT & DataNo
- Finance & Revenue CycleNo
- Patient Access & ExperienceYes
- Workforce & StaffingYes
- Operational & AdminNo
- Equity & AccessNo
- OtherNo
Stakeholders
- ProvidersMinor
- Nursing StaffModerate
- PatientsModerate
- AdminMinor
Engagement strategy
Rotation schedule agreed with the affected teams before the start date.
Training, communication, and implementation
- Training required
- Yes
- Training formats
- Job Aids and Reference Materials
- Communication methods
- Department Meeting(s), Email update(s)
- Pilot
- Yes
- Rollback plan
- Yes
- Target go-live
- Aug 17, 2026
Review activity
- Test Reviewer TwoJul 6, 2026, 4:05 PM
Returned for revision on 6 July: coverage detail and the fallback plan were missing.
- Test Submitter TwoJul 16, 2026, 10:35 AM
Resubmitted with the coverage detail and a documented fallback for the first 30 days.
History
- DraftTest Submitter Two · Jun 22, 2026, 9:00 AM
- Reviewer assignedTest Reviewer Two · Jul 2, 2026, 2:00 PM
- Submitted → Under ReviewTest Reviewer Two · Jul 2, 2026, 2:00 PM
- Under Review → Returned for RevisionTest Reviewer Two · Jul 2, 2026, 2:00 PMCoverage detail and the fallback plan were missing.
- Comment addedTest Reviewer Two · Jul 6, 2026, 4:05 PM
- Draft → SubmittedTest Submitter Two · Jul 16, 2026, 10:30 AM
- Returned for Revision → ResubmittedTest Submitter Two · Jul 16, 2026, 10:30 AM
- Comment addedTest Submitter Two · Jul 16, 2026, 10:35 AM
Workflow
Recommended next steps
For a Minor change. Current status: Resubmitted.
- 1.Department or Site Manager review
- 2.Confirm the affected team
- 3.Confirm the communication approach
- 4.Approve, revise, or return the request
These steps follow from the impact level. They are recommendations — the platform does not record any of them as complete, and none of them is an approval.
Established impact logic
The earlier reading, kept for continuity. The official classification is the impact score above.
- Highest individual impact identified
- Moderate
- Recommended review route
- Operations Leadership
How this was reached
- Highest affected-area impact: Moderate.
- Highest stakeholder impact: Moderate.
- Overall impact is the higher of the two: Moderate.
- Recommended review route: Operations Leadership. Overall impact: Moderate. This is a routing recommendation and does not record an approval decision.
- Moderate areas
- 3
- Major areas
- 0
- Moderate stakeholders
- 2
- Major stakeholders
- 0
- Unresolved items
- 0
- Days to go-live
- 32
These figures describe the answers; they are not a second classification. This request has one official classification, shown with the impact score above. The recommended route indicates who should review this change. It does not record that an approval has been given. Calculated by logic revision cia-logic-v1 from the answers as submitted.
IDEL internal
- Client
- Test Community Health
- Request id
- req_th_004
- Template version
- change-impact-analysis-v1
- Submitted by (member)
- mem_th_submitter2
- Internal notes
- 0 on this request
This panel and every internal note are excluded from client responses by the serializer, not by this page.
Impact reference
- Minor
- Form update, scripting change — Department / Site Manager
- Moderate
- Workflow change across multiple departments — Operations Leader
- Major
- New service line, major EHR change — CEO / Board
Highest individual area rating: Moderate · Highest individual stakeholder rating: Moderate