Without replacing your EHR
Integration without replacing your EHR
You do not have to change your clinical system to govern your numbers. In the default configuration, SeniorCRE reads the incumbent clinical system one direction only — no clinical write-back, no change to documentation workflow, no second medication administration record — and governs the operating record above it. Clinical record surfaces are built; medication administration and eMAR remain roadmap — not built. Any future clinical system-of-record function requires cleared Production-Entry Gates and operator acceptance, with one authoritative MAR in either configuration. Govern first. Replace only by choice.
- Default direction
- Read one direction only from the incumbent clinical system
- Non-negotiable rule
- Exactly one authoritative MAR at all times
- Configurations
- Governed coexistence, or SeniorCRE as clinical system of record
- Who decides
- The operator, on the operator’s timetable
Evidence posture. Connector coverage below is stated at its Product Record state — the third-party source-system connector framework is BUILT as a framework and exercised against vendor-documented interfaces and synthetic fixtures. No third-party integration runs in an operator production environment. Read every connector row as scope, not as a deployment. Last reviewed August 30, 2026.
Configurations
Two named configurations, one rule that never bends
Both are supported deployments. The rule that holds across both is that exactly one MAR is authoritative at all times.
| Configuration | Clinical system of record | Data direction | Authoritative MAR | Who it suits |
|---|---|---|---|---|
| Configuration A — Governed coexistence | The operator’s incumbent clinical system | SeniorCRE reads one direction only; no clinical write-back | The incumbent eMAR remains the single authoritative MAR | Operators mid-contract, mid-survey cycle, or unwilling to touch clinical workflow while they settle governance first |
| Configuration B — SeniorCRE as clinical system of record | SeniorCRE’s own EHR and eMAR | Clinical documentation and medication administration occur in SeniorCRE | SeniorCRE’s eMAR is the single authoritative MAR | Operators choosing to consolidate the clinical and operating record, on their own timetable |
Architecture
Governance above the systems you already run
Layer 1 — Source systems (unchanged)
Layer 2 — Immutable landing and lineage
Raw payloads retained as received, each field tagged with source system, source identifier, interface and extraction timestamp.
Layer 3 — Canonical entities
Layer 4 — operator-controlled operating record
Accepted value, rejected value, basis of acceptance and restatement history. When systems disagree, the operator governs.
Layer 5 — Consumers
Board and lender reporting, operating reviews, BI tools, and AI workflows that read the governed record rather than the raw sources. Govern the truth before you automate the decision.
Source to operator-controlled operating record
What is read, and what is governed
| Canonical entity | Typical source fields | Authority rule | Reconciliation test |
|---|---|---|---|
| Resident | EHR resident master, CRM prospect record, billing account, unit roster | Clinical system of record for clinical identity; operator-declared identity key for the governed record | Deterministic match on name, date of birth and admission date; unmatched records surface as an exception, never a silent merge |
| Care Plan | EHR assessments, service plans, MAR, acuity scoring | One authoritative MAR. The clinical system of record governs clinical content | Acuity level and service minutes reconciled to the billed level of care; variance is reported, not resolved by preference |
| Ledger | General ledger, AR sub-ledger, billing system, payroll register, agency invoices | General ledger is authoritative for posted amounts; source systems are authoritative for pre-posting activity | Period totals tie to the GL within a written tolerance before any derived metric is published |
| Shift | Scheduling system, time and attendance, payroll worked hours, agency invoice detail | Payroll worked hours are authoritative for hours paid; the schedule is authoritative for intent | Scheduled, worked and paid hours reconciled to the same period; agency hours cause-coded |
| Property/Unit | Property management system unit table, occupancy roster, CRM move-in pipeline | Property management system is authoritative for the unit inventory | Physical, licensed and available unit counts held as distinct fields so census is never computed from an ambiguous denominator |
| Entity | Chart of accounts, legal entity register, ownership and management agreements | Operator-declared entity structure | Every property maps to exactly one operating entity per effective date, with history retained |
Doctrine
Access is not authority
Govern first. Replace only by choice.
SeniorCRE has built clinical record surfaces; medication administration and eMAR remain roadmap — not built. It can run alongside an incumbent clinical system, reading one direction only, with that system’s MAR authoritative. Any future SeniorCRE clinical system-of-record function must clear its own Production-Entry Gates and operator acceptance.
Access is not authority. A vendor that can read your data has access; the operator who decides which value the business accepts has authority. Integration delivers the first. Only a governed record delivers the second.
The distinction is developed further in hosting versus governing and in the integration posture.
Lineage
What coexistence has to prove
DATA
Where did this value come from?
Every field carries its source system, source identifier, extraction timestamp and interface used. A value with no traceable origin is not admitted to the record.
TRUTH
Which value does the operator accept?
When two systems disagree, both values are retained, the conflict is raised, and the governed record shows the accepted value plus the rule or the named person that accepted it.
DECISION
What was decided on this number?
Decisions reference the record version they were made against, so a later restatement does not quietly rewrite the basis of a past decision.
EXECUTION
What happened next, and who confirmed it?
Actions taken from the record are logged with the confirming human. Nothing writes back into a source system without an explicit, scoped, operator-authorised write.
Frequently asked questions
Can I integrate senior housing & care systems without replacing my EHR?
Yes. The default deployment reads the incumbent clinical system one direction only and governs the operating record above it, leaving clinical documentation, medication administration and survey workflow unchanged. The operator keeps the clinical system as its clinical system of record until it decides otherwise.
What does “read one direction only” mean in practice?
Clinical data flows out of the incumbent system into the governed record and nothing flows back. No orders, assessments, medication records or clinical notes are created, modified or synchronised into the clinical system, so there is no possibility of a competing clinical record and no change to the clinician’s workflow.
Will there be two medication administration records?
No. Exactly one MAR is authoritative at all times. In governed coexistence that is the incumbent eMAR. If an operator chooses SeniorCRE as its clinical system of record, SeniorCRE’s eMAR becomes the single authoritative MAR, and any transition is sequenced so that the authoritative MAR is unambiguous on every day of the change.
Does SeniorCRE include clinical capability of its own?
Yes. SeniorCRE has built clinical record surfaces; medication administration and eMAR remain roadmap — not built. A future clinical system-of-record function may proceed only after its own Production-Entry Gates clear. Whether an operator uses that capability is a configuration decision, not a limitation of the platform. Clinical surfaces are stated at their Product Record maturity state, and no clinical outcome, diagnostic or performance claim is made.
What is the operational advantage of governing before replacing?
Sequencing. Replacing a clinical system while the definitions of census, acuity and worked hours are still contested means migrating a disagreement. Governing first produces a reconciled, lineage-complete record that makes any later system decision reversible in judgment and comparable in history.
Does the incumbent vendor need to cooperate?
The operator needs the interface access its own agreement provides — a published API, HL7 v2 feed, FHIR endpoint or scheduled extract. Permitted uses and any fees are governed by the operator’s contract with that vendor, and operators should confirm scope with the vendor and their own counsel.
Evidence behind the evaluation
These pages carry the governance and clinical evidence a shortlist cannot: source authority rules, escalation controls, data limits, and survey-ready evidence.
- senior housing & care data governance for multi-state portfolios
How differing state definitions and survey regimes are governed in one record.
- human review and escalation controls for clinical AI
Mandatory human review, escalation paths, and what the system may never do.
- clinical AI data sources and limitations
What the signals are computed from, and where the evidence stops.
- how to evaluate senior housing & care software for 10+ locations
Six-criteria, vendor-neutral evaluation frame for multi-state portfolios.
Continue in this cluster
Data integration for senior housing & care
The pillar: canonical entities, connector coverage, lineage and the phased sequence every page here shares.
Combining PointClickCare® with accounting and payroll data
How clinical census and acuity from an EHR reconcile against the general ledger and worked payroll hours in one governed record.
Connecting EHR, CRM, payroll and general-ledger data
The four-system join: which system is authoritative for which field, and how conflicts are resolved rather than averaged.
Acquisition-day integration
What has to be connected, reconciled and owned before the first close-day board number is defensible.
Multi-state data governance
One authoritative source per field across states that define census, acuity, staffing and incidents differently — without forking the record.
Integration implementation checklist
The stage-gated checklist: definitions and entitlement, read-only connection, reconciliation, then authority — each item with an owner and an evidence test.
Data integration platform buyer’s guide
Nine evaluation criteria instead of connector counts, the categories of approach and where each one structurally stops.
Operator-controlled operating record and integration architecture
Six entities with declared grain and identity rules inside a five-layer read-only architecture, from landing and lineage to governed consumers.
- Connector inventory: Integration ecosystem · Integration posture
- Canonical model: One Operator-Controlled Operating Record · The operating record · What is a senior housing & care operating infrastructure?
- Comparisons: SeniorCRE vs PointClickCare® · SeniorCRE vs Yardi® · Hosting versus governing
Bring your own systems to the conversation
The useful version of this discussion is your actual stack, your actual contested numbers, and the reconciliation you cannot currently produce on demand.
PointClickCare® is a registered trademark of PointClickCare Technologies. MatrixCare® is a registered trademark of ResMed. Yardi® is a registered trademark of Yardi Systems, Inc. DocuSign® is a registered trademark of DocuSign, Inc. Salesforce® and Tableau® are registered trademarks of Salesforce, Inc. Power BI® and Microsoft® are registered trademarks of Microsoft Corporation. QuickBooks® is a registered trademark of Intuit Inc. ADP® is a registered trademark of ADP, Inc. Oracle® is a registered trademark of Oracle Corporation. All other product names, logos, and brands are property of their respective owners. SeniorCRE is an independent platform and is not affiliated with, endorsed by, or sponsored by any of the aforementioned companies. Comparisons are based on publicly available information and may not reflect all product capabilities.