{"id":3800,"date":"2026-03-06T13:02:51","date_gmt":"2026-03-06T13:02:51","guid":{"rendered":"https:\/\/itlawco.com\/?p=3800"},"modified":"2026-03-06T13:06:35","modified_gmt":"2026-03-06T13:06:35","slug":"popia-health-data-regulations-2026","status":"publish","type":"post","link":"https:\/\/itlawco.com\/fr\/popia-health-data-regulations-2026\/","title":{"rendered":"POPIA health data regulations 2026: What you need to know"},"content":{"rendered":"\n\t\t
<\/div><\/div><\/div>
\n\t
\n\t\t
\n\t\t\t
\n\t\t\t\t\n
\n\t

Key takeaway:<\/strong> The Information Regulator<\/a>\u2019s Regulations relating to the Processing of Data Subjects’ Health Information by Certain Responsible Parties, 2026<\/em> came into force today, 6 March 2026. They are binding, immediate, and enforceable. Eight categories of organisations\u2014including employers, insurers and medical schemes\u2014must now comply with explicit obligations around lawful processing, security safeguards, and cross-border data transfers.<\/p>\n<\/div>\n\n\n\n\n

\n\t

What are these regulations and why do they matter?<\/h2>\n

South Africa has, for some time, had the architecture for robust health data protection under the Protection of Personal Information Act, 2013 (POPIA)<\/a>. What has sometimes been lacking is sector-specific clarity about what that protection demands in practice.<\/p>\n

Today, the Information Regulator closes that gap. Published in Government Gazette No. 54268 (Notice No. 7198) and signed by Chairperson Adv Pansy Tlakula on 27 February 2026, the Regulations relating to the Processing of Data Subjects’ Health Information by Certain Responsible Parties, 2026<\/em> (the Regulations) are issued under section 112(2)(c)<\/em> of POPIA. They operationalise section 32(6) of the Act and represent the most substantive sector-specific rules the Regulator has published since POPIA’s commencement provisions came into effect.<\/p>\n

They came into force today. There is no grace period.<\/p>\n<\/div>\n\n\n\n\n

\n\t

Who is covered?<\/h2>\n

The Regulations apply to eight categories of responsible party and their applicable operators:<\/p>\n

    \n
  1. Insurance companies<\/li>\n
  2. Medical schemes<\/li>\n
  3. Medical scheme administrators<\/li>\n
  4. Managed healthcare organisations<\/li>\n
  5. Administrative bodies<\/li>\n
  6. Pension funds<\/li>\n
  7. Employers<\/li>\n
  8. Institutions working on behalf of employers, administrative bodies or pension funds<\/li>\n<\/ol>\n

    The inclusion of employers<\/strong> is particularly significant. Many organisations routinely collect, store and act on employee health data\u2014through sick leave management, occupational health programmes, disability assessments and return-to-work processes\u2014without applying the same rigour as a medical scheme or insurer. The Regulations place employers squarely within the same compliance framework as sophisticated financial services entities.<\/p>\n<\/div>\n\n\n\n\n

    \n\t

    What do the Regulations require?<\/h2>\n

    A lawful basis for every instance of processing (Regulation 4)<\/h3>\n

    Responsible parties may not process health information (or other special personal information such as race, religion or biometrics) unless the requirements of section 27 of POPIA<\/strong> are satisfied. That section permits processing of special personal information only in narrowly defined circumstances. Consent is one, but not the only, ground.<\/p>\n

    A general company policy acknowledging that health data will be collected is not sufficient. Each instance of processing must be mapped to an identifiable, documented ground of justification.<\/p>\n

    Explicit security safeguards (Regulation 5)<\/h3>\n

    Responsible parties must maintain the confidentiality, integrity and availability<\/strong> of health information in their possession or control. The required safeguards have two specific dimensions.<\/p>\n

    Security and confidentiality of records<\/strong> \u2014 measures must address risks associated with both physical records (paper files, printed reports) and electronic ones (databases, cloud storage, email). Many organisations have modernised their electronic security posture while leaving physical records handling surprisingly casual. Both must now be addressed.<\/p>\n

    Proper disposal<\/strong> \u2014 health records must be disposed of in a manner that prevents any reasonably foreseeable unauthorised access or disclosure after the information is no longer needed. Deletion protocols, paper shredding policies and archive management practices all fall under scrutiny here.<\/p>\n

    Processing must also occur under a duty of confidentiality<\/strong> \u2014 whether arising from legislation, a professional code, an employment relationship or a written agreement, as contemplated in section 32(2) of POPIA. This is a notable requirement for employers and pension funds, which may not traditionally have regarded their health data handling as governed by the same confidentiality norms that apply to a registered nurse or medical scheme administrator.<\/p>\n

    Finally, technical and organisational measures must align with generally accepted information security practices<\/strong> applicable to the responsible party’s own sector or industry, as contemplated in section 19 of POPIA. This is a contextualised standard: a large insurer will be held to practices appropriate for financial services; a small employer to a standard proportionate to its size and context.<\/p>\n

    Cross-border transfer restrictions (Regulation 6)<\/h3>\n

    Health data may not be transferred to third parties in foreign countries unless one or more of the conditions in section 72(1) of POPIA<\/strong> are met. Those conditions include, among others, the data subject’s consent, a binding agreement between the parties, or the recipient country having comparable data protection laws in place.<\/p>\n

    This restriction has immediate practical consequences for multinational employers who transmit employee health or disability data to offshore HR systems, and for insurers who rely on international reinsurers or processing partners.<\/p>\n<\/div>\n\n\n\n\n

    \n\t

    What does this mean for your organisation?<\/h2>\n

    For employers<\/h3>\n

    Employment law has always required some engagement with employee health information. What changes is the formalisation of the obligation to process that information with documented justification, under confidentiality obligations, with appropriate security controls, and with a clear disposal policy.<\/p>\n

    HR policies and employment contracts should be reviewed. Occupational health service providers retained by employers are likely \u201coperators\u201d within the meaning of POPIA and should be subject to written operator agreements that impose equivalent obligations.<\/p>\n

    For insurers and pension funds<\/h3>\n

    Underwriting and claims processes necessarily involve the collection and assessment of health information. The Regulations reinforce existing POPIA obligations but add specificity around security controls and cross-border transfer restrictions that should be assessed against existing data flows. Processing by third-party claims assessors, medical advisers and reinsurers deserves particular attention.<\/p>\n

    For medical schemes and their administrators<\/h3>\n

    These entities have long operated under the Medical Schemes Act, 1998 (Act No. 131 of 1998) and its regulations, and many have mature data governance frameworks. The new POPIA Regulations are largely complementary but introduce explicit disposal and cross-border transfer requirements that should be assessed against current practices, particularly for schemes using offshore administration platforms or technology providers.<\/p>\n

    For managed healthcare organisations<\/h3>\n

    The clinical nature of managed care means health data is processed at high volume and often shared across multiple parties: schemes, treating providers, pharmaceutical benefit managers. Each data flow should be assessed for POPIA compliance, and managed care contracts should reflect the confidentiality and security obligations now codified in the Regulations.<\/p>\n<\/div>\n\n\n\n\n

    \n\t

    FAQs<\/h2>\n<\/div>\n\n\n\n

    <\/i>Do these Regulations apply immediately?<\/a><\/h3>
    \n
    \n\t

    Yes. Regulation 7.2 states that the Regulations commence on the date of publication in the Gazette<\/em> \u2014 today, 6 March 2026. There is no transitional period.<\/p>\n<\/div>\n\n\n\n<\/div><\/div><\/div>

    <\/i>What is \u201chealth information\u201d under the Regulations?<\/a><\/h3>
    \n
    \n\t

    The Regulations define \u201chealth information\u201d as personal information relating to the physical and\/or mental health of a data subject, including the provision of healthcare services and any testing, treatment and diagnosis which reveals information about the data subject’s health status.<\/p>\n<\/div>\n\n\n\n<\/div><\/div><\/div>

    <\/i>Does this apply if we only process employee sick leave records?<\/a><\/h3>
    \n
    \n\t

    Yes. Employers are explicitly listed as responsible parties within scope. Sick leave records, occupational health assessments, disability documentation and return-to-work records all constitute health information under the Regulations.<\/p>\n<\/div>\n\n\n\n<\/div><\/div><\/div>

    <\/i>Can health information be shared with an offshore parent company?<\/a><\/h3>
    \n
    \n\t

    Only if one or more of the conditions in section 72(1) of POPIA are met. Transfers solely on the basis of group policy or operational convenience are unlikely to satisfy the requirements without additional steps such as obtaining the data subject’s consent or putting binding transfer agreements in place.<\/p>\n<\/div>\n\n\n\n<\/div><\/div><\/div>

    <\/i>What are the penalties for non-compliance?<\/a><\/h3>
    \n
    \n\t

    The Information Regulator may issue compliance notices and administrative fines of up to R10 million. Serious cases may result in criminal prosecution of responsible individuals under POPIA.<\/p>\n<\/div>\n\n\n\n<\/div><\/div><\/div>

    <\/i>What is a \u201cresponsible party\u201d versus an \u201coperator\u201d?<\/a><\/h3>
    \n
    \n\t

    A responsible party determines the purpose and means of processing. An operator processes information on behalf of a responsible party. The Regulations apply to responsible parties and their applicable operators. Operators are typically bound through written operator agreements that mirror the responsible party’s obligations.<\/p>\n<\/div>\n\n\n\n<\/div><\/div><\/div><\/div>\n

    \n\t

    The enforcement outlook<\/h2>\n

    One of the stated purposes of the Regulations is to give the Information Regulator a clearer enforcement framework. Until today, enforcement of health data obligations under POPIA required the Regulator to reason from general principles. These Regulations draw a more precise line.<\/p>\n

    Non-compliant organisations face the Regulator’s full enforcement toolkit. Given the Regulator\u2019s stated commitment to enforcement and the public sensitivity of health data, compliance should be treated as an immediate operational priority rather than a medium-term project.<\/p>\n<\/div>\n\n\n\n\n

    \n\t

    Five steps to take today<\/h2>\n
      \n
    1. Map<\/strong> all health data flows within your organisation and to third parties, including operators and offshore recipients.<\/li>\n
    2. Review<\/strong> the legal basis for each category of processing activity and document it.<\/li>\n
    3. Audit<\/strong> physical and electronic security controls against sector-appropriate standards.<\/li>\n
    4. Update<\/strong> disposal and retention policies to address both digital deletion and physical destruction.<\/li>\n
    5. Check<\/strong> cross-border transfers for compliance with section 72(1) of POPIA and put transfer agreements in place where required.<\/li>\n<\/ol>\n<\/div>\n\n\n\n\n
      \n\t

      How ITLawCo can help<\/h2>\n

      ITLawCo advises employers, insurers, medical schemes and financial services entities on POPIA compliance, data governance and regulatory risk. The table below maps the Regulations’ key obligations to ITLawCo’s service offering.<\/p>\n

      \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
      Obligation under the Regulations<\/th>\nHow ITLawCo can help<\/th>\n<\/tr>\n<\/thead>\n
      Lawful basis assessment (Reg 4)<\/strong><\/td>\nReview and document the legal grounds for each category of health data processing across your organisation, including consent frameworks and legitimate interest assessments.<\/td>\n<\/tr>\n
      Processing inventory and data mapping<\/strong><\/td>\nConduct a health data flow mapping exercise to identify what is collected, how it is used, where it is stored, and with whom it is shared.<\/td>\n<\/tr>\n
      Security safeguards \u2014 policy and procedure (Reg 5)<\/strong><\/td>\nDraft or update information security policies, records management procedures and data classification frameworks aligned to POPIA and sector-specific standards.<\/td>\n<\/tr>\n
      Security safeguards \u2014 physical and electronic records<\/strong><\/td>\nAdvise on security controls for both physical and electronic health records, including access controls, encryption, and secure storage practices.<\/td>\n<\/tr>\n
      Disposal and retention (Reg 5.2.2)<\/strong><\/td>\nDesign retention schedules and secure disposal protocols for health records in both digital and physical formats.<\/td>\n<\/tr>\n
      Confidentiality obligations (Reg 5.3)<\/strong><\/td>\nDraft confidentiality clauses for employment contracts, operator agreements and professional services arrangements.<\/td>\n<\/tr>\n
      Operator agreements<\/strong><\/td>\nPrepare POPIA-compliant operator agreements for occupational health providers, managed care organisations, claims assessors and other third-party processors.<\/td>\n<\/tr>\n
      Cross-border transfer compliance (Reg 6)<\/strong><\/td>\nAssess offshore data flows, identify transfers requiring justification under section 72(1) of POPIA, and draft transfer agreements or consent mechanisms where required.<\/td>\n<\/tr>\n
      Regulator engagement and enforcement response<\/strong><\/td>\nAdvise on responses to Information Regulator enquiries, compliance notices or investigations arising from health data processing.<\/td>\n<\/tr>\n
      Training and awareness<\/strong><\/td>\nDeliver targeted training for HR, occupational health, compliance and IT teams on their obligations under the Regulations.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

      To discuss your organisation’s compliance position, contact us<\/a>.<\/p>\n<\/div>\n\n\n\n\n

      \n\t

      End thoughts<\/h2>\n

      Privacy law without enforcement is aspiration. What these Regulations signal is that South Africa is moving beyond aspiration toward accountability \u2014 at least in the domain of health data. The obligations are not new in spirit; they are new in specificity, and that distinction matters when the Regulator comes knocking.<\/p>\n

      For regulated entities, the message is as clear as the law now is: the time to act is today.<\/p>\n<\/div>\n\n\n\n\n

      \n\t

      This article is for informational purposes only and does not constitute legal advice. Organisations should seek guidance from qualified legal counsel regarding their specific compliance obligations under the Protection of Personal Information Act, 2013, and these Regulations. Health data matters are treated with strict confidentiality in all professional engagements.<\/em><\/p>\n<\/div>\n\n\n\n\n

      \n\t
      <\/div>