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 A team is deciding where to document the architecture of an E2B(R3) gateway, including interface components, authentication mechanisms and network dependencies. Where does this information primarily belong?

User Requirements Specification Functional Specification Design Specification User acceptance test script

Question 2 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 3 of 10 Which sequence best represents progressive refinement through the validation lifecycle?

Design Specification, URS, Functional Specification, testing, configuration URS, Functional Specification, Design or Configuration Specification, implementation, validation testing Validation testing, URS, Design Specification, business need, operational use Configuration Specification, business need, URS, supplier selection, testing

Question 4 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 5 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 6 of 10 Which statement best describes the validation focus for configuration rather than custom software development?

The organisation must validate the supplier's underlying source code as if it developed it The organisation primarily verifies that approved configuration correctly supports the intended business process Configuration is outside the validated system because no code was written locally Configuration changes never require regression testing

Question 7 of 10 A proposed system change alters the way duplicate cases are identified and routed for review but does not change the underlying infrastructure. Which specification is most directly relevant to assessing the business-process impact?

Functional Specification Disaster recovery plan only Supplier financial assessment Network architecture diagram only

Question 8 of 10 When may an organisation reasonably combine Functional and Design Specifications into one controlled document?

Whenever the system is used for pharmacovigilance, regardless of risk Only when the supplier refuses to provide technical documentation For a relatively simple or low-risk system, provided functional and technical perspectives remain clear and traceability is maintained Whenever combining documents reduces the number of approval signatures

Question 9 of 10 Which example most clearly represents a traceability gap?

A Design Specification references the relevant Functional Specification A validation test is linked to a functional requirement and records objective results A configured reporting rule exists in the system but has no documented requirement or implementation rationale A supplier architecture document is referenced under document control

Question 10 of 10 Which responsibility remains with the Marketing Authorisation Holder when a supplier has validated its commercial pharmacovigilance application?

Ensuring the local configuration and implementation are fit for intended use Owning all supplier source code Performing all supplier software development testing again without evaluation Guaranteeing that no future supplier release will affect the system

Knowledge Assessment: Functional and Design Specifications in Pharmacovigilance

Cookie Settings