Skip to content
Free previewYou are reading 1 of 42 lessons, in the same interface members use. Everything else unlocks with full access.Get full access · $150

GxP Systems and Regulations | Foundational

GxP computerized system fundamentals

A computerized system is more than an application. Your first assurance decision is to establish the regulated activity, the intended use, and the people, technology, and records that support it. That foundation determines what evidence is relevant and which controls need attention.

What you will learn

  • Classify manufacturing, nonclinical laboratory, and clinical investigation activities within the appropriate GxP context. Mapping: GxP computerized system fundamentals, regulated activity recognition.
  • Distinguish computerized system validation, computer software assurance, software validation, and infrastructure qualification. Mapping: GxP computerized system fundamentals, assurance terminology.
  • Define system boundaries across applications, interfaces, data, equipment, infrastructure, services, users, and procedures. Mapping: GxP computerized system fundamentals, system scope.
  • Compare custom, configured, commercial, embedded, infrastructure, and SaaS system characteristics. Mapping: GxP computerized system fundamentals, system classification.
  • Separate application validation from equipment qualification, process validation, and infrastructure qualification. Mapping: GxP computerized system fundamentals, evidence boundaries.

Blueprint mapping: GxP Systems and Regulations → Regulated Systems and Frameworks → GxP Computerized System Fundamentals, blueprint anchor bp.d1.t1. Topic weight is not supplied.

EST. TIME 20-25 minutes for the core lesson; allow additional time for all practice questions.

PREREQS None.

OUTPUTS You should be able to choose an activity-based GxP classification, outline a defensible system boundary, and identify which assurance evidence addresses a proposed use.

WHY

Why it matters

  • A system can perform technically as designed while producing incomplete regulated records or supporting the wrong business decision.
  • Supplier evidence, infrastructure checks, equipment qualification, and application testing answer different questions. Treating them as interchangeable creates assurance gaps.
  • A clear boundary makes responsibility visible, particularly when interfaces and cloud services divide control across organizations.

Source-pack baseline: November 1, 2026. The supplied course identifies FDA's September 2025 final Computer Software Assurance guidance as a driver for risk-based assurance. Its detailed scope is addressed in the later FDA CSA Guidance and Scope topic. Do not assume that every GxP application falls within the same guidance scope or that CSA removes applicable requirements.

The supplied blueprint names binding U.S. provisions separately from FDA guidance and industry approaches. It identifies Part 11 controls where electronic records and signatures fall within scope, pharmaceutical computerized-system controls under 21 CFR 211.68, and related pharmaceutical quality and record obligations. FDA's September 2003 Part 11 guidance explains an interpretation and enforcement approach; it does not repeal the regulation or predicate rules. This lesson establishes the vocabulary needed to investigate applicability, rather than providing a complete jurisdictional determination.

Where things stand: The supplied material supports practical distinctions between regulations, guidance, and assurance methods. It does not establish a universal adoption rate, a new EU implementation date, or an agency-issued examination. This is a professional course, and no endorsement or joint credential issuance by the named organizations is implied.
KEY TERMS

Key Terms & Must-Know Facts

Table 1. Working vocabulary for system assurance
TermPractical meaning
GxPAn umbrella term for good-practice requirements associated with particular regulated activities; it is not one universal regulation.
Good Manufacturing Practice, GMPThe good-practice context associated with regulated manufacturing and related quality operations.
Good Laboratory Practice, GLPThe good-practice context associated with applicable nonclinical laboratory studies; it does not describe every laboratory activity.
Good Clinical Practice, GCPThe good-practice context associated with clinical investigations and their conduct and records.
Computerized systemThe combination of software, hardware, data, associated equipment, people, and procedures needed to perform an intended function.
Intended useA statement of what the system does, for whom, in which process, and for which decisions or records.
Computerized system validation, CSVA lifecycle approach to establishing and maintaining documented evidence that a computerized system is suitable for its intended use.
Computer software assurance, CSAA risk-based approach to establishing confidence in software and its use, with assurance activities and evidence selected using critical thinking.
Software validationEvaluation of whether software satisfies its intended use and relevant requirements; the surrounding computerized-system scope may be broader.
Infrastructure qualificationEvidence that supporting infrastructure is established and operates suitably for its specified role.
Commercial off-the-shelf, COTSA commercially available product whose suitability still depends on the regulated organization's intended use and implementation.
ConfigurationSelection or adjustment of supported settings, rules, roles, workflows, or other product features.
Software as a service, SaaSA delivery model in which a supplier operates an application service while customer responsibilities remain to be defined.
Predicate ruleAn underlying applicable requirement governing an activity or record, considered alongside relevant electronic record and signature requirements.

Must-know facts

  • GxP relevance follows the regulated activity and the function's role in that activity.
  • A laboratory location alone does not establish GLP applicability.
  • System boundaries include material data transfers and external dependencies.
  • A software sourcing category does not establish its GxP impact.
  • Supplier assurance can contribute evidence without resolving every customer responsibility.
  • Validation evidence must be relevant to the intended use, implementation, and applicable controls.
  • A qualified technical platform does not by itself establish that an application workflow is suitable.
CORE

Core content

1.1.1.1 1. Identify the regulated activity before naming the system

A Explanation

Decision conflict: Classify by the activity being supported, or classify by the department, product label, or room containing the computer. Choose the activity. WHY THIS IS TESTED: An incorrect starting classification sends the assurance team toward the wrong records, controls, and accountable process owner.

GMP, GLP, and GCP are useful starting categories, but none is assigned merely because the organization manufactures medicines or employs scientists. A manufacturing quality-control laboratory can support GMP activities. A nonclinical study laboratory can support applicable GLP studies. A clinical research system can support GCP activities. One technical platform may support several activities, so evaluate uses separately when necessary.

Begin with a plain statement: who uses the function, what activity it performs, what record it creates or changes, and what decision relies on its output. Then identify the applicable requirements through the organization's regulatory applicability process. Other GxP contexts may apply; this source pack does not provide a complete catalogue of them. See Fig 1.

Fig 1. Activity-based GxP orientation
Exam takeaway: The regulated activity provides the starting point for applicability, while location supplies context.
flowchart TD; A[Describe intended activity] --> B{What does the function support?}; B --> C[Manufacturing and related quality]; B --> D[Applicable nonclinical study]; B --> E[Clinical investigation]; C --> F[Assess GMP requirements]; D --> G[Assess GLP requirements]; E --> H[Assess GCP requirements]; F --> I[Confirm applicable rules and records]; G --> I; H --> I;
Same laboratory, different regulated purposes
Exam takeaway: Similar instruments can support different regulatory contexts because their activities and records differ.
{"prompt":"Three-panel professional educational illustration on a white background, blue and gray flat vector style. Show the same type of laboratory workstation in three contexts: manufacturing quality control with a batch record, nonclinical study testing with a study record, and clinical investigation specimen tracking with a participant code. Label panels Manufacturing QC, Nonclinical study, Clinical investigation. Use arrows from each workstation to its distinct record. Do not imply every laboratory is GLP. No figure numbers, no decorative background.","caption":"Same laboratory, different regulated purposes","size":"1024x1024"}
From activity to applicability
Exam takeaway: Identify the use and record before selecting the relevant framework.
1. Describe the activity.
2. Identify the resulting record or decision.
3. Identify potentially applicable GxP requirements.
4. Confirm the applicability rationale with the responsible functions.

B Worked example

A 48-year-old laboratory lead with hypertension and migraine reviews an instrument application used to generate tablet release-test results. The room also contains a research freezer, and a development sample has an unusual pH. A supplier brochure calls the application GLP-ready. What is the most appropriate initial classification approach?

  1. Identify the task: Classify this use of the application, rather than the whole laboratory.
  2. Extract key facts: The output supports manufacturing release testing; the research freezer and lead's health history do not define this use.
  3. Apply the rule: Begin with the manufacturing quality-control activity and assess the applicable GMP controls.
  4. Eliminate: The GLP-ready label describes a supplier claim, not a determination that this activity is a GLP study.
  5. Verify: Confirm the records, intended use, process owner, and applicability rationale before developing the assurance scope.

C Common trap

Wrong choice: Treat all laboratory software as GLP software. Why tempting: Laboratory appears in the name of the framework. Single eliminating clue: The stated use is manufacturing release testing.

D Checkpoint

A shared platform supports a nonclinical study and manufacturing quality-control testing. Which approach is most appropriate?

  1. Apply the supplier's single GxP classification to both uses.
  2. Evaluate the regulated activities, records, and applicable controls for each use.
  3. Classify both uses according to the department that owns the server.
  4. Use the classification associated with the platform's original deployment.

Answer: 2. Option 1 is tempting because a common label simplifies governance, but it can conceal different obligations. Option 2 is correct because activity and use determine applicability. Option 3 is tempting because the department provides ownership, but server ownership does not classify regulated work. Option 4 is tempting because existing evidence may be reusable, but historical deployment does not settle a new use.

If you missed this: Review Identify the regulated activity before naming the system - focus on activity-specific applicability.

1.1.1.2 2. Distinguish assurance approaches from the object being assured

A Explanation

Decision conflict: Select evidence that addresses the intended-use question, or accept a familiar assurance label as sufficient. Choose the evidence question first. WHY THIS IS TESTED: CSV, CSA, software validation, and qualification can overlap in a lifecycle, but the terms do not establish identical scope or interchangeable evidence.

CSV addresses the computerized system over its lifecycle. CSA emphasizes risk-based confidence and critical thinking in selecting assurance activities and evidence. A comparison of methods should therefore ask what needs to be established and how the evidence supports that conclusion. It should not assume that one term means extensive scripts and another means no documentation.

Software validation concerns the software's suitability for intended use. Infrastructure qualification concerns the supporting technical environment. A statement about one layer cannot automatically answer a question about another. For example, evidence that storage is available does not demonstrate that an application preserves the complete regulated record.

Table 2. Assurance terms and their practical questions
TermQuestion it helps answerConclusion it does not establish alone
CSVIs the computerized system suitable and maintained for its intended use?Every use of the same product is covered.
CSAWhat risk-based activities provide sufficient confidence in the software and its use?Applicable records or controls can be omitted.
Software validationDoes the software satisfy its intended use and relevant requirements?All people, interfaces, and procedures are controlled.
Infrastructure qualificationIs the supporting environment suitable for its specified role?The business application and workflow are suitable.

See Fig 2 for the evidence distinction. Detailed CSA guidance applicability belongs in FDA CSA Guidance and Scope; this introduction does not extend that guidance to every pharmaceutical, laboratory, or clinical use.

Fig 2. Match evidence to the question
Exam takeaway: A valid assurance claim needs evidence addressing the particular use and layer under review.
flowchart TD; A[State the assurance question] --> B{What needs confidence?}; B --> C[Software behavior]; B --> D[Supporting environment]; B --> E[End to end computerized use]; C --> F[Assess software validation evidence]; D --> G[Assess infrastructure evidence]; E --> H[Assess lifecycle system evidence]; F --> I[Identify remaining gaps]; G --> I; H --> I;
Evidence claims at different layers
Exam takeaway: Infrastructure evidence and application evidence should be connected without being treated as equivalent.
{"prompt":"Professional educational comparison illustration, white background, cool blue and gray flat vector style. Left column shows server, storage, and network labeled Infrastructure evidence. Right column shows a laboratory application workflow, user roles, and a complete electronic result record labeled Intended-use evidence. Between them place a small connector labeled Supports, not substitutes. Use simple clean icons and short labels. No certification seals or regulatory endorsements, no figure numbers.","caption":"Evidence claims at different layers","size":"1024x1024"}
Choose assurance by the question
Exam takeaway: Select the method after identifying the intended use and evidence gap.
1. State the intended-use question.
2. Identify the relevant software and system layers.
3. Assess available objective evidence.
4. Select proportionate additional assurance.

B Worked example

A 55-year-old validation manager with type 2 diabetes and osteoarthritis reviews a newly hosted laboratory application. The infrastructure package shows successful server installation checks and a storage-capacity alert that was resolved. The project dashboard is green, and the team proposes release without evaluating the configured result-approval workflow.

  1. Identify the task: Decide whether the evidence supports the laboratory application's intended use.
  2. Extract key facts: Infrastructure evidence is available, but the configured approval workflow has not been evaluated.
  3. Apply the rule: Supporting-platform suitability does not establish application-workflow suitability.
  4. Eliminate: The green dashboard summarizes project status; it is not evidence that the approval function behaves appropriately.
  5. Verify: Review requirements and risk for the approval function, assess any relevant supplier evidence, and address the remaining gap before authorization under local procedures.

C Common trap

Wrong choice: Accept infrastructure qualification as application validation. Why tempting: Both packages can contain technical checks and approvals. Single eliminating clue: The proposed conclusion concerns an unevaluated configured workflow.

D Checkpoint

Which statement best describes the relationship between CSA and CSV in this lesson?

  1. CSA makes supplier documentation sufficient for all customer uses.
  2. CSV limits assurance to scripted software testing before deployment.
  3. CSA emphasizes risk-based confidence without removing applicable obligations.
  4. CSV establishes that qualified infrastructure covers the application lifecycle.

Answer: 3. Option 1 is tempting because supplier evidence can be useful, but customer-use gaps remain possible. Option 2 is tempting because legacy projects often emphasize scripts, but CSV is a lifecycle concept. Option 3 is correct because method selection must remain linked to evidence and applicable obligations. Option 4 is tempting because infrastructure supports the application, but it does not establish the application's suitability over time.

If you missed this: Review Distinguish assurance approaches from the object being assured - focus on evidence relevance rather than labels.
Quick Recall:
  • Fill in: A laboratory's regulated classification begins with its ______. Answer: activity.
  • True or false: A qualified server establishes the suitability of every hosted workflow. Answer: False.
  • One line: What must a supplier assurance claim be compared against? Answer: The customer's intended use and implementation.

1.1.1.3 3. Map the boundary and classify system characteristics

A Explanation

Decision conflict: Draw the boundary around the purchased application, or include the dependencies that can affect the regulated outcome. Choose an end-to-end boundary. WHY THIS IS TESTED: A narrowly drawn application boundary can omit the interface, user action, or service that actually changes a regulated record.

A practical boundary follows the activity from input to output and onward to required retention and retrieval. Include relevant hardware, software, databases, interfaces, automated equipment, cloud services, users, and procedures. A component may sit outside the organization's direct control while remaining a relevant dependency. Distinguish what the team controls from what the process relies upon.

Classifications describe characteristics, not a universal ranking of safety or documentation burden. A COTS product may be configured. A SaaS product may be commercial, configured, and dependent on custom interfaces. Embedded software can control automated equipment. Infrastructure supports applications but can still affect availability, access, or data preservation. See Fig 3.

Table 3. System characteristics and scoping questions
CharacteristicWhat it describesUseful scoping question
Custom-developedSoftware developed for particular needs.Which requirements, design decisions, and changes need evidence?
ConfiguredProduct behavior established through supported settings or rules.Which local settings affect regulated decisions or records?
COTSA commercially available software product.Which supplier evidence is relevant to the implemented use?
EmbeddedSoftware integrated into equipment or a device.How does software behavior interact with equipment performance?
InfrastructureSupporting technical services and components.Which dependencies affect operation, security, or record availability?
SaaSAn application delivered as a supplier-operated service.Who controls configuration, updates, access, recovery, and data exit?
Fig 3. Boundary follows records and dependencies
Exam takeaway: Follow data and decisions across interfaces rather than stopping at the application name.
flowchart TD; A[Regulated process] --> B[Users and procedures]; A --> C[Application and configuration]; C --> D[Database and records]; C --> E[Equipment and interfaces]; C --> F[Infrastructure and cloud services]; B --> G[Decisions and required outputs]; D --> G; E --> G; F --> H[Availability and preservation]; H --> G;
The application is only part of the system
Exam takeaway: Relevant people, procedures, equipment, and services belong in the scope assessment.
{"prompt":"Labeled educational system-boundary illustration for a regulated laboratory, white background with thin blue and gray vector outlines. Place application and database in the center, connected to analyst and SOP, analytical instrument, interface service, identity provider, cloud infrastructure, and retained record retrieval. Use a clearly labeled System scope outline enclosing the relevant dependencies, and a separate small label Direct control varies. No vendor logos, no figure numbers.","caption":"The application is only part of the system","size":"1024x1024"}
Categories can overlap
Exam takeaway: SaaS delivery, commercial sourcing, configuration, and custom interfaces describe different characteristics.
{"prompt":"Clean educational comparison illustration in blue and gray on white. Show one central commercial SaaS laboratory application with four attached labeled cards: Commercial product, Supplier hosted, Customer configured, Custom interface. Place a small separate embedded instrument connected by the interface. Make clear these characteristics coexist rather than forming a ranking. Short labels only, generous margins, no figure numbers.","caption":"Categories can overlap","size":"1024x1024"}
Build a useful boundary
Exam takeaway: Trace the regulated outcome before assigning ownership to each dependency.
1. Trace inputs and record creation.
2. Identify processing and decisions.
3. Follow interfaces and retained outputs.
4. Record dependencies and responsibilities.

B Worked example

A 43-year-old laboratory supervisor with asthma and hypothyroidism uses a commercial SaaS application to receive instrument results through a locally developed interface. A workstation screen is slow, but the result transfer is automated. The supplier's validation package excludes the local interface, and the project team proposes a boundary ending at the SaaS login page.

  1. Identify the task: Define the computerized-system boundary for the regulated result flow.
  2. Extract key facts: The local interface transfers results and is excluded from supplier evidence.
  3. Apply the rule: A dependency that can affect record completeness or accuracy must be considered even when another organization hosts the application.
  4. Eliminate: The SaaS label does not remove the local interface from scope; the slow screen is a separate observation requiring relevance assessment.
  5. Verify: Map source fields, transformations, destinations, transfer failures, and responsible parties; determine the assurance needed for the transfer.

C Common trap

Wrong choice: Use the supplier contract boundary as the complete system boundary. Why tempting: Contract ownership looks like a clear technical limit. Single eliminating clue: Regulated data cross a locally developed interface outside that contract scope.

D Checkpoint

A commercial application is supplier-hosted, customer-configured, and connected to an instrument by custom code. Which description is most defensible?

  1. Classify it only as SaaS because hosting determines assurance scope.
  2. Classify it only as custom because one interface was developed locally.
  3. Classify it only as COTS because the principal application was purchased.
  4. Record the overlapping characteristics and assess their relevant boundaries.

Answer: 4. Option 1 is tempting because hosting divides responsibilities, but it does not describe all relevant behavior. Option 2 is tempting because custom code creates evidence needs, but it does not convert every component into custom software. Option 3 is tempting because procurement identifies the product, but it misses configuration and integration. Option 4 is correct because the characteristics coexist and direct attention to different evidence questions.

If you missed this: Review Map the boundary and classify system characteristics - focus on overlapping characteristics rather than one exclusive label.

1.1.1.4 4. Separate assurance responsibilities and integrate the evidence

A Explanation

Decision conflict: Release because one component has an approved package, or determine whether the combined evidence supports the regulated use. Choose the combined-evidence assessment. WHY THIS IS TESTED: Teams often possess substantial documentation while leaving one critical intended-use question unanswered.

Application validation, equipment qualification, process validation, and infrastructure qualification have related but distinct objects. The distinction is functional: ask which claim each package supports and whether its assumptions match the implementation. Reuse relevant evidence, identify exclusions, and address gaps without repeating work solely to create a second document.

Table 4. Similar assurance activities with different objects
ActivityPrimary object and questionEvidence gap it may leave
Application validationThe application and configured workflow: suitable for the intended use?Physical equipment performance outside the application evidence.
Equipment qualificationThe equipment: installed and operating suitably for its specified role?Locally configured electronic approvals or record transfers.
Process validationThe process: capable of consistently producing the intended result?Specific software access, audit-trail, or retrieval behavior.
Infrastructure qualificationThe technical environment: suitable for supporting the system?The meaning and completeness of application records.

Roles must also connect. The business or process owner defines the regulated use; IT supports technical operation; validation coordinates assurance evidence; and the quality function exercises applicable authority and organization-defined approval responsibilities. In pharmaceutical CGMP contexts, the blueprint specifically identifies quality-unit authority under 21 CFR 211.22. It does not prescribe the same signature sequence for every project. See Fig 4.

Fig 4. Combine evidence without merging its claims
Exam takeaway: Release confidence comes from relevant evidence across layers plus resolution of remaining gaps.
flowchart TD; A[Application evidence] --> E[Compare with intended use]; B[Equipment evidence] --> E; C[Infrastructure evidence] --> E; D[Supplier and process evidence] --> E; E --> F{Relevant gaps remain?}; F -->|Yes| G[Address gaps and reassess]; G --> E; F -->|No| H[Seek authorization under applicable procedures];
Choose evidence by the object under review
Exam takeaway: Equipment, process, infrastructure, and application evidence answer related but distinct questions.
{"prompt":"Four-panel professional educational illustration, white background, cool blue and gray flat vector style. Panels show: Application validation with configured approval workflow; Equipment qualification with analytical instrument checks; Process validation with manufacturing process and consistent output; Infrastructure qualification with servers, network, and storage. Give each panel one short question: Suitable workflow?, Suitable equipment?, Consistent process?, Suitable environment? Show no regulatory seals, no figure numbers, no gradients.","caption":"Choose evidence by the object under review","size":"1024x1024"}
Supplier service and customer use meet at shared controls
Exam takeaway: Hosting a service does not transfer every regulated-use responsibility to the supplier.
{"prompt":"Side-by-side educational responsibility illustration for SaaS in regulated laboratory operations. Left panel Supplier shows operated application service, platform maintenance, and supplier evidence. Right panel Regulated organization shows intended use, local configuration, user roles, procedures, and release decision. Center bridge labeled Defined agreement and evidence review connects them. Blue and gray vector style on white with crisp outlines, no universal assignment of backup ownership, no figure numbers.","caption":"Supplier service and customer use meet at shared controls","size":"1024x1024"}
Integrate evidence and ownership
Exam takeaway: A release recommendation should connect the intended use, evidence, unresolved issues, and responsible authority.
1. Define the release claim.
2. Map evidence to relevant layers.
3. Assess exclusions and unresolved issues.
4. Obtain the required authorization.

B Worked example

A 51-year-old quality specialist with chronic kidney disease and hypertension reviews a packaging line with embedded controls and an electronic batch-record interface. Equipment checks passed. A label color changed during the project, and the vendor reports broad industry use. However, the locally configured interface has not been assessed for transferring rejected-unit counts into the batch record.

  1. Identify the task: Determine whether the integrated regulated use has sufficient supporting evidence.
  2. Extract key facts: Equipment evidence exists, while a local record-transfer function remains unevaluated.
  3. Apply the rule: Evidence about physical equipment operation does not automatically establish correct transfer into the electronic batch record.
  4. Eliminate: Broad industry use and a cosmetic change do not close the identified interface gap.
  5. Verify: Confirm the required record content and interface behavior, assess relevant existing evidence, address remaining assurance needs, and document the release decision through applicable quality procedures.

C Common trap

Wrong choice: Release the integrated system because equipment qualification passed. Why tempting: The equipment generates the production information and already has an approved package. Single eliminating clue: A locally configured regulated-record transfer remains outside that evidence.

D Checkpoint

A SaaS supplier supplies a substantial test package. What is the most appropriate next action?

  1. Assess its relevance to intended use, configuration, interfaces, and responsibilities.
  2. Repeat every supplier test to create a complete customer-owned package.
  3. Accept the package as sufficient because the supplier operates the application.
  4. Use the number of documented tests to determine whether release is justified.

Answer: 1. Option 1 is correct because relevance and coverage determine what can be used and what remains. Option 2 is tempting because duplication appears conservative, but repetition without an evidence need is not a proportionate strategy. Option 3 is tempting because the supplier controls much of the technology, but customer use can introduce distinct requirements. Option 4 is tempting because test counts are easy to compare, but volume does not demonstrate coverage of the relevant risk.

If you missed this: Review Separate assurance responsibilities and integrate the evidence - focus on coverage and exclusions before deciding additional work.
Quick Recall:
  • Fill in: A system category describes a characteristic, not an automatic ______ level. Answer: risk.
  • True or false: Evidence outside a supplier package must always be generated by repeating the supplier's tests. Answer: False; first assess the actual gap.
  • One line: What connects different assurance packages? Answer: The defined intended use and the claims each package supports.
TRAPS

Exam Traps & Differentiators

Common traps & distractors:
  • One label settles the project. Tempting because a category makes planning fast; the eliminating clue is a second use with different records or decisions.
  • A full document set guarantees coverage. Tempting because completeness of filing resembles completeness of assurance; the eliminating clue is a requirement with no relevant evidence.
  • A low-complexity tool needs no assessment. Tempting because its behavior looks easy to understand; the eliminating clue is a regulated decision that depends on its output.
Table 5. Looks similar but is not equivalent
StatementMore precise distinctionDiscriminating question
The product is available commercially.Sourcing does not establish local suitability.What does this implementation do?
The application is hosted externally.Hosting does not define all responsibilities.Who controls each relevant activity?
The equipment passed its checks.Physical operation does not establish every electronic-record function.Was the record path included?
The data are backed up.A backup statement does not by itself demonstrate usable record retrieval.Can the required records be recovered and accessed?

See Fig 5 for a practical choose-versus-reject comparison.

Fig 5. Choose a supported conclusion
Exam takeaway: Prefer a conclusion tied to the intended use over one tied only to a product label or package size.
flowchart TD; A[Proposed assurance conclusion] --> B{What supports it?}; B --> C[Relevant use and evidence coverage]; B --> D[Label or document volume alone]; C --> E[Assess adequacy and remaining issues]; D --> F[Reject the shortcut]; F --> G[Return to use and evidence]; G --> E;
  • If the scenario says manufacturing release result, think manufacturing quality-control use and applicable GMP requirements.
  • If it says locally configured workflow, think evidence relevant to that configuration.
  • If it says supplier excludes the interface, think an explicit boundary and coverage gap to assess.
  • If it says technically installed, think whether the intended-use claim has actually been addressed.
Review connection: Return to Map the boundary and classify system characteristics whenever evidence appears complete but a data path or responsibility is missing.
What is coming next: The course proceeds from these foundations to regulatory hierarchy, Part 11 scope, and more detailed CSA guidance applicability. The source pack supports a trend toward proportionate assurance and greater supplier/SaaS evidence assessment, but supplies no specific future rule text or implementation deadline. Distinguish an announced proposal from an effective requirement before changing a control strategy.
ALGO

Algorithm / Approach

Use this five-step intake before selecting a validation template or accepting a supplier assurance claim. See Fig 6.

1. State the regulated activity and intended use.
2. Identify the decisions and records that depend on the function.
3. Map components, interfaces, people, procedures, and external dependencies.
4. Match existing evidence to the use and identify gaps.
5. Assign responsibilities and plan proportionate assurance under applicable procedures.
Fig 6. System-assurance intake decision tree
Exam takeaway: Clarify unresolved use or boundary questions before treating existing evidence as sufficient.
flowchart TD; A[Start assurance intake] --> B{Use and regulated role clear?}; B -->|No| C[Clarify with process owner]; C --> B; B -->|Yes| D[Map records and system boundary]; D --> E{Existing evidence covers the use?}; E -->|No| F[Define gaps and assurance activities]; E -->|Yes| G[Confirm responsibility and lifecycle controls]; F --> G;

Three key outputs

  • A specific intended-use statement that identifies the supported activity.
  • A boundary map with relevant data paths and responsibilities.
  • An evidence-gap assessment that informs the next assurance decision.
QUIZ

Self-check quiz

Questions 1 and 2 provide a brief quick check. Complete all five to apply the concepts across boundaries and evidence decisions.

1. Activity or location?

A spreadsheet calculates a manufacturing release-test result in a laboratory also used for nonclinical research. What is the best initial approach?

  1. Classify it under GLP because laboratory personnel maintain it.
  2. Assess its manufacturing quality-control use and applicable GMP requirements.
  3. Apply the framework used for the laboratory's largest research project.
  4. Use its spreadsheet format to determine regulatory applicability.

2. What does the evidence establish?

A server installation package is approved. The hosted application's approval workflow has been configured locally. Which conclusion is supported?

  1. The application workflow is covered because it runs on the approved server.
  2. The application workflow is covered if the supplier tested the standard product.
  3. The infrastructure evidence is relevant, but workflow suitability still needs assessment.
  4. The infrastructure package is irrelevant because validation concerns applications alone.

3. Where does the boundary end?

A SaaS laboratory application receives results through a customer-developed interface. The supplier package explicitly excludes that interface. What is the most appropriate next action?

  1. Record and assess the interface as part of the relevant regulated data path.
  2. Limit the boundary to the SaaS application because the supplier hosts it.
  3. Replace all supplier evidence with customer testing of the complete service.
  4. Limit interface evaluation to whether a network connection can be established.

4. Which assurance object is involved?

A project needs evidence that a manufacturing process consistently produces its intended result. Which activity primarily addresses that question?

  1. Application validation.
  2. Equipment qualification.
  3. Infrastructure qualification.
  4. Process validation.

5. How should supplier evidence be used?

A supplier package covers standard functionality but not customer-configured approval roles. The local procedure assigns release authorization responsibilities. What is the best next step?

  1. Accept the package because the supplier has more technical knowledge.
  2. Assess the configuration gap and obtain relevant assurance before the local release decision.
  3. Repeat every standard supplier test before assessing the local configuration.
  4. Use the approved local procedure as sufficient evidence that the roles behave correctly.
ANSWERS

Answer key & explanations

1. Answer: 2

  • Option 1: Tempting because GLP names a laboratory context; incorrect because this use supports manufacturing release testing.
  • Option 2: Correct because the regulated activity and use provide the starting point for applicability.
  • Option 3: Tempting because a dominant project can shape local procedures; incorrect because another project's framework does not classify this use.
  • Option 4: Tempting because spreadsheet tools have recognizable technical characteristics; incorrect because format does not determine the regulated activity.
If you missed this: Review Identify the regulated activity before naming the system - focus on the purpose of the result.

2. Answer: 3

  • Option 1: Tempting because the server is necessary for operation; incorrect because infrastructure evidence does not establish configured workflow behavior.
  • Option 2: Tempting because standard-product evidence may be useful; incorrect because its relevance to local configuration remains unestablished.
  • Option 3: Correct because the infrastructure package can contribute evidence without closing the application-use question.
  • Option 4: Tempting because application behavior is central; incorrect because supporting infrastructure remains a relevant dependency.
If you missed this: Review Distinguish assurance approaches from the object being assured - focus on the conclusion supported by each evidence layer.

3. Answer: 1

  • Option 1: Correct because the interface participates in regulated result transfer and has an explicit evidence exclusion.
  • Option 2: Tempting because supplier hosting provides a clear contractual limit; incorrect because regulated data cross that limit.
  • Option 3: Tempting because independent testing appears comprehensive; incorrect because relevant supplier evidence should be evaluated before deciding what additional work is needed.
  • Option 4: Tempting because connectivity is necessary; incorrect because connection success does not establish transfer accuracy or completeness.
If you missed this: Review Map the boundary and classify system characteristics - focus on following the record across interfaces.

4. Answer: 4

  • Option 1: Tempting because applications can control process steps; incorrect because the stated claim concerns consistent process results.
  • Option 2: Tempting because equipment contributes to production; incorrect because suitable equipment alone does not establish consistent performance of the complete process.
  • Option 3: Tempting because reliable infrastructure supports operation; incorrect because its primary object is the technical environment.
  • Option 4: Correct because process validation primarily addresses the process's capacity to produce its intended result consistently.
If you missed this: Review Separate assurance responsibilities and integrate the evidence - focus on the object of the assurance claim.

5. Answer: 2

  • Option 1: Tempting because supplier expertise is valuable; incorrect because expertise does not establish coverage of excluded customer settings.
  • Option 2: Correct because the identified configuration gap needs relevant assurance and the release decision must follow applicable responsibilities.
  • Option 3: Tempting because repeating tests creates visible activity; incorrect because it postpones assessment of the actual gap.
  • Option 4: Tempting because a procedure establishes expected conduct; incorrect because prescribing a role does not demonstrate that the configured software implements it.
If you missed this: Review Separate assurance responsibilities and integrate the evidence - focus on distinguishing expected controls from evidence of implemented behavior.
RAPID

Rapid review / cheat-sheet

  • Intake ambiguity → ask which decision would change if the output were wrong.
  • Shared platform → separate use statements before assuming one classification covers all work.
  • Boundary discussion → ask what happens immediately before input and after output.
  • Category dispute → record multiple characteristics when one label hides a dependency.
  • Evidence review → check exclusions before counting completed tests.
  • Configured role → distinguish a documented expectation from demonstrated behavior.
  • Release recommendation → state the supported claim and remaining limitations.
  • Lifecycle handoff → identify who responds when the use, configuration, or supplier service changes.

See also: Regulatory Hierarchy and Applicable Standards; Part 11 Electronic Records and Signatures; Pharmaceutical and Laboratory System Controls; System Inventory and Ownership; Intended Use and System Boundaries. These topics extend the present foundation; their content is not assumed here.

Blueprint anchor recap: GxP Systems and Regulations → Regulated Systems and Frameworks → GxP Computerized System Fundamentals, bp.d1.t1; subject: gxp-systems-and-scope. Coverage includes regulated activity recognition, assurance terminology, boundaries, overlapping system characteristics, and validation-versus-qualification distinctions.

References / further study

References below identify authorities named in the supplied blueprint. They do not represent external retrieval or a complete applicability assessment.

  1. United States. Code of Federal Regulations. Title 21, part 11, Electronic Records; Electronic Signatures. Regulatory authority identified in the supplied course blueprint.
  2. United States. Code of Federal Regulations. Title 21, part 211, especially sections 211.22 and 211.68. Regulatory authority identified in the supplied course blueprint.
  3. U.S. Food and Drug Administration. Part 11, Electronic Records; Electronic Signatures: Scope and Application. Sept. 2003. Guidance identified in the supplied course blueprint.
End of your free lesson

Keep going with the full Computer Software Assurance and Computerized System Validation Professional Certificate

You just studied the way members do, in the same lesson interface. Full access unlocks every lesson, the question bank and flashcards for a full year.

Up next with full access1.1.2 - Regulatory Hierarchy and Applicable Standards

One payment per program