California AB 352: EHR Segmentation for Reproductive Health Records

Kevin Henry

Data Protection

Published Updated

10 minutes read
Share this article
California AB 352: EHR Segmentation for Reproductive Health Records

California AB 352 amended the Confidentiality of Medical Information Act (CMIA) to strengthen protections for certain information in electronic health records (EHRs) and health information exchanges. It addresses both how specified data should be segmented and restricted and when identifiable information about lawful California abortion care may be shared across state lines.

The law sets out different duties for health-information businesses and health care providers. It also leaves some technical choices—such as how systems identify sensitive details in narrative records—to implementation. This overview reflects the law and agency guidance available as of November 19, 2026; it is not legal advice.

What reproductive health information does AB 352 cover?

For EHR segregation, Civil Code section 56.101 specifically identifies medical information related to gender-affirming care, abortion and abortion-related services, and contraception. The information must be separated from the rest of the patient’s record and subject to the law’s access and out-of-state safeguards. The text of California Civil Code section 56.101 sets out these categories and system capabilities.

The abortion-disclosure restrictions have a more specific scope: they concern identifiable information related to someone seeking, obtaining, providing, supporting, or aiding in an abortion lawful under California law. That makes it important to distinguish AB 352’s particular EHR segmentation categories from its rules for out-of-state disclosures about abortion care.

The CMIA’s definition of “sensitive services” includes additional areas of care, but the specific segmentation list in section 56.101 names gender-affirming care, abortion and abortion-related services, and contraception. Providers and vendors should assess both the broader CMIA requirements and the specific rule that applies to the information and activity at issue. See California Civil Code section 56.05 and the California Department of Public Health’s AB 352 guidance.

How must EHRs segment and restrict access to sensitive records?

AB 352 requires covered businesses that electronically store or maintain medical information about the specified services on behalf of listed organizations to develop capabilities, policies, and procedures that support four protections:

  • Restrict user access privileges to authorized users and specified information.
  • Prevent improper out-of-state handling of the covered information, including disclosure, access, transfer, transmission, or processing.
  • Segregate the information from the rest of the patient’s record.
  • Enable automatic disabling of access to segregated information by individuals and entities in another state.

In practice, role-based access controls can help align a user’s permissions with their authorized role and the specific information they need. Segmentation does not necessarily mean creating a separate chart: it can involve separating designated information within the record and applying permissions to those elements. The law does not prescribe one particular EHR design or access-control model.

Section 56.101 also requires EHR and electronic medical record systems to protect the integrity of electronic medical information and automatically record and preserve changes or deletions. The record must include who accessed and changed the information, when it was accessed, and what change was made. These integrity and audit requirements are distinct from the sensitive-information segmentation features.

How can systems automatically disable access for out-of-state users?

The statute requires the capability to automatically disable access to segregated information for individuals and entities in another state. It does not specify a particular technical method for determining where a user or entity is located, or require a particular geolocation product.

For implementation, organizations can evaluate what trustworthy signals their systems can use, such as verified user identity, organizational affiliation, network or access location, and the destination of a record exchange. Because no single signal necessarily establishes a user’s location or authority, systems should be tested for both mistaken access grants and mistaken denials. These are implementation considerations, not a technical recipe mandated by AB 352.

Automatic restrictions should operate alongside authorized access for legitimate care and other permitted purposes. Organizations should test how restrictions apply to remote staff, shared accounts, health information exchanges, and users whose work involves more than one state. The statutory requirement concerns access to the segregated information; it does not itself prescribe how every clinical workflow must be configured.

What restrictions apply to out-of-state disclosures of abortion-care information?

Under Civil Code section 56.110, covered entities must not knowingly disclose, transmit, transfer, share, or grant access through an EHR or health information exchange to an out-of-state individual or entity when the identifiable information relates to a person seeking, obtaining, providing, supporting, or aiding in an abortion lawful in California—unless a specified authorization or exception applies.

Exceptions include a valid written patient authorization that clearly permits the disclosure for stated purposes; disclosures needed for payment; specified accreditation and health care quality-review activities; and bona fide research. The statute also addresses patient or personal-representative access, qualifying California or federal court orders with protections for the patient’s identity and records, and disclosures expressly required by preemptive federal law. See California Civil Code section 56.110.

Separate provisions restrict responses to subpoenas or requests based on another state’s laws that interfere with rights under California’s Reproductive Privacy Act, or on a foreign penal civil action. They also limit cooperation with certain out-of-state inquiries or investigations involving lawful California abortion care. These rules do not mean that every out-of-state request is handled identically: the request’s source, purpose, legal basis, and any applicable statutory exception matter. Review requests with qualified counsel rather than assuming that an out-of-state subpoena alone authorizes disclosure. See California Civil Code section 56.108.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

How should organizations identify sensitive information in unstructured records?

AB 352 requires covered information to be segregated, but it does not prescribe a universal taxonomy, automated classifier, or other method for finding every sensitive detail in free-text records. The CMIA’s definition of medical information is not limited to structured diagnosis or procedure fields; it can include individually identifiable information in electronic or physical form. That broad definition makes it prudent to assess relevant narrative and document-based information as well as coded data.

Potentially relevant content may appear in clinician notes, scanned documents, imported records, patient messages, encounter descriptions, or text copied forward from an earlier visit. These are practical examples, not an exhaustive statutory list. Organizations can map where such content is stored, identify how sensitive services are documented, and test whether segmentation and access controls continue to work when information is copied, exported, searched, or exchanged.

Automated text detection may help flag records for review, but it can miss context or incorrectly classify information. A practical program can combine data mapping, clear documentation rules, testing of EHR and exchange workflows, staff training, and defined procedures for reviewing uncertain cases. Because the statute does not specify a single detection method, organizations should document their approach and assess it against their systems and legal obligations.

What security capabilities and policies were due by July 1, 2024?

By July 1, 2024, businesses within the scope of section 56.101 that electronically store or maintain medical information on the specified services on behalf of listed organizations were required to develop the capabilities, policies, and procedures needed to limit access, prevent improper out-of-state handling, segregate the information, and automatically disable out-of-state access. The deadline applies to the law’s specified businesses; it should not be treated as a blanket requirement that every provider build its own EHR technology. The current Civil Code section 56.101 and CDPH’s All Facilities Letter 24-03 describe the requirements.

Organizations should also account for the EHR integrity and audit-trail rules in section 56.101. A compliant system must preserve the integrity of electronic medical information and automatically record and preserve changes or deletions, including the user’s identity, the date and time, and the change made. Patients retain applicable rights to access or receive copies of their records.

A separate, limited provision concerns health care providers’ liability for failures to meet section 56.110: as of November 19, 2026, the statute provides protection for qualifying failures before January 31, 2027, when a provider is working diligently and in good faith to come into compliance. This is not a general extension of the July 1, 2024 system-capability deadline, and it should not be assumed to protect vendors or every other entity. AB 260, Chapter 136, Statutes of 2025, extended the relevant provider provision.

What implementation challenges and compliance limits should providers consider?

Organizations may need to coordinate EHR configuration, health information exchanges, vendor contracts, identity systems, and internal privacy and security procedures. Legacy records, narrative notes, copied-forward text, and documents imported from other systems can make it difficult to reliably identify all relevant information. Cross-state workflows also require testing so that restrictions apply to the appropriate users and destinations without creating avoidable barriers to authorized care.

AB 352 does not remove the need to analyze a disclosure under other applicable laws, nor does segmentation alone make an organization compliant. HIPAA and other federal requirements may also apply. The federal landscape has changed: the U.S. Department of Health and Human Services says a court order issued June 18, 2025, vacated most of the 2024 HIPAA reproductive-health Privacy Rule, while leaving certain Notice of Privacy Practices modifications in effect. For current federal status, consult HHS Office for Civil Rights guidance.

For a practical compliance review, identify which information falls within each rule, confirm which organization has each statutory duty, test access and exchange workflows, preserve the required audit trail, and document how staff handle uncertain records and disclosure requests. AB 352’s key distinctions are the specific information categories, the separate duties for system businesses and providers, and the limited exceptions to the out-of-state abortion-care disclosure restrictions.

FAQs.

Which reproductive health records must be segregated under AB 352?

The EHR segregation requirements specifically cover medical information related to gender-affirming care, abortion and abortion-related services, and contraception. The law requires this information to be separated from the rest of the patient’s record and protected by access controls and other specified capabilities.

How must an EHR restrict out-of-state access to segregated information?

Covered businesses must enable systems to automatically disable access to segregated information by individuals and entities in another state and must support controls that prevent unauthorized out-of-state disclosure, access, transfer, transmission, or processing. AB 352 does not prescribe a particular location-detection technology.

When may providers disclose identifying information about lawful California abortion care to out-of-state entities?

Section 56.110 allows specified disclosures, including under a valid written authorization for stated purposes, for payment, certain accreditation and quality-review activities, or bona fide research. It also addresses patient access, qualifying court orders with privacy protections, and disclosures expressly required by preemptive federal law. Separate restrictions apply to certain out-of-state subpoenas, requests, and investigations, so providers should assess the specific facts and legal basis before disclosing.

How should providers protect sensitive information embedded in unstructured records?

AB 352 does not prescribe a particular method for identifying unstructured data. Providers should assess where sensitive information may appear in notes, scanned or imported records, messages, and other narrative content; test whether segmentation controls protect it; and document procedures for uncertain cases. Automated detection can support review but should be evaluated for missed context and incorrect flags.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

Related Articles