Build HIPAA-compliant apps
What you need before an app stores health information (PHI) on Tadabase: a signed BAA, a HIPAA-designated app, and the security settings to configure.
- Verified Nov 17, 2026
- Classic builder
On this page
This page is for customers who want to store or process protected health information (PHI) in a Tadabase app. It explains what has to be in place before any PHI goes into the app, and which settings you configure to meet your side of HIPAA's technical safeguards.
What HIPAA asks for, in brief #
HIPAA is the US law that protects patient health information. It applies to healthcare providers, health plans and clearinghouses (covered entities) and to the business associates that handle PHI for them. When PHI is stored or sent electronically (ePHI), the HIPAA Security Rule asks for administrative, physical and technical safeguards: control who can access the data, record activity, protect the data from improper change, confirm who users are, and protect data in transit. See the HHS Security Rule guidance.
Compliance is shared. Tadabase runs the hosting, the database and the platform controls under the BAA. You decide who uses your app, what each user can see, and how your organization handles PHI.
Get a BAA and a HIPAA app #
- Contact Tadabase Contact us and say which apps will hold PHI. HIPAA has to be enabled for your account; it is not switched on by default on any plan.
- Sign the BAA Review and sign the Business Associate Agreement with Tadabase.
- Have your app designated Tadabase places each app that will hold PHI on a HIPAA database and turns HIPAA on for it. Having HIPAA on your account does not, by itself, make any app HIPAA.
- Configure the app Set up the controls in the checklist below before you load any PHI.
Only the apps Tadabase has designated are covered. Keep PHI out of every other app in your account, including copies and test apps.
Checklist: settings to configure #
| Control | What to do | How |
|---|---|---|
| Password rules | Require long, complex passwords and block reuse of old ones | User security |
| Two-factor sign-in | Require an emailed code at sign-in for app users | Login methods |
| Auto logout | Sign users out after a short time away, such as 15 minutes | Log users out automatically after inactivity |
| IP restrictions | If your users work from known networks, allow only those addresses | Allow or block app access by IP address |
| Page and layout security | Make every page and layout that shows PHI require login and the right roles | Pages, Layouts |
| Record-level security | Give each role only the records and fields it needs | Control which records each user can see |
| Secure files | Store documents with PHI in file fields with Secured on, and restrict who can download them | Attachments field, File logs |
| Record change and delete logs | Turn on logging for every table that holds PHI | Record history |
| Login logs and sessions | Review sign-ins, failed logins and active sessions regularly | User logs |
| Backups | Confirm backups run and test a restore | Backing up and restoring your app |
| Builder access | Turn on 2FA for every builder account and share the builder only with people who need it | Secure your Tadabase builder account, Sharing your app builder |
Good practices on your side #
- Train everyone who uses the app on handling PHI, and keep a record of the training.
- Give each person their own login. Never share app or builder accounts.
- Review who has app and builder access on a schedule, and remove people who leave right away.
- Give API keys clear names, and delete keys you no longer use.
- Keep written procedures for access reviews, incidents and breach notification.
Was this page helpful?
Something wrong or missing on this page? Tell us.