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: Extended Operations Client Consent Server

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

Extended Operations 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/OperationDefinition-file-consent.json.html

Conformance: SHALL

Parent: Requirements-extended-operations-client-consent-server.html#requirement-463

Notes: For the most part, I'm not going to trace to everything in StructDefs, because the FHIR validator will check these. We may revisit this decision.

Specification: HL7 FAST Consent IG

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

Conformance: SHALL

Parent: Requirements-extended-operations-client-consent-server.html#requirement-463

Notes: Note no defined way to return Consent ID


Language: en

These requirements apply to the following actors:

requirement-463SHALL

OperationDefinition FileConsent

Links:

requirement-133SHALL

The FileConsent operation is invoked as [base]/Consent/$fileConsent

Links:

requirement-134SHALL

The FileConsent operation input parameters SHALL conform to the FileConsentParameters profile<br/><br/>For the most part, I'm not going to trace to everything in StructDefs, because the FHIR validator will check these. We may revisit this decision.

Links:

requirement-135SHALL

The FileConsent operation "consent" input parameter SHALL be 1..1 and a Consent resource

Links:

requirement-166SHALL

The FileConsent operation "document" input parameter SHALL be 1..1 and any resource

Links:

requirement-168SHALL

The FileConsent operation "return" output parameter SHALL be 0..1 and be an OperationOutcome<br/><br/>Note no defined way to return Consent ID

Links:

requirement-466SHALL

OperationDefinition RevokeConsent

Links:

requirement-438SHALL

The RevokeConsent operation is invoked as [base]/Consent/$revokeConsent

Links:

requirement-439SHALL

The RevokeConsent operation input parameters SHALL conform to the RevokeConsentParameters profile

Links:

requirement-444SHALL

The RevokeConsent operation "return" output parameter SHALL be 0..1 and be an OperationOutcome

Links: