HIPAA-compliant infrastructure

SOC 2 Type I certified and built for HIPAA. Here is what happens to practice data on every call.

10,000+

connected practice locations

15+

systems behind one API

HundredsHundreds

of healthtech developers on one API

99.9%

uptime SLA

SecurityData protectionComplianceCustomers

What protects the data

HIPAA compliant

Full HIPAA compliance with administrative, physical, and technical safeguards.

SOC 2

Security controls audited by an independent firm.

AES-256 encryption

Encrypted at rest with AES-256 and in transit with TLS.

BAA included

A Business Associate Agreement comes with every production account.

How data is protected

One path from the practice system to your app, encrypted the whole way.

Practice data
US AWS
In transitTLS, every call
At restAES-256
RegionUnited States
AccessOnly practices that authorized you
KeysSandbox and production, separate
AgreementBAA on every production account
HIPAA compliant · SOC 2 Type I certified

Encrypted end to end, scoped to each practice

Synchronizer reads from the practice system over TLS, stores the replica encrypted at rest with AES-256 in US AWS regions, and serves it to your app through short-lived bearer tokens issued from your API key. Each key sees only the practices that authorized it, with separate sandbox and production keys. A Business Associate Agreement comes with every production account.

Request the security packet

Compliance and certifications

What we are audited against.

HIPAA compliant

Administrative safeguards

Physical safeguards

Technical safeguards

BAA agreements included

SOC 2 Type I

Independent audit

Security controls

Availability monitoring

Confidentiality measures

Who builds on Synchronizer

Align TechnologyDentina.AIRevenueWellTruelark by WeaveYobiDearDoc

Operation Dental: 25% more new patients with a custom scheduling API

“Technology is a big part of what we do. When all the small tasks don’t quite fit, we build our own.”

Dave Womble, Chief Marketing Officer, Operation Dental

Read the story
A medical assistant on the phone at a clinic front desk

Common questions

Is it HIPAA compliant, and do I need a BAA?

NexHealth is HIPAA compliant and SOC 2 Type I certified. Data is encrypted in transit and at rest and stored in US AWS. A Business Associate Agreement with NexHealth is part of the developer portal license, at no extra cost, and we’ll send a countersigned copy on request. You still need your own BAA with each practice you serve. Security documents are in our trust center.

Do I need permission from the practice system vendor?

No. The practice owns its data and gives written permission for access. You sign one agreement and one BAA, with NexHealth, not one with each software vendor.

Who owns the data?

The practice does. Synchronizer keeps a replica of the practice database in NexHealth’s cloud so your API calls are fast and the practice’s own server is never under load. The BAA and API license govern how that data is used, and it isn’t used for anything else.

Where is data stored, and how is it protected?

In US AWS regions. Data is encrypted at rest with AES-256 and in transit with TLS. Security documents, including the SOC 2 report, are in the trust center.

Talk to our team

Security review, BAA and data flow questions.