AB 1129 authorizes the California Department of Public Health’s Birth Defects Monitoring Program to collect and store umbilical cord blood samples it receives from hospitals and make them available for approved research. The bill ties collection and storage to financial safeguards—researcher fees, federal startup grants, or other confirmation of funding—allows the department to cap annual collections, and exempts local health officer–supervised collections.
The measure creates a framework for fees (capped at cost), directs fee revenue into three named state funds, prescribes permitted research uses, and imposes confidentiality, recordkeeping, and CPHS review requirements before samples or personally identifying data may be released. It also lets the department bill researchers for data-protection work and permits other IRBs to approve projects if security standards are met.
At a Glance
What It Does
The bill requires the Birth Defects Monitoring Program to collect and store umbilical cord blood samples it receives and permits sharing those samples with department-approved researchers subject to confidentiality, CPHS review, and cost‑recovery fees. It authorizes the department to set fees up to the cost of administration and to deposit proceeds into specified state funds.
Who It Affects
State public‑health administrators, genetic and newborn screening programs, researchers seeking biospecimens, hospital labor/delivery units that provide cord blood, and institutional review boards (CPHS and others) that will review release requests and data protection plans.
Why It Matters
The bill creates a state‑level repository pathway for cord blood tied to explicit privacy controls and a cost‑recovery model, shifting operational costs toward researchers while formalizing CPHS oversight and technical safeguards that will shape how identifiable maternal/infant data are shared for research.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 1129 expands the Birth Defects Monitoring Program (BDMP) so the department will collect and store umbilical cord blood samples that hospitals send to the program. The department must ensure financial stability for this new activity: it can rely on researcher fees, federal startup grants, or confirmations that a researcher’s request will fund collection and storage.
The statute lets the department limit the number of cord blood samples collected each year and excludes local health officer–supervised collections from this provision.
To pay for collection, storage, and program administration, the bill directs the department to set fees no higher than actual costs and to collect those fees from department‑approved researchers requesting cord, pregnancy, or newborn blood for research. Fees are deposited into three explicitly named funds—the Birth Defects Monitoring Program Fund, the Genetic Disease Testing Fund, and a newly created Cord Blood Banking Fund—and may be used for reporting, data management, and the full lifecycle of sample handling, but only upon appropriation by the Legislature.The bill establishes strict confidentiality and access controls.
The department must limit access to authorized individuals who sign written confidentiality agreements, keep a record of all disclosures, and may deny access and impose a civil penalty up to $1,000 for violations. When identifiable samples or linked data are to be shared or processed outside department staff, the State Committee for the Protection of Human Subjects (CPHS) must review and confirm that technical, administrative, and physical safeguards are in place, that plans exist to destroy or return personal information when no longer needed (or to justify long‑term retention), and that only the minimum necessary personal information is released.CPHS’s review includes procedural checks—verifying need, restricting access to essential personal data, requiring subject codes instead of social security numbers where possible, and, if feasible, directing the agency to perform portions of the data processing to minimize release of identifiers.
The department may bill researchers separately for those data‑protection services. Finally, the bill permits the department to use other institutional review boards to approve research activities if they meet the statute’s data‑security requirements, giving some flexibility in oversight while keeping the security bar high.
The Five Things You Need to Know
The department may collect and store umbilical cord blood samples it receives, but may limit the number of cord blood samples collected each year.
Fees charged to approved researchers must not exceed the costs of administering the program and storing samples; those fees go into the Birth Defects Monitoring Program Fund, the Genetic Disease Testing Fund, or the newly created Cord Blood Banking Fund.
CPHS must verify data‑security plans before any release of samples or personally identifying information and may require the department to do data processing itself to reduce disclosure.
A person who violates a signed confidentiality agreement can be denied further access and faces a civil penalty not exceeding $1,000, in addition to other legal remedies.
The department may bill researchers for specific data‑protection work—such as removing identifiers, encrypting data, assigning subject codes, or performing data processing on the agency’s systems.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Conditions for collecting and storing umbilical cord blood
This subsection directs the Birth Defects Monitoring Program to collect and store any umbilical cord blood samples it receives but ties that obligation to concrete financial conditions: researcher fees sufficient to cover costs, confirmation that a researcher’s request includes funding, or receipt of federal startup grants. The practical effect is conditional expansion—collection proceeds only if a funding pathway is demonstrated, limiting unexpected fiscal exposure for the department.
Collection limits and local exemptions
The department can cap the number of cord blood samples it accepts annually, giving it direct operational control to match capacity. Collections overseen by local health officers for local monitoring or other purposes are expressly excluded, preserving local surveillance arrangements and preventing overlap with county‑led programs.
Confidentiality, access controls, and enforcement
All information tied to cord blood samples is confidential and may be used only for the program or approved research. The department must record every disclosure and require written confidentiality agreements. Violators can be barred from access and face a civil penalty up to $1,000; the provision preserves other legal remedies. This creates a compliance backbone but relies on administrative enforcement rather than criminal penalties.
Fee authority, fund allocation, and permitted uses
The department establishes fees to recover the administration, collection, and storage costs and deposits revenues into three specified funds based on sample source and program purpose. Money in those funds may be appropriated by the Legislature and used for reporting, data management (including linkage and entry), collection, storage, retrieval, processing, inventory, and shipping—spelling out a full cost base that fees must support.
Authorized research purposes
The statute limits allowable uses of samples and associated patient information to research on risk factors, screening tests, prevention strategies, and treatments for women’s and children’s diseases. This narrows permissible research to public‑health and clinical aims and excludes commercial or unrelated research purposes unless those uses fall within the defined categories and pass department review.
CPHS review and data‑protection requirements; cost recovery for protections
Before releasing samples or personal data, CPHS must confirm that requestors and the department have adequate administrative, physical, and technical safeguards, a plan to destroy or return identifiers, assurances against reuse, and that only minimum necessary data are released. CPHS can require subject codes in place of social security numbers and, where feasible, have the department perform data processing to limit disclosure. The department may charge researchers for these protective services, creating a direct cost item tied to privacy compliance.
Delegation to other IRBs with security caveat
The department may enter agreements allowing other institutional review boards to approve research activities, projects, or classes of projects on its behalf, but only when the external IRB satisfies the statute’s data‑security requirements. This provides flexibility for IRB review while keeping statutory security standards binding.
This bill is one of many.
Codify tracks hundreds of bills on Healthcare across all five countries.
Explore Healthcare in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Department‑approved researchers studying maternal, newborn, or pediatric conditions — they gain a centralized repository of cord, pregnancy, and newborn blood tied to screening programs, improving access to linked biospecimens for hypothesis‑driven and translational research.
- California Department of Public Health — the department acquires an expanded biospecimen capability and a defined cost‑recovery mechanism that can sustain operations without relying solely on general fund allocations.
- Genetic and newborn screening programs — closer integration with the Birth Defects Monitoring Program and dedicated funds can improve data linkage, inventory management, and research translation for screening test evaluation.
- Public health and future patients — by enabling research on risk factors, screening, prevention, and treatments, the statute could accelerate evidence development that benefits pregnant people, infants, and children over time.
Who Bears the Cost
- Researchers requesting identifiable or processed data — they must pay fees capped at cost and may be billed additionally for the department’s protective data‑processing services, which raises the price of access, especially for smaller academic teams.
- Department operations and Legislature — while fees are meant to cover costs, initial startup may rely on federal grants, and use of funds for operations still requires legislative appropriation, creating potential budgetary and timing dependencies.
- Hospitals and clinical staff — providing cord blood to the program will impose administrative and logistics work for collection, labeling, and transfer, for which the bill does not create an explicit reimbursement mechanism.
- CPHS and IRBs — expanded review responsibilities and scrutiny of security plans increase workload and may require additional staffing or resources to meet statutory review standards.
Key Issues
The Core Tension
The bill tries to balance enabling valuable, identifiable biospecimen research with strong privacy and cost‑recovery controls: it expands access to cord blood for research but ties that access to fees, CPHS scrutiny, and administrative safeguards—creating a trade‑off between maximizing scientific access and protecting donor privacy, affordability, and program capacity.
The bill is heavy on procedural safeguards but light on donor consent mechanics. It mandates confidentiality, CPHS review, and destruction/return plans for personal information, but it does not specify whether hospitals must obtain explicit maternal consent for storage or secondary research use, or how existing newborn screening consents intersect with cord blood.
That gap leaves operational ambiguity for hospitals, the department, and IRBs when it comes to consent documentation and notice.
The finance model shifts recurring costs to researchers through fees and authorizes billing for protective data processing, but it also makes use of funds contingent on legislative appropriation. That creates a gap between collected fees and the department’s ability to spend them, potentially delaying procurement of storage infrastructure or staffing even when revenue is available.
Additionally, the $1,000 civil penalty for confidentiality breaches is modest and may not deter willful or high‑impact disclosures; enforcement leans on administrative access denial and other unspecified legal remedies.
Operationally, the CPHS requirement that the department perform parts of data processing “if feasible” raises questions about technical capacity and timelines: performing in‑house processing can reduce identifier release but requires infrastructure and personnel that the statute does not fund directly. Finally, while the bill narrows research purposes to public‑health goals, it does not expressly prohibit commercialization or downstream transfer to commercial entities, which could raise ethical and equity concerns unless addressed in implementation rules or agreements.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.