Programs that run on the calendar
Using AI for care management follow-up makes sense because these programs are driven by dates more than by visits. Chronic care management is counted by the calendar month, with staff time and activity documented for each one. Transitional care management starts a clock on the day of discharge. Remote monitoring depends on readings arriving and being reviewed.
In a small practice, one or two people carry all of those dates for every enrolled patient. Gateway helps configure AI-assisted workflows that read the practice’s own records and bring forward what is due, what is late and what is undocumented. Staff and clinicians act on the list.
What the workflow surfaces
- Enrolled patients with no contact or activity logged yet this month
- Contacts planned for this week, by program
- Care plans not updated since a set date or since a recent hospital stay
- Recent discharges that open a transitional care window, with the contact and visit dates that follow
- Remote monitoring patients whose devices have gone quiet
- Contacts logged without the time spent or another item the practice’s checklist requires
- Consent or enrollment records that are missing or incomplete
- Patient questions waiting for a clinician’s answer
Why each item shows its reason
A list that only says “call this patient” invites doubt. Each item shows where it came from and why it was raised: the date of the last logged contact, the discharge date and the facility named in the notice, the last day a reading arrived.
Staff can check the source in seconds and dismiss an item that is wrong, such as a call that was made but logged under another patient. Dismissals are counted, because an item that is often wrong points to a data problem.
From a month-end scramble to a daily list
Without a forward view, care management work bunches up in the last week of the month, when staff find out which patients have not been reached. Rushed calls are less useful to patients and harder to document well.
A daily list spreads the work out. The care coordinator starts each day with the contacts due, the follow-ups promised on earlier calls and the documentation still open from yesterday. The clinician sees a shorter list: care plans to review, questions to answer and items that staff have escalated.
One patient, several programs
A patient in chronic care management may also have a blood pressure cuff from the remote patient monitoring program, and may have just come home from the hospital, which brings transitional care management into play. Kept in three spreadsheets, that is three calls from three people.
The workflow shows one view per patient across programs, so a single well-prepared contact can cover what is due. The same applies to a patient followed for one serious condition under principal care management. Which services can be billed together in the same period depends on rules that vary by service and payer. The practice confirms them.
What the AI does not do
- It does not call, text or message patients (staff make the contacts)
- It does not interpret a reading or judge a symptom
- It does not decide who is eligible for a program or enroll anyone
- It does not decide that a month’s requirements have been met for billing
- It does not write or alter the clinical record
A quiet device or a missed contact is an administrative prompt. An out-of-range reading or a worrying report from a patient follows the practice’s own clinical review process, which the clinician defines. The workflow is not an alarm system.
What stays with the practice
Eligibility, consent, clinical supervision, the care plan and every clinical decision belong to the practice and its clinicians. So do final coding decisions and responsibility for claims. Gateway’s part is configuring the workflow and keeping it matched to the practice’s program checklists.
Practices preparing for quality contracts can connect the same lists to value-based care readiness.
How an engagement starts
Reach us through the practice support inquiry form or at 314-325-0126. Please do not include patient details.
We start with one program and one clinician’s enrolled patients. For the first few weeks, your care coordinator compares the daily list with what they already know, and we correct what is wrong. Practices still designing a program may want to read our CCM program startup questions first. Other workflow automation can follow if it would help.
Common questions
What happens when a remote monitoring reading is out of range?
That is handled by the clinical review process the practice has set for its monitoring program, including who looks at readings and how quickly. The follow-up workflow described here tracks administrative items, such as a device that has stopped sending data. It does not screen readings for clinical urgency.
Can it tell us which patients qualify for a program?
It can organize the review. Using criteria the practice sets, the workflow can list patients for the clinician to consider and track where each review stands. The clinician decides who is appropriate, the practice confirms eligibility under the program’s rules, and consent is obtained before enrollment.
Does the list tell us when a month can be billed?
No. It shows what has been logged against the practice’s own checklist for each program and what is still open. Whether the requirements for a service were met, and whether to bill it, is a decision for the practice. Final coding decisions and responsibility for claims do not move.
We track contacts in a spreadsheet. Is that enough to begin with?
Often, yes. The workflow needs a dependable record of who is enrolled and when each contact took place. A spreadsheet that is kept up to date can serve as the first source. If entries are patchy, the first job is tidying the record, since no workflow can surface a contact that was never logged.