Scalable Consent Management
1.0.0-ballot - STU 1 Ballot United States of America flag

This page is part of the Scalable Consent Management (v1.0.0-ballot: STU 1 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. No current official version has been published yet. For a full list of available versions, see the Directory of published versions

Requirements: Conformance Client Admin Service

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

Conformance 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: Subscriptions R5 Backport

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

Conformance: SHALL

Notes: Not sure why, but this requirement is nearly repeated a couple sentences later as "The status entry SHALL be the first entry of each notification bundle." No need to capture that.

Specification: Subscriptions R5 Backport

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

Conformance: SHALL


These requirements apply to the following actors:

requirement-562SHALL

Notification bundles SHALL contain a FHIR R4 Parameters resource, conforming to the R4 Backported R5 SubscriptionStatus profile, as the first entry<br/><br/>Not sure why, but this requirement is nearly repeated a couple sentences later as "The status entry SHALL be the first entry of each notification bundle." No need to capture that.

Links:

requirement-537SHALL

Subscription.criteria SHALL contain the canonical URL for the Subscription Topic

Links: