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: Artifacts Summary Consent Server

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

Artifacts Summary 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/artifacts.html

Conformance: SHALL

Notes: Does this mean a conforming system has to reference the "requirements" CS here, or could they just have their own CS that happens to be compatible? Also, what test should this be traced to? I'm thinking this traces to test procedure that ensures the right complement of tests are applied to a given system.


Language: en

These requirements apply to the actor Consent Server

requirement-1SHALL

Consent Administration Service SHALL implement the server CapabilityStatement<br/><br/>Does this mean a conforming system has to reference the "requirements" CS here, or could they just have their own CS that happens to be compatible? Also, what test should this be traced to? I'm thinking this traces to test procedure that ensures the right complement of tests are applied to a given system.

Links: