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 Client

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

Artifacts Summary Requirements for Client

Requirements Actor(s)

These requirements apply to the following actors:

  • Client An application or product that implements the Client.

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: - Interpreting this as: a client doesn't necessarily have to maintain and make available a client CS, but does have to implement the functionality therein. So specific requirements from the CS are traced to tests that exercise them. - 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?


Language: en

These requirements apply to the actor Client

requirement-48SHALL

Consent Client SHALL implement the client CapabilityStatement<br/><br/>- Interpreting this as: a client doesn't necessarily have to maintain and make available a client CS, but does have to implement the functionality therein. So specific requirements from the CS are traced to tests that exercise them.

  • 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?

Links: