HL7 FHIR Security Framework
The HL7 FHIR (Fast Healthcare Interoperability Resources) Security Framework provides security and privacy specifications for FHIR-based health data exchange. It defines authentication, authorization, audit logging, and consent management patterns for FHIR APIs. Includes SMART on FHIR (Substitutable Medical Applications and Reusable Technologies) for OAuth 2.0-based authorization. Central to US ONC interoperability rules and international health data exchange.
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (23)
Abuse
| Code | Title |
|---|---|
| FHIR-SEC-14 | Rate Limiting and Anti Abuse |
Access
| Code | Title |
|---|---|
| FHIR-SEC-13 | Patient Compartment Enforcement |
App Launch
| Code | Title |
|---|---|
| FHIR-SEC-03 | SMART on FHIR App Launch |
Audit
| Code | Title |
|---|---|
| FHIR-SEC-07 | AuditEvent Logging |
| FHIR-SEC-08 | Audit Log Integrity and Retention |
Audit and Provenance
| Code | Title |
|---|---|
| FHIR-SEC-4.1 | AuditEvent Logging |
| FHIR-SEC-4.2 | Provenance Tracking |
| FHIR-SEC-4.3 | Audit Log Review |
Authentication
| Code | Title |
|---|---|
| FHIR-SEC-2.1 | User Authentication |
| FHIR-SEC-2.2 | SMART App Launch |
| FHIR-SEC-2.3 | System-to-System Authentication |
Authorization
| Code | Title |
|---|---|
| FHIR-SEC-02 | OAuth 2.0 Authorization |
| FHIR-SEC-06 | Scope Granularity |
Authorization and Access Control
Risks related to broken access control and security misconfiguration
| Code | Title |
|---|---|
| A01:2025 | Broken Access Control |
| A02:2025 | Cryptographic Failures |
| FHIR-SEC-3.1 | Security Labels |
| FHIR-SEC-3.2 | Consent-Based Access Control |
| FHIR-SEC-3.3 | Scope-Based Authorization |
Bulk
| Code | Title |
|---|---|
| FHIR-SEC-15 | Bulk Data Export Authorization |
CORS
| Code | Title |
|---|---|
| FHIR-SEC-20 | Cross Origin Resource Sharing |
Capability
| Code | Title |
|---|---|
| FHIR-SEC-19 | Server CapabilityStatement Security |
Communications Security
| Code | Title |
|---|---|
| FHIR-SEC-1.1 | Transport Layer Security |
| FHIR-SEC-1.2 | Time Keeping |
Consent
| Code | Title |
|---|---|
| FHIR-SEC-09 | Consent Resource Enforcement |
Data Protection
Personal data protection provisions
Emergency Access
| Code | Title |
|---|---|
| FHIR-SEC-17 | Break the Glass |
Identity
| Code | Title |
|---|---|
| FHIR-SEC-04 | OpenID Connect Identity |
Privacy
| Code | Title |
|---|---|
| FHIR-SEC-12 | De-identification for Research |
Provenance
| Code | Title |
|---|---|
| FHIR-SEC-11 | Provenance Tracking |
Server to Server
| Code | Title |
|---|---|
| FHIR-SEC-05 | Backend Services Authentication |
Signature
| Code | Title |
|---|---|
| FHIR-SEC-10 | Digital Signatures on Resources |
Token
| Code | Title |
|---|---|
| FHIR-SEC-18 | Token Lifetime and Refresh |
Transport
| Code | Title |
|---|---|
| FHIR-SEC-01 | Communication Security TLS |
Verifiable
| Code | Title |
|---|---|
| FHIR-SEC-16 | SMART Health Cards Verification |
Your Compliance Coverage
If you comply with HL7 FHIR Security Framework, you already cover:
Proposal for a Regulation on Cyber Resilience Act (CRA)
33%
11 controls mapped
Compare →NIST SP 800-171A Rev 3 — Assessing CUI Security Requirements
33%
11 controls mapped
Compare →NIST SP 800-171
33%
11 controls mapped
Compare →+ 574 more: ETSI EN 303 645 (33%), CSA CCM v4 (33%)
See all 577 mapped frameworks ↓Maps to 577 other frameworks
Frequently Asked Questions
What is HL7 FHIR Security Framework?
HL7 FHIR Security Framework is a compliance framework from International (Healthcare) with 23 domains and 33 controls. The HL7 FHIR (Fast Healthcare Interoperability Resources) Security Framework provides security and privacy specifications for FHIR-based health data exchange. It defines authentication, authorization, audit logging, and consent management patterns for FHIR APIs. Includes SMART on FHIR (Substitutable Medical Applications and Reusable Technologies) for OAuth 2.0-based authorization. Central to US ONC interoperability rules and international health data exchange. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does HL7 FHIR Security Framework have?
HL7 FHIR Security Framework has 33 controls organised across 23 domains. The largest domains are Authorization and Access Control (5 controls), Audit and Provenance (3 controls), Authentication (3 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
What frameworks does HL7 FHIR Security Framework map to?
HL7 FHIR Security Framework maps to 577 other compliance frameworks. The top mapping partners are Proposal for a Regulation on Cyber Resilience Act (CRA) (33% coverage), NIST SP 800-171A Rev 3 — Assessing CUI Security Requirements (33% coverage), NIST SP 800-171 (33% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with HL7 FHIR Security Framework compliance?
Start your HL7 FHIR Security Framework compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about HL7 FHIR Security Framework requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 33 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 718 frameworks.
Get Started Free →Free forever — no credit card required