Test Scheduling Workflow 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 · How many areas are affected · Departments affected
Raised to 75 by an escalation rule
At least one affected area is rated Major. The weighted total was 64.8, which understates a change of this severity, so the rule sets a minimum.
Where the points came from
- How many areas are affected9.5 / 15
7 of the 11 listed areas were rated above N/A.
- How severely those areas are affected10.7 / 15
Across the 7 areas that were rated, the average is 2.1 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 affected5.0 / 10
4 of the 8 operational categories were answered Yes.
- How many stakeholder groups are affected6.3 / 10
5 of the 8 stakeholder groups were rated above N/A.
- How severely those groups are affected7.3 / 10
Across the 5 groups that were rated, the average is 2.2 on the Minor-to-Major scale.
- Compliance and risk position8.0 / 10
Compliance review: yes. Risk assessment: needs_evaluation. A completed risk assessment scores zero here — the points reflect what is outstanding.
- Implementation complexity9.0 / 15
Training yes, pilot no, rollback plan needs_evaluation, 3 communication methods, go-live in 25 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
- 64.8 / 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
- A compliance review is required while the risk assessment is unresolved — sets a minimum of 50 (already exceeded)
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
- Executive Leadership
- Executive sponsor
- Test Executive A
- Date submitted
- Jun 15, 2026
- Target go-live
- Jul 10, 202627 days overdue
- Departments impacted
- Finance, Patient Services, Administration
- Rationale
- Regulatory Requirement, Compliance / Risk Management
- Assigned reviewer
- Test Reviewer One
Description of change
Fictional demonstration record. A proposed revision to the standard scheduling workflow, touching eligibility screening, downstream billing configuration, and the reporting extract. Included to exercise a Major-impact request with an open compliance review.
Affected areas
- Patient ServicesModerate
- Billing / Revenue CycleMajor
- TechnologyMinor
- ComplianceMajor
- Reporting (UDS / HRSA)Moderate
- FinanceModerate
- PatientsModerate
Description of impact
Screening steps, the intake form, the fee configuration, and the reporting mappings all require coordinated updates before the effective date.
Compliance and risk
- Is a regulatory or compliance review required?
- Yes
- Has a Risk Assessment been completed?
- Needs to be evaluated
Operational impact
- Clinical CareNo
- IT & DataNo
- Finance & Revenue CycleYes
- Patient Access & ExperienceYes
- Workforce & StaffingNo
- Operational & AdminYes
- Equity & AccessYes
- OtherNo
Stakeholders
- Front DeskMajor
- ITMinor
- LeadershipModerate
- PatientsModerate
- AdminMajor
Engagement strategy
Two briefings for front-desk staff, a written summary for leadership, and a plain-language handout at each site.
Training, communication, and implementation
- Training required
- Yes
- Training formats
- Live Sessions, Job Aids and Reference Materials
- Communication methods
- Announcement from leadership, Department Meeting(s), Email update(s)
- Pilot
- No
- Rollback plan
- Needs Evaluation
- Target go-live
- Jul 10, 2026
Other milestones
Compliance sign-off, configuration change, staff briefing, effective date.
Review activity
- Test Reviewer OneJun 18, 2026, 10:30 AM
Please add the compliance review completion date to the milestones once it is scheduled.
- Test IDEL ConsultantJul 21, 2026, 3:00 PMIDEL internal
Internal note (visible to IDEL staff only): the go-live date has passed and the rollback position is still unresolved. Worth raising at the next governance call.
History
- DraftTest Client Administrator · Jun 8, 2026, 9:00 AM
- Draft → SubmittedTest Client Administrator · Jun 15, 2026, 2:20 PM
- Reviewer assignedTest Reviewer One · Jun 18, 2026, 10:05 AM
- Submitted → Under ReviewTest Reviewer One · Jun 18, 2026, 10:05 AM
- Comment addedTest Reviewer One · Jun 18, 2026, 10:30 AM
- Comment addedTest IDEL Consultant · Jul 21, 2026, 3:00 PM
Workflow
Recommended next steps
For a Major change. Current status: Under Review.
- 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.
- Risk assessment status not yet determined
Whether a risk assessment is needed has not been established.
Implementation readiness
- Rollback plan not yet determined
Whether a rollback plan is needed has not been established.
- Moderate areas
- 4
- Major areas
- 2
- Moderate stakeholders
- 2
- Major stakeholders
- 2
- Unresolved items
- 2
- Days to go-live
- 25
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_001
- Template version
- change-impact-analysis-v1
- Submitted by (member)
- mem_th_admin
- Internal notes
- 1 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