Security + Compliance
MedReception answers every patient call, captures intake, and routes to providers without ever putting PHI at risk. Encryption, BAAs, audit logs, and redaction tools are built in so legal and security teams sign off fast.
Proof point
We sign a BAA and define allowed PHI workflows before routing your first call.
Proof point
Structured call summaries with redaction controls plug into Epic, Cerner, and CareStack.
Proof point
Provider handoffs move through TLS 1.2+ channels with access logging for every view.
Why HIPAA matters
Most AI phone agents were built for retail call centers. Medical groups pay the price in fines and reputational damage. Here are the failure modes your compliance team watches for:
Integrates anywhere
MedReception pushes summaries and structured intake back into Epic In Basket, Cerner messaging, CareStack workflows, or Weave inboxes without storing PHI longer than necessary. HL7, FHIR, secure email, SFTP, and webhook delivery are all supported.
• Automatic redaction for medications + diagnoses
• Role-based routing to billing, referrals, or nursing pods
• After-hours policies that align with your on-call tree
Battle-tested comparisons
Share these comparison briefs when stakeholders ask how MedReception handles PHI versus traditional answering services or phone-platform AI.
FAQ
Will you sign a BAA before launch?
Yes. Every medical customer receives a signed Business Associate Agreement plus a HIPAA scope of services before go-live.
How is PHI encrypted?
Voice, transcripts, routing metadata, and attachments are encrypted in transit (TLS 1.3) and at rest (AES-256). Access is gated by MFA and role-based controls.
Where are logs stored?
All audit logs remain in US-based cloud environments with configurable retention windows so compliance teams can run investigations anytime.
We’ll route sample calls through your scripts, show the encryption trail, and hand over the BAA + controls checklist.
