Reference

Glossary

Terms in plain language, paired with practical examples from regulated software assurance.

Editorial previewTechnical review and author byline approval pending
TermPlain-language explanationPractical example
Intended useThe job people rely on the system to performERP blocks issue of quarantined material
Context of useThe circumstances in which the task is performedExpert reviewers using source documents during protocol review
CSVEstablishing and maintaining evidence that a computerized system suits its intended useAssessing and supporting an eQMS lifecycle
CSASoftware-assurance thinking focused on confidence in use through risk-informed activitiesSelecting tests around meaningful production or quality failures
GxPShorthand covering different regulated good-practice areasGMP and GCP have different contexts
RequirementA defined need or expected behaviorAn unauthorized user cannot close a CAPA
RiskThe assessed relationship between a possible failure and its consequences, using the applicable methodWrong unit mapping could support an incorrect acceptance decision
ControlA measure that prevents, detects, or manages a failureBlocking an unknown disposition code
Residual riskRisk remaining after the assessed controlsAn unresolved failure possibility accepted within defined conditions
Objective evidenceInformation that supports an assessable conclusionA traced transaction comparison with expected and actual outcomes
TraceabilityA visible connection among use, requirement, risk, evidence, and decisionRequirement MAT-02 linked to interface test IF-T08
Scripted testingTesting with predefined conditions, actions, and expected resultsExpiry boundary check at a defined time
Exploratory testingLearning, test design, and execution conducted together within a purposeInvestigating CAPA reassignment combinations
Negative testA challenge to behavior that should be rejected or preventedAttempting approval without permission
Boundary testA check around a point where behavior changesJust below, at, and above a specification limit
Regression testingChecking relevant existing behavior after a changeRechecking routing after a workflow-engine update
Supplier evidenceEvidence supplied by the product or service providerVersion-specific standard-feature test records
SaaSSoftware delivered as an online serviceA hosted eQMS with supplier-managed releases
eQMSElectronic quality management systemControlled documents, deviations, CAPA, and related workflows
LIMSLaboratory information management systemSample, test, result, and laboratory workflow management
MESManufacturing execution systemManaging and recording defined production execution activities
ERPEnterprise resource planning systemMaterial, inventory, and business-process management
CAPACorrective and preventive actionInvestigating and addressing a quality problem through a controlled process
Audit trailRecorded history of relevant events and changesWho changed a controlled value and when, with required context
Data lineageThe path from source information through transformations to usePDF extraction, indexing, retrieval, and AI finding
ALCOACommon data-integrity shorthand: attributable, legible, contemporaneous, original, accurateA result linked to its creator, context, and trustworthy record
RAGRetrieval-augmented generation: retrieved material is supplied to support generationAn assistant answers using selected approved procedure passages
GroundednessThe extent to which a claim is supported by its provided sourceA cited passage actually supports the stated instruction
HallucinationGenerated content presented as factual without adequate supportAn invented procedure requirement
False positiveA proposed finding that is not a real issue under the reference definitionFlagging an approved exception as a defect
False negativeA reference issue the system fails to identifyMissing an incorrect acceptance limit
PrecisionCorrect findings divided by all proposed findings32 correct out of 38 proposed findings
RecallCorrectly identified reference issues divided by all reference issues32 identified out of 40 reference issues
Evaluation leakageEvaluation information influences development or otherwise undermines the intended independenceTuning a prompt repeatedly on the final test cases
DriftA change in data, behavior, or performance relevant to the useNew document formats lead to more extraction failures
Prompt injectionUntrusted content attempts to redirect the assistant’s behaviorA document tells the assistant to disclose restricted information
AgentAn AI-enabled application that can select or execute actions through toolsAn assistant creating proposed investigation tasks
Human oversightDefined human checks and decisions with suitable authority and capabilityA qualified reviewer verifies sources and disposes findings
ReassessmentRevisiting a conclusion when relevant conditions changeEvaluating a new parser or source corpus