HL7 FHIR Security FrameworkvsICAO Annex 17 — Aviation Security (AVSEC)
See exactly how HL7 FHIR Security Framework controls map to ICAO Annex 17 — Aviation Security (AVSEC). Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
HL7 FHIR Security Framework maps to ICAO Annex 17 — Aviation Security (AVSEC) with 31% coverage across 4 directly mapped controls. Analysis of 13 HL7 FHIR Security Framework controls identifies 9 compliance gaps — primarily concentrated in Audit and Provenance.
Source: TheArtOfService Knowledge Graph | 13 controls analysed | 693 frameworks | 819K+ cross-framework mappings
Control Mappings
Showing 8 of 8 mapped controls across 2 domains. Sign up to explore all 819K+ mappings across 693 frameworks.
Authorization and Access Control(7 mappings)
Authentication(1 mappings)
Related Comparisons
Other HL7 FHIR Security Framework comparisons
Other ICAO Annex 17 — Aviation Security (AVSEC) comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.
Free
- ✓ 693 framework browser
- ✓ Cross-framework mappings (819K+)
- ✓ 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 HL7 FHIR Security Framework and ICAO Annex 17 — Aviation Security (AVSEC)?
HL7 FHIR Security Framework has 13 controls across its framework, while ICAO Annex 17 — Aviation Security (AVSEC) covers 23 controls. Direct mapping analysis identifies 4 overlapping controls (31% coverage). The frameworks diverge most significantly in Audit and Provenance, where 3 HL7 FHIR Security Framework controls have no direct ICAO Annex 17 — Aviation Security (AVSEC) equivalent.
How many controls map between HL7 FHIR Security Framework and ICAO Annex 17 — Aviation Security (AVSEC)?
Of 13 total HL7 FHIR Security Framework controls, 4 map directly to ICAO Annex 17 — Aviation Security (AVSEC) controls — representing 31% coverage. The remaining 9 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping HL7 FHIR Security Framework to ICAO Annex 17 — Aviation Security (AVSEC)?
9 HL7 FHIR Security Framework controls have no direct equivalent in ICAO Annex 17 — Aviation Security (AVSEC). The highest concentration of gaps is in Audit and Provenance with 3 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 HL7 FHIR Security Framework and ICAO Annex 17 — Aviation Security (AVSEC)?
The domain with the highest gap count is Audit and Provenance (3 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.