Role card
Post-market signal owner: a functional role
Who makes sure that what is learned about a device in the field reaches its risk file, its IFU and its claims?
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 post-market signal owner collects complaints, field data, literature and real-world performance, assesses each signal against the risk file and names the documents a resulting CAPA or change affects. Reporting deadlines for vigilance run separately; the role makes sure the documentation follows what was learned.
For: Technical writers, technical marketers, project managers and documentation systems developers in medical device companies
Key points
- Each signal is assessed against the risk file and the claims.
- A CAPA names the labelling and IFU it changes.
- Vigilance reports keep their own deadlines; documentation updates never replace them.
Functional role
Post-market signal owner
The role in one sentence
The functional role that collects and assesses post-market signals and makes sure their consequences reach the risk management file, the labelling and the claims of the device.
Responsibilities
- Collect signals per product version: complaints, field data, literature, PMCF, real-world performance.
- Assess each against the risk file, the clinical evaluation and the claims.
- Name the documents affected by a CAPA or change and follow up their update.
- Feed PMS reports, PSURs and trend reports.
Decides
- Whether a signal needs assessment and by whom
- The list of documents a CAPA or change affects
Does not decide
- The decision to report a serious incident (vigilance process)
- The risk estimate itself
- Labelling wording
Receives
- Complaints, service and field data
- PMCF and literature
- Performance monitoring reports
Hands over
- Signal assessments
- Affected-document lists for CAPAs
- Input to PMS reports and PSURs
Typically held by
Reader roles of the pathway map that usually take on this function.
- Technical writers
- Receives the affected-document list and updates the IFU.
- Technical marketers
- Stops claims that a signal undermines.
- Technical project managers
- Tracks CAPAs until the documents are released.
- Documentation systems developers
- Links signals to versions, risks and documents.
On the map
- Post-market signals into the file· The medical-device evidence chain: from intended purpose to post-market evidence
Collects and assesses signals and names the documents a CAPA or change affects.
- Real-world performance· The medical-device evidence chain: from intended purpose to post-market evidence
Treats a drop in real-world performance as a signal.
- Risk management file· The medical-device evidence chain: from intended purpose to post-market evidence
Hands assessed signals to the risk management 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:
- Post-market signals into the file — Collects and assesses signals and names the documents a CAPA or change affects.
- Real-world performance — Treats a drop in real-world performance as a signal.
- Risk management file — Hands assessed signals to the risk management file.
Why a functional role
The functional role that collects and assesses post-market signals and makes sure their consequences reach the risk management file, the labelling and the claims 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 “Post-market signal owner” a job title?
- No. Not the vigilance reporting function, which keeps its own deadlines. The map describes what has to be done, not who does it on the org chart.
- What does the role not decide?
- The decision to report a serious incident (vigilance process); The risk estimate itself; Labelling wording.
Sources
- Regulation (EU) 2017/745 on medical devices (MDR) — EUR-Lex, 5 May 2017Law in force: Binding legislation that applies as of the review date.
- Regulation (EU) 2017/746 on in vitro diagnostic medical devices (IVDR) — EUR-Lex, 5 May 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.