HL7 FHIR Implementation Guide: Data Access Policies
1.0.0-current - ci-build
HL7 FHIR Implementation Guide: Data Access Policies
1.0.0-current - ci-build
HL7 FHIR Implementation Guide: Data Access Policies, published by HL7 International / Security. This guide is not an authorized publication; it is the continuous build for version 1.0.0-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/data-access-policies/ and changes regularly. See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/dap/ImplementationGuide/hl7.fhir.uv.dap | Version: 1.0.0-current | |||
| IG Standards status: Informative | Maturity Level: 0 | Computable Name: DataAccessPolicies | ||
This is the Security WG, FHIR data-access-policy sandbox Implementation Guide.
This documentation and set of artifacts are still undergoing development. This content is only for informative purposes.
The top menu allows quick navigation to the different sections, and a Table of Contents is provided with the entire content of this Implementation Guide. (Be aware that some pages have multiple tabs).
This IG purpose is to include use-case analysis to enable the FHIR Permission resource to mature. These use-cases will confirm where the Permission resource is properly constructed, where updates are needed, and where core extensions and vocabulary are needed.
The use-cases and analysis are found on these pages:
Permission is a portion of an Access Control environment. It is provided in FHIR form to enable Access Control rules to more naturally utilize the FHIR model.
While this implementation guide and the underlying FHIR are licensed as public domain, this guide includes examples making use of terminologies such as LOINC, SNOMED CT and others which have more restrictive licensing requirements. Implementers should make themselves familiar with licensing and any other constraints of terminologies, questionnaires, and other components used as part of their implementation process. In some cases, licensing requirements may limit the systems that data captured using certain questionnaires may be shared with.
| IG | Package | FHIR | Comment |
|---|---|---|---|
  HL7 FHIR Implementation Guide: Data Access Policies | hl7.fhir.uv.dap#1.0.0-current | R5 | |
 HL7 Terminology (THO) | hl7.terminology.r5#6.0.2 | R5 | Automatically added as a dependency - all IGs depend on HL7 Terminology |
| FHIR Extensions Pack | hl7.fhir.uv.extensions.r5#5.1.0 | R5 | Automatically added as a dependency - all IGs depend on the HL7 Extension Pack |
 FHIR Data Segmentation for Privacy | hl7.fhir.uv.security-label-ds4p#1.0.0 | R4 | |
 HL7 Terminology (THO) | hl7.terminology#5.1.0 | R4 |
Package hl7.fhir.uv.extensions.r5#5.1.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Apr 27, 2024 18:39+1000+10:00) |
Package hl7.fhir.uv.security-label-ds4p#1.0.0 FHIR data segmentation for privacy security label implementation guide (built Mon, Apr 17, 2023 18:47+0000+00:00) |
There are no Global profiles defined
This publication includes IP covered under the following statements.
The specification herewith documented is a demo working specification, and may not be used for any implementation purposes. This draft is provided without warranty of completeness or consistency, and the official publication supersedes this draft. No liability can be inferred from the use or misuse of this specification, or its consequences.
You can also download:
The source code for this Implementation Guide can be found on IHE HL7 data-access-policies Github Repo.
IG © 2023+ HL7 International / Security. Package hl7.fhir.uv.dap#1.0.0-current based on FHIR 5.0.0. Generated 2024-08-21
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change