What it actually does
New orders and new progress notes arrive from PointClickCare by webhook, as they are written. The check matches one against the other. Where an order has been written and nothing in the notes supports it, that resident appears on a worklist — within minutes of the order, not in tomorrow morning's batch.
Where the drug belongs to a high-alert class, the row says which class, because "started on an anticoagulant with no note" and "started on a stool softener with no note" are not the same morning's work.
The screen is today. The alert remembers the week.
The worklist shows the last 24 hours, because that is today's work. The emailed alert looks back seven days, and the difference matters for one specific reason: an order written on a Friday night with nothing supporting it used to fall off the screen by Saturday morning whether or not anybody had opened the tab.
So the alert reports age, not just presence. "Written last night" and "still outstanding from a previous day" are different sentences, and the second one is the one that survives a handover.
It names the clock it used
An order's age can come from when your facility entered it, or from when we first saw it, or from the date the order starts. These are not equally good. When the age comes from when we first saw a record, the digest says so and calls the number a floor — because that is the age of our knowledge, not the age of the chart.
An order that carries no usable date at all is reported as undated and counted as neither new nor outstanding. Quietly sorting it into one of the two would have been easier and would have made both numbers wrong.
Four states, because two is not enough
Most alerting tools have two: something to look at, or nothing. That collapses the most important distinction in a compliance product.
- Needs attention — we read it and something is missing.
- Read, nothing found — we read it and it is fine.
- Still to read — in scope, not yet worked. Counting this as attention is how an attention count silently becomes a row count.
- Could not look — a scope we do not have, a record that did not arrive. Never shown as a clean result.
That last one is why lab orders currently appear as blocked rather than as nothing found. The lab scopes arrive in November 2026, and until then the row says so.
A tick says somebody looked. A disposition says what they did.
Ticking a chart marks it as worked. It does not stop the alert mentioning it again, deliberately — a bare tick is a claim about a person, not about a chart.
Recording a disposition does stop the repeat. There are three:
- Note added — the documentation now exists. The next read finds it and the finding closes itself.
- Not required — and this one asks for a reason in writing, because it is the only one of the three that nothing else in the record can confirm.
- Referred — passed to somebody else.
The number of suppressed charts is printed beside the open ones. A building that answers "not required" to everything does not disappear from the report; it becomes visible in it.
Three emails, three questions
| Answers | Contains | |
|---|---|---|
| Nightly digest | Did the overnight review run? | Worksheets, findings and any errors. |
| Chart-check alert | What did the chart check find? | Orders with no note, high-alert classes, new against outstanding, and what has been dispositioned. |
| Review reminder | Is there work left? | One number, per building: residents awaiting review. Nothing else, by request. |
They are kept apart on purpose. Folding any two together is how each one stops being read.
Silence always means nothing is wrong
A facility with nothing outstanding gets no alert. A facility we could not read gets one anyway, saying we could not read it.
That sounds obvious and almost no alerting system does it, because the failure is invisible from the inside: a job that stops running sends nothing, and nothing looks exactly like good news. "We looked and found nothing" and "we could not look" are different facts, and this product never lets them arrive in the same envelope.
Related: What it reads from PointClickCare · After an incident · Security and your BAA · The 60-day pilot