Scalable Consent Management
0.1.0 - ci-build 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 0.1.0 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 Admin Service

Official URL: http://hl7.org/fhir/us/consent-management/Requirements/extended-operations-client-admin-service Version: 0.1.0
Standards status: Trial-use Maturity Level: 1 Computable Name: ExtendedOperationsClientAdminService

Extended Operations Requirements for Client Admin Service

Requirements Actor(s)

These requirements apply to the following actors:

  • Admin Service An application or product that implements the Admin Service.
  • Client An application or product that implements the Client.

Requirements Statement List

Specification: HL7 FAST Consent IG

Reference: https://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-file-consent.html

Conformance: SHALL

Specification: HL7 FAST Consent IG

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

Conformance: SHALL

Parent: Requirements-extended-operations-client-admin-service.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/OperationDefinition-file-consent.json.html

Conformance: SHALL

Parent: Requirements-extended-operations-client-admin-service.html#requirement-463

Notes: Note no defined way to return Consent ID

Specification: HL7 FAST Consent IG

Reference: https://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-update-consent.html

Conformance: SHALL

Specification: HL7 FAST Consent IG

Reference: https://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-revoke-consent.html

Conformance: SHALL

Specification: HL7 FAST Consent IG

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

Conformance: SHALL

Parent: Requirements-extended-operations-client-admin-service.html#requirement-466

Notes: - See http://hl7.org/fhir/us/core/STU6.1/StructureDefinition-us-core-patient.html - Consider tracking that

Specification: HL7 FAST Consent IG

Reference: https://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-record-disclosure.html

Conformance: SHALL

Specification: HL7 FAST Consent IG

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

Conformance: SHALL


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-465SHALL

OperationDefinition UpdateConsent

Links:

requirement-431SHALL

The UpdateConsent operation is invoked as [base]/Consent/$updateConsent

Links:

requirement-432SHALL

The UpdateConsent operation input parameters SHALL conform to the UpdateConsentParameters profile

Links:

requirement-433SHALL

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

Links:

requirement-435SHALL

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

Links:

requirement-437SHALL

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

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-440SHALL

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

Links:

requirement-447SHALL

The RevokeConsent operation "patient" input parameter SHALL be 1..1 and conform to the us-core-patient profile<br/><br/>- See http://hl7.org/fhir/us/core/STU6.1/StructureDefinition-us-core-patient.html

  • Consider tracking that

Links:

requirement-442SHALL

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

Links:

requirement-444SHALL

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

Links:

requirement-467SHALL

OperationDefinition RecordDisclosure

Links:

requirement-445SHALL

The RecordDisclosure operation is invoked as [base]/AuditEvent/$recordDisclosure

Links:

requirement-446SHALL

The RecordDisclosure operation input parameters SHALL conform to the RecordDisclosureParameters profile

Links:

requirement-451SHALL

The RecordDisclosure operation "disclosure" input parameter SHALL be 1..1 and an AuditEvent resource

Links:

requirement-449SHALL

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

Links:

requirement-453SHALL

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

Links: