Expensive problems start invisible.The nine trust markers enterprise buyers evaluate — documented, enforced, reviewable.

Enterprise procurement in senior housing & care doesn’t ask many questions out loud. It evaluates the same nine markers, quietly, before any pricing conversation. This page documents each marker in the language of the people who sign — Chief Compliance Officers, CISOs, REIT asset managers, lender credit committees, and multi-state operators.

1 · Current assurance status

SeniorCRE operates HIPAA-safeguarded security and privacy controls, including encryption at rest and in transit, role-based access control, and comprehensive audit logging. The platform is BAA-ready; operator BAA execution is a pilot-readiness gate and no LLM-provider BAA is in place. Multi-tenant architecture enforces data isolation between operators, with tenant-layer RLS hardening active. The underlying AWS infrastructure is covered by AWS’s own SOC assurance reports; SeniorCRE does not claim SOC 2 certification or its own SOC 2 report. Control-readiness evidence is collected internally alongside HIPAA, and any SeniorCRE SOC 2 report will be published only if and when one is issued.

2 · HIPAA posture

HIPAA-safeguarded today. Controls are operating in production; the SOC 2 report is the attestation that the controls work as designed.

3 · Architecture overview

Operator-controlled definitions, source authority, reconciliation, preserved alternatives, and lineage govern the stack. The systems may stay in place; authority is explicit for each decision.

• Governed data layer (C1/C2)
  Accepted resident, care-plan, ledger, shift, property/unit, and entity records preserve definitions, source authority, reconciliation state, alternate values, and lineage.
• Operator-Controlled Operating Record
  Clinical, financial, workforce, CRM, and compliance evidence governed with definitions, source authority, reconciliation, and lineage.
• Operational intelligence surface (C3)
  Target-state portfolio rollups, threshold alerts, NOI modeling, and capital-facing telemetry read from accepted records after authority is declared.
• AI grounding
  SeniorCRE Intelligence surfaces are designed to cite accepted records, definitions, and lineage. AI features are on the post-pilot roadmap and not in pilot scope.
• Edge & integration
  Serverless functions for integration, signed-URL access to PHI, and transactional email via Resend.
• Identity & access
  Enterprise authentication with MFA, role-based access checks, and property-level tenant isolation enforced at the database.

4 · Interoperability standards

Operators do not adopt SeniorCRE on a blank slate. Governed ingestion preserves incumbent-system authority first; replacement happens only where the operator chooses it.

5 · Deployment methodology

Procurement asks how long it takes and what breaks. The answer is a published, renewal-aligned path that retires vendors at their natural breakpoints.

1. Step 1 · support@seniorcre.com scoping
   Scope sources, integration map, RBAC mapping, success criteria, and the Trust-by-Design procurement package.
2. Step 2 · Validate one community
   Run a bounded historical validation with identities, residents, ledger, and schedule records from operator-declared sources of authority.
3. Step 3 · Parallel-review one close cycle
   Compare against a month-end close and document census, AR, eMAR, and payroll disagreements before any production acceptance decision.
4. Step 4 · Renewal-aligned decision
   Retain systems that work and replace only where the operator chooses. Accepted records preserve authority, reconciliation, and lineage.
5. Step 5 · Open the capital surface by approval
   Target-state property-level access controls expose approved capital evidence to REITs, PE, lenders, and allocators with the documented role hierarchy and audit logging on every read.

6 · Security framework

• SOC 2: No SeniorCRE certification or report is claimed. The underlying AWS infrastructure is covered by AWS’s own SOC assurance reports, which are not a SeniorCRE report
• HIPAA Compliance: BAA available, PHI protection, audit logs
• GDPR Compliance: Data privacy, right to erasure, consent management
• CCPA Compliance: California privacy rights, data disclosure
• State Licensing: Meets state-specific senior care regulations
• Penetration Testing: No completed independent penetration-test report claimed
• Vulnerability Scanning: Continuous automated scanning
• Incident Response: 24/7 monitoring and response plan

7 · Audit logging

Immutable, append-only audit logs with UTC millisecond timestamps, full user/session context, and 7-year retention to support regulatory and forensic requirements.

Every PHI read, every role grant, every export request, and every administrative action is written to an immutable append-only log scoped to the same entity hierarchy as the read path. Survey, SOC 2, and HIPAA evidence assemble from a single query, not nine.

8 · Role-based permissions

Role-based access control with a documented role hierarchy is enforced at the database, scoped by property, and audited. Permissions are auditable and revocable per role.

Family-channel access is governed separately: medications and diagnoses are strictly excluded by both policy and tenant-isolation controls — never surfaced through the family portal under any role.

9 · Enterprise scalability

A Holding Co → Operator → Region → Property → Unit hierarchy lets multi-state, multi-payer, multi-entity ownership preserve source authority, reconciliation, and lineage across accepted records. The same architecture is designed to serve a single-property operator and a 200-property REIT portfolio without forking the audit log.

• Multi-state regulatory variance
  State-by-state licensing, payer rules (SNF / AL / IL), and survey readiness handled inside the operational model — not in spreadsheets.
• Portfolio rollups computed at request time
  Census, NOI, agency exposure, payer mix, and covenant evidence aggregate across every property, computed from the Operator-Controlled Operating Record at request time.
• Cross-tenant access
  Hardened multi-tenant access layer tied to the authenticated session. Strong tenant isolation, audited against HIPAA requirements.
• Capital-layer access
  REITs, PE, lenders, and allocators read the same operator-controlled operating record as the operator on the floor — with property-level access controls and audit logging on every read.

The Trust-by-Design procurement package

For enterprise procurement teams, the full evidence inventory — control narrative, architecture diagrams, RBAC matrix, audit-log schema, BAA template, sub-processor list, penetration-test plan, and migration runbook — is available under NDA as the Trust-by-Design package. Request it from support@seniorcre.com.

Mutual NDA — download & execute

Most procurement teams start here. The SeniorCRE mutual NDA is a standard two-year, Texas-governed instrument that covers the Trust-by-Design package (SIG Lite, CAIQ, architecture diagrams, control narrative, incident response plan, and pen-test scope). Reasonable redlines are returned by counsel within one business day.