Scalable Consent Management
1.0.0-preview - STU 1 PReview
US
Scalable Consent Management
1.0.0-preview - STU 1 PReview
US
Scalable Consent Management, published by HL7 International / Community Based Collaborative Care. This guide is not an authorized publication; it is the continuous build for version 1.0.0-preview built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-consent-management/ and changes regularly. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
There are no Global profiles defined
The following artifacts define the types of individuals and/or systems that will interact as part of the use cases covered by this implementation guide.
| Consent Client System |
A system responsible for gathering patient consent decisions and filing them with a consent administration service. Typically implemented as an EHR system, patient portal, or similar application. Corresponds to the IHE-PCF Consent Recorder actor. |
| Consent Server System |
A consent server system is responsible for storing consent records and servicing requests for consent data. Implements the File Consent and Revoke Consent operations, supports consent search and subscriptions, and maintains audit events for consent access decisions. Corresponds to the IHE-PCF Consent Registry actor. |
The following artifacts describe the specific requirements to be met by systems compliant with the implementation guide.
| CapStmt Admin Service |
CapStmt Requirements for Admin Service |
| CapStmt Client |
CapStmt Requirements for Client |
| Components Admin Service |
Components Requirements for Admin Service |
| Components Client |
Components Requirements for Client |
| Conformance Admin Service |
Conformance Requirements for Admin Service |
| Conformance Client |
Conformance Requirements for Client |
| Conformance Client Admin Service |
Conformance Requirements for Client Admin Service |
| Extended Operations Client Admin Service |
Extended Operations Requirements for Client Admin Service |
| Narrative Conformance Statements |
Conformance statements found throughout the narrative of the IG consolidated into this computable resource for traceability purposes |
| Search Parameters Client Admin Service |
Search Parameters Requirements for Client Admin Service |
| Structure Definitions Client Admin Service |
Structure Definitions Requirements for Client Admin Service |
| SubscriptionTopic FASTConsentSubscriptionTopic Admin Service |
SubscriptionTopic FASTConsentSubscriptionTopic Requirements for Admin Service |
| SubscriptionTopic FASTConsentSubscriptionTopic Client |
SubscriptionTopic FASTConsentSubscriptionTopic Requirements for Client |
| SubscriptionTopic FASTConsentSubscriptionTopic Client Admin Service |
SubscriptionTopic FASTConsentSubscriptionTopic Requirements for Client Admin Service |
| Technical Specification Admin Service |
Technical Specification Requirements for Admin Service |
| Technical Specification Client |
Technical Specification Requirements for Client |
| Workflow Client Admin Service |
Workflow Requirements for Client Admin Service |
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
| Consent Client Capabilities |
Capabilities required for a Consent Client system filing and reviewing consents. |
| Consent Server Capabilities |
Capabilities required for a Consent Server system (consent administration service) receiving and managing consents. |
These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide.
| File a Consent |
This operation is used to file a consent with a consent administration service. The parameters are the Consent resource along with accompanying documentation in the form of a DocumentReference (for PDF or other forms) or QuestionnaireResponse. |
| Revoke a Consent |
This operation is used to revoke a consent with a consent administration service. The parameters are a reference to the Consent resource along with accompanying documentation in the form of a DocumentReference (for PDF or other forms) or QuestionnaireResponse. |
These define the properties by which a RESTful server can be searched. They can also be used for sorting and including related resources.
| fast-consent-controller |
The Consent controller reference which is defined by the Consent extension controller. |
| fast-consent-manager |
The Consent manager reference which is defined by the Consent extension manager. |
These define the types of information that can be subscribed to on systems conforming to this this implementation guide.
| FAST Consent Subscription Topic |
This is the subscription topic used for ensuring Consent records are updated amongst a set of Consent Registries. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| FASTConsent |
This profile captures the details of a Patient's Consent. |
| FASTConsentAuditEvent |
Disclosures are recorded as FHIR AuditEvent instances. These AuditEvents reflect the Consent instance that was consulted and whether the decision to disclose data was made or not. |
| FASTDocumentReference |
This profile records non-structured documentation that records a patient's consent. |
| FASTSubscription |
A profile for FAST subscriptions. |
| File Consent Operation Parameters |
A profile that indicates the parameters for the File Consent operation. |
| Revoke Consent Operation Parameters |
A profile that indicates the parameters for the Revoke Consent operation. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| FASTReference |
A profile on the Reference datatype that requires the identifier and exposes a set of additional identifiers in an extension. |
These define sets of codes used by systems conforming to this implementation guide.
| FAST Consent Statuses |
The two codes that are applicable to FAST Consent instances. 'active' for active Consents, and 'inactive' for revoked Consents. |
| LOINC Consent Document Types |
These codes are used to convey the type of consent document being referenced. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| ConsentAuditEventExample |
An example of a Consent Audit Event |
| ConsentExample |
An example of a consent. |
| DocumentReferenceExample |
An example of a consent document. |
| FASTOrganizationSubscriptionExample |
An example of a FAST Subscription for a specific organization (controller). |
| FASTPatientSubscriptionExample |
An example of a FAST Subscription for a specific patient. |
| FASTSubscriptionNotification |
An example of a FAST Subscription Notification |
| FASTSubscriptionNotificationParameters |
An example of the parameters going back for a FAST subscription notification |
| FileConsentDocRefExample |
An example of a $fileConsent Parameters resource with an optional DocumentReference. |
| FileConsentQuestionnaireExample |
An example of a $fileConsent Parameters resource with an optional QuestionnaireResponse. |
| QuestionnaireResponseExample |
An example of a consent questionnaire response. |
| RevokeConsentExample |
An example of a $revokeConsent Parameters resource. |
IG © 2024+ HL7 International / Community Based Collaborative Care.
Package hl7.fhir.us.consent-management#1.0.0-preview based on FHIR 4.0.1.
Generated
2026-05-21
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change