---
title: "A HIPAA and GDPR Checklist for Founders Before You Write a Line of Code"
url: "https://doccure.io/hipaa-gdpr-checklist-for-founders/"
updated: "2026-11-13T05:04:59+00:00"
type: "post"
business:
  name: "Doccure"
  phone: "+44 7438 823475"
  location: "City Business Centre, 11a Lower Road, London SE16 2XB, United Kingdom"
---

# A HIPAA and GDPR Checklist for Founders Before You Write a Line of Code

Most healthcare founders meet HIPAA and GDPR for the first time when a hospital or an employer sends a security questionnaire, usually a week before a deal should close. By then the product is built, and some answers are “no”. This checklist is meant for the other end of the project: before a developer writes anything. It is general information for founders, not legal advice. Laws differ by country and change, so confirm the details with a lawyer.

## First, the two laws in a paragraph each

**HIPAA** is United States law. It applies to healthcare providers, health plans and clearinghouses, called covered entities, and to the vendors that handle patient information for them, called business associates. If you sell software to US healthcare organisations, you are probably a business associate, and you will be asked to sign a business associate agreement (BAA).

**GDPR** applies when you handle personal data of people in the European Union, and the UK has its own equivalent. It does not matter where your company is. Health data is a special category with stricter conditions.

Two things to know about both. Neither has an official certificate, so be wary of anyone selling one. And neither is satisfied by software alone. They are about how your organisation behaves.

## Part 1: decisions to make before any code

1. **List the countries your patients and customers will be in.** That tells you which laws apply. A US employer brings HIPAA. A patient in France brings GDPR. India, the Gulf states and others have their own rules.
2. **Write down every piece of personal and health data you plan to collect.** For each, ask why you need it. If you cannot say, do not collect it.
3. **Decide your role.** Are you the provider of care, or a vendor to providers? Under GDPR, are you the controller or a processor? The contracts you need follow from this.
4. **Decide where data will be hosted.** Some customers and regulators expect a particular country or region.
5. **Name the person responsible.** One person owns privacy and security, even in a team of three.

## Part 2: vendors

6. **List every outside service that will touch patient data:** hosting, database, email, SMS, video, AI, analytics, error logging, support desk.
7. **For each, confirm it will sign a BAA or data processing agreement, and on which plan.** Many do so only on higher tiers.
8. **Remove those that will not,** or keep patient data out of them entirely.
9. **Watch the quiet ones.** Error logs, analytics and chat widgets collect patient data by accident more often than any other tools.

## Part 3: what the software must do

10. **Unique sign-in for every user.** No shared accounts.
11. **Role-based access.** Each role sees the minimum it needs.
12. **Separation between customers.** If you serve several organisations, each one’s data is kept apart, ideally in the database itself and not only in the application.
13. **An audit trail.** Who viewed or changed which record, and when, in a form that shows tampering.
14. **Encryption** of data in transit and at rest.
15. **Consent records.** What the patient agreed to, when, and the wording they saw.
16. **Patient rights.** A way to give a patient a copy of their data, correct it and, where the law allows, delete it.
17. **Retention.** How long each type of record is kept, and how it is removed afterwards.
18. **Automatic sign-out** and sensible password or passkey rules.
19. **Backups, with a tested restore.**
20. **No patient data in notifications.** An SMS says “you have an appointment”, not what it is for.

## Part 4: if you use AI

21. **Know which AI provider receives data,** and have an agreement with it.
22. **Remove identifying details before sending** where you can.
23. **Give customers a way to switch AI off.**
24. **Keep a clinician in the loop,** and say so to users.

## Part 5: the organisation

25. **A written risk assessment.** HIPAA requires one. A few honest pages are better than a template nobody has read.
26. **Policies your team actually follows:** access, devices, passwords, leaving staff.
27. **Training** for everyone who can see patient data, with a record of it.
28. **An incident plan.** Who decides, who is told, and within what time. GDPR’s reporting deadline for serious breaches is 72 hours.
29. **A register of agreements** with customers and vendors, with expiry dates.
30. **A privacy notice** in plain language that matches what the product really does.

## Part 6: before launch

31. **Test the permissions.** Log in as each role and try to see what you should not.
32. **Have someone independent test security.**
33. **Use invented data in development and demos.** Never copy real patients into a test system.
34. **Prepare your answers.** Write a short security summary you can send to customers.

## Common mistakes

- Believing that a hosting provider’s compliance makes your product compliant. It covers their part only.
- Free tiers of tools used “just for the pilot” with real patients.
- Screenshots of real records in sales decks.
- Developers with standing access to the production database.
- Collecting everything “in case it is useful”.
- Claiming to hold a HIPAA or GDPR certificate. No such certificate exists.

## What you inherit when you start from a platform

Parts 3 and 4 are software, and they are most of the engineering work. If you launch on an existing healthcare platform, you inherit that work. Parts 1, 2, 5 and 6 remain yours whichever route you take.

On Doccure:

- Each organisation’s data is isolated by Postgres row-level security.
- Record access and changes go to a tamper-evident audit trail, and patients can see who viewed their record.
- Consent is recorded for care, telehealth, recording, marketing and data sharing.
- Prescriptions and lab results carry tamper-evident signatures.
- PHI is redacted before data is sent to an AI provider, and AI can be turned off.
- Card data never touches Doccure servers. Payments are processed by PCI-compliant gateways.
- Registers are provided for BAAs with expiry alerts, breaches, data-subject requests and retention.

Doccure is HIPAA-ready and GDPR-ready. We sign a BAA. The details are in the [Trust Center](/trust-center/).

## Frequently asked questions

### Is there a HIPAA certificate?

No. There is no official government certificate for HIPAA or for GDPR. You show compliance through your controls, documents and agreements.

### Does HIPAA apply to my startup?

If you handle patient information for US healthcare providers or health plans, almost certainly, as a business associate.

### Does GDPR apply if my company is outside Europe?

Yes, if you offer services to people in the EU or UK or monitor their behaviour.

### What is a BAA?

A business associate agreement: the contract HIPAA requires between a healthcare organisation and a vendor that handles patient information for it.

### Can I add compliance after the pilot?

The software parts are far cheaper to design in from the start, and you may not use real patient data without them.

## Want to skip the engineering half?

See what is already in place in the [Trust Center](/trust-center/), read about [custom development](/custom-development/) on Doccure, or [book a 30-minute call](/book-a-demo/).
