Scalable Consent Management
1.0.0-preview - STU 1 PReview United States of America flag

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

Requirements: Structure Definitions Consent Server

Official URL: http://hl7.org/fhir/us/consent-management/Requirements/structure-definitions-consent-server Version: 1.0.0-preview
Standards status: Trial-use Maturity Level: 1 Computable Name: StructureDefinitionsConsentServer

Structure Definitions Requirements for Consent Server

Requirements Actor(s)

These requirements apply to the following actors:

  • Consent Server An application or product that implements the Consent Server.

Requirements Statement List

Specification: Subscriptions R5 Backport

Link to Text: https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-definitions.html

Conformance: SHALL

Parent: Requirements-subscription-topics-client-consent-server.html#requirement-596

Notes: Not sure if there is a more direct requirement somewhere that says this.


Language: en

These requirements apply to the actor Consent Server

requirement-1030SHALL

Consent Administration Service SHALL support Consent read

Links:

requirement-1024SHALL

Consent Administration Service SHALL support FASTConsent search by _id

Links:

requirement-1026SHALL

Consent Administration Service SHALL support Consent search by identifier

Links:

requirement-1028SHALL

Consent Administration Service SHALL support FASTConsent search by patient

Links:

requirement-1032SHALL

Consent Administration Service SHALL support Consent search by the combination of the patient and status search parameters

Links:

requirement-1034SHOULD

Consent Administration Service SHOULD support Consent search by the combination of the patient and date search parameters

Links:

requirement-632SHALL

Consent Administration Service SHALL support Consent notification filter combinations, and they combine as AND<br/><br/>Not sure if there is a more direct requirement somewhere that says this.

Links: