What it reads from PointClickCare

The connection you already have

SurvAIHealth connects through the PointClickCare Marketplace using the access your organisation grants it. There is no second login for your staff, no export to schedule, and nothing to type twice. Your team keeps charting exactly as they do now; the reading happens on our side.

Access in PointClickCare is granted endpoint by endpoint. That matters more than it sounds, because it means the honest answer to "can it see X" is a list rather than a yes — and the list changes as grants are approved.

Read today

Record	State	What we do with it
Assessments, including the MDS	Read	The MDS is an assessment in PointClickCare — same pipe, not a separate feed. Types, dates and status are indexed; coding questions are checked against the answers already recorded.
Progress notes	Read	Delivered by webhook as they are written. This is what the chart check matches an order against.
Medications and orders	Read	Description, directions, route, class, status and dates — and, where your tenant records them, who ordered it and when it was entered. One route of entry carries both halves.
Incidents	Read	Each one read against the F-tags it actually touches, with the chart quoted back.
Activities of daily living	Read	Compared against the ADL coding on the assessment.
Conditions and diagnoses	Read	Context for the coding checks.
Coverage, admissions, transfers	Read	Used to work out which residents are in scope on a given day.

Granted later, with a date rather than a promise

Record	State	Where it stands
Care plans	Nov 2026	Until then, the product does not claim to check an order against a care plan. The screen says so on the row rather than in a footnote.
The rest of the order book	Nov 2026	Treatment, diet, therapy and lab orders. Medication orders are already read; these are not, and "no non-medication orders found" is reported as a gap in our reading, not as a finding about your facility.
Lab orders and results	Nov 2026	Both halves are blocked, and they are different facts — a lab ordered is activity on the chart the day it is written, separately from whatever comes back.
Vitals as a dedicated feed	On grant	A vital charted on a facility assessment is already read. The standalone observations feed is not yet granted; the code for it is written and switches on the day it is.

Not reachable, and not on a roadmap

Record	State	Why it is marked permanent
Signed consent forms	Permanent	No endpoint exposes the signed-forms library. A coded item cannot stand in for a signature, so any worksheet row that needs one stays unanswerable and is marked that way rather than inferred.
The CNA Kardex	Permanent	There is no Kardex feed and no plan for one.
Whether a dose was actually given	Permanent	The medication record is order-level. It carries the route a drug is given by and nothing about whether a dose was administered, when, or by whom. It answers what is ordered, not what was delivered.

Why the last table is the one to read

A system that cannot distinguish "we looked and found nothing" from "we could not look" will eventually show you a clean screen over a chart nobody read. That is not a hypothetical failure — it is the normal one, and it is how a compliance tool becomes a liability.

So the three states above are the same three states the product uses internally, on every screen, in every export. A blocked column reads as blocked. No theme, setting or summary view can restyle it into a tick.

How current the data is

Orders and progress notes arrive by webhook from PointClickCare, so an order written overnight is matched against the notes on file within minutes rather than in the next morning's batch. Coding work runs on a nightly pass. Nothing waits on a person remembering to press refresh.

PointClickCare Marketplace No second login No double entry Webhook, not nightly export