Professional Documents
Culture Documents
2. Section B – Scope
<Include brief product description and type of users, jurisdictions/marketplace where device is
marketed, expected lifetime of device (single use or reusable), and historical safety and
performance data (if available).>
Intended use:
Example:
Servicing Representative Joe Smith, Serving Responsible for gathering warranty and
Manager service data
Training and Customer
Support
Manufacturing
Representative
Marketing Representative
Quality Assurance
Representative
Regulatory Affairs / Clinical
Affairs
Subject Matter Expert
Discussion:
Discussion:
Discussion:
Discussion:
<Data collection protocol – include:
What data will be collected (positive and negative)
Methodology – how data is collected and managed
Document the data source, including identification of search terms, field to use, qualifiers of
data sorting, date ranges, and how data is extracted
How data is recorded and by whom
Location of data repository
How data is monitored and updated
How to ensure data integrity and quality
Who is responsible for data integrity and quality>
Discussion:
Discussion:
Discussion:
Discussion:
13. Section M – Vigilance Reporting: Serious Incidents, Including Information from PSURs
Inputs: Responsible: Frequency:
Discussion:
Discussion:
Discussion:
Number Appraisal
Report Compilation Output Type or Structure
Methods
<Numbe Example: Example: Example:
r linked <Identify how to run a report from
<Output the data into an Excel <Review each data
to the the Customer Feedback Database
spreadsheet to allow further report against the
data for each search term or filter listed.>
sorting, organization, and raw data to ensure
source in
analysis of data. there is no missing
above
Each search criteria shall be information.
table
(e.g., on a different sheet in the All data must be
1,2,3> Excel spreadsheet. included based on
Maintain the Excel the search criteria;
spreadsheet as part of raw any references to
data component and save the reportable events
data in a standardized location or FSCA reporting
for the PMS Plan/Report.> shall be clearly
identified as part of
the customer
complaint
process.>
2. Etc. Etc. Etc.
3. Etc. Etc. Etc.
4. Etc. Etc. Etc.
PMS Data PMS Source Normal Activity Significant Alert Level Action Level
Source Type Trend Increase (GSPR) (GSPR)
Number
1 Customer and Recorded in the None required None None
market customer established or established or
feedback feedback required required
database
PMS Data PMS Source Normal Activity Significant Alert Level Action Level
Source Type Trend Increase (GSPR) (GSPR)
Number
2 Customer Complaints Review risk Review risk Require change
complaints recorded, analysis report analysis report to risk analysis
evaluated, and for individual for individual including
investigated risks. risks. severity or
according to Initiate a Initiate a occurrence
procedure; preventive preventive level.
monthly report action request. action request. Review benefit-
generated risk profile.
Initiate a
corrective action
request.
3 Patient and Determination of Initiate a Review None
marketing feedback or preventive customer established or
surveys complaint action request. complaint required
entered in those database for
databases trends.
Initiate a
preventive
action request.
Example: <The Postmarket Surveillance Report (PMSR)/Periodic Safety Update Report (PSUR) will be
generated as an output of the PMS Planning process and will be a compilation of activities associated with
postmarket surveillance. These reports are identified in the quality management system with an
identification number and linked to the Postmarket Surveillance Plan (PMS Plan) through reference to the
PMSR/PSUR document number. When changes to the PMS Plan or postmarket surveillance are required,
a review, update, and reapproval of the planning and report documentation will be initiated. The PMS Plan
is part of the product technical documentation updated and maintained through the life of the product. The
PMS Plan for the product family is referenced in the technical documentation file and the PMSR/PSUR for
location of the records. These files are maintained in accordance with the record retention policies.>
Technology; consider design changes, changes in the Indications for Use, and changes that could affect
safety and performance.>
REVISION HISTORY:
Revision Date Revision History