Table of contents
At a glance
What are Part 11 device checks, and which input sources should they cover?
Section 11.10(h) requires appropriate checks of devices, such as terminals, to establish whether the source of data input or an operational instruction is valid. Determine the check from the actual data path. Device identity, user authority and calibration answer different questions. Where they can affect use of a regulated record, test mix-ups, new connections and changed assignments.
- A valid registration does not prove the correct origin of a measurement value.
- Verify continuous device assignment rather than relying on only a displayed device name.
- Calibration and source verification each require appropriate supporting evidence.
What actually does §11.10(h) verify?
The starting point is an electronic record within the scope of Part 11. Section (h) addresses equipment validation, including terminals, where applicable. This applies to both data entry and operational instructions. Therefore, equipment validation is not limited to laboratory instruments connected to the system. An operational instruction originating from a defined source may also be affected.
The review addresses: Does this input originate from a source valid for the intended process? The regulatory text provides neither a specific device type nor a universal technical procedure. The following work aids refer to an assumed drug CGMP data pathway. They do not constitute claims regarding the functions of a specific product.
Separate source, authorization, and measurement capability
User authentication as specified in §11.10(g) and device validation as specified in paragraph (h) are complementary. An authorized personnel member may inadvertently select the incorrect device. Conversely, the correct device may provide data while the triggering user lacks the required authorization. A positive result from one validation does not substitute for the other.
A calibration addresses a different question: it relates to the measurement suitability within the defined scope. A current calibration label does not prevent incorrect channel assignment in the target system. §211.68, in the relevant Drug-CGMP context, covers among other things calibration, inspection, or testing according to a written procedure, as well as the verification of input and output data, with the scope and frequency of such activities being determined by the system's complexity and reliability (§ 211.68(b)). The specific implementation must be determined by the system in use.
Make the relevant data pathway visible
Capture for each critical input the professional identity of the source, its technical representation, and its application within the target process. A mere display name is insufficient if it can be altered independently of the actual connection. What is critical is identifying where a misassignment is detected and ensuring that validation evidence remains available.
The following completed matrix serves as an internal reference tool. A technical lock herein refers to a specifically defined required function of the example, not a universally derived product function inferred from Part 11.
| Source / Transfer | Expected outcome for the process | To be investigated error | Expected evidence |
|---|---|---|---|
| Waage W-01 → Gateway G-01 | Net weight for order A-17 | W-02 is operated at the existing connection point. | False source assignment is detected; affected value is not used unchecked. |
| Gateway G-01 → Import channel K-01 | Device identity and unit remain assigned | Gateway still provides the old alias | Assignment is verified against the approved configuration. |
| Bedienterminal T-01 → Order A-17 | Instruction applies to the selected order | Instruction received for order A-18 | Order basis is verified; unexpected execution is treated as a deviation. |
| Manual fallback entry | Designated Exemption Route | Handwert appears as an automated measurement | Data capture method, source, and required verification remain identifiable. |
A device change with plausible values
Example: For order A-17, a quantity of 8.0 kg from W-01 is planned. W-02 also supplies 8.0 kg, but is not assigned to this data path. The value alone does not distinguish the sources. Additionally, a test value of 8,000 g is transmitted. Computationally, this equates to 8.0 kg; a source with incorrect unit assignment must not be interpreted as supplying 8,000 kg.
Conduct these cases in an appropriate test environment with documented baseline configuration. Capture inputs, device identifiers, transmission pathways, and actually generated records. The expected matrix describes anticipated behavior. This does not serve as evidence that a product possesses these controls, nor that the tests have been performed.
| Case | Entry / Exit Condition | Expected decision | Rationale |
|---|---|---|---|
| -reference | W-01; A-17; 8.0 kg; approved assignment | Assign 8.0 kg to the correct order. | Source, unit, and intended use correspond to specification. |
| Equal value, external source | W-02; A-17; 8.0 kg | Do not accept as a valid W-01 value. | Numerical plausibility does not replace source verification. |
| Other unit | W-01; A-17; 8,000 g | If the defined conversion applies, store 8.0 kg. | 8,000 ÷ 1,000 = 8; the conversion rule and unit must be consistent. |
| Wrong order | W-01; A-18; 8.0 kg instead of A-17 | Detect a reference to the wrong order | The correct source alone does not prove correct use. |
| Alternate inclusion | W-01 not accessible; hand weight 8.0 kg | Use the defined exemption pathway | Manual entry must not falsely imply an automated origin. |
Gateways and interfaces alter the testing boundary
Between device and application, multiple systems may perform identity translations or intermediate data storage. Define which identity is used at each transition point. Specifically assess reused interfaces, modified mapping tables, and replacement devices. Verification at the entrance to the first application does not automatically extend to all subsequent steps.
In the case of delayed transmission, it must be clarified whether a currently altered assignment is retrospectively applied to older data. This is a specific test question related to the data pathway, not a prescribed architectural requirement. For required metadata, their contribution to understanding and reconstructing the record is significant. Not every technical network protocol becomes subject to retention obligations as a result.
Edit operational changes and findings
Device replacements, new drivers, renamed interfaces, and altered interfaces can affect an originally correct mapping. Associate the change with the affected data pathways and existing validation evidence. The required retests are determined by the impact; a full system test after every name change does not follow.
If a incorrect source is identified, determine the affected time period and the records used. Assess whether a decision had already been based on these data. Correctly document the correction and obtain the required original information. A misattribution alone does not imply intentional misconduct or a specific product outcome.
Release checklist for the data pathway
Use this internal checklist for joint preparation by process owners, IT, and the relevant quality unit. Assign open items to a responsible party and a justified usage decision. This list does not replace system-specific requirements or risk assessment.
- The relevant record and its applicability are specified.
- Device identity, technical connectivity, and intended use are assigned.
- User permissions and device origin are considered separately.
- Unit identifiers, mapping of codes, and alternate pathways are described.
- Identical plausible values from invalid sources are considered in the testing design.
- Changes and handling of affected inventory data are governed.
- The required evidence can be attributed to the verified configuration status.
Focus effort on the actual transfer points
For a small team, a manageable source matrix is often the most practical starting point. Technical expertise in data usage and knowledge of transmission protocols are required. Manufacturer documentation can demonstrate existing validation mechanisms; however, their coverage must align with the installed configuration and the organization's specific data flow.
Effort arises primarily due to numerous transitions, changing equipment, undocumented alias names, and unclear exception pathways. Start with inputs whose misclassification could alter a significant decision. This does not automatically reduce the review burden, but it clearly identifies areas where additional evidence is required and where existing documentation is sufficiently specific.
Project experience and collaboration
Trace the input device through to the record that uses its data
With the laboratory or Production and IT, we trace a controlled value from its device to the record used. In a suitable test environment, we also change a connection or deliberately assign the wrong source. A focused test may suffice where provenance is unambiguous and effectively protected. Ambiguous identifiers call for better mapping or further controls. We assess calibration and user authorisation separately.
Frequently asked questions about Input sources and devices
Is a calibration intended by equipment validation under Part 11?
No. § 11.10(h) addresses the validity of the source of a data entry or operating instruction. The metrological calibration is a separate issue, for example under § 211.68(a) in the Drug-CGMP context. In a measurement data pathway, both controls may be necessary. A calibration certificate, for example, does not confirm correct channel or order assignment within the target system.
Must every connected device be technically authenticated?
The regulatory text requires appropriate device testing but does not specify a universal authentication technique. Identify potential false sources that could arise in the actual workflow and determine which controls prevent or reliably detect their improper use. A random device inventory lacking reference to relevant records constitutes an insufficient test protocol.
Sources: [1]
Is a unique IP address sufficient as evidence?
Not automatically. It is essential whether the address in the actual system provides a reliable assignment to the intended source. A technical identifier may be part of the control. However, you must consider its management, potential changes, and its relationship to the intended use; Part 11 does not specify a universally sufficient type of address for this purpose.
Sources: [1]
Why is operator login alone insufficient?
The registration pertains initially to the individual and their authorizations. The logged-in operator may still receive data from the wrong device or select the incorrect interface. Sections 11.10(g) and (h) address distinct control questions. Evaluate both in context, without equating them.
Sources: [1]
What should be assessed when identical measurement values are obtained from two devices?
In the event of a discrepancy, deliberately use the same plausible value from a correct and incorrect source. This test will demonstrate whether the source of the data is actually verified or merely the numerical range is checked. Define the expected behavior in advance and document the resulting record, including the required source attribution.
Are units included in medical device testing?
The unit can be critical for understanding input and ensuring the accuracy of its processing. It does not replace device identity but must align with the data pathway. A correct source with incorrect unit interpretation will still generate inappropriate results. Therefore, source validation and processing control should be evaluated together.
Must a replacement device be fully revalidated?
Such a general rule does not follow from §11.10(h). Assess which identity, interface, measurement function, and processing activities have changed. The required validation evidence for the intended use shall be generated accordingly. Existing evidence is only applicable to the extent that it actually covers the modified configuration.
Sources: [1]
Are manual substitute values fundamentally prohibited?
No, the mentioned section does not universally prohibit any manual data entry. However, the alternative pathway must be appropriate and traceable for the specific process. Origin, method of entry, authorisation, and required checks must not be obscured. A manual entry should not create the impression of an automated measurement transfer.
Must all network protocols be permanently archived?
No. Determine which information pertaining to a regulated record is required for understanding and reconstruction. The FDA outlines the importance of associated metadata, but this does not establish a universal, perpetual retention requirement for all technical logs. Applicable recordkeeping obligations and deadlines remain decisive.
Does the FDA Guidance from 2003 include the withdrawal of device inspections?
The Guidance identifies specific areas of operational retention, such as validation and certain audit trail requirements. It explicitly states the continued application of other controls, including equipment inspections as specified in §11.10(h). The Guidance does not supersede the regulatory text and remains no general waiver of data integrity controls.
Sources and review date
Source date: 7 October 2026. eCFR notice period until 5 October 2026; separate consideration of binding regulatory text and non-binding FDA Guidance. Examples and tables are internal work aids and do not represent completed product testing.
- 21 CFR Part 11 – Electronic Records; Electronic SignatureseCFR display until 05.10.2026; §§11.1–11.300.
- 21 CFR §211.1 – ScopeeCFR notice until 05.10.2026; Scope: Drug-CGMP.
- 21 CFR §211.68 – Automatic, mechanical, and electronic equipmenteCFR notice until 05.10.2026; paragraphs (a)–(c).
- FDA: Data Integrity and Compliance With Drug CGMP – Questions and AnswersFDA Data Integrity Q&A, December 2018: Question 1(b) regarding required metadata context. Source and device validations and calibration are distinguished based on the separately referenced CFR sections.
- FDA: Part 11 – Scope and ApplicationFinal guidance. The PDF is dated August 2003 and the status page September 2003. See sections I and III.A–C.
Sources checked: .
Jointly develop the specific evidence process
We support you in identifying relevant input sources, assessing risks of confusion, and establishing appropriate evidence for your actual system configuration.
- 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.

