SOC 2 Type I certified and built for HIPAA. Here is what happens to practice data on every call.
connected practice locations
systems behind one API
of healthtech developers on one API
uptime SLA
Full HIPAA compliance with administrative, physical, and technical safeguards.
Security controls audited by an independent firm.
Encrypted at rest with AES-256 and in transit with TLS.
A Business Associate Agreement comes with every production account.
One path from the practice system to your app, encrypted the whole way.
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 packetWhat we are audited against.
Administrative safeguards
Physical safeguards
Technical safeguards
BAA agreements included
Independent audit
Security controls
Availability monitoring
Confidentiality measures
“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
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.
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.
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.
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.
Security review, BAA and data flow questions.