PDPA Compliance for Malaysian GP Clinics: What Patient Data You Can Collect, Store, and Share
PDPA compliance

The Personal Data Protection Act 2010 (PDPA) has been in force in Malaysia for over a decade, yet most GP clinic owners have never sat down and thought through what it actually means for their practice. The answer to “are we PDPA compliant?” is usually somewhere between “not entirely” and “I’m not sure.”
This guide translates the PDPA’s requirements into practical terms for a GP clinic. What can you collect, what can you store, what can you share, and what do your patients have the right to request?
What the PDPA Covers for GP Clinics
The PDPA regulates the processing of personal data by data users — which includes any GP clinic that collects, stores, uses, or discloses patient information. Patient data in a clinic context includes names, NRIC numbers, dates of birth, contact information, medical records, diagnoses, medications, and payment information.
Medical data is classified as “sensitive personal data” under the PDPA and is subject to stricter protections than ordinary personal data. This means you need explicit consent to process it in most circumstances, and you cannot share it without either consent or a specific legal basis.
The 7 Principles of the PDPA and How They Apply to Your Clinic
1. General Principle
You can only process patient data if you have the patient’s consent, or if processing is necessary for a contract (e.g., the patient is seeking treatment from you). In practice, a well-drafted patient registration form that the patient signs or acknowledges covers your consent basis for treatment-related data processing.
2. Notice and Choice Principle
You must inform patients, before or at the time of collection, what data you are collecting and how you will use it. Your patient registration form should include a clear notice: what data is collected, for what purposes, and who it may be shared with (e.g., referral specialists, panel TPAs, LHDN for MyInvois).
3. Disclosure Principle
You cannot disclose patient data to third parties without the patient’s consent, unless disclosure is required by law (e.g., notifiable disease reporting to MOH, MyInvois submission to LHDN) or is within the purpose the patient consented to at registration.
4. Security Principle
You must take practical steps to protect patient data from loss, misuse, unauthorised access, or disclosure. This applies whether data is stored in paper files or digital systems.
5. Retention Principle
You must not retain patient data for longer than necessary for the purpose it was collected. For medical records, this is governed by MOH guidelines (see below). For billing data, it aligns with tax retention requirements (typically 7 years).
6. Data Integrity Principle
The personal data you hold must be accurate, complete, and not misleading. If a patient informs you of a change (new address, new phone number), you are obligated to update your records.
7. Access Principle
Patients have the right to access their personal data held by your clinic and to correct inaccurate data. You must have a process for handling these requests.
What You Can Share and With Whom
With a TPA (HealthMetrics, MediExpress, etc.)
Sharing patient consultation data with a TPA for the purpose of panel claim processing is within the scope of the consent given at registration, provided your registration form discloses that data will be shared with panel providers for billing purposes. If your registration form does not mention this, you technically need separate explicit consent.
With a referral specialist
Sharing relevant medical history with a specialist to whom you are referring a patient is within the scope of treatment consent. A standard referral letter with clinical details is acceptable under PDPA.
With LHDN for MyInvois
This is a statutory obligation, not a consent-based disclosure. Sharing patient data with LHDN for MyInvois compliance is permitted under PDPA because it is required by law. You do not need patient consent for this specific disclosure.
With another clinic or hospital without referral
Sharing patient records with another healthcare provider without the patient’s explicit consent is not permitted under PDPA unless there is a direct treatment relationship and the sharing is clearly within the patient’s interest. If a patient calls and asks you to send their records to another clinic they are now attending, that request constitutes consent — document it.
With a researcher or for marketing purposes
You cannot use patient data for research or marketing without explicit opt-in consent. This includes using patient contact information to send promotional messages about your clinic’s new services.
Patient Consent: What Your Registration Form Must Say
The minimum your patient registration form should disclose:
What personal data is being collected (name, NRIC, contact details, medical information)
For what purposes (treatment, billing, TPA panel claims, LHDN e-invoicing)
Who the data may be shared with (panel TPAs if applicable, referral specialists, LHDN)
How long it will be retained (align with MOH record retention guidelines)
The patient’s right to access and correct their data
Contact details for data-related queries
This disclosure should be signed or acknowledged by the patient at registration. For returning patients, a periodic refresh (every 2–3 years) is good practice.
How Long to Retain Patient Records
The MOH guideline under the Private Healthcare Facilities and Services Act (PHFSA) 1998 requires retention of:
Adult patient records: Minimum 7 years from the date of last attendance
Minor patient records: Until the patient turns 25 years old, or 7 years from last attendance — whichever is later
Mental health records: Subject to additional requirements under the Mental Health Act 2001
After the retention period, records should be disposed of securely — shredding for paper, secure deletion for digital records. Leaving records in a bin or unsecured storage is a PDPA breach.
Cloud Storage and PDPA
Most clinic management systems today store data in the cloud. PDPA compliance for cloud storage requires:
Data processed within Malaysia or in a jurisdiction with equivalent data protection laws. If your CMS stores data on overseas servers (e.g., US or Europe), the provider should confirm they comply with Malaysian data transfer requirements.
Encryption in transit and at rest. Patient data transmitted to and stored on cloud servers must be encrypted.
Access controls. Only authorised clinic staff should be able to access patient records. Your CMS should support role-based access (doctor sees clinical notes, front desk sees registration, billing staff sees invoices).
Breach notification. If patient data is compromised, you have an obligation to notify affected patients and potentially the relevant authorities.
When evaluating any clinic management software, ask directly: where is patient data stored, how is it secured, and what is the breach notification process?
→ Medinex stores all patient data on Malaysian cloud servers, encrypted in transit and at rest. PDPA-compliant from day one. Book a demo to see our data handling setup.


