Table of contents
At a glance
What does ICH Q7 require of computerised systems used in API manufacturing?
ICH Q7 section 5.4 addresses computerised systems in API manufacturing. Section 5.40 calls for validation of GMP-relevant systems, with extent and depth based on diversity, complexity and criticality. Sections 5.41–5.47 cover qualification, protection from unauthorised changes, traceable data changes, additional accuracy checks on critical manual entries, investigation of relevant incidents and controlled changes. EU GMP Part II incorporates the ICH Q7 framework for active substances. Section 5.42 separately addresses qualified purchased software and adequately documented existing systems. Apply it to the actual API process.
- First determine the GMP-relevant active pharmaceutical ingredient process and its limitations.
- Critical manual entries require an appropriate additional accuracy check.
- Existing evidence can limit inspection effort but cannot create proof for missing data.
1. Determine how ICH Q7 and EU GMP Part II apply
Sources checked on 7 October 2026. ICH Q7 addresses good manufacturing practice for active pharmaceutical ingredients. For the EU scope discussed here we use the official August 2014 version of EU GMP Part II, which incorporates that basis and addresses computerised systems in section 5.4.
This contribution focuses on active substances for human medicinal products. Finished dosage forms, their QP certification, and the specific requirements for sterile or aseptic processing are not considered equivalent. Part II describes the application start based on the defined active substance starting material and the respective manufacturing process.
Therefore, determine which activity the application actually supports. A software system may provide data for a GMP-relevant manufacturing step without itself being part of the production control system. Its significance is derived from the information it provides and the potential for error propagation.
2. The rules from Section 5.4 apply to the application.
Section 5.40 links the validation scope to diversity, complexity, and criticality. This is not a blanket exemption for simpler applications. It forms the basis for clearly identifying relevant functions and appropriate validation evidence.
The following work matrix presents selected requirements in relation to practical inspection questions. It does not replace the complete process and documentation assessment as specified in Part II.
| Source | Main conclusion | Practical Evidence Question |
|---|---|---|
| 5.40–5.41 | Validation and appropriate installation and operational qualification | Does the hardware and software fulfill the assigned functions? |
| 5.43 | Control access, modifications, and omissions | Are relevant values, previous entry, operator, and timestamp traceable? |
| 5.45 | Verify critical manual entries additionally. | Which independent or system-level control detects a wrong value? |
| 5.46 | Document and investigate significant incidents | What impact does the error have on active ingredient quality or records? |
| 5.47–5.48 | Control changes and protect data | Are the verified state and required records retained? |
Sources: [1]
3. Do not secure critical entries with any confirmation
Section 5.45 specifies an additional verification of accuracy for critical manual entries. This can be performed by a second individual or by the system itself. A universal two-persons-check procedure for each input field cannot be derived therefrom.
The control must align with the potential error. A required field prevents empty values but does not prevent incorrect units. A sole plausibility limit may overlook a swapped batch number. A second person must know against which reliable source document the verification is being performed.
Therefore, describe the error sequence and the expected detection. If the application itself controls, the suitability of this control belongs to the proof. The mere name "automatic testing" does not say anything about which false entries are actually recorded.
4. Make a unit error deliberately detectable
In the following example, a scale of 0.250 kg is manually transferred to an application that requires its calculation value in grams. The specified target is: explicitly record the unit, convert the value correctly and do not meet unnoticed standard acceptance if the unit is missing. Expected are 250 g.
The case examines the input and conversion logic, not the suitability of an analytical method or the calibration of the balance. Evidence regarding these aspects addresses different questions. The software output may be mathematically correct and yet be based on a misassigned sample.
Therefore, in addition to the correct grammatical case, ensure the absence of a unit reference and incorrect identity. For documentation, it must remain clearly evident what was entered, accepted, and if applicable, corrected.
| Input or action | Specified expected result | Purpose of the test case |
|---|---|---|
| 0.250 kg for sample P01 | 250 g, assigned to P01 | Correct conversion: 0.250 × 1,000 |
| 250 g for sample P01 | 250 g, without additional multiplication | Avoid converting a value that already has the correct unit |
| 0.250 unitless | No undetected further processing; clarification required | Recognize missing context |
| Correct value for incorrect sample P02 | Detect assignment errors according to defined control | Accuracy alone is not sufficient |
| Correction of a carried-over value | Previous entry, person, and time point traceable | Changes must not obscure the original facts. |
5. Differentiate the treatment of commercial software and system validation records
Section 5.42 states that qualified commercial software does not require the same extent of testing. This assertion is subject to existing appropriate evidence. It does not mean that any purchased software, regardless of configuration or usage, is inherently sufficiently validated.
Assess whether the requirements actually covered by supplier documentation are adequately addressed. Additional formulas, interfaces, roles, or the specific operational environment may raise further questions. Evaluate the alignment instead of dismissing supplier documentation outright or accepting it without review.
For a legacy system not validated at installation, Section 5.42 permits a retrospective validation provided appropriate and available documentation is present. Retrospective protocols are not allowed. Describe the current status, using verifiable existing evidence, and clearly justify the relevant gaps.
6. Link data and changes to the active ingredient process
Section II, Paragraph 6.60 describes laboratory records including raw data, assignment to materials and batch, and calculations with units and conversion factors. A standalone stored end value cannot automatically meet these requirements.
Section 5.43 addresses records of data modifications including the previous entry, person, and timestamp. Section 5.47 requires a controlled, authorized, documented, and tested approach to system changes. The extent of testing required is derived from the specific change and its impact.
An error in a conversion may impact both future processing and previous affected results. Investigate the relationship and maintain existing records in a traceable manner. Simply correcting the program version alone does not address which prior decisions remain subject to evaluation.
Sources: [1]
7. Checklist for API System Validation
The checklist helps structure the evidence along the active ingredient process. It does not require a specific software model nor a general GAMP category for the entire application.
- Scope and GMP-relevant process step as defined in Part II.
- Described are the intended tasks, relevant data, and possible consequences of errors.
- Appropriate qualification and validation documentation assigned.
- Commercial supplier evidence on specific compatibility verified.
- Critical manual entries and corresponding additional controls defined.
- Units, identities, and required calculation bases verified.
- Access, data modifications, and potential omissions controlled.
- Incident investigation and impact assessment within operations are governed.
- Changes, data backup, and continued accessibility of records are considered.
8. What level of involvement is required from the active ingredient suppliers
The process owner and quality unit must be able to demonstrate which information is critical for the manufacture or evaluation of the active substance. The IT department and the supplier shall describe how this information is generated, processed, and protected.
For a SME, a clear data flow serves as a strong starting point: weighing, sample identification, calculation, result verification, and subsequent decision-making. This approach makes manual transitions and supplementary tables visible, which might otherwise be missing in a simple server list.
Limit effort based on feasible existing evidence. A simple tool may require special attention due to its critical calculations; a comprehensive application might include numerous functions irrelevant to the described GMP usage. This justified distinction is essential.
Project experience and collaboration
Determine the evidence required for the actual active substance process
With your active substance process owners and system owners, we start at a critical step such as manual data entry or a calculation reused downstream. What could happen if it fails, which control already operates and what evidence is missing? Suitable existing documents may need only targeted additions. Unclear configuration or changed use calls for broader testing. We map computerised system requirements to the specific API process and explain the scope needed.
Frequently asked questions about ICH Q7 and computerised systems
Does ICH Q7 apply to every computerized system of a pharmaceutical company?
Is EU-GMP Part II the same as a general guide for finished pharmaceutical products?
No. Part II covers active substances and has a separate scope of application. Separate or additional requirements apply to ready-made medicinal products and specific activities. The common use of an ERP system does not eliminate this professional distinction.
Sources: [1]
Does every manual entry require a second person?
Section 5.45 relates to critical manual data. An additional accuracy check may be performed by a second person or by the system itself. Verify which errors the selected control is actually required to detect and whether it is appropriate for that purpose.
Sources: [1]
Is a mandatory field enough to control sample weighing?
Must purchased off-the-shelf software be fully revalidated?
Not automatically. Section 5.42 takes into account qualified commercial software with reduced testing requirements. Assess the actual existing evidence and only supplement application-specific gaps. A purchase agreement alone does not constitute qualification evidence.
Sources: [1]
Can we assess a long-used system retrospectively?
Yes, appropriate existing documentation can support a retrospective validation. Describe the actual evidence and remaining gaps. Do not invent or retroactively date prior tests; current assessments must remain clearly identifiable as such.
Sources: [1]
Which changes must remain traceable?
Section 5.43 requires for data modifications the previous entry, the individual responsible, and the timestamp. System changes are controlled, authorized, documented, and tested in accordance with Section 5.47. The specific implementation must adequately cover the data and functions relevant to the GMP process.
Sources: [1]
Does a correct calculation already establish the suitability of the analytical method?
No. Software logic, device function, and analytical method address different questions. The example validation only demonstrates the specified behavior of input and conversion. Calibration and method suitability remain to be evaluated separately within their respective areas of application.
Sources: [1]
Must a deviation be investigated even in the absence of visible product defects?
Following 5.46, incidents that could potentially affect the quality of the active substance or the reliability of records and test results must be documented and investigated. The mere presence of a previously identified product defect is not the only prerequisite.
Sources: [1]
Which documentation should we gather first?
Sources and review date
Source: 7 October 2026. Production of active substance for medicinal products for human use in the described EU-GMP Part II Scope; no comparison with pre-filled medicinal product QP certification or aseptic processing. Tables and case studies are own work aids, no product tests carried out. Draft versions do not justify any additional requirements.
- EudraLex Part II: Active Substances as Starting MaterialsAugust 2014 version listed in EudraLex for active substances used in human medicinal products. The introduction and sections 1.1–1.2, 5.30–5.35, 5.40–5.49, 6.10–6.18 and 6.60–6.61 cover API scope, equipment, computerised systems and laboratory records.
- EMA: ICH Q7 – Good manufacturing practice for active pharmaceutical ingredientsCurrent effective version: ICH Q7 Step 5, CPMP/ICH/4106/00; Status date as of 7 October 2026; Page content and Current effective version: Active ingredient – Scope and ICH-Q7 Edition
- PIC/S: PI 041-1, Data Management and IntegrityPIC/S PI 041-1, 1 July 2021. Sections 9.1.1–9.1.6 and 9.2–9.3 address GMP and GDP data processes, critical transitions and controls over existing records.
- EMA/ICH: Q7 – Good Manufacturing Practice for Active Pharmaceutical Ingredients, Step 5CPMP/ICH/4106/00, November 2000; Section 5.4 with subsections 5.40–5.49. Reviewed directly on 18 October 2026 and cross-referenced against the currently valid EMA version.
Sources checked: .
Determine the evidence from your API manufacturing process
We support you in defining GMP-relevant functions, assessing critical data transfers, and evaluating existing system documentation. The scope is the specific task within your active ingredient manufacturing process.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

