At a glance

  • BAA available before production PHI

    Available for review before production PHI is connected.

  • Human approval on family send

    Sensitive updates always require a named approver.

  • AI boundaries

    No diagnosis, no prescribing, no autonomous family messages.

  • Audit trail

    Every signal, override, and approval is recorded with source.

  • Export & deletion

    Operator data leaves on demand. Backups roll off on schedule.

  • Incident response

    Written plan; affected operators notified without unreasonable delay.

Trust

HIPAA & AI use

How AcuityRow handles PHI as a business associate, designed for HIPAA-aware workflows, and where AI authority stops.

Last reviewed: July 26, 2026

This is an audit-update date, not a legal approval date. AcuityRow, Llc will publish an approved effective date here once counsel signs off.

Section 01

Overview

AcuityRow supports senior-living operators that handle PHI. The system drafts, clusters, and summarizes care-loop information for review; the operator remains responsible for care decisions, family communication, and compliance obligations.

AcuityRow is designed for HIPAA-aware workflows. It is not certified under HIPAA, SOC 2, or HITRUST, and this page does not claim guaranteed compliance.

Section 02

HIPAA posture

AcuityRow, Llc acts as a business associate to senior living operators that are covered entities or business associates themselves. A business associate agreement (BAA) is available for review and execution before production PHI is connected. The BAA controls in any conflict with these public statements.

Our operational program addresses the HIPAA Privacy, Security, and Breach Notification rules: administrative, physical, and technical safeguards; workforce training; access controls; incident response; and breach notification procedures.

Section 03

Minimum necessary access

Internal access to PHI is least-privilege. Engineers do not have routine production data access. Time-bound, audited break-glass access is used for incident response and is logged for review.

  • Role-based access inside the operator product (caregiver, nurse, manager, family).
  • Workforce SSO and MFA on internal systems.
  • Quarterly access reviews on operator-impacting systems.

Section 04

Where AI is used

AcuityRow uses AI inside three operator-facing surfaces:

  • Care Signals. Cluster and rank observations from the EHR, eMAR, PT logs, and incident reports.
  • Family Loop. Draft family-facing language from approved source observations, scoped by the operator's policy controls.
  • Survey Trail. Summarize chronological events and attach source links for human review.

Model calls run inside a private inference path under a BAA with the underlying provider. Prompts and outputs are not used to train any third-party model and are not shared across operators.

Section 05

Human review is required

No AI output reaches a resident's family, a surveyor, or a regulator without a named human approver. End-of-life, hospitalization, and incident messages always require an approver assigned by name in the operator's policy.

The approving reviewer is recorded on every delivered family update and on every export from the survey trail. If the approver is unavailable, the draft holds in the queue; nothing auto-sends as a fallback.

Section 06

AI authority boundaries

AI may summarize notes, cluster signals, draft family-facing language, and prepare source-linked review packets. AI may not diagnose, prescribe, approve care plans, determine staffing compliance, or send messages without human approval.

  • Does not diagnose residents.
  • Does not prescribe treatment.
  • Does not submit survey responses.
  • Trigger emergency response or replace the operator's emergency procedures.
  • Does not send family updates without named human approval.
  • Make hiring, scheduling, or disciplinary decisions about staff.

Section 07

Incident response and breach notification

We maintain a written incident response plan covering detection, triage, containment, eradication, recovery, and post-incident review. In the event of a security incident that affects PHI, we notify affected operators without unreasonable delay and cooperate with the operator's own breach notification obligations under HIPAA.

Section 08

Not medical advice, not autonomous clinical decisioning

AcuityRow supports care operations and human review. It is not a medical device, does not deliver clinical care, and does not take autonomous action on behalf of a clinician. Output is decision support for licensed staff — every consequential action (medication, hospitalization, end-of-life conversations, emergency response, sensitive family communication) is owned by a named human and governed by the operator's own clinical and compliance policies.

We do not promise to prevent falls, eliminate staffing shortages, guarantee survey outcomes, or replace licensed clinical judgement. Where AcuityRow surfaces a signal or drafts language, treat it as one input into a human decision, not the decision itself.

Section 09

Operator duties

  • Maintain valid resident and family consent under your jurisdiction's rules.
  • Configure family update policies and approvers before turning on Family Loop.
  • Review the survey trail and audit logs as part of your compliance program, not as a substitute for it.
  • Notify security@acuityrow.com of any suspected security incident on your side.

Questions about this page?

Write us at security@acuityrow.com. A person from the AcuityRow team will reply.

AcuityRow, Llc · 1489 W Palmetto Park Rd Ste 500, Boca Raton, FL 33486, United States · +1 (561) 310-6295 · https://acuityrow.com/

support@acuityrow.com · privacy@acuityrow.com · security@acuityrow.com