Generated Narrative: Requirements capstmt-admin-service These requirements apply to the actor Admin Service requirement-1 SHALL Consent Administration Service SHALL implement the server CapabilityStatement 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? Also, what test should this be traced to? I'm thinking this traces to test procedure that ensures the right complement of tests are applied to a given system. Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/artifacts.html requirement-2 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.json.html requirement-34 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.json.html requirement-43 SHALL Consent Administration Service 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-35 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.json.html requirement-331 SHALL Consent Administration Service 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-332 SHALL Consent Administration Service SHALL support searching by the _profile parameter for Consent resources that conform to the FASTConsent profile Base FHIR requirement, applies because of declaring supportedProfile Links: Derived From: HL7 FHIR R4 Satisfied By: http://hl7.org/fhir/R4/profiling.html requirement-36 SHALL Consent Administration Service SHALL support Consent read Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentAdministrativeServerCapabilities.html requirement-37 SHALL Consent Administration Service SHALL support Consent search Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentAdministrativeServerCapabilities.html requirement-199 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.json.html requirement-72 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.json.html requirement-38 SHALL Consent Administration Service SHALL support Consent search by FASTConsentGrantee Missing corresponding req in Tech spec 6.2.3.4 Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentAdministrativeServerCapabilities.json.html requirement-200 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.json.html requirement-39 SHALL Consent Administration Service SHALL support Consent search by FASTConsentOrganizationId Matches identifier of grantee, manager, controller or the provision.actor.reference Missing corresponding req in Tech spec 6.2.3.4 Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentAdministrativeServerCapabilities.json.html requirement-40 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.json.html requirement-368 SHALL Consent Administration Service SHALL support Consent search by FASTConsentPatientId Matches patient.identifier or patient.extension additionalIdentifier Missing corresponding req in Tech spec 6.2.3.4 Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentAdministrativeServerCapabilities.json.html requirement-42 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.json.html requirement-41 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.json.html requirement-46 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.json.html requirement-374 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.json.html requirement-661 SHALL Consent Administration Service SHALL support Subscription resource Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentAdministrativeServerCapabilities.json.html requirement-377 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.json.html requirement-378 SHALL Consent Administration Service SHALL support Subscription create For now, testing limited to the topic declared in the CapStmt Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentAdministrativeServerCapabilities.json.html requirement-379 SHALL Consent Administration Service SHALL support Subscription update Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentAdministrativeServerCapabilities.json.html requirement-380 SHALL Consent Administration Service SHALL support Subscription delete Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentAdministrativeServerCapabilities.json.html requirement-415 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.json.html requirement-397 SHALL Consent Administration Service SHALL support AuditEvent resource Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentAdministrativeServerCapabilities.json.html requirement-398 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.json.html requirement-399 SHALL Consent Administration Service 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-400 SHALL Consent Administration Service SHALL support searching by the _profile parameter for AuditEvent resources that conform to the FASTConsentAuditEvent profile Base FHIR requirement, applies because of declaring supportedProfile Links: Derived From: HL7 FHIR R4 Satisfied By: http://hl7.org/fhir/R4/profiling.html requirement-404 SHALL Consent Administration Service SHALL support AuditEvent read Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/CapabilityStatement-ConsentAdministrativeServerCapabilities.json.html requirement-406 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.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-ConsentAdministrativeServerCapabilities.json.html requirement-409 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.json.html requirement-412 SHALL Consent Administration Service 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-ConsentAdministrativeServerCapabilities.json.html requirement-505 SHALL Consent Administration Service SHALL support Subscription read Links: Derived From: Subscriptions R5 Backport Satisfied By: http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement-backport-subscription-server-r4.html requirement-503 SHOULD Consent Administration Service SHOULD support Subscription write via POST or PUT - "After POSTing the subscription, the client parses the Location header and saves the new Subscription's logical id for use in subsequent operations." - implies server should always return Location Links: Derived From: Subscriptions R5 Backport Satisfied By: http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement-backport-subscription-server-r4.html requirement-509 SHOULD Consent Administration Service SHOULD support Subscription update via PUT or PATCH The CapStmt and the rendered page disagree - the raw CS does not include patch and the page does. Not testing patch at this time. Links: Derived From: Subscriptions R5 Backport Satisfied By: http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement-backport-subscription-server-r4.html requirement-510 SHOULD Consent Administration Service SHOULD support Subscription delete Links: Derived From: Subscriptions R5 Backport Satisfied By: http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement-backport-subscription-server-r4.html requirement-511 SHOULD Consent Administration Service SHOULD support Subscription search Not testing search at this time Links: Derived From: Subscriptions R5 Backport Satisfied By: http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement-backport-subscription-server-r4.html requirement-602 SHALL Consent Administration Service SHALL support Subscription search by url Not testing search at this time. Also, the raw CapStmt (linked) and the rendered page for the CapStmt disagree: the raw says SHALL, the page says SHOULD. See: http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement-backport-subscription-server-r4.html#:~:text=Search%20Parameter%20Summary,uri Links: Derived From: Subscriptions R5 Backport Satisfied By: http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement-backport-subscription-server-r4.html requirement-604 SHOULD Consent Administration Service SHOULD support Subscription search by status Not testing search at this time Links: Derived From: Subscriptions R5 Backport Satisfied By: http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement-backport-subscription-server-r4.html requirement-508 SHALL Consent Administration Service SHALL support $status operation against Subscription resource Links: Derived From: Subscriptions R5 Backport Satisfied By: http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement-backport-subscription-server-r4.html requirement-694 MAY Consent Administration Service MAY support $events operation against Subscription resource Not testing at this time Links: Derived From: Subscriptions R5 Backport Satisfied By: <a href="http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement-backport-subscription-server-r4.html#:~:text=%22extension%22%20%3A%20%5B%7B%0D%0A%20%20%20%20%20%20%20%20%20%20%22url%22%20%3A%20%22http%3A//hl7.org/fhir/StructureDefinition/capabilitystatement%2Dexpectation%22%2C%0D%0A%20%20%20%20%20%20%20%20%20%20%22valueCode%22%20%3A%20%22MAY,http%3A//hl7.org/fhir/uv/subscriptions%2Dbackport/OperationDefinition/backport%2Dsubscription%2Devents%22">http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement-backport-subscription-server-r4.html requirement-695 MAY Consent Administration Service MAY support $get-ws-binding-token operation against Subscription resource Not testing at this time Links: Derived From: Subscriptions R5 Backport Satisfied By: http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement-backport-subscription-server-r4.html requirement-517 SHALL Consent Administration Service SHALL support Subscription resources that conform to BackportSubscription profile Links: Derived From: Subscriptions R5 Backport Satisfied By: http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement-backport-subscription-server-r4.html requirement-514 SHALL Consent Administration Service SHALL mark with profile assertions Subscription resources that conform to the BackportSubscription 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-515 SHALL Consent Administration Service SHALL support searching by the _profile parameter for Subscription resources that conform to the BackportSubscription profile Base FHIR requirement, applies because of declaring supportedProfile Links: Derived From: HL7 FHIR R4 Satisfied By: http://hl7.org/fhir/R4/profiling.html
HL7 International / Community Based Collaborative Care
Consent Administration Service SHALL implement the server CapabilityStatement 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? Also, what test should this be traced to? I'm thinking this traces to test procedure that ensures the right complement of tests are applied to a given system.
Consent Administration Service 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 Administration Service 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 Administration Service SHALL support Consent resource
Consent Administration Service SHALL support Consent resources that conform to FASTConsent profile
Consent Administration Service 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 Administration Service SHALL support searching by the _profile parameter for Consent resources that conform to the FASTConsent profile Base FHIR requirement, applies because of declaring supportedProfile
Consent Administration Service SHALL support Consent read
Consent Administration Service SHALL support Consent search
Consent Administration Service SHALL support Consent search by FASTConsentController
Consent Administration Service SHALL support Consent search by date
Consent Administration Service SHALL support Consent search by FASTConsentGrantee Missing corresponding req in Tech spec 6.2.3.4
Consent Administration Service SHALL support Consent search by FASTConsentManager
Consent Administration Service SHALL support Consent search by FASTConsentOrganizationId Matches identifier of grantee, manager, controller or the provision.actor.reference Missing corresponding req in Tech spec 6.2.3.4
Consent Administration Service SHALL support Consent search by patient
Consent Administration Service SHALL support Consent search by FASTConsentPatientId Matches patient.identifier or patient.extension additionalIdentifier Missing corresponding req in Tech spec 6.2.3.4
Consent Administration Service SHALL support Consent search by scope
Consent Administration Service SHALL support Consent search by status
Consent Administration Service SHALL support $fileConsent operation against Consent resource
Consent Administration Service SHALL support $revokeConsent operation against Consent resource
Consent Administration Service SHALL support Subscription resource
Consent Administration Service SHALL support Consent subscriptions as defined by the FASTConsentSubscriptionTopic for FHIR R4 with Subscriptions Backport
Consent Administration Service SHALL support Subscription create For now, testing limited to the topic declared in the CapStmt
Consent Administration Service SHALL support Subscription update
Consent Administration Service SHALL support Subscription delete
Consent Administration Service SHALL support $recordDisclosure operation against AuditEvent resource
Consent Administration Service SHALL support AuditEvent resource
Consent Administration Service SHALL support AuditEvent resources that conform to FASTConsentAuditEvent profile
Consent Administration Service 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 Administration Service SHALL support searching by the _profile parameter for AuditEvent resources that conform to the FASTConsentAuditEvent profile Base FHIR requirement, applies because of declaring supportedProfile
Consent Administration Service SHALL support AuditEvent read
Consent Administration Service SHALL support AuditEvent search
Consent Administration Service SHALL support AuditEvent search by FASTAuditEventConsent
Consent Administration Service SHALL support AuditEvent search by patient
Consent Administration Service SHALL support Subscription read
Consent Administration Service SHOULD support Subscription write via POST or PUT - "After POSTing the subscription, the client parses the Location header and saves the new Subscription's logical id for use in subsequent operations." - implies server should always return Location
Consent Administration Service SHOULD support Subscription update via PUT or PATCH The CapStmt and the rendered page disagree - the raw CS does not include patch and the page does. Not testing patch at this time.
Consent Administration Service SHOULD support Subscription delete
Consent Administration Service SHOULD support Subscription search Not testing search at this time
Consent Administration Service SHALL support Subscription search by url Not testing search at this time. Also, the raw CapStmt (linked) and the rendered page for the CapStmt disagree: the raw says SHALL, the page says SHOULD. See: http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement-backport-subscription-server-r4.html#:~:text=Search%20Parameter%20Summary,uri
Consent Administration Service SHOULD support Subscription search by status Not testing search at this time
Consent Administration Service SHALL support $status operation against Subscription resource
Consent Administration Service MAY support $events operation against Subscription resource Not testing at this time
Consent Administration Service MAY support $get-ws-binding-token operation against Subscription resource Not testing at this time
Consent Administration Service SHALL support Subscription resources that conform to BackportSubscription profile
Consent Administration Service SHALL mark with profile assertions Subscription resources that conform to the BackportSubscription 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 Administration Service SHALL support searching by the _profile parameter for Subscription resources that conform to the BackportSubscription profile Base FHIR requirement, applies because of declaring supportedProfile