Yes, SeniorCRE can be your clinical system of record. Whether it is, is your call.
SeniorCRE is the operator-controlled operating infrastructure for senior housing & care. Its clinical record surfaces are built; medication administration build-out remains roadmap — not built. After the applicable clinical-safety and acceptance gates are cleared, an operator may select SeniorCRE for defined clinical system-of-record functions. Until then, no community runs SeniorCRE as its clinical system of record.
The direct answer
SeniorCRE is designed for two operator-selected clinical configurations. Operators may retain their incumbent EHR/eMAR and govern clinical data through the SeniorCRE operating record, or, after build, validation, clinical-safety, and acceptance gates are cleared, select SeniorCRE’s native clinical capabilities for defined clinical system-of-record functions. Clinical configuration is an operator choice—not a prerequisite for adopting SeniorCRE’s operating infrastructure.
How it would be deployed remains the operator’s choice: after the required gates are cleared, SeniorCRE may carry defined clinical system-of-record functions, or it may run alongside an operator’s existing eMAR, reading one direction only, so one medication record remains authoritative.
Its architectural core is the Operator-Controlled Operating Record: the governed record itself, with defined rules for which system wins when two disagree and full lineage to source.
Is this replacing my eMAR?
Only if the operator decides it should and the required build, clinical-safety, validation, and acceptance gates are cleared. In a parallel configuration SeniorCRE does not write to the MAR — it reads one direction only so exactly one medication record stays authoritative. The configuration is written down before production entry or acceptance, per community. Maturity, stated plainly as of September 29, 2026: medication administration and eMAR remain roadmap — not built, other clinical functions have not passed operator-production readiness review, and no independent validation or clinical sign-off has been performed.
Two configurations, written down before go-live
SeniorCRE as the clinical system of record
Target configuration after build, clinical-safety, validation, and acceptance gates are cleared: SeniorCRE’s EHR and eMAR would carry care planning and medication administration. No community uses this configuration in operator production today.
- Medication administration
- Target state after all function-specific gates clear: written in SeniorCRE’s eMAR. Not available today.
- Care plan
- After complete workflow validation and operator acceptance: authored in SeniorCRE’s clinical record against the governed resident record.
- Data direction
- Ancillary systems (pharmacy, labs, payroll, GL, CRM) exchange data with SeniorCRE; there is no second clinical record to reconcile.
- Choose this when
- The operator is consolidating a clinical stack, standing up new communities, or replacing a clinical system at renewal.
SeniorCRE alongside an existing eMAR, reading one direction only
The incumbent clinical system keeps medication administration. SeniorCRE reads from it and does not write to it, so exactly one medication record is authoritative.
- Medication administration
- Written in the incumbent eMAR. SeniorCRE’s eMAR is not enabled for those communities.
- Care plan
- Authored in the incumbent clinical system; consumed in SeniorCRE with lineage.
- Data direction
- One direction only — inbound to SeniorCRE. A parallel configuration must never create two writable medication records.
- Choose this when
- The clinical stack is stable, mid-contract, or surveyor-sensitive, and the operator’s first objective is governed reconciliation across care, labor, revenue, compliance, and NOI.
One authoritative medication record
One authoritative medication record per community, always. In a parallel configuration SeniorCRE reads and never writes the MAR, because two writable medication records is a patient-safety failure mode, not an integration preference.
What a DON asks first
Is this replacing my eMAR?
Only if the operator decides it should and the required build, clinical-safety, validation, and acceptance gates are cleared. In a parallel configuration SeniorCRE does not write to the MAR — it reads one direction only so exactly one medication record stays authoritative. The configuration is written down before production entry or acceptance, per community. Maturity, stated plainly as of September 29, 2026: medication administration and eMAR remain roadmap — not built, other clinical functions have not passed operator-production readiness review, and no independent validation or clinical sign-off has been performed.
What clinical functions are available today?
Clinical record, care-planning, documentation, vitals, and incident surfaces are built. Medication administration and eMAR remain roadmap — not built. Technical capability does not establish operator reliance.
Why do most deployments keep the incumbent eMAR?
Medication administration and eMAR remain roadmap — not built. In a parallel configuration SeniorCRE reads one direction only, so the incumbent medication record remains authoritative and no operator reliance is implied.
Could two medication records ever be writable at once?
No. One authoritative medication record per community is a hard rule. Today the incumbent MAR remains authoritative. Any future SeniorCRE medication function requires its own build, clinical-safety, data, workflow-validation, and operator-acceptance gates.
What happens when the clinical record and another system disagree?
The Operator-Controlled Operating Record carries survivorship rules written in advance — which system wins, for which field, under whose authority — with full lineage back to the source row. When systems disagree, the operator governs.
Do AI agents administer medications?
No. Medication administration is excluded from agent scope. Agents are record-native, human-approved, and operator-authorized; a clinician remains the actor of record.
Decide the configuration with your clinical leadership in the room
The briefing walks the record, the survivorship rules, and the configuration decision per community — with the DON, not around her.
Request an Executive Briefing