Compliance

Healthcare-grade handling for reminder calls

Clear prototype data handling today, with HIPAA eligible infrastructure and Business Associate Agreements planned before real patient data is processed.

Prototype Deployment

This build is a prototype for validation only. No real patient data should be uploaded or processed at this stage. Database, file storage, and deployment are currently local to the prototype environment.

Planned HIPAA Eligible Infrastructure

When validated, production will migrate to Azure Virginia with Azure Database for PostgreSQL, Azure Blob Storage, and full HIPAA compliance controls. The application is configured through environment variables so this migration can be handled as an infrastructure and configuration change.

Data Handling

  • No real patient data is processed in the current prototype environment
  • Prototype appointment data is processed solely to validate reminder call flows
  • Audio recordings are not retained after call completion
  • Production patient data will be stored within Azure's HIPAA eligible environment in Virginia
  • Data is never sold or shared with third parties

Business Associate Agreement

voice.med is designed to execute Business Associate Agreements before any real patient data is processed. Production deployment will use infrastructure providers covered by appropriate agreements, including Deepgram and Microsoft Azure. BAAs are signed by Realtime Comms Ltd, a company incorporated in England and Wales.

To request your BAA contact hi@voice.med - we typically turn these around within 24 hours via DocuSign.

Voice Infrastructure

Reminder calls are powered by Deepgram's Voice Agent API. Deepgram maintains a signed BAA and HIPAA compliant infrastructure.

Legal Entity

voice.med is operated by Realtime Comms Ltd, a company incorporated in England and Wales.