Harold moves into Maple Grove. The front desk does what it always does: admits him.
Nothing new for the facility. This is the census work they already do.
Harold's record
Room 214-B
moving in today
Maple Grove Senior Living
a new resident arrives, like any other day
How it works
What happens
The facility admits, discharges, and transfers residents in PointClickCare exactly as it always has. CCN listens to that same activity: an admit creates the resident in CCN with their full profile (name, date of birth, room and bed, medical record number, Medicare beneficiary ID, language), a discharge is handled per your workflow, and a cancelled admission removes the record cleanly. For a brand-new site, one click imports the entire active census.
How it works
CCN subscribes to PointClickCare's ADT event webhooks (POST .../webhook-subscriptions) so admit, readmit, transfer, discharge, and cancellation events arrive as they happen. Each event is matched to the org, facility, and resident; profile data is pulled from the patients endpoint (GET .../patients?facId={facility}&patientStatus=Current) and formatted onto the CCN record, including the room and bed parsed from the census. Bulk import walks the same endpoint page by page for the whole facility.
The benefit to your practice
No one maintains a second roster, ever. New residents are monitorable the day they arrive, departed residents stop billing the day they leave, and there are never phantom patients. The census work the facility already does is the only census work that exists.
What you get
- Admit / readmit / transfer: the resident is created or reactivated with the full profile pulled
- Discharge handled per your workflow; a cancelled admission removes the record cleanly
- One-click bulk import stands up a new site's entire active census in minutes
- Who's monitored in CCN always matches who's in the building