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: Conformance Admin Service

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

Conformance Requirements for Admin Service

Requirements Actor(s)

These requirements apply to the following actors:

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

Requirements Statement List

Specification: Subscriptions R5 Backport

Link to Text: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALL

Specification: Subscriptions R5 Backport

Link to Text: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALL

Specification: Subscriptions R5 Backport

Link to Text: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALL

Specification: Subscriptions R5 Backport

Link to Text: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHOULD

Specification: Subscriptions R5 Backport

Link to Text: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALLSHOULD

Specification: Subscriptions R5 Backport

Link to Text: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALL

Specification: Subscriptions R5 Backport

Link to Text: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALL

Notes: Expect this means include the same declarations in addition to including it in some way

Specification: Subscriptions R5 Backport

Link to Text: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHOULD

Notes: Not exactly sure how to test this

Specification: Subscriptions R5 Backport

Link to Text: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHOULD

Specification: Subscriptions R5 Backport

Link to Text: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALL

Specification: Subscriptions R5 Backport

Reference: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALL

Specification: Subscriptions R5 Backport

Reference: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALL

Specification: Subscriptions R5 Backport

Reference: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALL

Specification: Subscriptions R5 Backport

Reference: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALL

Specification: Subscriptions R5 Backport

Reference: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALL

Notes: Will test with a variety of query strings that are not supported per the server's CapStmt.

Specification: Subscriptions R5 Backport

Reference: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALL

Specification: Subscriptions R5 Backport

Reference: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALL

Specification: Subscriptions R5 Backport

Reference: https://hl7.org/fhir/uv/subscriptions-backport/conformance.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.

Specification: Subscriptions R5 Backport

Reference: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALL

Specification: Subscriptions R5 Backport

Reference: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALL

Specification: Subscriptions R5 Backport

Reference: https://hl7.org/fhir/uv/subscriptions-backport/conformance.html

Conformance: SHALL


These requirements apply to the actor Admin Service

requirement-496SHALL

Consent Administration Service SHALL support Subscription read

Links:

requirement-497SHALL

Consent Administration Service SHALL support Subscription write

Links:

requirement-498SHALL

Consent Administration Service SHALL support $status operation against Subscription resource

Links:

requirement-499SHOULD

Consent Administration Service SHOULD support Subscription topic discovery via the CapabilityStatement SubscriptionTopic Canonical extension

Links:

requirement-500SHALL, SHOULD

Consent Administration Service SHALL support at least one Subscription channel type, and SHOULD include one from Subscriptions R5 Backport IG

Links:

requirement-501SHALL

Consent Administration Service SHALL support at least one Subscription Payload Type

Links:

requirement-502SHALL

Consent Administration Service SHALL conform to the BackportSubscriptionCapabilityStatementR4 CapabilityStatement<br/><br/>Expect this means include the same declarations in addition to including it in some way

Links:

requirement-567SHOULD

Consent Administration Service SHOULD NOT use cross version extensions on R4 subscriptions to describe any elements also described by this guide<br/><br/>Not exactly sure how to test this

Links:

requirement-504SHOULD

Consent Administration Service SHOULD declare conformance with the BackportSubscriptionCapabilityStatementR4 using CapabilityStatement.instantiates

Links:

requirement-513SHALL

Consent Administration Service SHALL support Subscription resources that conform to BackportSubscription profile

Links:

requirement-506SHALL

Consent Administration Service SHALL be able to read values in the backport-channel-type extension

Links:

requirement-507SHALL

Consent Administration Service SHALL reject the subscription request if a client requests an unsupported channel via the backport-channel-type extension

Links:

requirement-529SHALL

Consent Administration Service SHALL be able to read values in the backport-filter-criteria extension

Links:

requirement-530SHALL

Consent Administration Service SHALL be able to apply filters as described by any Subscription Topics the server advertises support for

Links:

requirement-531SHALL

Consent Administration Service SHALL reject the subscription request if any filters are unsupported<br/><br/>Will test with a variety of query strings that are not supported per the server's CapStmt.

Links:

requirement-533SHALL

Consent Administration Service SHALL be able to read values in the backport-payload-content extension

Links:

requirement-534SHALL

Consent Administration Service SHALL include information in notifications as described in this guide based on the value of the backport-payload-content extension

Links:

requirement-535SHALL

Consent Administration Service SHALL reject the subscription request if a client asks for a content level the server does not intend to support (e.g., does not meet security requirements)<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:

requirement-563SHALL

Consent Administration Service SHALL be able to generate a valid and correct R4 Backported R5 SubscriptionStatus resource for each notification

Links:

requirement-538SHALL

Consent Administration Service SHALL be able to read values in Subscription.criteria for subscription topics referenced by it

Links:

requirement-539SHALL

Consent Administration Service SHALL reject the subscription request if it does not support a requested topic or will not honor the subscription otherwise

Links: