Role card
Risk management file owner: a functional role
Who keeps the risk management file of a medical device connected to the requirements, tests and warnings that depend on it?
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.
The short answer
The risk management file owner keeps the ISO 14971 file with stable ids for hazards, hazardous situations, harms and risk control measures, and keeps each control linked to its implementation and verification. The role hands controls that end as information for safety to the labeling owner and assesses post-market signals against the file.
For: Technical writers, technical marketers, project managers and documentation systems developers in medical device companies
Key points
- Stable ids for hazards, hazardous situations, harms and controls.
- Information for safety is the last control in the order, never a replacement for a possible design measure.
- Post-market signals come back into the file.
Functional role
Risk management file owner
The role in one sentence
The functional role that keeps the risk management file current and keeps every risk control linked to its implementation, its verification and, where it is information for safety, its place in the labeling.
Responsibilities
- Keep hazards, hazardous situations, harms, estimates and controls with stable ids.
- Link each control to its requirement and verification.
- Name the controls that end as information for safety and hand them to labeling.
- Update the file from post-market signals and keep the overall benefit-risk conclusion current.
Decides
- The content and ids of the risk management file
- Whether a signal changes a risk estimate
Does not decide
- The wording of the warning (labeling)
- The release of the device
- Clinical conclusions on benefit
Receives
- Design inputs and outputs
- Usability and verification results
- Post-market signals
Hands over
- Risk management file and report
- Control-to-labeling handover list
Typically held by
Reader roles of the pathway map that usually take on this function.
- Technical writers
- Receives the ids of controls that end in the IFU.
- Technical marketers
- Checks that no claim plays down a residual risk.
- Technical project managers
- Plans risk reviews as milestones.
- Documentation systems developers
- Gives the file stable ids and typed links.
On the map
- Risk management file· The medical-device evidence chain: from intended purpose to post-market evidence
Keeps the risk management file with ids for hazards, situations, harms and controls.
- Risk-to-IFU traceability· The medical-device evidence chain: from intended purpose to post-market evidence
Hands the ids of controls that end as information for safety to labeling.
- Post-market signals into the file· The medical-device evidence chain: from intended purpose to post-market evidence
Assesses post-market signals against the file.
The context
Where the role acts
The role belongs to the pathway map of the medical-device evidence chain. It acts at these stations:
- Risk management file — Keeps the risk management file with ids for hazards, situations, harms and controls.
- Risk-to-IFU traceability — Hands the ids of controls that end as information for safety to labeling.
- Post-market signals into the file — Assesses post-market signals against the file.
Why a functional role
The functional role that keeps the risk management file current and keeps every risk control linked to its implementation, its verification and, where it is information for safety, its place in the labeling. 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 “Risk management file owner” a job title?
- No. Not the risk manager of the whole company. The map describes what has to be done, not who does it on the org chart.
- What does the role not decide?
- The wording of the warning (labeling); The release of the device; Clinical conclusions on benefit.
Sources
- ISO 14971:2019, Medical devices — Application of risk management to medical devices (cited under the MDR as EN ISO 14971:2019/A11:2021) — ISO, December 2019Harmonized standard (cited): A harmonized standard whose reference is published in the Official Journal of the EU; applying it can give a presumption of conformity for the requirements it covers.
- Regulation (EU) 2017/745 on medical devices (MDR) — EUR-Lex, May 5, 2017Law in force: Binding legislation that applies as of the review date.
- ISO 13485:2016, Medical devices — Quality management systems — Requirements for regulatory purposes (cited under the MDR as EN ISO 13485:2016/A11:2021) — ISO, March 2016Harmonized standard (cited): A harmonized standard whose reference is published in the Official Journal of the EU; applying it can give a presumption of conformity for the requirements it covers.
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.