Migration Architecture | PointClickCare to SeniorCRE Entity Mapping
Where this page sits. Integration philosophy is the parent doctrine: we govern the systems an operator chooses to retain and do not require their replacement, and the default motion moves no data out of your EHR. This page is the nested child that applies only when an operator qualifies into a gated exception motion — a greenfield opening or a paper turnaround — where data genuinely has to land somewhere. If you are on the default motion, read the parent, not this page.
1. PointClickCare → SeniorCRE entity map
One row per PCC entity. The transform column is the actual operation; the notes column is what your clinical and finance teams will care about.
2. Other source systems
MatrixCare, Yardi, and QuickBooks follow the same mapping discipline. Named-vendor connectors remain roadmap, and the exact target fields are finalized in written scope.
3. The cutover model
Migration is a sequence, not a flip. Each community follows written readiness and acceptance gates rather than a fixed calendar.
Frequently asked questions
- How long does migration take?
- No standard migration duration is published. Timing depends on source access, definition authority, reconciliation scope, security review, clinical-safety review where applicable, and written operator acceptance. No named-vendor connector is live in operator production.
- Do we lose history?
- No. In a governed migration, locked clinical history can be preserved as read-only evidence. Open balances become opening entries where the operator accepts that treatment, and the written acceptance boundary governs what moves.
- What happens if migration finds bad data?
- A reconciliation report flags gaps such as orphan medication orders, payers with no resident, or missing care-plan versions. The operator reviews and signs off before any accepted cutover; nothing silent.
- Can we run dual systems during cutover?
- Where a governed migration is contracted, the pattern is a bounded parallel review: staff keep using the incumbent clinical system until the operator accepts the cutover boundary. SeniorCRE does not claim a live named-vendor production connector today.
- What about controlled substances?
- Controlled substance reconciliation requires a fresh operator-approved count at the accepted boundary. SeniorCRE does not silently inherit C2 counts.
https://seniorcre.com/migration-architecture