IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board SystemsvsHL7 FHIR Security Framework
See exactly how IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls map to HL7 FHIR Security Framework. Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems maps to HL7 FHIR Security Framework with 16% coverage across 3 directly mapped controls. Analysis of 19 IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls identifies 16 compliance gaps — primarily concentrated in IACS UR E26 Survey + Approval.
Source: TheArtOfService Knowledge Graph | 19 controls analysed | 723 frameworks | 332K+ cross-framework mappings
Control Mappings
Showing 5 of 5 mapped controls across 3 domains. Sign up to explore all 332K+ mappings across 723 frameworks.
IACS UR E26 Detect(2 mappings)
IACS UR E27 User Auth(1 mappings)
IACS UR E27 Logging + Forensics(2 mappings)
Related Comparisons
Other IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems comparisons
Other HL7 FHIR Security Framework comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 723 frameworks — at a fraction of consulting costs.
Free
- ✓ 723 framework browser
- ✓ Cross-framework mappings (332K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems and HL7 FHIR Security Framework?
IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems has 19 controls across its framework, while HL7 FHIR Security Framework covers 7 controls. Direct mapping analysis identifies 3 overlapping controls (16% coverage). The frameworks diverge most significantly in IACS UR E26 Survey + Approval, where 1 IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls have no direct HL7 FHIR Security Framework equivalent.
How many controls map between IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems and HL7 FHIR Security Framework?
Of 19 total IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls, 3 map directly to HL7 FHIR Security Framework controls — representing 16% coverage. The remaining 16 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems to HL7 FHIR Security Framework?
16 IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls have no direct equivalent in HL7 FHIR Security Framework. The highest concentration of gaps is in IACS UR E26 Survey + Approval with 1 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 IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems and HL7 FHIR Security Framework?
The domain with the highest gap count is IACS UR E26 Survey + Approval (1 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
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.