QPPV.COM KNOWLEDGE ASSESSMENT

Knowledge Assessment: Functional and Design Specifications in Pharmacovigilance

Test your understanding of the concepts covered by Functional Specifications and Design Specifications in Pharmacovigilance.

Question 1 of 10Pass mark: 80%

Question 1 of 10 For a highly configured global safety database supporting expedited reporting, what is the most defensible documentation approach?

Use no specifications because the software is commercial Apply extensive but risk-justified functional and configuration documentation with traceability to testing Document only the supplier's marketing brochure Use the same minimal documentation required for a low-risk administrative repository

Question 2 of 10 Which statement best distinguishes a Functional Specification from a User Requirements Specification?

The Functional Specification defines business objectives, whereas the URS defines database architecture The Functional Specification translates approved requirements into expected system behaviour, whereas the URS defines what the business needs The Functional Specification documents supplier qualification, whereas the URS documents user training The Functional Specification is always technology specific, whereas the URS is always configuration specific

Question 3 of 10 A cloud-based pharmacovigilance SaaS provider manages infrastructure and security patching. Which activity remains necessary for the regulated organisation?

No validation activity because infrastructure is outsourced Assessment of supplier governance, change notifications, disaster recovery and ongoing service performance Rebuilding the provider's data centre qualification package Treating all supplier changes as non-impacting

Question 4 of 10 Which consideration is most consistent with GAMP 5 Second Edition and CSA principles when determining documentation depth?

Use a fixed document template for every system Base the approach on complexity, intended use, patient-safety impact, data-integrity risk and configuration Produce the maximum possible volume of technical documents Minimise documentation solely according to project budget

Question 5 of 10 Which change would most clearly require review of the Design Specification?

A change to a user's preferred screen colour A change to network architecture supporting the reporting gateway A correction to a training-room attendance list A change to the wording of a non-controlled presentation

Question 6 of 10 Which inspection evidence would best support the conclusion that an organisation has maintained control of a configured E2B(R3) reporting process?

A supplier advertisement describing E2B capability A current configuration record linked to requirements, approved changes, interface testing and submission evidence An obsolete system screenshot with no version information A list of all software features that are not used

Question 7 of 10 Which statement best captures the overall purpose of Functional, Design and Configuration Specifications?

To maximise the number of controlled documents in the validation package To provide a clear, proportionate and traceable explanation of how approved business needs become validated operational capability To transfer responsibility for system compliance to the software supplier To document technical details regardless of their relevance to intended use

Question 8 of 10 What is the principal validation significance of traceability between requirements, specifications and tests?

It demonstrates that every document has been written by a different department It demonstrates that approved business needs were translated into implemented and objectively verified functionality It proves that the supplier's source code is error free It permits testing to be omitted when supplier documentation exists

Question 9 of 10 During an inspection, the live safety database behaves differently from the approved Functional Specification. What is the most appropriate interpretation?

The discrepancy is irrelevant if users have become accustomed to the workflow The documentation may no longer reflect the validated state and should be investigated through change control or remediation The live system automatically supersedes all controlled documentation The discrepancy proves that the Design Specification is too detailed

Question 10 of 10 A COTS supplier provides architecture and functional documentation for a safety database. What should the regulated organisation do before relying on it?

Accept it automatically because it was produced by the supplier Reproduce the entire documentation set internally regardless of relevance Review it for adequacy, assess it against intended use and supplement it with local implementation records where needed Discard it and validate the supplier's software development process from the beginning

Knowledge Assessment: Functional and Design Specifications in Pharmacovigilance

Cookie Settings