SATUSEHAT Security: Protecting Health Data Under UU PDP

SATUSEHAT Security: Protecting Health Data Under UU PDP

Indonesia's healthcare sector is becoming increasingly connected. Hospitals, clinics, healthtech companies, laboratories, pharmacies, and pharmaceutical firms are exchanging more data across digital platforms to improve patient care and streamline healthcare services.

At the centre of this transformation is SATUSEHAT, Indonesia's national health data exchange platform. By enabling healthcare providers and other ecosystem participants to exchange health information through standardised digital systems, SATUSEHAT is helping create a more connected healthcare ecosystem.

But greater interoperability also creates greater cybersecurity responsibility.

Every API connection, data exchange, and system integration creates another pathway through which sensitive health information could be accessed, altered, or exposed. For organisations handling patient data, protecting these pipelines is not only a cybersecurity priority. It is also a data protection obligation under Indonesia's Law No. 27 of 2022 on Personal Data Protection (UU PDP).

The challenge is clear: how can organisations integrate with SATUSEHAT while keeping sensitive health data secure?

What Is SATUSEHAT?

SATUSEHAT is Indonesia's national health data exchange platform, developed to connect healthcare facilities and other stakeholders through interoperable health information systems.

The platform aims to improve how health information is exchanged across the healthcare ecosystem, allowing relevant data to move between systems in a more standardised way.

For hospitals and healthcare providers, this can support more connected patient journeys. For healthtech companies, it creates opportunities to build services that work across a wider healthcare ecosystem. Pharmaceutical companies and other organisations can also benefit from better data connectivity where their activities involve healthcare information.

However, interoperability means that security can no longer be managed within one organisation's boundaries. A vulnerability in one connected system could potentially create risks for other systems and organisations in the ecosystem.

Why SATUSEHAT Integration Creates New Security Risks

Connecting to a national health data platform introduces several security considerations that organisations must address before and during integration.

1. More data exchanges

Health information may move between multiple systems, applications, and organisations. Each transfer creates a need for strong authentication, encryption, access controls, and monitoring.

1. Sensitive health data

Health information is highly sensitive and can cause serious harm if exposed or misused. Under the UU PDP, specific personal data includes health information, which means organisations handling it need stronger safeguards.

1. API dependencies

APIs enable systems to communicate, but poorly secured APIs can expose sensitive information or allow unauthorised users to interact with backend systems.

1. Multiple third parties

Healthcare ecosystems often involve hospitals, technology providers, laboratories, insurers, pharmaceutical companies, and other partners. Each connection can introduce additional security and privacy risks.

1. Shared responsibility

Organisations cannot assume that security is entirely handled by the platform they are connecting to. Each organisation remains responsible for securing its own systems, credentials, endpoints, and data processing activities.

Protecting Patient Data Across the SATUSEHAT Ecosystem

Security needs to be considered across the entire data lifecycle, from collection to transmission, processing, storage, and deletion.

1. Secure APIs from the start

API security should be built into the integration architecture rather than added after deployment.

Organisations should use strong authentication and authorisation mechanisms, validate requests, apply rate limits, and monitor API activity. Access should also be restricted to the specific data and functions each application or user requires.

1. Apply strong identity and access controls

Not every employee, application, or third party needs access to the same health information.

Organisations should apply role-based or attribute-based access controls and follow the principle of least privilege. Service accounts and machine-to-machine connections should also have clearly defined permissions and lifecycle management.

1. Encrypt data in transit and at rest

Sensitive health information should be protected when it moves between systems and when it is stored. Encryption helps reduce the impact of unauthorised access, particularly when data travels across networks or is stored in cloud environments.

1. Monitor data access

Organisations need visibility into who is accessing patient information, which systems are making API requests, and whether activity appears unusual. Centralised logging and continuous monitoring can help detect suspicious behaviour, such as unusual access patterns, excessive data requests, or compromised credentials.

1. Minimise the data you share

Interoperability does not mean every connected system should have access to everything. Organisations should only collect, process, and exchange the data required for a specific purpose. Data minimisation reduces exposure and limits the potential impact of a security incident.

Securing Healthcare APIs Against Unauthorised Access

APIs are a critical part of modern healthcare interoperability, but they are also a common attack surface.

A secure API architecture should address several areas.

• Authentication: Verify the identity of users, applications, and systems making API requests.
• Authorisation: Ensure authenticated users and applications can only access the resources they are permitted to use.
• Input validation: Validate API requests to prevent malicious or unexpected data from reaching backend systems.
• Rate limiting: Restrict excessive requests that could indicate abuse or automated attacks.
• Encryption: Protect sensitive health information while it moves between systems.
• Logging and monitoring: Record API activity and detect unusual access patterns.
• Credential management: Protect API keys, tokens, and service credentials throughout their lifecycle.

Security teams should also regularly test APIs for vulnerabilities. A system may appear secure during development but expose weaknesses once it is integrated with external systems and real-world data flows.

SATUSEHAT and UU PDP: What Organisations Need to Consider

SATUSEHAT integration must also be considered within Indonesia's wider data protection framework. Under UU PDP, health information is classified as specific personal data. Organisations that process this information need to consider how they collect, use, store, share, and protect it.

Several requirements are particularly relevant to healthcare organisations and technology providers.

1. Establish clear data governance

Organisations should understand what data they process, why they process it, where it is stored, and who can access it. Clear data ownership and accountability are essential when information moves between multiple systems and organisations.

1. Assess privacy risks

High-risk processing may require a Data Protection Impact Assessment (DPIA) under UU PDP. Organisations should assess whether their processing activities could create significant risks to individuals and implement appropriate safeguards.

1. Control third-party access

Healthcare organisations often depend on external technology providers and service partners. Contracts should define security responsibilities, access requirements, incident notification procedures, and data handling obligations.

1. Prepare for data breaches

Organisations need clear procedures for detecting, investigating, and responding to personal data breaches. Incident response plans should define responsibilities across security, IT, privacy, legal, and management teams so that incidents can be contained and reported appropriately.

Security Blueprint for SATUSEHAT Integration

A secure SATUSEHAT integration should cover five core areas:

• Data: Identify what health data is collected, exchanged, and stored, and minimise unnecessary data exposure.
• Identity: Secure users, applications, and machine identities with strong authentication and least-privilege access.
• APIs: Protect interfaces through authentication, authorisation, validation, encryption, rate limiting, and continuous monitoring.
• Visibility: Maintain logs and monitoring across data flows and connected systems to detect suspicious activity.
• Response: Prepare clear processes for investigating incidents, containing threats, and recovering affected systems.

This approach helps organisations move beyond basic compliance and build a security architecture that can support long-term healthcare interoperability.

Common Security Mistakes in Healthcare Integration

Even organisations with strong cybersecurity programmes can overlook risks created by interoperability.

1. Treating API security as an IT issue. API security affects privacy, compliance, and business operations. It should involve security, IT, privacy, and business teams rather than being left solely to developers.
2. Giving excessive access. Broad permissions increase the impact of compromised credentials. Access should be limited to the minimum data and functionality required.
3. Ignoring third-party risk. A healthcare organisation may have strong internal controls but still be exposed through a vulnerable vendor or integration partner.
4. Failing to monitor API activity. Without sufficient logging and monitoring, organisations may not know when credentials have been compromised or unusual data access is taking place.

Building a More Secure SATUSEHAT Ecosystem

SATUSEHAT can help create a more connected and efficient healthcare ecosystem in Indonesia. But interoperability also means that security must extend across every system, API, organisation, and third party involved in the data flow.

For hospitals, healthtech companies, pharmaceutical firms, and other healthcare ecosystem participants, the priority should be to build security into the integration from the start.

Zentara helps organisations strengthen cybersecurity across complex digital ecosystems, from assessing vulnerabilities and testing APIs to improving security monitoring and incident readiness.

Healthcare data should move when it needs to. It should never move without the right protection.

Ready to strengthen your healthcare data security? Explore how Zentara can help secure your APIs, connected systems, and sensitive data across the healthcare ecosystem.

Frequently Asked Questions About SATUSEHAT Security

1. What is SATUSEHAT?

SATUSEHAT is Indonesia's national health data exchange platform, designed to connect healthcare facilities and stakeholders through interoperable digital health systems.

1. Why is SATUSEHAT security important?

SATUSEHAT connects multiple healthcare systems and organisations. Weaknesses in APIs, access controls, or connected systems could increase the risk of unauthorised access to sensitive health information.

1. How does UU PDP apply to SATUSEHAT?

Health information is classified as specific personal data under UU PDP. Organisations processing this information must implement appropriate safeguards and meet applicable data protection obligations.

1. How can organisations secure SATUSEHAT APIs?

Organisations should use strong authentication and authorisation, encrypt data, validate API requests, apply rate limits, manage credentials securely, and continuously monitor API activity.

1. Who is responsible for securing SATUSEHAT integrations?

Security is a shared responsibility. While the platform provides the infrastructure for health data exchange, each organisation remains responsible for securing its own systems, credentials, endpoints, and data processing activities.

1. Should SATUSEHAT integrations undergo security testing?

Yes. Organisations should regularly assess and test their APIs, applications, infrastructure, and access controls to identify vulnerabilities before attackers can exploit them.