Medicine · FDA PCCP

FDA PCCP for clinical AI workflows

FDA PCCP in clinical AI workflows: what compliance requires, who asks for evidence, and the records to keep.

Legal forceNon-binding guidance; an authorized PCCP binds the manufacturer to its terms
Applies from4 Dec 2024
SectorMedicine
Checked21 Oct 2026

01 / The rule

What FDA PCCP requires

Manufacturers of medical devices with AI-enabled device software functions seeking 510(k) clearance, De Novo classification or PMA approval, including device-led combination products.

  1. 01Describe each planned modification specifically enough for FDA to assess it (Description of Modifications).
  2. 02Specify how each modification will be developed, validated and implemented, with acceptance criteria (Modification Protocol).
  3. 03Assess the benefits and risks of the planned modifications, individually and together (Impact Assessment).
  4. 04Keep every modification within the device's authorized intended use.
  5. 05Implement changes only as the authorized PCCP describes; changes outside it need a new submission.
  6. 06Update labeling and keep version control and quality system records for each implemented change.

02 / In this sector

In a clinical AI workflow

The guidance is written for AI-enabled device software functions, the final version having broadened the draft's machine-learning-only scope. It is how a manufacturer gets authorization in advance for model retraining or performance updates.

Usually asked by

Clinical committees and health system AI governance.

Named alongside

HHS §1557 · HIPAA · FDA PCCP.

Sector pagePlanisphere for medicine

03 / Records

Records to keep

  1. 01Authorized PCCP from the 510(k), De Novo or PMA file
  2. 02Verification and validation results for each implemented modification
  3. 03Version history linking each released model to the PCCP
  4. 04Updated labeling describing the modification and its performance

Optional evidence · where Planisphere fits

Keep a record anyone can check

When your team meets a duty, Planisphere can seal the event it reports as a receipt.

01 · Your teamRecord the event

A disclosure shown, a review signed, a model change approved: the event your system reports.

02 · PlanisphereSeal it

The event becomes a sealed receipt, dated and attributed to whoever is signed in.

03 · AnyoneCheck it

Paste the receipt into Verify. No account or key.

A record supports your compliance evidence process. It is not a legal finding or a certification. Systems that call Planisphere's gate API can also hold or refuse an action before it runs.

SOURCES

Go back to the source

SECONDARY
FDA Regulation of AI-Enabled Devices (CRS In Focus IF13245, June 10, 2026)

Congressional Research Service (via EveryCRSReport)

RELATED

Related: FDA PCCP: the full guide · FDA PCCP for defense · FDA PCCP for law · FDA PCCP for education