These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Healthcare Analytics
- Features
- Follow-up actions
Follow-up actions
Assign corrective work raised from published outcomes and close it with a recorded resolution.
OverviewMy follow-up actions×
Healthcare Analytics · Follow-up actions
New
My follow-up actions
Follow up actions
| Title | Source | Due date | Status | Completed at | Resolution | |
|---|---|---|---|---|---|---|
| Open fua-935 | OC-53071 | 13 Oct | Open | RSL-570 | ||
| In progress fua-924 | OC-40187 | 27 Oct | In progress | RSL-502 | ||
| Completed fua-756 | OC-57921 | 07 Oct | Completed | 09 Oct | RSL-155 | |
| Cancelled fua-287 | OC-97535 | 10 Oct | Open | RSL-620 | ||
| Open fua-244 | OC-92133 | 25 Oct | In progress | RSL-618 |
6 of 6 records
Open fua-935Follow up actions · FUA-98645
OpenSourceOC-53071
Due date13 Oct
ResolutionRSL-570
What you can do
Turn a published rate into assigned work
A rate that moves the wrong way needs someone to act on it. A follow-up action records that work: a title, the cohort it came from, the person it is assigned to, a due date, a status and, when it is finished, the completion date and resolution. Because each action points at its cohort, a reviewer can see which published result prompted it and what was done about it.
How the work is organized
The Analytics Manager raises follow-up actions from a published cohort and assigns each one to a person with a due date. The assignee moves it Open → InProgress → Completed and records the resolution, or moves it to Cancelled with a reason in the resolution field. Actions that are still open or in progress after their due date appear in the overdue exception queue on the Healthcare Analytics Overview page.
- One assignee per action. assigned to names a single person, and the “My follow-up actions” view shows only their work.
- A resolution on every close. Completed and cancelled actions keep a written resolution and a completion date.
- Linked to the source cohort. Each action keeps its cohort reference, so the outcome that prompted it stays one click away.
What to agree during setup
Agree which published outcomes should prompt a follow-up action, for example a readmission rate above an agreed threshold for two consecutive windows. Agree who raises actions, how due dates are set and who can reassign or cancel an action. Decide what a resolution must contain before an action can be completed, such as the change made, the owner and the date it took effect. Agree how often the overdue queue is reviewed and by whom.
Check the handoff on an actual case
Publish a cohort whose readmission rate has risen. Ask the Analytics Manager to raise a follow-up action against it, assign it to a Quality Improvement Lead and set a due date in the past for the test. The action should appear in the “Follow-up actions due” view and in the overdue queue on the overview page.
Ask the Quality Improvement Lead to move it to InProgress, then try to complete it without a resolution. Once the agreed resolution rule is configured, completion should be refused until the resolution text is recorded. Once completed with a resolution, the action should leave the overdue queue and keep its completion date. A second assignee should not see it in their “My follow-up actions” view.
What your team sees
- Follow-up actions due — open and in-progress actions at or past their due date, with cohort, assignee and status.
- My follow-up actions — actions assigned to the signed-in person, with due date, status, completion date and resolution.
Follow the work through
- Follow-up action to resolution: Assign, work and close corrective actions raised from published outcomes.
- Independent review to publication: Approve the exact revision and publish its outcome rates.
Review the implementation plan and the data model before preparing your import files.
What it keeps track of
Data model- Follow up actions
- Assigned corrective and follow-up actions with due dates.
- Outcome cohorts
- Measured web properties with lifecycle status and observed outcome fields.
- People
- Analysts, owners and reviewers belonging to an organization.
Who uses it
Permissions- Quality Improvement Lead
- , Analytics Manager, Outcomes Analyst.
- The Quality Improvement Lead works and closes actions.
- The Analytics Manager raises and assigns them.
- An Outcomes Analyst may be assigned an action that concerns the data behind a cohort.
Set up Healthcare Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.