Sample Records Retention Update
Impact analysis
Calculated from the submitted answers by fixed rules.
75/ 100
Organization-level. Executive visibility before implementation.
- Recommended review route
- Executive Leadership
- Highest individual impact identified
- Major
- What drove this score
- How severely those areas are affected · Departments affected · How severely those groups are affected
Raised to 75 by an escalation rule
At least one affected area is rated Major. The weighted total was 55.1, which understates a change of this severity, so the rule sets a minimum.
Where the points came from
- How many areas are affected6.8 / 15
5 of the 11 listed areas were rated above N/A.
- How severely those areas are affected12.0 / 15
Across the 5 areas that were rated, the average is 2.4 on the Minor-to-Major scale. Areas marked N/A are excluded here — they are counted in the breadth dimension above.
- Departments affected9.0 / 15
3 of 5 departments were selected.
- Operational categories affected3.8 / 10
3 of the 8 operational categories were answered Yes.
- How many stakeholder groups are affected3.8 / 10
3 of the 8 stakeholder groups were rated above N/A.
- How severely those groups are affected7.8 / 10
Across the 3 groups that were rated, the average is 2.3 on the Minor-to-Major scale.
- Compliance and risk position5.0 / 10
Compliance review: yes. Risk assessment: yes. A completed risk assessment scores zero here — the points reflect what is outstanding.
- Implementation complexity7.0 / 15
Training yes, pilot yes, rollback plan yes, 2 communication methods, go-live in 69 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.
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
- 55.1 / 100
- After escalation floors
- 75.0 → displayed as 75
- Classification bands
- Minor below 50 · Moderate 50–74 · Major 75 and above
- Scoring version
- change-impact-score-v1
Escalation rules that matched
- At least one affected area is rated Major — sets a minimum of 75 (this one governs)
- At least one stakeholder group is rated Major — sets a minimum of 75
- A Major rating in a critical area — clinical care, patients, compliance, technology, or reporting — sets a minimum of 75
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 Client Administrator
- Role
- Compliance Staff
- Executive sponsor
- Test Executive A
- Date submitted
- May 26, 2026
- Target go-live
- Aug 3, 20263 days overdue
- Departments impacted
- Administration, Finance, Clinical Staff
- Rationale
- Regulatory Requirement, Technology Initiative
- Assigned reviewer
- Test Reviewer Two
Description of change
Fictional demonstration record. Updates how long each category of record is kept and where it is stored.
Affected areas
- TechnologyMajor
- ComplianceModerate
- Reporting (UDS / HRSA)Major
- FinanceModerate
- Grants / ContractsModerate
Description of impact
Retention periods, storage locations, and the disposal schedule all change together.
Compliance and risk
- Is a regulatory or compliance review required?
- Yes
- Has a Risk Assessment been completed?
- Yes
Operational impact
- Clinical CareNo
- IT & DataYes
- Finance & Revenue CycleYes
- Patient Access & ExperienceNo
- Workforce & StaffingNo
- Operational & AdminYes
- Equity & AccessNo
- OtherNo
Stakeholders
- ITMajor
- LeadershipModerate
- AdminModerate
Engagement strategy
Weekly checkpoint with the records owner and IT.
Training, communication, and implementation
- Training required
- Yes
- Training formats
- Recorded Learning Module(s), Job Aids and Reference Materials
- Communication methods
- Email update(s), Internet posting / Internal Communication
- Pilot
- Yes
- Rollback plan
- Yes
- Target go-live
- Aug 3, 2026
Other milestones
Inventory, mapping, verification run, effective date.
Review activity
History
- DraftTest Client Administrator · May 18, 2026, 9:00 AM
- Draft → SubmittedTest Client Administrator · May 26, 2026, 10:00 AM
- Reviewer assignedTest Reviewer Two · May 29, 2026, 9:00 AM
- Submitted → Under ReviewTest Reviewer Two · May 29, 2026, 9:00 AM
- Under Review → ApprovedTest Reviewer Two · Jun 10, 2026, 9:00 AM
- Approved → ScheduledTest Reviewer Two · Jun 15, 2026, 9:00 AM
Workflow
Recommended next steps
For a Major change. Current status: Scheduled.
- 1.Senior Executive Leadership review
- 2.Consider executive or board approval, as configured for this client
- 3.Confirm organization-wide timing and capacity
- 4.Complete the compliance and risk review
- 5.Confirm stakeholder, training, pilot, communication, and rollback plans
- 6.Review overlap with other Major changes in flight
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
- Major
- Recommended review route
- Executive Leadership
How this was reached
- Highest affected-area impact: Major.
- Highest stakeholder impact: Major.
- Overall impact is the higher of the two: Major.
- Recommended review route: Executive Leadership. Overall impact: Major. This is a routing recommendation and does not record an approval decision.
Compliance and risk
- Regulatory or compliance review required
The requester indicated that a regulatory or compliance review is required before implementation.
- Moderate areas
- 3
- Major areas
- 2
- Moderate stakeholders
- 2
- Major stakeholders
- 1
- Unresolved items
- 0
- Days to go-live
- 69
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_006
- Template version
- change-impact-analysis-v1
- Submitted by (member)
- mem_th_admin
- 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: Major · Highest individual stakeholder rating: Major