AI built to assist your staff — never to replace their judgment
Before we ship any assistant, we ask the same three questions: how it protects resident data, how your staff stay in control of the outcome, and how it holds up against the rules your facility already answers to. Three assistants have met that bar so far — and we hold every future one to the exact same standard, as we grow.
What we promise, in plain terms
A typical AI assisted workflow
AI drafts from what it hears or reads
A first pass only — never the final record.
Staff reviews the draft
Edits, corrects, or discards it — same as reviewing any other note.
Staff approves and signs
Approval is attributed to the reviewing staff member, not the AI.
We recommend only a reviewed draft is charted
Same record, same audit trail as any other entry.
What we do — and don't do — with resident data
Resident data access is governed by your EHR. AI Assistants act on behalf of your staff and access resident data during the session only.
HIPAA Compliant Data Access
Resident data access governed through EHR. EHR compliance extended to AI Assistants.
Data stays inside your facility's record
Resident Data stays within EHR. Never copied anywhere else.
AI Assistants operate under BAA
Relic AI runs on Azure - HIPAA Compliant and covered by BAA
Laws We're Tracking, and How They Apply to Us
AI regulation in healthcare is moving fast, and we keep an eye on it so you don't have to track it alone. As of this page's effective date, here's where things stand. We'll keep this list updated as these laws evolve and as new ones take effect. This page is meant to support your own facility's compliance program — it doesn't replace your facility's own legal notice obligations.
Requires AI developers (like us) to document training data practices, foreseeable risks, and system goals, and to keep that documentation current.
Requires a disclaimer on AI-generated patient communications, unless a licensed provider reviews them first.
Requires telling patients when they’re interacting with generative AI, for healthcare and other regulated professions.
Models and subprocessors we use
We believe you should know exactly which vendors are involved in handling facility or patient data — not just take our word for it. Here’s the full list:
- Cloud infrastructure — Microsoft Azure: hosting, storage, database.
- AI / ML providers — Microsoft Azure AI Service: AI response generation and chat orchestration. Groq: VoIP call listening and listener orchestration.
- Speech / Transcription — Azure Cognitive Services (Speech): audio transcription for clinical documentation.
- EHR integration — Medplum, PointClickCare: chart and records interoperability.
- Communications — Azure Communication Services: email, SMS, in-app messaging.
- Billing — Stripe: payment processing.
This list covers every vendor that can see facility or patient data. It doesn't list internal engineering tools that never touch customer data.
Questions or BAA requests?
Facilities and partners with security, compliance, or BAA questions can reach us directly.