Glossary Updates16 new terms added to the glossaries · 12 November 2026, 21:23 CET
AI TechDocKnowledge
  • English (US)
  • English (UK)
  • Deutsch
All context cards

Role card

Model change approver: a functional role

Who decides whether an update of an AI model in a medical device stays inside its planned modifications — and who stops it when it doesn’t?

A role card explains a functional role: what has to be done, not a job title. One person can hold several of them, and one can be spread over several people.

By knowledge.aitechdoc.world

Reviewed

Review log and changes

The short answer

The model change approver checks every model update against the modification plan — a PCCP in the US, predetermined changes assessed by the notified body in the EU — and approves it as a new released device state or sends it to a full change assessment. The role keeps model, software and device versions apart and never approves its own changes.

For: Technical writers, technical marketers, project managers and documentation systems developers in medical device companies

Key points

  • Model, software and device versions are kept apart.
  • An update inside the plan still needs verification against the plan’s acceptance criteria.
  • A change outside the plan is a change with its own assessment, whatever it is called.

Functional role

Model change approver

The role in one sentence

The functional role that decides whether an update of a device’s AI model is covered by its modification plan and approves it as a new released state of the device.

Responsibilities

  • Compare each update with the modification plan, its methods and its limits.
  • Check verification results against the acceptance criteria.
  • Approve the update as a new released device state, or send it to a full change assessment.
  • Make sure labelling describes the current model performance.

Decides

  • Whether an update is inside the plan
  • Approval of the update within the plan

Does not decide

  • Changing the plan itself (needs its own authorisation)
  • The data science work of the update
  • Vigilance decisions

Receives

  • Modification plan or PCCP
  • Update and verification records
  • Real-world performance reports

Hands over

  • Approval or referral record per model version
  • Updated version and labelling references

Typically held by

Reader roles of the pathway map that usually take on this function.

Technical writers
Updates performance figures in the IFU after an approved change.
Technical marketers
Holds back claims until the new version is released.
Technical project managers
Plans the approval step into every update cycle.
Documentation systems developers
Keeps model, software and device versions as separate records.

On the map

The context

Where the role acts

The role belongs to the pathway map of the medical-device evidence chain. It acts at these stations:

  • Planned model change — Checks each model update against the modification plan and approves or stops it.
  • Real-world performance — Uses real-world performance to decide whether an update is needed.
  • Release with product and document version — Approves the new model version as part of a released device state.

Why a functional role

The functional role that decides whether an update of a device’s AI model is covered by its modification plan and approves it as a new released state of the device. One person can hold several functional roles, and one role can be spread over several people. What matters is the test: who can decide or change something here — and who can’t?

The map and this role describe documentation work; they don’t confer conformity.

Questions readers ask next

Is “Model change approver” a job title?
No. Not the developer of the model: approving one’s own change is not independent. The map describes what has to be done, not who does it on the org chart.
What does the role not decide?
Changing the plan itself (needs its own authorisation); The data science work of the update; Vigilance decisions.

Sources

  1. Marketing Submission Recommendations for a Predetermined Change Control Plan for Artificial Intelligence-Enabled Device Software Functions — U.S. Food and Drug Administration, December 2024Final guidance: Guidance published in its final form by an authority or an official body. Guidance explains the law; it is not law itself.
  2. Regulation (EU) 2024/1689 (Artificial Intelligence Act), as amended by Regulation (EU) 2026/1744; high-risk requirements for devices apply from 2028-08-02 — EUR-Lex, 12 July 2024Law adopted, not yet applicable: Adopted and published legislation whose obligations apply from a later date.
  3. IEC 62304:2006+A1:2015, Medical device software — Software life cycle processes — IEC, June 2015Standard: A published standard or specification. Not cited in the Official Journal as a harmonized standard, so it gives no presumption of conformity on its own.

Review log and changes

Every context card is checked against its sources before it is published, and again whenever it changes; the date under the byline is the last review. Corrections (something was wrong) and additions (something was missing) are logged below with date and time (Berlin time). Typos, formatting and link fixes are not listed.

Reviewed

No corrections or additions since publication.