Skip to main content

How Sydra handles protected health information.

Every document uploaded to Sydra is protected health information under HIPAA. An operative note, an EOB, an insurance card: all of it. This page documents how it is handled, who can reach it, and what you can request in writing.

Practice executive comparing two payment offers across printed documents

SOC 2

SOC 2 alignment.

Sydra is built to SOC 2 criteria for security, availability and confidentiality. We are aligned to those criteria and are not yet certified against them. The report is available under NDA, and we would rather say that plainly than let the badge imply otherwise.

Safeguards

How Claude via Amazon Bedrock handles your PHI.

Sydra runs on Claude via Amazon Bedrock. Claude is contractually barred from training on your PHI, and Bedrock is covered under our AWS Business Associate Agreement. Your claim data is processed inside the same HIPAA aligned boundary as the rest of your workflow.

AWS Bedrock is a HIPAA eligible service. AWS's HIPAA BAA covers Amazon Bedrock when used in the context of a covered healthcare workload. Sydra operates within that BAA scope.

When Sydra generates an IDR draft from your operative note: the operative note is processed by Claude via Amazon Bedrock. PHI in that document stays inside the AWS HIPAA eligible service boundary. No PHI is transmitted to Anthropic's systems or any other third party during generation. No data is used to train the Claude model or any other model.

Infrastructure and encryption.

  • Hosting: Sydra production workloads run on AWS infrastructure in US regions.
  • Encryption at rest: Documents are stored in Amazon S3 with AES 256 server side encryption. Keys managed through AWS Key Management Service (KMS).
  • Encryption in transit: All data between your browser and Sydra's servers is transmitted over TLS 1.2 or higher.
  • Document access: Documents aren't accessible through persistent public URLs. Retrieval uses signed URLs with short expiry windows (minutes, not days).
  • Database: PHI is stored with row level security. Each practice has a unique tenant identifier. Queries are scoped to the authenticated practice's tenant by default.

Access control and isolation.

Within your practice: Role based access control. You define which staff members can view, draft, approve, or export. Permissions are granted explicitly, not inherited by default.

Between practices: Strict tenant isolation enforced at multiple layers: application logic, API authorization, database row level security, and audit logging.

Within Sydra: Software engineering team access is governed by internal HIPAA training. Sydra Full Service RCM team access to PHI only for practices using Sydra + Support. Leadership access for quality review and escalated cases. No PHI accessible to sales or marketing without an operational need.

Audit logging.

Every log entry captures: user name, email, user ID, timestamp (UTC to the second), action performed, record affected (submission ID, document ID), IP address, session identifier. Logs are available to your account administrator on request.

Business Associate Agreement.

A BAA is available for all covered entities and business associates using Sydra to process PHI. The BAA is executed during contracting. What the BAA covers: permitted uses and disclosures of PHI, our obligation to safeguard PHI, breach notification timelines (60 day notification per HIPAA), your right to audit our compliance, data return or destruction on termination, subprocessor obligations.

If you want to review the BAA template before booking a demo, email sales@sydrahealth.com. We send it the same business day.

Incident response.

Documented incident response procedures covering detection, escalation, containment, recovery, and customer notification. If an incident involves your PHI: We notify you per the timeline in your BAA.

Requesting security documentation.

Available to qualified prospects during evaluation: BAA template, security one pager, subprocessor list (AWS, Stedi, ModMed, and others in scope), AWS Bedrock HIPAA eligibility documentation, SOC 2 report under NDA.

Request: email sales@sydrahealth.com with your compliance contact copied. Response within one business day.

Security FAQ

Is patient data encrypted?

Yes. Documents are stored in Amazon S3 with AES 256 server side encryption, with keys managed through AWS Key Management Service. All data between your browser and Sydra's servers is transmitted over TLS 1.2 or higher.

Is Sydra HIPAA compliant?

Sydra handles PHI under HIPAA controls, running on Claude via Amazon Bedrock, a HIPAA eligible AWS service, and operating within AWS's HIPAA Business Associate Agreement for that workload. Claude is contractually barred from training on your PHI, no PHI is transmitted to Anthropic's systems, and no data is used to train the Claude model or any other model. A standard BAA is available for all covered entities and business associates using Sydra to process PHI.

Who has access to my billing data?

Within your practice, access is role based. You define which staff can view, draft, approve, or export, and permissions are granted explicitly rather than inherited by default. Between practices, strict tenant isolation is enforced at the application logic, API authorization, database row level security, and audit logging layers. Internally at Sydra, software engineering team access is governed by internal HIPAA training, the Full Service RCM team only has access for practices using Sydra plus Support, leadership has access for quality review and escalated cases, and no PHI is accessible to sales or marketing without an operational need.

Where is data hosted?

Sydra production workloads run on AWS infrastructure in US regions.

What happens if there's a security incident involving my data?

Sydra maintains documented incident response procedures covering detection, escalation, containment, recovery, and customer notification. If an incident involves your PHI, notification follows the timeline specified in your BAA, which is 60 days per HIPAA.

Does Sydra share data with payers or third parties beyond what's required to file a dispute?

Subprocessors with access to data in scope are AWS, Stedi, ModMed, and others listed in the subprocessor list available on request. Data submitted in an IDR filing goes to the certified IDR entity and the payer as required by the federal process, consistent with what the dispute itself requires.

Can I get an audit trail of who accessed my data?

Yes. Every log entry captures user name, email, user ID, UTC timestamp, action performed, record affected, IP address, and session identifier. Logs are available to your account administrator on request.

Built on Claude via Amazon Bedrock · Built to support HIPAA safeguards · BAA on request · ModMed and Stedi integrations · SOC 2 aligned, report under NDA · Security details

Clinician and a practice advisor reviewing claim figures on a tablet in a hospital lobby

Book a demo

We'd welcome a short call to see whether this is worth pursuing. Bring one denied out of network claim and you will see what federal IDR would do with it before the call ends.

Or email sales@sydrahealth.com with a question.