Pharmaceutical Serialization, Business Analysis, and System Validation

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/45

flashcard set

Earn XP

Description and Tags

Vocabulary practice flashcards covering serialization standards (GS1, L1-L5 architecture), business analysis methodologies (process mapping, requirements gathering, stakeholder management), and computer systems validation (SDLC V-model, GAMP 5, 21 CFR Part 11, and test qualification phases).

46 Terms

1
New cards

Serialization

The process of assigning a unique number or identifier to a given product or packaging level, typically requiring manufacturers to print a 2D barcode or DataMatrix encoding a GTIN, unique serial number, batch or lot number, and expiry date.

2
New cards

Track

The process of determining where a product is currently located within the supply chain.

3
New cards

Trace

The process of identifying all entities that a product has been in contact with, serving as a system of record.

4
New cards

GTIN (Global Trade Item Number)

A GS1 identification standard used to uniquely identify products.

5
New cards

GLN (Global Location Number)

A GS1 identification standard used to identify physical and legal locations.

6
New cards

SSCC (Serial Shipping Container Code)

A GS1 identification standard used to identify logistics units.

7
New cards

GDTI (Global Document Type Identifier)

A GS1 standard used to identify documents.

8
New cards

GSRN (Global Service Relation Number)

A GS1 standard used to identify service relationships.

9
New cards

GIAI (Global Individual Asset Identifier)

A GS1 identification standard used to identify individual fixed assets.

10
New cards

GRAI (Global Returnable Asset Identifier)

A GS1 identification standard used to identify returnable assets.

11
New cards

GSIN (Global Shipment Identification Number)

A GS1 identification standard used to identify shipments.

12
New cards

GINC (Global Identification Number for Consignment)

A GS1 identification standard used to identify consignments.

13
New cards

GS1 DataBar

A GS1 barcode capture format used for product data at the point of care/use and for coupons.

14
New cards

GDSN (Global Data Synchronization)

A GS1 standard used to share master product data across organizations.

15
New cards

EPCIS (Electronic Product code Information Services)

A GS1 standard used to share product event data across the supply chain.

16
New cards

Level 1 Serialization

The device level of serialization architecture, consisting of physical hardware such as printers printing GS1 DataMatrix codes, vision inspection cameras verifying readability, reject mechanisms, and line performance sensors/controllers.

17
New cards

Level 2 Serialization

The packaging line layer that communicates with Level 1 equipment to receive serial numbers, assign them to packs, instruct printers, collect vision verification results, handle rejects, and manage aggregation hierarchies from packs to cartons, cases, and pallets.

18
New cards

Level 3 Serialization

The central serialization management platform within a manufacturing facility that coordinates multiple packaging lines, manages site serial number pools, stores site-level event data, manages aggregation hierarchies, and handles exceptions and rework.

19
New cards

Level 4 Serialization

The enterprise management layer that generates and distributes global serialization numbers, tracks supply chain events across the organization, and integrates with enterprise systems like ERP and warehouse management platforms.

20
New cards

Level 5 Serialization

The external network and regulatory ecosystem outside the manufacturer, including national drug verification systems, regulatory traceability platforms, supply chain partner networks, and global data exchange networks.

21
New cards

Current-State ("As-Is") Process Map

A process mapping artifact that documents how a process operates today in order to identify bottlenecks, redundancies, manual handoff rework loops, and delays.

22
New cards

Future-State ("To-Be") Process Map

A process mapping artifact designed to streamline work, automate manual steps, standardize procedures, reduce risk, and establish target KPIs.

23
New cards

ALCOA+

A data integrity framework for regulated environments requiring data to be Attributable (who, when, why), Legible (clear, permanent), Contemporaneous (recorded at time of action), Original (first capture), Accurate (true, error-free), and Complete (+ no missing entries).

24
New cards

JAD Sessions (Joint Application Development)

Collaborative workshop sessions used in requirements elicitation to align multiple departments simultaneously.

25
New cards

Gemba Walk

An elicitation technique involving direct floor observation to see how work is actually executed in practice, rather than relying solely on SOP descriptions.

26
New cards

Functional Requirements

Requirements defining the specific behaviors, actions, or functions a system must perform (e.g., displaying daily yield reports by batch).

27
New cards

Non-Functional Requirements

Requirements specifying system criteria such as performance, security, usability, and regulatory compliance (e.g., loading reports within 10 seconds or complying with 21 CFR Part 11 audit trails).

28
New cards

INVEST

A quality criteria checklist for Agile user stories: Independent, Negotiable, Valuable, Estimable, Small, and Testable.

29
New cards

Use Case

A formal, step-by-step description of user-system interactions outlining actors, preconditions, main flow, alternate flows, exception flows, and postconditions; well-suited for complex or validated systems.

30
New cards

Requirement Traceability Matrix (RTM)

A matrix linking each system requirement directly to its design specification, corresponding test case, and validation results.

31
New cards

MoSCoW

A requirements prioritization framework that categorizes requirements into Must have, Should have, Could have, and Won't have.

32
New cards

Power/Interest Grid

A stakeholder analysis tool categorizing stakeholders into four quadrants: High Power/Low Interest (Keep satisfied), High Power/High Interest (Manage closely), Low Power/Low Interest (Monitor), and Low Power/High Interest (Keep informed).

33
New cards

RACI Matrix

A responsibility assignment chart mapping roles to project tasks using four designations: Responsible, Accountable, Consulted, and Informed.

34
New cards

URS (User Requirements Specification)

The foundation document written by the business/system owner defining what business and user needs the system must fulfill without specifying how; verified directly by PQ/UAT in the V-model.

35
New cards

FS (Functional Specification)

The specification defining how each system function operates, which is mapped directly against Operational Qualification (OQ) on the V-model.

36
New cards

DS (Design/Configuration Specification)

The technical specification defining system build, design, and configuration parameters, verified directly by Installation Qualification (IQ) on the V-model.

37
New cards

IQ (Installation Qualification)

The validation phase that verifies whether the system is installed correctly, covering correct versions, patches, server configurations, user roles, and required documentation.

38
New cards

OQ (Operational Qualification)

The validation phase that verifies whether each function operates as specified across operational limits and boundary/error conditions, such as correct workflow routing and invalid entry rejection.

39
New cards

PQ (Performance Qualification)

The validation phase that verifies whether a system operates reliably in real-world use by running end-to-end business processes with real users and production-like data.

40
New cards

GAMP 5 Category 1

Infrastructure software (e.g., operating systems and databases) that requires a low validation effort consisting primarily of recording the configuration.

41
New cards

GAMP 5 Category 3

Non-configured software (e.g., firmware and off-the-shelf tools) that requires a low-to-moderate validation effort.

42
New cards

GAMP 5 Category 4

Configured software (e.g., SAP, LIMS, and MES) requiring a moderate validation effort focused on verifying application configuration.

43
New cards

GAMP 5 Category 5

Custom software (e.g., custom code and macros) that entails the highest validation effort.

44
New cards

21 CFR Part 11 Audit Trail

A secure, computer-generated, time-stamped record tracking who performed an action, what was done, when it occurred, and the reason for changes, which cannot be modified by users.

45
New cards

UAT (User Acceptance Testing)

Testing conducted before go-live (after functional testing) to confirm that the system meets business requirements, fits real user workflows, and answers 'Does this solve our problem?'.

46
New cards

Regression Testing

Testing conducted after any patch, upgrade, configuration change, or bug fix to verify that modifications did not break existing system functions, answering 'Does everything that worked before still work?'.