Last updated: August 2026
HIPAA - Subprocessors and Integrations
This page explains how to use the platform when working with Protected Health Information (“PHI”), and which parts of the system are approved for that use.
1. Core (Platform Foundation)
The Core includes the main parts of the platform such as infrastructure, storage, processing, and access controls, and is designed to meet HIPAA requirements, so PHI can be used within the Core, subject to the terms of the BAA.
2. Platform Features (Including Subprocessors)
Features are capabilities within the platform that extend how you use it such as automations, AI tools, workflows, exports, and similar functionality. Some Features may rely on or involve subprocessors.
Some features are Approved for use with PHI and some are not so before using any Feature with PHI, check its status in this document.
Relevant subprocessors for Features: [Subprocessor / Provider Name] [Subprocessor / Provider Name] [Subprocessor / Provider Name]
3. Integrations (Third-Party Services and Subprocessors)
Integrations include external tools, APIs, connectors, or third-party services used with the platform. These are typically operated by third parties and may act as subprocessors.
Some integrations are Approved for use with PHI and some are not so before using any integration to process PHI check its status in this document.
Relevant subprocessors and providers: [Subprocessor / Provider Name] [Subprocessor / Provider Name] [Subprocessor / Provider Name]
To use PHI safely, you are responsible for checking the status of any Feature or Integration before using it and making sure PHI is not sent to non-approved components
Statuses on this page may change as the platform evolves, so you should review this page before using new Features or Integrations with PHI. If you are unsure about a specific use case involving PHI, contact privacy@blocks.diy