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: Conformance Expectations Consent Server

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

Conformance Expectations 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: HL7 FAST Consent IG

Link to Text: https://build.fhir.org/ig/HL7/fhir-consent-management/en/conformance.html

Conformance: SHALL

Specification: HL7 FAST Consent IG

Link to Text: https://build.fhir.org/ig/HL7/fhir-consent-management/en/conformance.html

Conformance: SHALL

Specification: HL7 FAST Consent IG

Link to Text: https://build.fhir.org/ig/HL7/fhir-consent-management/en/conformance.html

Conformance: SHALL


Language: en

These requirements apply to the actor Consent Server

requirement-1157SHALL

Consent Server systems SHALL be capable of processing resource instances containing data elements without generating an error or causing the application to fail.

Links:

requirement-1159SHALL

Consent Server systems SHALL interpret missing data elements within resource instances as data not being present in the sending system or not being shareable for privacy or other business reasons.

Links:

requirement-1160SHALL

Consent Server systems SHALL be able to process resource instances containing data elements that have extensions in place of a value where such extensions are declared as part of the profile.

Links: