For Care Teams
Learn how the application's evidence, analytics and workflow can support review.
A review, start to finish
Imagine a nurse or care coordinator responsible for the diabetes population at a practice. Their question each week is the same: who has gone too long without an A1C, why, and what is being done about it. The application is organised around that question, in six steps.
This is a hypothetical workflow for a demonstration built on synthetic data. It shows how the pieces fit together; it is not a protocol, and the application makes no clinical decisions.
The workflow
- Care Gaps
Step 1: Identify an open monitoring gap
Start from the patients with no A1C result in the 365 days before the data date.
Home shows the first five; Care Gaps lists every open gap, never tested first.
- Derived status
- Review on Care Gaps
Step 2: Review the supporting evidence
Check why the patient has the status: the latest A1C, its date, days overdue, last encounter and care setting.
- Clinical source
- Derived status
- Patients
Step 3: Inspect the patient's history
Open the patient workspace for every A1C on file, testing per year, medications and procedures.
There is no orders table, so the history shows tests that happened, never tests that were requested.
- Clinical source
- Tasks
Step 4: Record follow-up
Move the gap's task through review, outreach and scheduling; assign it, set a due date, add a workflow note.
Nothing is sent to a patient. Task data is saved in this browser only.
- Demo workflow data
- Tasks
Step 5: Monitor completion
Follow open tasks to completion, and watch for the qualifying A1C result that actually closes the gap.
Completing a task never closes the gap. Only a new qualifying result in the source data does.
- Demo workflow data
- Derived status
- Analytics
Step 6: Review population analytics
Step back to coverage, the make-up of the gaps, where they sit by age and setting, and testing over time.
- Derived status
- Clinical source
Evidence first, workflow second
Every gap rests on clinical source data: an A1C result and its date, or the absence of any result. The application derives the gap status from that data the same way on every page. Follow-up work is recorded separately, as workflow, and nothing recorded there can change the status. A completed task on an overdue patient is still an overdue patient until a new qualifying result arrives.
In this demo, task status, assignment, due dates, notes and workflow activity are application data saved in your browser only. They do not represent real outreach: no patient has been contacted, and nothing is sent anywhere.