PointClickCare does not automatically transfer patient data when a resident moves between care settings within the same organisation. When a resident transitions from skilled nursing to assisted living, or from assisted living to memory care, clinical staff at the receiving setting re-enter demographics, reconcile medication lists, rebuild care plans, and verify allergy records manually. This is the most consequential gap in the dominant US post-acute EHR — confirmed by KLAS Research reviews and documented across facilities of every size. It is a clinical safety problem: every manual re-entry is an opportunity for a transcription error in a medication list or allergy record.
What data does PointClickCare not transfer between care settings?
PointClickCare treats each care setting — SNF, assisted living, memory care, independent living — as a separate clinical environment. When a resident transitions, the following data does not carry over automatically:
| Data Type | What Should Transfer | What Actually Happens |
|---|---|---|
| Demographics and insurance | Name, DOB, insurance, emergency contacts, advance directives | Re-entered manually at the receiving setting |
| Active medication list | Current medications with dosages, schedules, prescribing physician | Manually reconciled — staff compare printouts from both settings |
| Care plans | Active care plan with goals, interventions, responsible staff | Rebuilt from scratch at the receiving setting |
| Allergy and adverse reaction records | Known allergies, documented reactions, severity | Re-entered manually — missed allergies are a patient safety event |
| Assessment history | MDS, OASIS, functional assessments, wound documentation | Accessible in the prior setting's record — not copied to the new one |
The medication list gap is the most dangerous. A missed medication or incorrect dosage during a care transition is a preventable adverse event. In a multi-setting organisation where residents transition regularly — SNF to assisted living after a rehab stay is the most common pattern — this happens weekly or daily, not occasionally.
Why does PointClickCare treat each care setting as a separate system?
PointClickCare was built for skilled nursing facilities first. SNF documentation requirements — MDS assessments, Medicare billing, state survey compliance — are specific to that care setting. When PointClickCare expanded to assisted living and memory care, it added those as separate modules with their own clinical workflows, documentation templates, and billing models.
The separate-module architecture made sense when most PointClickCare customers operated a single care setting. It breaks when a CCRC (continuing care retirement community) or a multi-site operator runs SNF, assisted living, memory care, and independent living under one roof — which is increasingly common. The resident is one person. The clinical record should be one record. But PointClickCare treats each setting as a separate chart.
KLAS Research reviews confirm the interface complexity. Implementing data exchanges between PointClickCare settings is described as complex and time-consuming — often taking months. For organisations that need the data to flow now, the implementation timeline for PointClickCare's own interface programme doesn't match the clinical urgency.
What is the clinical risk of manual data re-entry during care transitions?
Three categories of clinical risk. Each is documented in post-acute care safety literature.
Medication errors during reconciliation. When a nurse at the receiving setting manually copies a medication list from a printout or a screen, transcription errors occur. A dose written as "0.5mg" gets entered as "5mg." A PRN medication gets entered as a standing order. A discontinued medication gets copied because the printout was generated before the discontinuation was documented. Each of these produces a medication administration error that is entirely preventable with automated data transfer.
Missing allergy records. Allergies documented in the SNF chart do not carry over. If the receiving setting's admitting nurse doesn't ask about allergies — or the resident has cognitive impairment and cannot self-report — the allergy record at the new setting is incomplete. A medication that the resident is allergic to can be administered before the gap is discovered.
Care plan gaps. A care plan developed over weeks or months in skilled nursing — including fall risk interventions, wound care protocols, and behavioural health strategies — starts over when the resident transitions. The receiving setting's care team doesn't have visibility into what was working. They start from assessment, not from continuity. The resident's care quality drops during the rebuilding period.
How much time does manual care transition data entry cost per month?
A CCRC or multi-setting operator processing 15 to 25 care transitions per month — a typical volume for a 200-bed campus — spends 1.5 to 3 hours per transition on data re-entry, medication reconciliation, and care plan rebuilding. That is 22.5 to 75 nursing hours per month dedicated to copying data that already exists in the same EHR platform.
At an RN hourly rate of $40 to $55 fully loaded, the monthly cost is $900 to $4,125. Annually: $10,800 to $49,500. Larger organisations with multiple campuses multiply that figure by the number of sites.
The cost isn't just hours. It is nursing time diverted from direct patient care. The hours spent on data re-entry are hours not spent on clinical assessment, family communication, or care coordination. The opportunity cost is higher than the labour cost.
Why hasn't PointClickCare fixed the cross-setting data problem?
PointClickCare has an interface programme for data exchange between settings. But implementation is complex, expensive, and slow — months-long projects per interface, per setting pair. For an organisation running four care settings, that is six bidirectional interfaces to implement. The total implementation cost and timeline can exceed what most operators budget for EHR enhancement in a given year.
The deeper issue is architectural. PointClickCare's data model was not designed for a single longitudinal patient record across care settings. Adding that capability is not a feature update — it is a re-architecture of how the platform stores and references clinical data. That is a multi-year engineering project that PointClickCare may be working on, but today's operators need the data to flow today.
PointClickCare has a marketplace but few add-on developers addressing this problem. The marketplace has solutions for specific clinical workflows — pharmacy integration, wound care documentation — but no product that solves cross-setting data continuity as a unified layer.
What do post-acute operators build to fix cross-setting data continuity?
The highest-value custom build is a cross-setting patient data continuity layer that sits alongside PointClickCare and automatically reconciles and syncs clinical records when a resident transitions. It pulls data from the originating setting — demographics, medications, allergies, care plans, recent assessments — validates it, and pushes it to the receiving setting's record. The clinical team at the receiving setting starts with a pre-populated chart, not a blank one.
The build typically takes 12 to 18 weeks. It requires access to PointClickCare's data — either through their API programme, database-level access, or a combination. HIPAA compliance is a scoping input, not a barrier: the custom layer must meet the same technical safeguard requirements as any system handling PHI — encryption, access controls, audit logging, BAA coverage.
The second highest-value build is an HL7/FHIR integration bridge that connects PointClickCare to external systems — hospital EHRs, pharmacy platforms, lab systems — for organisations where the data continuity problem extends beyond PointClickCare's own settings. Timeline is typically 12 to 18 weeks.
Madgeek builds custom software for healthcare providers alongside PointClickCare, Netsmart myUnity, Tebra, and NextGen Healthcare. See the full post-acute EHR gap map for how each platform compares. For related work: healthcare workflow automation and healthcare software development.
Need a team to build this for your business?