Cross-Framework Mapping

API 1164vsICH E6(R3) - Good Clinical Practice

See exactly how API 1164 controls map to ICH E6(R3) - Good Clinical Practice. Pre-computed mappings, identified gaps, and coverage analysis.

4
Controls Mapped
20
Gaps Found
8%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

API 1164 maps to ICH E6(R3) - Good Clinical Practice with 8% coverage across 4 directly mapped controls. Analysis of 24 API 1164 controls identifies 41 compliance gaps — primarily concentrated in API 1164: Access Management.

Source: TheArtOfService Knowledge Graph | 24 controls analysed | 718 frameworks | 332K+ cross-framework mappings

Control Mappings

Showing 4 of 4 mapped controls across 4 domains. Sign up to explore all 332K+ mappings across 718 frameworks.

Endpoint(1 mappings)

API1164-18Field Device Security
ICH-E6-Annex1-ElectronicSystems-CSV-eSig-Audit-ALCOA-DataIntegrityICH E6(R3) Annex 1 - Computer Systems + Computer System Validation (CSV) + Electronic Signature + Audit Trail + ALCOA+ Data Integrity

API 1164: Incident Response & Recovery(1 mappings)

API1164-18Field Device Security
ICH-E6-Annex1-ElectronicSystems-CSV-eSig-Audit-ALCOA-DataIntegrityICH E6(R3) Annex 1 - Computer Systems + Computer System Validation (CSV) + Electronic Signature + Audit Trail + ALCOA+ Data Integrity

Regulatory(1 mappings)

API1164-21TSA Pipeline Security Directive Alignment
ICH-E6-Scope-Principles-R3-2025-Risk-Based-DecentralisedClinicalICH E6 Good Clinical Practice - Scope + 13 Principles + R3 January 2025 + Risk-Based + Decentralised + Modernisation

API 1164: Supply Chain & Configuration(1 mappings)

API1164-21TSA Pipeline Security Directive Alignment
ICH-E6-Scope-Principles-R3-2025-Risk-Based-DecentralisedClinicalICH E6 Good Clinical Practice - Scope + 13 Principles + R3 January 2025 + Risk-Based + Decentralised + Modernisation

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 718 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 718 framework browser
  • Cross-framework mappings (332K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between API 1164 and ICH E6(R3) - Good Clinical Practice?

API 1164 has 24 controls across its framework, while ICH E6(R3) - Good Clinical Practice covers 9 controls. Direct mapping analysis identifies 4 overlapping controls (8% coverage). The frameworks diverge most significantly in API 1164: Access Management, where 5 API 1164 controls have no direct ICH E6(R3) - Good Clinical Practice equivalent.

How many controls map between API 1164 and ICH E6(R3) - Good Clinical Practice?

Of 24 total API 1164 controls, 4 map directly to ICH E6(R3) - Good Clinical Practice controls — representing 8% coverage. The remaining 41 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping API 1164 to ICH E6(R3) - Good Clinical Practice?

41 API 1164 controls have no direct equivalent in ICH E6(R3) - Good Clinical Practice. The highest concentration of gaps is in API 1164: Access Management with 5 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between API 1164 and ICH E6(R3) - Good Clinical Practice?

The domain with the highest gap count is API 1164: Access Management (5 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.