Blog
Patient Data Protection Under Indonesia's PDP Law: A Clinic Checklist
A plain-language checklist for clinic owners on handling patient data under Indonesia's PDP Law: consent, access, vendors, breach response, and when to get help.
- mid
- clinic
If you run a clinic in Indonesia, patient records are almost certainly covered by Law No. 27 of 2022 on Personal Data Protection (UU PDP). Health data is listed in the law as “specific personal data,” a category that carries heavier expectations than ordinary customer data such as a name and phone number (CMS).
The short answer: the law’s two-year transition period, which began on enactment on 17 October 2022, has ended, so the obligations are live. You do not need a legal department to start, but you do need a written, repeatable way of handling patient data. The checklist below is a practical starting point, not legal advice.
Where the rules stand
- The PDP Law was enacted on 17 October 2022 with a two-year transitional period (CMS).
- Law firms report that the supervisory authority was slow to arrive. Rajah & Tann noted that a draft Presidential Regulation to establish the authority was made public in February 2026 and was awaiting presidential approval at the time of writing.
- Rajah & Tann reports that Government Regulation No. 33 of 2026 implements the law, with a six-month transition from its 16 July 2026 promulgation (to around January 2027) before administrative sanctions apply to non-compliance with it. That same commentary notes the regulation had not yet been officially published when they wrote, so treat the details as something to confirm.
Because this is moving, ask your lawyer to check the current primary texts before you finalize any policy.
The checklist
1. Know what patient data you hold and where
List every place patient data lives: the clinic system, WhatsApp chats, paper files, spreadsheets, lab emails, staff phones, backup drives, and any vendor platform. Most clinics are surprised by how many copies exist. You cannot protect what you have not mapped.
2. Record consent properly
Commentary on the law indicates that consent should be explicit and provable, and that verbal or implied consent is unlikely to be enough where consent is your legal basis (CMS). Practical steps:
- Use a short registration form in plain Bahasa Indonesia that states what you collect, why, who sees it, and how long you keep it.
- Store the signed or recorded consent with the patient file.
- Do not bundle unrelated uses (marketing messages, promotions) into the same tick-box as treatment.
- Have a process for patients who want to withdraw consent or correct their data.
Other legal bases exist, such as legal obligations, and not everything you do needs consent. Ask your lawyer which basis applies to which activity.
3. Limit who can see what
A receptionist rarely needs clinical notes, and a doctor in one branch rarely needs every branch’s records. Set role-based access, give each person their own login, and remove access the day someone leaves. Shared passwords make it impossible to tell who opened a record.
4. Keep an access trail
You should be able to answer, “Who viewed or changed this patient’s record, and when?” A basic audit trail helps with internal disputes, patient complaints, and breach investigations.
5. Secure the basics
- Encrypted, tested backups stored separately from the main system.
- Screen locks and device passcodes on any phone or laptop that touches patient data.
- No patient files sent through personal messaging accounts where avoidable.
- Updated software and a named person responsible for it.
6. Vet your vendors
Your software provider, cloud host, lab partner, and any marketing agency may handle patient data on your behalf. Ask them in writing:
- Where is the data stored, and who can access it?
- What happens to our data if we end the contract?
- How and how quickly will you tell us about a security incident?
- Can we export our data in a usable format?
Put the answers in the contract. Using an outside vendor does not remove your own responsibility as the clinic.
7. Prepare a breach response plan
Commentary on the law says affected individuals and the authority must be notified within 72 hours of becoming aware of a breach (CMS). Rajah & Tann reports that GR 33 clarifies the 72 hours runs from when a failure is established with certainty and on reasonable grounds, backed by documentation such as system logs. Either way, you cannot meet a deadline if nobody knows who decides.
Write a one-page plan: who is the incident lead, who contacts patients, who contacts your IT vendor, and where the incident log is kept. Run through it once with staff.
8. Decide who owns data protection
Rajah & Tann’s summary of GR 33 says a Data Protection Officer must be appointed when any one of the statutory conditions applies. Whether a small clinic meets one depends on the scale and nature of its processing, so ask your lawyer. Even where it is not required, name one person who owns this topic. Unowned tasks do not get done.
9. Train staff and keep records
Most incidents start with people: a photo of a screen sent to the wrong chat, a lost phone, a clicked phishing link. A 30-minute annual briefing, a short written policy staff sign, and a simple record of what you do and why go a long way.
What goes wrong
- Treating it as an IT project. The software is only one part. Consent forms, staff habits, and contracts matter just as much.
- Over-collecting. Photocopying every ID “just in case” increases what you must protect.
- Forgetting old data. Paper files in a storeroom and old laptops are still patient data.
- Assuming the vendor handles it. They handle their part. You answer to the patient.
What it costs
Much of this is time rather than money: mapping data, rewriting forms, and training staff. Typical paid items are legal review, a security assessment, and possibly software changes. Prices vary widely with clinic size and provider, so get quotes rather than relying on a rule of thumb. The penalties are serious by comparison. The law provides for administrative fines of up to 2% of annual revenue and criminal penalties for offences such as unlawful disclosure or misuse of personal data (CMS).
When to get outside help
Bring in a lawyer or specialist when you operate several branches, share data with partners or overseas providers, use patient photos or data for marketing, suffer a suspected breach, or are choosing a new clinic system. If the system you want does not fit how you work, or you need your existing tools connected with proper access control and logging, that is also a good moment to talk to a technical partner. No software makes a clinic “compliant” by itself. It can support good practice, and your policies and people do the rest.
A conversation, if useful
Teknologia Solutions builds custom software and works with Odoo, and we also offer a clinic management system. If you are reviewing how your clinic handles patient data and want a practical second opinion, we are happy to have a no-charge conversation. No pressure and no obligation.
Sources: CMS, Compliance with Indonesia’s PDP Law by October 2024; Rajah & Tann Asia, PDP Law Updates: the Implementing Regulation; Rajah & Tann Asia, PDP Law Updates: DPA and court rulings. These are secondary summaries by law firms, and the regulatory picture is still developing. Verify everything against the primary legal texts and with qualified Indonesian counsel before acting.