PCCP for AI medical devices: planning model updates with the FDA
Teams that build AI-enabled device software often want to retrain or improve a model after launch. This page explains how the FDA's Predetermined Change Control Plan (PCCP) guidance lets them plan those changes up front.
Posez votre question
Compte gratuit requisLes réponses sont rédigées par un modèle de langage à partir des seuls documents de cette base, avec leurs sources numérotées. Elles peuvent être inexactes et ne constituent pas un conseil juridique, médical ou financier : vérifiez les sources avant toute décision importante.
What a PCCP allows
Section 515C of the Federal Food, Drug, and Cosmetic Act provides that a new 510(k) or a PMA supplement is not required for a change that is consistent with a PCCP cleared or approved by FDA. The guidance covers modifications that would otherwise require a new marketing submission.
A device with a PCCP can be authorized through the PMA, 510(k) or De Novo pathway. The plan should be discussed in the marketing submission alongside the device description, labeling and the safety and effectiveness or substantial equivalence assessment.
The building blocks of the plan
The final PCCP guidance is organized around a Description of Modifications, a Modification Protocol and an Impact Assessment, with traceability between the planned changes and the protocol.
The Modification Protocol describes data management practices, re-training practices, performance evaluation and update procedures.
Questions fréquentes
Does a PCCP cover minor changes that never needed a submission?
No. The guidance states that a PCCP is meant for modifications that generally would otherwise require a new marketing submission, and it does not address plans for changes that would not require one.
Can FDA require labeling for the planned changes?
Yes. Section 515C allows FDA to require that a PCCP include labeling for safe and effective use of the device as it changes under the plan.
Is the separate AI lifecycle guidance final?
No. The lifecycle guidance for AI-enabled device software functions is a draft, while the PCCP marketing submission guidance is final.
Intégrer / API / MCP
Branchez cette base à Claude, Cursor, ChatGPT ou votre propre application. Chaque requête API ou MCP coûte 0,10 €, débitée de votre crédit Kopik (non facturée si rien n'est trouvé). Il vous faut une clé API : créez-la depuis votre tableau de bord.
MCP pour vos agents
Adresse du serveur MCP de cette base (outils ask_base et search_base) :
https://kopik.io/api/mcp?base=us-fda-surgical-robotics-samdClaude Code, Cursor et autres clients
claude mcp add --transport http kopik-us-fda-surgical-robotics-samd "https://kopik.io/api/mcp?base=us-fda-surgical-robotics-samd" --header "Authorization: Bearer kpk_…"{
"mcpServers": {
"kopik-us-fda-surgical-robotics-samd": {
"url": "https://kopik.io/api/mcp?base=us-fda-surgical-robotics-samd",
"headers": {
"Authorization": "Bearer kpk_…"
}
}
}
}API REST pour vos applications
mode vaut "answer" (réponse rédigée + sources) ou "passages" (passages bruts seulement). Ajoutez un maxPriceCents facultatif pour plafonner le prix : si la base coûte plus cher, l'appel est refusé sans rien débiter.
curl -X POST https://kopik.io/api/v1/bases/us-fda-surgical-robotics-samd/query \
-H "Authorization: Bearer kpk_…" \
-H "Content-Type: application/json" \
-d '{"question": "Votre question ici", "mode": "answer"}'Pour commencer
- Créez une clé dans votre tableau de bord et rechargez votre crédit.
- Remplacez
kpk_…par votre clé. - Tout le détail (réponses, erreurs, exemples JS et Python) : documentation développeurs.