Which frameworks actually shape your IT
For an India-based laboratory or CRO doing regulated pharmaceutical work, this is the set worth designing around. Applicability depends on your intended use and client base — this is a map, not a determination.

How to read this page
Each framework below shapes infrastructure in a different way, and most laboratories are touched by several at once. Nothing here is a determination that a framework applies to you — that depends on your intended use, your client base and your quality system, and it is a decision for your QA and regulatory advisers.
What this page does state honestly is where IT infrastructure contributes, and where it does not.
Frameworks and where they matter
| Framework | Where it matters | What infrastructure contributes |
|---|---|---|
| US FDA 21 CFR Part 11 | Electronic records and signatures used in FDA-regulated activities | Access controls, audit-trail configuration, record protection. Applicability and signature meaning stay with QA. |
| 21 CFR Part 58 | GLP and nonclinical laboratory studies, where applicable | Controlled systems, data retention and retrieval. |
| 21 CFR Parts 210 and 211 | GMP activities, QC laboratories and manufacturing-related testing | Segregated networks, controlled instrument systems, protected records. |
| FDA Data Integrity guidance | Electronic GxP records, audit trails, metadata and system controls | ALCOA+ translated into deletion controls, synchronised time and preserved source data. |
| ICH Q9 | Quality-risk management | Risk-based prioritisation of technical controls. The risk framework itself is yours. |
| ICH Q10 | Pharmaceutical quality systems | Systems that support, rather than obstruct, the quality system. |
| ICH E6 / GCP | Clinical trial and CRO work, where applicable | Access control, data protection and traceability. |
| OECD GLP | Nonclinical safety work, where applicable | Controlled, documented computerised systems. |
| EU GMP Annex 11 | A strong computerised-system benchmark, particularly where EU clients are expected | A useful design target even where it does not formally apply. |
| GAMP 5 | Risk-based computerised system validation methodology | The approach our validation documentation support follows. |
| ISO/IEC 17025 | Testing and calibration laboratories seeking accreditation | IT becomes part of the evidence supporting competent operation. |
| ISO 15189 | Medical and clinical laboratories, where applicable | Controlled systems and accessible records, including LIMS. |
| ISO 20387 | Biobanks | Controlled storage, environmental monitoring and records. |
| ISO 27001 | Information-security management | The security controls and documentation set we implement. |
| India Schedule M and applicable Drugs Rules | The Indian pharmaceutical GMP environment, where applicable | Infrastructure supporting documented, controlled operations. |
| India DPDP Act | Processing and protection of applicable personal data | Access control, encryption and retention configuration. |
| CERT-In requirements | Cybersecurity incident reporting and applicable IT-security obligations | Logging, monitoring and incident records. |
| NABL accreditation | Laboratories seeking applicable Indian accreditation | Documented infrastructure and retained evidence. |
Infrastructure worth having before accepting regulated client work
- A controlled IT and server room with access logging and environmental monitoring
- UPS and power protection sized to the actual load
- A managed firewall and a segmented network
- Enterprise Wi-Fi with corporate and guest separation
- Redundant internet where business impact justifies it
- Network monitoring and centralised time synchronisation
- Unique user IDs, MFA, role-based access and periodic access review
- Centrally managed, encrypted endpoints with EDR and controlled patching
- A system inventory with owners, GxP classification and validation status
- Backup with restore verification, and a documented DR plan
Common questions
Which of these applies to us?
We cannot tell you that, and you should be cautious of any supplier who answers it quickly. Applicability depends on intended use, your client base and your quality system. The usual first deliverable in a programme like this is a regulatory applicability matrix produced with your QA and regulatory advisers — before infrastructure is purchased.
Does ISO/IEC 17025 accreditation involve IT?
Increasingly, yes. Where a laboratory relies on computerised systems, accreditation assessment touches the reliability of electronic records and the control of the supporting infrastructure, alongside equipment, calibration records, facilities and management-system documentation.
Is accreditation a one-off exercise?
No. Document review, assessment, resolution of nonconformances, annual review or surveillance and reassessment are all part of maintaining it, which is why evidence has to be produced continuously rather than assembled before a visit.
Where our responsibility ends
This page is a reference, not a determination. The applicability of 21 CFR Part 11, GxP, ISO standards and other requirements depends on the intended use and regulatory context of each system. Pracoda provides technical infrastructure and documentation support; regulatory interpretation, GxP applicability decisions, validation approval, SOP approval, data review and final quality release remain with the client's authorized QA, system owner or qualified regulatory and validation specialists. Compliance support does not constitute regulatory certification, legal advice or a guarantee of audit outcome.
Work out which frameworks shape your build
Tell us who your clients are or will be, and what work you intend to take on. That usually determines the list faster than anything else.
- Reply within one working day
- Applicability stays your QA's decision