Generated Narrative: Requirements capstmt-client These requirements apply to the actor Consent Client System requirement-48 SHALL Consent Client SHALL implement the client CapabilityStatement - Interpreting this as: a client doesn't necessarily have to maintain and make available a client CS, but does have to implement the functionality therein. So specific requirements from the CS are traced to tests that exercise them. Does this mean a conforming system has to reference the "requirements" CS here, or could they just have their own CS that happens to be compatible? Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/artifacts.html requirement-49 SHALL Consent Client SHALL support JSON FHIR - Plan is to have JSON and XML flavors of all tests, but explicitly tracing each of those back to these requirements is probably not necessary. Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-50 SHALL Consent Client SHALL support XML FHIR - Plan is to have JSON and XML flavors of all tests, but explicitly tracing each of those back to these requirements is probably not necessary. Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-333 SHALL Consent Client SHALL support Consent resource Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentAdministrativeServerCapabilities.json.html requirement-52 SHALL Consent Client SHALL support Consent resources that conform to FASTConsent profile Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-334 SHALL Consent Client SHALL mark with profile assertions Consent resources that conform to the FASTConsent profile Base FHIR requirement, applies because of declaring supportedProfile. Not marking as fully tested because I will continue to need to trace this to every transaction that applies. Links: Derived From: HL7 FHIR R4 Satisfied By: http://hl7.org/fhir/R4/profiling.html requirement-56 SHALL Consent Client SHALL support Consent read Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.html requirement-57 SHALL Consent Client SHALL support Consent search Links: Derived From: HL7 FAST Consent IG Satisfied By: <a href="http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html#:~:text=%22type%22%20%3A%20%22Consent%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22supportedProfile%22%20%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%20%20%F0%9F%94%97%20%22http%3A//hl7.org/fhir/us/consent%2Dmanagement/StructureDefinition/FASTConsent%22%0A%20%20%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%20%20%22interaction%22%20%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22code%22%20%3A%20%22search%2Dtype%22">http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-58 SHALL Consent Client SHALL support Consent search by FASTConsentController Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-369 SHALL Consent Client SHALL support Consent search by date Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-370 SHALL Consent Client SHALL support Consent search by FASTConsentGrantee Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-371 SHALL Consent Client SHALL support Consent search by FASTConsentManager Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-59 SHALL Consent Client SHALL support Consent search by FASTConsentOrganizationId Matches identifier of grantee, manager, controller or the provision.actor.reference Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-60 SHALL Consent Client SHALL support Consent search by patient Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-372 SHALL Consent Client SHALL support Consent search by FASTConsentPatientId Matches patient.identifier or patient.extension additionalIdentifier Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-47 SHALL Consent Client SHALL support Consent search by scope Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-61 SHALL Consent Client SHALL support Consent search by status Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-53 SHALL Consent Client SHALL support $fileConsent operation against Consent resource Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-376 SHALL Consent Client SHALL support $revokeConsent operation against Consent resource Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-381 SHALL Consent Client SHALL support Consent subscriptions as defined by the FASTConsentSubscriptionTopic for FHIR R4 with Subscriptions Backport Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-382 SHALL Consent Client SHALL support Subscription create Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-383 SHALL Consent Client SHALL support Subscription update Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-384 SHALL Consent Client SHALL support Subscription delete Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-416 SHALL Consent Client SHALL support $recordDisclosure operation against AuditEvent resource Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-401 SHALL Consent Client SHALL support AuditEvent resource Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-402 SHALL Consent Client SHALL support AuditEvent resources that conform to FASTConsentAuditEvent profile Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-403 SHALL Consent Client SHALL mark with profile assertions AuditEvent resources that conform to the FASTConsentAuditEvent profile Base FHIR requirement, applies because of declaring supportedProfile. Not marking as fully tested because I will continue to need to trace this to every transaction that applies. Links: Derived From: HL7 FHIR R4 Satisfied By: http://hl7.org/fhir/R4/profiling.html requirement-405 SHALL Consent Client SHALL support AuditEvent read Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-408 SHALL Consent Client SHALL support AuditEvent search Links: Derived From: HL7 FAST Consent IG Satisfied By: <a href="http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html#:~:text=%22type%22%20%3A%20%22AuditEvent%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22supportedProfile%22%20%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%20%20%F0%9F%94%97%20%22http%3A//hl7.org/fhir/us/consent%2Dmanagement/StructureDefinition/FASTConsentAuditEvent%22%0A%20%20%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%20%20%22interaction%22%20%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22code%22%20%3A%20%22search%2Dtype%22">http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-411 SHALL Consent Client SHALL support AuditEvent search by FASTAuditEventConsent Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html requirement-414 SHALL Consent Client SHALL support AuditEvent search by patient Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentClientCapabilities.json.html
HL7 International / Community Based Collaborative Care
Consent Client SHALL implement the client CapabilityStatement - Interpreting this as: a client doesn't necessarily have to maintain and make available a client CS, but does have to implement the functionality therein. So specific requirements from the CS are traced to tests that exercise them. - Does this mean a conforming system has to reference the "requirements" CS here, or could they just have their own CS that happens to be compatible?
Consent Client SHALL support JSON FHIR - Plan is to have JSON and XML flavors of all tests, but explicitly tracing each of those back to these requirements is probably not necessary.
Consent Client SHALL support XML FHIR - Plan is to have JSON and XML flavors of all tests, but explicitly tracing each of those back to these requirements is probably not necessary.
Consent Client SHALL support Consent resource
Consent Client SHALL support Consent resources that conform to FASTConsent profile
Consent Client SHALL mark with profile assertions Consent resources that conform to the FASTConsent profile Base FHIR requirement, applies because of declaring supportedProfile. Not marking as fully tested because I will continue to need to trace this to every transaction that applies.
Consent Client SHALL support Consent read
Consent Client SHALL support Consent search
Consent Client SHALL support Consent search by FASTConsentController
Consent Client SHALL support Consent search by date
Consent Client SHALL support Consent search by FASTConsentGrantee
Consent Client SHALL support Consent search by FASTConsentManager
Consent Client SHALL support Consent search by FASTConsentOrganizationId Matches identifier of grantee, manager, controller or the provision.actor.reference
Consent Client SHALL support Consent search by patient
Consent Client SHALL support Consent search by FASTConsentPatientId Matches patient.identifier or patient.extension additionalIdentifier
Consent Client SHALL support Consent search by scope
Consent Client SHALL support Consent search by status
Consent Client SHALL support $fileConsent operation against Consent resource
Consent Client SHALL support $revokeConsent operation against Consent resource
Consent Client SHALL support Consent subscriptions as defined by the FASTConsentSubscriptionTopic for FHIR R4 with Subscriptions Backport
Consent Client SHALL support Subscription create
Consent Client SHALL support Subscription update
Consent Client SHALL support Subscription delete
Consent Client SHALL support $recordDisclosure operation against AuditEvent resource
Consent Client SHALL support AuditEvent resource
Consent Client SHALL support AuditEvent resources that conform to FASTConsentAuditEvent profile
Consent Client SHALL mark with profile assertions AuditEvent resources that conform to the FASTConsentAuditEvent profile Base FHIR requirement, applies because of declaring supportedProfile. Not marking as fully tested because I will continue to need to trace this to every transaction that applies.
Consent Client SHALL support AuditEvent read
Consent Client SHALL support AuditEvent search
Consent Client SHALL support AuditEvent search by FASTAuditEventConsent
Consent Client SHALL support AuditEvent search by patient