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
| Official URL: http://hl7.org/fhir/us/consent-management/Requirements/subscription-topics-consent-server | Version: 1.0.0-preview | ||||
| Standards status: Trial-use | Maturity Level: 1 | Computable Name: SubscriptionTopicsConsentServer | |||
Subscription Topics Requirements for Consent Server
These requirements apply to the following actors:
Specification: HL7 FAST Consent IG
Link to Text: https://build.fhir.org/ig/HL7/fhir-consent-management/en/SubscriptionTopic-FASTConsentSubscriptionTopic.json.html
Conformance: SHALL
Parent: Requirements-subscription-topics-client-consent-server.html#requirement-596
Related Requirement: 1090: Requirements-unknown.html#requirement-1090
Notes: build: replaced requirement 1090
Specification: HL7 FAST Consent IG
Link to Text: https://build.fhir.org/ig/HL7/fhir-consent-management/en/SubscriptionTopic-FASTConsentSubscriptionTopic.json.html
Conformance: SHALL
Specification: HL7 FAST Consent IG
Link to Text: https://build.fhir.org/ig/HL7/fhir-consent-management/en/SubscriptionTopic-FASTConsentSubscriptionTopic.json.html
Conformance: SHALL
Specification: HL7 FAST Consent IG
Link to Text: https://build.fhir.org/ig/HL7/fhir-consent-management/en/SubscriptionTopic-FASTConsentSubscriptionTopic.json.html
Conformance: SHALL
Parent: Requirements-subscription-topics-client-consent-server.html#requirement-596
Specification: HL7 FAST Consent IG
Link to Text: https://build.fhir.org/ig/HL7/fhir-consent-management/en/SubscriptionTopic-FASTConsentSubscriptionTopic.json.html
Conformance: SHALL
Parent: Requirements-subscription-topics-client-consent-server.html#requirement-596
Specification: HL7 FAST Consent IG
Link to Text: https://build.fhir.org/ig/HL7/fhir-consent-management/en/SubscriptionTopic-FASTConsentSubscriptionTopic.json.html
Conformance: SHALL
Specification: HL7 FHIR R5
Link to Text: https://hl7.org/fhir/subscriptiontopic.html
Conformance: SHALL
Parent: Requirements-subscription-topics-client-consent-server.html#requirement-596
Notes: This requirement is derived by the definition in the topic plus the actual behavior defined in R5 SubscriptionTopic (which is what's linked).
Specification: HL7 FHIR R5
Link to Text: https://hl7.org/fhir/subscriptiontopic.html
Conformance: SHALL
Parent: Requirements-subscription-topics-client-consent-server.html#requirement-596
Notes: This requirement is derived by the definition in the topic plus the actual behavior defined in R5 SubscriptionTopic (which is what's linked).
Language: en
These requirements apply to the actor Consent Server
| requirement-1174 | SHALL | Consent Administration Service SHALL support Consent notification triggers based on create and update<br/><br/>build: replaced requirement 1090 Links:
|
| requirement-1175 | SHALL | Consent Administration Service SHALL support Consent notification filter by patient identifier Links:
|
| requirement-1177 | SHALL | Consent Administration Service SHALL support Consent notification filter by controller identifier Links:
|
| requirement-629 | SHALL | Consent Administration Service SHALL support Consent notification filter by actor identifier Links:
|
| requirement-630 | SHALL | Consent Administration Service SHALL support Consent notification filter by status Links:
|
| requirement-1179 | SHALL | Consent Administration Service SHALL support Consent notification filter by category Links:
|
| requirement-600 | SHALL | Consent Administration Service SHALL trigger a notification for every Consent create, unless filtered out<br/><br/>This requirement is derived by the definition in the topic plus the actual behavior defined in R5 SubscriptionTopic (which is what's linked). Links:
|
| requirement-606 | SHALL | Consent Administration Service SHALL trigger a notification for every Consent update, unless filtered out<br/><br/>This requirement is derived by the definition in the topic plus the actual behavior defined in R5 SubscriptionTopic (which is what's linked). Links:
|