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 Client Consent Server

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

Structure Definitions Requirements for Client Consent Server

Requirements Actor(s)

These requirements apply to the following actors:

  • Client An application or product that implements the Client.
  • 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/StructureDefinition-FASTConsent.html

Reference: https://build.fhir.org/ig/HL7/fhir-consent-management/en/StructureDefinition-FASTConsent.html

Conformance: SHALL

Notes: Many nested profiles/requirements, including from US Core. Most will be checked by validator, so no need to capture. But I will capture Must Support requirements.

Specification: HL7 FAST Consent IG

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

Reference: https://build.fhir.org/ig/HL7/fhir-consent-management/en/StructureDefinition-FASTConsentAuditEvent.html

Conformance: SHALL

Notes: Many nested profiles, including from US Core. Will be checked by validator.

Specification: HL7 FAST Consent IG

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

Reference: https://build.fhir.org/ig/HL7/fhir-consent-management/en/StructureDefinition-FASTDocumentReference.html

Conformance: SHALL

Notes: Many nested profiles, including from US Core. Will be checked by validator.

Specification: HL7 FAST Consent IG

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

Reference: https://build.fhir.org/ig/HL7/fhir-consent-management/en/StructureDefinition-FASTSubscription.html

Conformance: SHALL

Related Requirement: 595: Requirements-structure-definitions-client-consent-server.html#requirement-595

Notes: The constraint that status is always "active" might not make sense. I think the client is supposed to POST it as "requested".

Specification: HL7 FAST Consent IG

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

Reference: https://build.fhir.org/ig/HL7/fhir-consent-management/en/StructureDefinition-FASTReference.html

Conformance: SHALL

Notes: Many nested profiles, including from US Core. Will be checked by validator.

Specification: Subscriptions R5 Backport

Link to Text: https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/ValueSet-backport-content-value-set.html

Reference: https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/ValueSet-backport-content-value-set.html

Conformance: SHALL

Notes: This cannot be fully tested for a given system unless we know its specific requirements, but we can hit it with each content level as an exploratory test.


Language: en

These requirements apply to the following actors:

requirement-597SHALL

StructureDefinition FASTConsent<br/><br/>Many nested profiles/requirements, including from US Core. Most will be checked by validator, so no need to capture. But I will capture Must Support requirements.

Links:

requirement-598SHALL

StructureDefinition FASTConsentAuditEvent<br/><br/>Many nested profiles, including from US Core. Will be checked by validator.

Links:

requirement-599SHALL

StructureDefinition FASTDocumentReference<br/><br/>Many nested profiles, including from US Core. Will be checked by validator.

Links:

requirement-477SHALL

StructureDefinition FASTSubscription<br/><br/>The constraint that status is always "active" might not make sense. I think the client is supposed to POST it as "requested".

Links:

requirement-601SHALL

StructureDefinition FASTReference<br/><br/>Many nested profiles, including from US Core. Will be checked by validator.

Links:

requirement-464SHALL

StructureDefinition FileConsentParameters

Links:

requirement-70SHALL

The FileConsent operation "consent" input parameter SHALL be 1..1 and conform to the FASTConsent profile

Links:

requirement-430SHALL

The FileConsent operation "document" input parameter SHALL be 1..1 and conform to either the us-core-questionnaireresponse or FASTDocumentReference profile

Links:

requirement-469SHALL

StructureDefinition RevokeConsentParameters

Links:

requirement-595SHALL

StructureDefinition BackportSubscription

Links:

requirement-892SHALL

StructureDefinition R4 Topic-Based Subscription Notification Bundle

Links:

requirement-893SHALL

StructureDefinition R4 Backported R5 SubscriptionStatus

Links:

requirement-535SHALL

ValueSet BackportContentValueSet<br/><br/>This cannot be fully tested for a given system unless we know its specific requirements, but we can hit it with each content level as an exploratory test.

Links: