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

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

Conformance Requirements for Client

Requirements Actor(s)

These requirements apply to the following actors:

  • Client An application or product that implements the Client.

Requirements Statement List

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

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

Conformance: MAY

Notes: Not testing at this time

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


These requirements apply to the actor Client

requirement-566SHOULD

Consent Client 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-516MAY

Consent Client MAY support the backport-channel-type extension<br/><br/>Not testing at this time

Links:

requirement-532SHALL

Consent Client SHALL be able to write values in the backport-filter-criteria extension

Links:

requirement-536SHALL

Consent Client SHALL be able to write values in the backport-payload-content extension

Links:

requirement-564SHALL

Consent Client SHALL be able to process a valid R4 Backported R5 SubscriptionStatus resource without errors

Links:

requirement-540SHALL

Consent Client SHALL be able to write subscription topic URLs in Subscription.criteria

Links: