subscriptions_test_kit 0.9.1 → 0.9.3

Sign up to get free protection for your applications and to get access to all the features.
Files changed (49) hide show
  1. checksums.yaml +4 -4
  2. data/lib/inferno_requirements_tools/tasks/collect_requirements.rb +51 -50
  3. data/lib/inferno_requirements_tools/tasks/requirements_coverage.rb +22 -19
  4. data/lib/subscriptions_test_kit/common/notification_conformance_verification.rb +4 -2
  5. data/lib/subscriptions_test_kit/endpoints/subscription_create_endpoint.rb +7 -3
  6. data/lib/subscriptions_test_kit/endpoints/subscription_status_endpoint.rb +16 -11
  7. data/lib/subscriptions_test_kit/requirements/generated/subscriptions-test-kit_requirements_coverage.csv +50 -50
  8. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client/common/subscription_simulation_utils.rb +9 -6
  9. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client/workflow/conformance_verification/notification_input_payload_verification_test.rb +3 -3
  10. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client/workflow/conformance_verification/notification_input_verification_test.rb +2 -2
  11. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client/workflow/conformance_verification/processing_attestation_test.rb +2 -2
  12. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client/workflow/conformance_verification/subscription_verification_test.rb +3 -3
  13. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client/workflow/conformance_verification_group.rb +6 -6
  14. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client/workflow/interaction_test.rb +15 -12
  15. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client/workflow/interaction_verification/event_notification_verification_test.rb +7 -6
  16. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client/workflow/interaction_verification/handshake_notification_verification_test.rb +6 -6
  17. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client/workflow/interaction_verification_group.rb +4 -4
  18. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client/workflow_group.rb +4 -4
  19. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client_suite.rb +6 -4
  20. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/{coverage/capability_statement → capability_statement}/cs_conformance_test.rb +2 -2
  21. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/{coverage/capability_statement → capability_statement}/topic_discovery_test.rb +5 -5
  22. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/capability_statement_group.rb +21 -0
  23. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/common/interaction/creation_response_conformance_test.rb +2 -2
  24. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/common/interaction/notification_delivery_test.rb +1 -1
  25. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/common/interaction/subscription_conformance_test.rb +11 -10
  26. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/common/interaction_group.rb +7 -7
  27. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/common/interaction_verification/notification_conformance_test.rb +1 -1
  28. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/common/interaction_verification_group.rb +2 -2
  29. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/common/subscription_status_operation.rb +3 -2
  30. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/{coverage/event_notification → event_notification}/empty_content/empty_conformance_test.rb +2 -2
  31. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/{coverage/event_notification → event_notification}/empty_content_group.rb +11 -10
  32. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/{coverage/event_notification → event_notification}/full_resource_content/full_resource_conformance_test.rb +4 -4
  33. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/{coverage/event_notification → event_notification}/full_resource_content_group.rb +11 -10
  34. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/{coverage/event_notification → event_notification}/id_only_content/id_only_conformance_test.rb +4 -4
  35. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/{coverage/event_notification → event_notification}/id_only_content_group.rb +11 -10
  36. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/{coverage/event_notification_group.rb → event_notification_group.rb} +6 -6
  37. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/{coverage/handshake_heartbeat → handshake_heartbeat}/handshake_conformance_test.rb +9 -8
  38. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/{coverage/handshake_heartbeat → handshake_heartbeat}/heartbeat_conformance_test.rb +6 -4
  39. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/{coverage/handshake_heartbeat_group.rb → handshake_heartbeat_group.rb} +3 -3
  40. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/{coverage/status_operation → status_operation}/status_invocation_test.rb +4 -4
  41. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/{coverage/status_operation_group.rb → status_operation_group.rb} +3 -3
  42. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/{coverage/subscription_rejection → subscription_rejection}/reject_subscriptions_test.rb +31 -27
  43. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/{coverage/subscription_rejection_group.rb → subscription_rejection_group.rb} +2 -2
  44. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/workflow_group.rb +3 -3
  45. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server_suite.rb +14 -5
  46. data/lib/subscriptions_test_kit/version.rb +1 -3
  47. metadata +21 -92
  48. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/coverage/capability_statement_group.rb +0 -21
  49. data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/coverage_group.rb +0 -26
data/lib/subscriptions_test_kit/requirements/generated/subscriptions-test-kit_requirements_coverage.csv CHANGED
@@ -1,57 +1,57 @@
1
1
  Req Set,ID,URL,Requirement,Conformance,Actor,Sub-Requirement(s),Conditionality,Subscriptions R5 Backport IG v1.1.0 FHIR R4 Client Test Suite Short ID(s),Subscriptions R5 Backport IG v1.1.0 FHIR R4 Client Test Suite Full ID(s),Subscriptions R5 Backport IG v1.1.0 FHIR R4 Server Test Suite Short ID(s),Subscriptions R5 Backport IG v1.1.0 FHIR R4 Server Test Suite Full ID(s)
2
- hl7.fhir.uv.subscriptions_1.1.0,2,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscription-topics-in-r4,"In order to allow for discovery of supported subscription topics, this guide defines the CapabilityStatement SubscriptionTopic Canonical extension. The extension allows server implementers to advertise the canonical URLs of topics available to clients and allows clients to see the list of supported topics on a server. The extension is expected to appear, if supported, on the Subscription resource entry. Note that servers are NOT required to advertise supported topics via this extension.",MAY,Server,,,NA,NA,2.1.02,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_capability_statement-subscriptions_r5_backport_r4_server_topic_discovery
2
+ hl7.fhir.uv.subscriptions_1.1.0,2,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscription-topics-in-r4,"In order to allow for discovery of supported subscription topics, this guide defines the CapabilityStatement SubscriptionTopic Canonical extension. The extension allows server implementers to advertise the canonical URLs of topics available to clients and allows clients to see the list of supported topics on a server. The extension is expected to appear, if supported, on the Subscription resource entry. Note that servers are NOT required to advertise supported topics via this extension.",MAY,Server,,,NA,NA,2.02,subscriptions_r5_backport_r4_server-subscriptions_r4_server_capability_statement-subscriptions_r4_server_topic_discovery
3
3
  hl7.fhir.uv.subscriptions_1.1.0,3,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscription-topics-in-r4,"Supported topics can also be advertised, for example, by the CapabilityStatement.instantiates or CapabilityStatement.implementationGuide elements of a CapabilityStatement, as defined by another Implementation Guide.",MAY,Server,,,NA,NA,Not Tested,Not Tested
4
4
  hl7.fhir.uv.subscriptions_1.1.0,4,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscription-topics-in-r4,"FHIR R4 servers MAY choose to leave topic discovery completely out-of-band and part of other steps, such as registration or integration.",MAY,Server,,,NA,NA,Not Tested,Not Tested
5
5
  hl7.fhir.uv.subscriptions_1.1.0,7,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,"When a FHIR Server accepts a request to create a Subscription, the server is indicating to the client that the server:
6
6
  - is capable of detecting when events covered by the requested SubscriptionTopic occur, and
7
- - is willing to make a simple best effort attempt at delivering a notification for each occurrence of a matching event.",SHALL,Server,,,NA,NA,"1.1.03, 2.2.1.1.03, 2.2.2.1.03, 2.2.3.1.03","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_workflow-subscriptions_r5_backport_r4_server_interaction-subscriptions_r5_backport_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction-subscriptions_r5_backport_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction-subscriptions_r5_backport_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction-subscriptions_r5_backport_r4_server_creation_response_conformance"
8
- hl7.fhir.uv.subscriptions_1.1.0,8,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,When processing a request for a Subscription...a server SHOULD validate…that the SubscriptionTopic is valid and implemented by the server,SHOULD,Server,,,NA,NA,2.5.01,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_subscription_rejection-subscriptions_r5_backport_r4_server_reject_subscriptions
9
- hl7.fhir.uv.subscriptions_1.1.0,9,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,When processing a request for a Subscription...a server SHOULD validate…that all requested filters are defined in the requested topic and are implemented in the server,SHOULD,Server,,,NA,NA,2.5.01,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_subscription_rejection-subscriptions_r5_backport_r4_server_reject_subscriptions
10
- hl7.fhir.uv.subscriptions_1.1.0,10,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,When processing a request for a Subscription...a server SHOULD validate…that the channel type is known and implemented by the server,SHOULD,Server,,,NA,NA,2.5.01,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_subscription_rejection-subscriptions_r5_backport_r4_server_reject_subscriptions
11
- hl7.fhir.uv.subscriptions_1.1.0,11,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,"When processing a request for a Subscription...a server SHOULD validate…that the channel endpoint is valid for the channel provided (e.g., is it a valid URL of the expected type)",SHOULD,Server,,,NA,NA,2.5.01,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_subscription_rejection-subscriptions_r5_backport_r4_server_reject_subscriptions
12
- hl7.fhir.uv.subscriptions_1.1.0,12,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,When processing a request for a Subscription...a server SHOULD validate…that the payload configuration is known and implemented by the server,SHOULD,Server,,,NA,NA,2.5.01,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_subscription_rejection-subscriptions_r5_backport_r4_server_reject_subscriptions
13
- hl7.fhir.uv.subscriptions_1.1.0,13,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,"When processing a request for a Subscription...a server SHOULD validate…that the payload configuration is valid for the channel type requested (e.g., complies with the server’s security policy)",SHOULD,Server,,,NA,NA,2.5.01,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_subscription_rejection-subscriptions_r5_backport_r4_server_reject_subscriptions
14
- hl7.fhir.uv.subscriptions_1.1.0,14,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscription-notifications,"In ... FHIR R4 ... notifications are based on a history Bundle. The first entry always contains SubscriptionStatus information, encoded as ... a Parameters resource using the Backport SubscriptionStatus Profile in FHIR R4",SHALL,Server,,,NA,NA,"1.2.01, 2.2.1.2.01, 2.2.1.2.02, 2.2.2.2.01, 2.2.2.2.02, 2.2.3.2.01, 2.2.3.2.02, 2.3.01, 2.3.02","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_workflow-subscriptions_r5_backport_r4_server_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_full_resource_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_handshake_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_heartbeat_conformance"
7
+ - is willing to make a simple best effort attempt at delivering a notification for each occurrence of a matching event.",SHALL,Server,,,NA,NA,"1.1.03, 3.1.1.03, 3.2.1.03, 3.3.1.03","subscriptions_r5_backport_r4_server-subscriptions_r4_server_workflow-subscriptions_r4_server_interaction-subscriptions_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction-subscriptions_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction-subscriptions_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction-subscriptions_r4_server_creation_response_conformance"
8
+ hl7.fhir.uv.subscriptions_1.1.0,8,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,When processing a request for a Subscription...a server SHOULD validate…that the SubscriptionTopic is valid and implemented by the server,SHOULD,Server,,,NA,NA,6.01,subscriptions_r5_backport_r4_server-subscriptions_r4_server_subscription_rejection-subscriptions_r4_server_reject_subscriptions
9
+ hl7.fhir.uv.subscriptions_1.1.0,9,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,When processing a request for a Subscription...a server SHOULD validate…that all requested filters are defined in the requested topic and are implemented in the server,SHOULD,Server,,,NA,NA,6.01,subscriptions_r5_backport_r4_server-subscriptions_r4_server_subscription_rejection-subscriptions_r4_server_reject_subscriptions
10
+ hl7.fhir.uv.subscriptions_1.1.0,10,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,When processing a request for a Subscription...a server SHOULD validate…that the channel type is known and implemented by the server,SHOULD,Server,,,NA,NA,6.01,subscriptions_r5_backport_r4_server-subscriptions_r4_server_subscription_rejection-subscriptions_r4_server_reject_subscriptions
11
+ hl7.fhir.uv.subscriptions_1.1.0,11,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,"When processing a request for a Subscription...a server SHOULD validate…that the channel endpoint is valid for the channel provided (e.g., is it a valid URL of the expected type)",SHOULD,Server,,,NA,NA,6.01,subscriptions_r5_backport_r4_server-subscriptions_r4_server_subscription_rejection-subscriptions_r4_server_reject_subscriptions
12
+ hl7.fhir.uv.subscriptions_1.1.0,12,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,When processing a request for a Subscription...a server SHOULD validate…that the payload configuration is known and implemented by the server,SHOULD,Server,,,NA,NA,6.01,subscriptions_r5_backport_r4_server-subscriptions_r4_server_subscription_rejection-subscriptions_r4_server_reject_subscriptions
13
+ hl7.fhir.uv.subscriptions_1.1.0,13,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,"When processing a request for a Subscription...a server SHOULD validate…that the payload configuration is valid for the channel type requested (e.g., complies with the server’s security policy)",SHOULD,Server,,,NA,NA,6.01,subscriptions_r5_backport_r4_server-subscriptions_r4_server_subscription_rejection-subscriptions_r4_server_reject_subscriptions
14
+ hl7.fhir.uv.subscriptions_1.1.0,14,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscription-notifications,"In ... FHIR R4 ... notifications are based on a history Bundle. The first entry always contains SubscriptionStatus information, encoded as ... a Parameters resource using the Backport SubscriptionStatus Profile in FHIR R4",SHALL,Server,,,NA,NA,"1.2.01, 3.1.2.01, 3.1.2.02, 3.2.2.01, 3.2.2.02, 3.3.2.01, 3.3.2.02, 4.01, 4.02","subscriptions_r5_backport_r4_server-subscriptions_r4_server_workflow-subscriptions_r4_server_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_full_resource_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_handshake_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_heartbeat_conformance"
15
15
  hl7.fhir.uv.subscriptions_1.1.0,15,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscription-notifications,"Note that since notifications use history type Bundles, all notifications need to comply with the requirements for that bundle type. Specifically, there are two invariants on Bundle (bdl-3 and bdl-4) that require a Bundle.entry.request element for every Bundle.entry.
16
16
  - For the status resource (entry[0]) the request SHALL be filled out to match a request to the $status operation.
17
- - for additional entries the request SHOULD be filled out in a way that makes sense given the subscription (e.g., a POST or PUT operation on the resource, etc.). However, a server MAY choose to simply include a GET to the relevant resource instead.",SHALL,Server,,,NA,NA,"1.2.01, 2.2.1.2.01, 2.2.1.2.02, 2.2.2.2.01, 2.2.2.2.02, 2.2.3.2.01, 2.2.3.2.02, 2.3.01, 2.3.02","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_workflow-subscriptions_r5_backport_r4_server_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_full_resource_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_handshake_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_heartbeat_conformance"
17
+ - for additional entries the request SHOULD be filled out in a way that makes sense given the subscription (e.g., a POST or PUT operation on the resource, etc.). However, a server MAY choose to simply include a GET to the relevant resource instead.",SHALL,Server,,,NA,NA,"1.2.01, 3.1.2.01, 3.1.2.02, 3.2.2.01, 3.2.2.02, 3.3.2.01, 3.3.2.02, 4.01, 4.02","subscriptions_r5_backport_r4_server-subscriptions_r4_server_workflow-subscriptions_r4_server_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_full_resource_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_handshake_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_heartbeat_conformance"
18
18
  hl7.fhir.uv.subscriptions_1.1.0,16,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#scoping-responsibilities,"Unless otherwise specified by a server implementation and channel, the Subscriptions Framework does not involve guaranteed delivery of notifications. While the Subscriptions Framework is able to support such mechanisms, defining them are beyond the scope of the standard or this guide. - Servers SHOULD detect errors and take appropriate action where possible. In general, this boundary is when the notification is delivered.",SHOULD,Server,,,NA,NA,,
19
19
  hl7.fhir.uv.subscriptions_1.1.0,17,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#scoping-responsibilities,"Therefore, clients SHOULD be aware of some limitations regarding delivery. In particular: - Some notifications might not be delivered. Some notifications might be delivered multiple times",SHOULD,Client,,,,,NA,NA
20
20
  hl7.fhir.uv.subscriptions_1.1.0,18,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/workflow.html#workflow-fhir-r4,"[When a client requests a Subscription, the] Server MAY accept the Subscription request and mark it active (e.g., supported channel and payload, no handshake required). ",MAY,Server,,,NA,NA,Not Tested,Not Tested
21
21
  hl7.fhir.uv.subscriptions_1.1.0,19,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/workflow.html#workflow-fhir-r4,"[When a client requests a Subscription, the] Server MAY accept the Subscription request and mark it requested (e.g., supported channel and payload, handshake required).",MAY,Server,,,NA,NA,Not Tested,Not Tested
22
- hl7.fhir.uv.subscriptions_1.1.0,20,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/workflow.html#workflow-fhir-r4,"[When a server sends a handshake bundle to a Subscription endpoint] If the Endpoint responds appropriately, per the channel requirements (e.g., in REST an HTTP Success code such as 200), the Server updates the subscription to active.",SHALL,Server,,,NA,NA,2.4.01,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_status_operation-subscriptions_r5_backport_r4_server_status_invocation
22
+ hl7.fhir.uv.subscriptions_1.1.0,20,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/workflow.html#workflow-fhir-r4,"[When a server sends a handshake bundle to a Subscription endpoint] If the Endpoint responds appropriately, per the channel requirements (e.g., in REST an HTTP Success code such as 200), the Server updates the subscription to active.",SHALL,Server,,,NA,NA,5.01,subscriptions_r5_backport_r4_server-subscriptions_r4_server_status_operation-subscriptions_r4_server_status_invocation
23
23
  hl7.fhir.uv.subscriptions_1.1.0,21,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/workflow.html#workflow-fhir-r4,"[When a server sends a handshake bundle to a Subscription endpoint] If the handshake fails (e.g., connection failure, bad response, etc.), the Server updates the subscription to error.",SHALL,Server,,,NA,NA,,
24
24
  hl7.fhir.uv.subscriptions_1.1.0,22,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/workflow.html#workflow-fhir-r4,"[When a client requests a Subscription, the] Server MAY reject the Subscription request (e.g., unsupported channel type).",MAY,Server,,,NA,NA,Not Tested,Not Tested
25
- hl7.fhir.uv.subscriptions_1.1.0,23,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,"To receive notifications via HTTP/S POST, a client should request a subscription with the channel type of rest-hook and set the endpoint to the appropriate client URL.",SHALL,Client,,,1.1.01,subscriptions_r5_backport_r4_client-subscriptions_r5_backport_r4_client_workflow-Group01-subscriptions_r5_backport_r4_client_interaction,NA,NA
26
- hl7.fhir.uv.subscriptions_1.1.0,24,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,This URL [for the subscription notification endpoint] must be accessible by the hosting server.,SHALL,Client,,,1.2.02,subscriptions_r5_backport_r4_client-subscriptions_r5_backport_r4_client_workflow-subscriptions_r5_backport_r4_client_interaction_verification-subscriptions_r5_backport_r4_client_event_notification_verification,NA,NA
27
- hl7.fhir.uv.subscriptions_1.1.0,25,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,"To convey an event notification, the server POSTs a Bundle to the client’s nominated endpoint URL",SHALL,Server,,,NA,NA,"1.1.03, 2.2.1.1.03, 2.2.2.1.03, 2.2.3.1.03, 2.3.01","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_workflow-subscriptions_r5_backport_r4_server_interaction-subscriptions_r5_backport_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction-subscriptions_r5_backport_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction-subscriptions_r5_backport_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction-subscriptions_r5_backport_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_handshake_conformance"
25
+ hl7.fhir.uv.subscriptions_1.1.0,23,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,"To receive notifications via HTTP/S POST, a client should request a subscription with the channel type of rest-hook and set the endpoint to the appropriate client URL.",SHALL,Client,,,1.1.01,subscriptions_r5_backport_r4_client-subscriptions_r4_client_workflow-Group01-subscriptions_r4_client_interaction,NA,NA
26
+ hl7.fhir.uv.subscriptions_1.1.0,24,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,This URL [for the subscription notification endpoint] must be accessible by the hosting server.,SHALL,Client,,,1.2.02,subscriptions_r5_backport_r4_client-subscriptions_r4_client_workflow-subscriptions_r4_client_interaction_verification-subscriptions_r4_client_event_notification_verification,NA,NA
27
+ hl7.fhir.uv.subscriptions_1.1.0,25,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,"To convey an event notification, the server POSTs a Bundle to the client’s nominated endpoint URL",SHALL,Server,,,NA,NA,"1.1.03, 3.1.1.03, 3.2.1.03, 3.3.1.03, 4.01","subscriptions_r5_backport_r4_server-subscriptions_r4_server_workflow-subscriptions_r4_server_interaction-subscriptions_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction-subscriptions_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction-subscriptions_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction-subscriptions_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_handshake_conformance"
28
28
  hl7.fhir.uv.subscriptions_1.1.0,26,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,The content-type of the POST SHALL match the MIME type on the Subscription (Subscription.channel.payload).,SHALL,Server,,,NA,NA,,
29
29
  hl7.fhir.uv.subscriptions_1.1.0,27,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,Each Subscription.channel.header value SHALL be conveyed as an HTTP request header.,SHALL,Server,,,NA,NA,,
30
- hl7.fhir.uv.subscriptions_1.1.0,28,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,The bundle SHALL comply with the Backported R5 Notification Bundle Profile.,SHALL,Server,,,NA,NA,"1.2.01, 2.2.1.2.01, 2.2.1.2.02, 2.2.2.2.01, 2.2.2.2.02, 2.2.3.2.01, 2.2.3.2.02, 2.3.01, 2.3.02","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_workflow-subscriptions_r5_backport_r4_server_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_full_resource_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_handshake_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_heartbeat_conformance"
31
- hl7.fhir.uv.subscriptions_1.1.0,29,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,"When a Subscription is created for a REST Hook channel type, the server SHALL set initial status to requested, pending verification of the nominated endpoint URL.",SHALL,Server,,,NA,NA,"1.1.03, 2.2.1.1.03, 2.2.2.1.03, 2.2.3.1.03","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_workflow-subscriptions_r5_backport_r4_server_interaction-subscriptions_r5_backport_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction-subscriptions_r5_backport_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction-subscriptions_r5_backport_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction-subscriptions_r5_backport_r4_server_creation_response_conformance"
32
- hl7.fhir.uv.subscriptions_1.1.0,30,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,"After a successful handshake notification has been sent and accepted [for a REST Hook channel type], the server SHALL update the status to active.",SHALL,Server,,,NA,NA,2.4.01,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_status_operation-subscriptions_r5_backport_r4_server_status_invocation
30
+ hl7.fhir.uv.subscriptions_1.1.0,28,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,The bundle SHALL comply with the Backported R5 Notification Bundle Profile.,SHALL,Server,,,NA,NA,"1.2.01, 3.1.2.01, 3.1.2.02, 3.2.2.01, 3.2.2.02, 3.3.2.01, 3.3.2.02, 4.01, 4.02","subscriptions_r5_backport_r4_server-subscriptions_r4_server_workflow-subscriptions_r4_server_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_full_resource_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_handshake_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_heartbeat_conformance"
31
+ hl7.fhir.uv.subscriptions_1.1.0,29,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,"When a Subscription is created for a REST Hook channel type, the server SHALL set initial status to requested, pending verification of the nominated endpoint URL.",SHALL,Server,,,NA,NA,"1.1.03, 3.1.1.03, 3.2.1.03, 3.3.1.03","subscriptions_r5_backport_r4_server-subscriptions_r4_server_workflow-subscriptions_r4_server_interaction-subscriptions_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction-subscriptions_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction-subscriptions_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction-subscriptions_r4_server_creation_response_conformance"
32
+ hl7.fhir.uv.subscriptions_1.1.0,30,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,"After a successful handshake notification has been sent and accepted [for a REST Hook channel type], the server SHALL update the status to active.",SHALL,Server,,,NA,NA,5.01,subscriptions_r5_backport_r4_server-subscriptions_r4_server_status_operation-subscriptions_r4_server_status_invocation
33
33
  hl7.fhir.uv.subscriptions_1.1.0,31,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,Any errors in the initial handshake [for a REST Hook channel type] SHALL result in the status being changed to error.,SHALL,Server,,,NA,NA,,
34
34
  hl7.fhir.uv.subscriptions_1.1.0,32,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#security-notes,"HTTP is neither a secure nor an encrypted channel, nor does it provide endpoint verification. It is strongly recommended that implementations refuse requests to send notifications to URLs using the HTTP protocol (use HTTPS instead).",SHOULD,Server,,,NA,NA,,
35
35
  hl7.fhir.uv.subscriptions_1.1.0,33,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/notifications.html#event-notifications-and-what-to-include,"In addition to the Subscription Status information, each notification MAY include additional resources or references to resources (URLs or ids).",MAY,Server,,,NA,NA,Not Tested,Not Tested
36
36
  hl7.fhir.uv.subscriptions_1.1.0,34,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/notifications.html#additional-resources,Servers MAY choose to include additional resources [other than the focus] with notifications that may be of interest to clients.,MAY,Server,,,NA,NA,Not Tested,Not Tested
37
- hl7.fhir.uv.subscriptions_1.1.0,35,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/notifications.html#additional-resources,"Servers SHALL conform to the payload configuration of the subscription when adding additional resources (e.g., if the subscription is id-only, then only ids of additional resources may be provided; if the subscription is full-resource, then full resources should be provided).",SHALL,Server,,,NA,NA,"2.2.1.2.02, 2.2.2.2.02, 2.2.3.2.02","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_full_resource_conformance"
37
+ hl7.fhir.uv.subscriptions_1.1.0,35,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/notifications.html#additional-resources,"Servers SHALL conform to the payload configuration of the subscription when adding additional resources (e.g., if the subscription is id-only, then only ids of additional resources may be provided; if the subscription is full-resource, then full resources should be provided).",SHALL,Server,,,NA,NA,"3.1.2.02, 3.2.2.02, 3.3.2.02","subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_full_resource_conformance"
38
38
  hl7.fhir.uv.subscriptions_1.1.0,36,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#payload-types,"If a server will not honor a payload type (e.g., will not send full-resource over HTTP), it SHOULD reject the Subscription request",SHOULD,Server,,,NA,NA,,
39
39
  hl7.fhir.uv.subscriptions_1.1.0,37,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#payload-types,"If a server will not honor a payload type (e.g., will not send full-resource over HTTP), it ... MAY accept the subscription with modifications.",MAY,Server,,,NA,NA,Not Tested,Not Tested
40
- hl7.fhir.uv.subscriptions_1.1.0,38,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#empty,"When populating the SubscriptionStatus.notificationEvent structure for a notification with an empty payload, a server SHALL NOT include references to resources (e.g., SubscriptionStatus.notificationEvent.focus and SubscriptionStatus.notificationEvent.additionalContext SHALL NOT be present).",SHALL NOT,Server,,,NA,NA,2.2.1.2.02,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_empty_conformance
41
- hl7.fhir.uv.subscriptions_1.1.0,39,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#empty,"When the content type is empty, notification bundles SHALL not contain Bundle.entry elements other than the SubscriptionStatus for the notification.",SHALL NOT,Server,,,NA,NA,2.2.1.2.02,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_empty_conformance
42
- hl7.fhir.uv.subscriptions_1.1.0,40,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#id-only,"When the content type is id-only, notification bundles SHALL include references to the appropriate focus resources in the SubscriptionStatus.notificationEvent.focus element.",SHALL,Server,,,NA,NA,2.2.2.2.02,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_id_only_conformance
40
+ hl7.fhir.uv.subscriptions_1.1.0,38,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#empty,"When populating the SubscriptionStatus.notificationEvent structure for a notification with an empty payload, a server SHALL NOT include references to resources (e.g., SubscriptionStatus.notificationEvent.focus and SubscriptionStatus.notificationEvent.additionalContext SHALL NOT be present).",SHALL NOT,Server,,,NA,NA,3.1.2.02,subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_empty_conformance
41
+ hl7.fhir.uv.subscriptions_1.1.0,39,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#empty,"When the content type is empty, notification bundles SHALL not contain Bundle.entry elements other than the SubscriptionStatus for the notification.",SHALL NOT,Server,,,NA,NA,3.1.2.02,subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_empty_conformance
42
+ hl7.fhir.uv.subscriptions_1.1.0,40,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#id-only,"When the content type is id-only, notification bundles SHALL include references to the appropriate focus resources in the SubscriptionStatus.notificationEvent.focus element.",SHALL,Server,,,NA,NA,3.2.2.02,subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_id_only_conformance
43
43
  hl7.fhir.uv.subscriptions_1.1.0,41,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#id-only,"Additionally, [id-only] notification bundles MAY contain, in addition to the SubscriptionStatus used to convey status information, at least one Bundle.entry for each resource relevant to the notification. For example, a notification for a topic based on Encounter MAY include a reference to the Encounter and MAY also include additional resources deemed relevant (e.g., the linked Patient).",MAY,Server,,,NA,NA,Not Tested,Not Tested
44
- hl7.fhir.uv.subscriptions_1.1.0,42,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#id-only,"Each Bundle.entry for id-only notification SHALL contain a relevant resource URL in the fullUrl and request elements, as is required for history bundles.",SHALL,Server,,,NA,NA,2.2.2.2.02,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_id_only_conformance
45
- hl7.fhir.uv.subscriptions_1.1.0,43,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#full-resource,"When the content type is full-resource, notification bundles SHALL include references to the appropriate focus resources in the SubscriptionStatus.notificationEvent.focus element.",SHALL,Server,,,NA,NA,2.2.3.2.02,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_full_resource_conformance
46
- hl7.fhir.uv.subscriptions_1.1.0,44,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#full-resource,"Notification bundles for full-resource subscriptions SHALL contain, in addition to the SubscriptionStatus, at least one Bundle.entry for each resource relevant to the notification. For example, a notification for a topic based on the Encounter resource SHALL include an Encounter and MAY include additional resources deemed relevant (e.g., the referenced Patient).",SHALL,Server,,,NA,NA,2.2.3.2.02,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_full_resource_conformance
47
- hl7.fhir.uv.subscriptions_1.1.0,45,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#full-resource,"Each Bundle.entry for a full-resource notification SHALL contain a relevant resource in the entry.resource element. If a server cannot include the resource contents due to an issue with a specific notification, the server SHALL populate the entry.request and/or entry.response elements.",SHALL,Server,,,NA,NA,2.2.3.2.02,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_full_resource_conformance
48
- hl7.fhir.uv.subscriptions_1.1.0,47,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHALL support the $status operation on the Subscription resource.",SHALL,Server,,,NA,NA,2.4.01,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_status_operation-subscriptions_r5_backport_r4_server_status_invocation
49
- hl7.fhir.uv.subscriptions_1.1.0,48,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHOULD support topic discovery via the CapabilityStatement SubscriptionTopic Canonical extension",SHOULD,Server,,,NA,NA,2.1.02,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_capability_statement-subscriptions_r5_backport_r4_server_topic_discovery
50
- hl7.fhir.uv.subscriptions_1.1.0,49,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHALL support at least one channel type",SHALL,Server,,,NA,NA,"1.1.03, 2.2.1.1.03, 2.2.2.1.03, 2.2.3.1.03","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_workflow-subscriptions_r5_backport_r4_server_interaction-subscriptions_r5_backport_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction-subscriptions_r5_backport_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction-subscriptions_r5_backport_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction-subscriptions_r5_backport_r4_server_creation_response_conformance"
44
+ hl7.fhir.uv.subscriptions_1.1.0,42,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#id-only,"Each Bundle.entry for id-only notification SHALL contain a relevant resource URL in the fullUrl and request elements, as is required for history bundles.",SHALL,Server,,,NA,NA,3.2.2.02,subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_id_only_conformance
45
+ hl7.fhir.uv.subscriptions_1.1.0,43,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#full-resource,"When the content type is full-resource, notification bundles SHALL include references to the appropriate focus resources in the SubscriptionStatus.notificationEvent.focus element.",SHALL,Server,,,NA,NA,3.3.2.02,subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_full_resource_conformance
46
+ hl7.fhir.uv.subscriptions_1.1.0,44,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#full-resource,"Notification bundles for full-resource subscriptions SHALL contain, in addition to the SubscriptionStatus, at least one Bundle.entry for each resource relevant to the notification. For example, a notification for a topic based on the Encounter resource SHALL include an Encounter and MAY include additional resources deemed relevant (e.g., the referenced Patient).",SHALL,Server,,,NA,NA,3.3.2.02,subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_full_resource_conformance
47
+ hl7.fhir.uv.subscriptions_1.1.0,45,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#full-resource,"Each Bundle.entry for a full-resource notification SHALL contain a relevant resource in the entry.resource element. If a server cannot include the resource contents due to an issue with a specific notification, the server SHALL populate the entry.request and/or entry.response elements.",SHALL,Server,,,NA,NA,3.3.2.02,subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_full_resource_conformance
48
+ hl7.fhir.uv.subscriptions_1.1.0,47,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHALL support the $status operation on the Subscription resource.",SHALL,Server,,,NA,NA,5.01,subscriptions_r5_backport_r4_server-subscriptions_r4_server_status_operation-subscriptions_r4_server_status_invocation
49
+ hl7.fhir.uv.subscriptions_1.1.0,48,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHOULD support topic discovery via the CapabilityStatement SubscriptionTopic Canonical extension",SHOULD,Server,,,NA,NA,2.02,subscriptions_r5_backport_r4_server-subscriptions_r4_server_capability_statement-subscriptions_r4_server_topic_discovery
50
+ hl7.fhir.uv.subscriptions_1.1.0,49,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHALL support at least one channel type",SHALL,Server,,,NA,NA,"1.1.03, 3.1.1.03, 3.2.1.03, 3.3.1.03","subscriptions_r5_backport_r4_server-subscriptions_r4_server_workflow-subscriptions_r4_server_interaction-subscriptions_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction-subscriptions_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction-subscriptions_r4_server_creation_response_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction-subscriptions_r4_server_creation_response_conformance"
51
51
  hl7.fhir.uv.subscriptions_1.1.0,50,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHOULD include one [channel type] from this guide",SHOULD,Server,,,NA,NA,,
52
- hl7.fhir.uv.subscriptions_1.1.0,51,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHALL support at least one Payload Type",SHALL,Server,,,NA,NA,"2.2.1.2.02, 2.2.2.2.02, 2.2.3.2.02","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_full_resource_conformance"
53
- hl7.fhir.uv.subscriptions_1.1.0,52,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-artifacts-1,"FHIR Servers claiming conformance to this Implementation Guide must conform to the expectations described in the Capability Statement appropriate to the implemented FHIR version. For FHIR R4 servers, this guide defines the R4 Server CapabilityStatement (https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html).",SHALL,Server,,,NA,NA,2.1.01,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_capability_statement-subscriptions_r5_backport_r4_server_cs_conformance
54
- hl7.fhir.uv.subscriptions_1.1.0,53,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-artifacts-1,"In addition to the basic support in the CapabilityStatement (e.g., resources, interactions, and operations), a conformant server SHALL support at least one Payload Type … listed in this IG.",SHALL,Server,,,NA,NA,"2.2.1.2.02, 2.2.2.2.02, 2.2.3.2.02","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_full_resource_conformance"
52
+ hl7.fhir.uv.subscriptions_1.1.0,51,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHALL support at least one Payload Type",SHALL,Server,,,NA,NA,"3.1.2.02, 3.2.2.02, 3.3.2.02","subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_full_resource_conformance"
53
+ hl7.fhir.uv.subscriptions_1.1.0,52,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-artifacts-1,"FHIR Servers claiming conformance to this Implementation Guide must conform to the expectations described in the Capability Statement appropriate to the implemented FHIR version. For FHIR R4 servers, this guide defines the R4 Server CapabilityStatement (https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html).",SHALL,Server,,,NA,NA,2.01,subscriptions_r5_backport_r4_server-subscriptions_r4_server_capability_statement-subscriptions_r4_server_cs_conformance
54
+ hl7.fhir.uv.subscriptions_1.1.0,53,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-artifacts-1,"In addition to the basic support in the CapabilityStatement (e.g., resources, interactions, and operations), a conformant server SHALL support at least one Payload Type … listed in this IG.",SHALL,Server,,,NA,NA,"3.1.2.02, 3.2.2.02, 3.3.2.02","subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_full_resource_conformance"
55
55
  hl7.fhir.uv.subscriptions_1.1.0,54,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-artifacts-1,"In addition to the basic support in the CapabilityStatement (e.g., resources, interactions, and operations), a conformant server ... SHOULD support one Channel Type listed in this IG.",SHOULD,Server,,,NA,NA,,
56
56
  hl7.fhir.uv.subscriptions_1.1.0,57,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#profile-support-1,a conformant server…SHOULD declare conformance with the Backport Subscription Server Capability Statement by including its official URL in the server’s CapabilityStatement.instantiates element: http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement/backport-subscription-server-r4.,SHOULD,Server,,,NA,NA,,
57
57
  hl7.fhir.uv.subscriptions_1.1.0,58,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#profile-support-1,"a conformant server…SHALL specify the full capability details from the CapabilityStatement it claims to implement, including declaring support for the Backport Subscription Profile by including its official URL in the server’s CapabilityStatement.rest.resource.supportedProfile element: http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-subscription",SHALL,Server,,,NA,NA,Not Tested,Not Tested
@@ -60,18 +60,18 @@ hl7.fhir.uv.subscriptions_1.1.0,60,https://hl7.org/fhir/uv/subscriptions-backpor
60
60
  hl7.fhir.uv.subscriptions_1.1.0,61,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-channel-type-1,"Clients supporting this guide MAY support this [backport-channel-type extension - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-channel-type.html] extension, as necessary for their use case.",MAY,Client,,,Not Tested,Not Tested,NA,NA
61
61
  hl7.fhir.uv.subscriptions_1.1.0,63,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-filter-criteria-1,"If a server is capable of supporting filter criteria in general but unable to support criteria requested in a subscription [via the extension backport-filter-criteria - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-filter-criteria.html], the server SHALL reject the subscription.",SHALL,Server,,,NA,NA,,
62
62
  hl7.fhir.uv.subscriptions_1.1.0,64,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-filter-criteria-1,Clients supporting this guide SHALL be able to write values in this [backport-filter-criteria - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-filter-criteria.html] extension.,SHALL,Client,,,,,NA,NA
63
- hl7.fhir.uv.subscriptions_1.1.0,65,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-payload-content-1,Servers supporting this guide SHALL be able to read values from this [backport-payload-content - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-payload-content.html] extension.,SHALL,Server,,,NA,NA,"2.2.1.2.02, 2.2.2.2.02, 2.2.3.2.02","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_full_resource_conformance"
63
+ hl7.fhir.uv.subscriptions_1.1.0,65,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-payload-content-1,Servers supporting this guide SHALL be able to read values from this [backport-payload-content - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-payload-content.html] extension.,SHALL,Server,,,NA,NA,"3.1.2.02, 3.2.2.02, 3.3.2.02","subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_full_resource_conformance"
64
64
  hl7.fhir.uv.subscriptions_1.1.0,66,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-payload-content-1,"A server SHALL reject the subscription request if a client asks for a content level the server does not intend to support (e.g., does not meet security requirements) [using the extension backport-payload-content - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-payload-content.html].",SHALL,Server,,,NA,NA,,
65
- hl7.fhir.uv.subscriptions_1.1.0,67,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-payload-content-1,Servers SHALL include information in notifications as described in this guide based on this value [in the extension backport-payload-content - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-payload-content.html].,SHALL,Server,,,NA,NA,"2.2.1.2.02, 2.2.2.2.02, 2.2.3.2.02","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_full_resource_conformance"
66
- hl7.fhir.uv.subscriptions_1.1.0,68,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-payload-content-1,Clients supporting this guide SHALL be able to write values in this [backport-payload-content - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-payload-content.html] extension.,SHALL,Client,,,1.3.01,subscriptions_r5_backport_r4_client-subscriptions_r5_backport_r4_client_workflow-subscriptions_r5_backport_r4_client_conformance_verification-subscriptions_r5_backport_r4_client_subscription_verification,NA,NA
67
- hl7.fhir.uv.subscriptions_1.1.0,69,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#notification-entry-subscriptionstatus-1,Servers supporting this guide SHALL be able to generate a valid and correct R4 Backported R5 SubscriptionStatus resource for each notification. ,SHALL,Server,,,NA,NA,"1.2.01, 2.2.1.2.01, 2.2.1.2.02, 2.2.2.2.01, 2.2.2.2.02, 2.2.3.2.01, 2.2.3.2.02, 2.3.01, 2.3.02","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_workflow-subscriptions_r5_backport_r4_server_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_full_resource_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_handshake_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_heartbeat_conformance"
68
- hl7.fhir.uv.subscriptions_1.1.0,70,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#notification-entry-subscriptionstatus-1,The status entry SHALL be the first entry of each notification bundle.,SHALL,Server,,,NA,NA,"1.2.01, 2.2.1.2.01, 2.2.1.2.02, 2.2.2.2.01, 2.2.2.2.02, 2.2.3.2.01, 2.2.3.2.02, 2.3.01, 2.3.02","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_workflow-subscriptions_r5_backport_r4_server_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_full_resource_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_handshake_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_heartbeat_conformance"
69
- hl7.fhir.uv.subscriptions_1.1.0,71,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#notification-entry-subscriptionstatus-1,Clients supporting this guide SHALL be able to process a valid R4 Backported R5 SubscriptionStatus resource without errors.,SHALL,Client,,,"1.2.01, 1.2.02","subscriptions_r5_backport_r4_client-subscriptions_r5_backport_r4_client_workflow-subscriptions_r5_backport_r4_client_interaction_verification-subscriptions_r5_backport_r4_client_handshake_notification_verification, subscriptions_r5_backport_r4_client-subscriptions_r5_backport_r4_client_workflow-subscriptions_r5_backport_r4_client_interaction_verification-subscriptions_r5_backport_r4_client_event_notification_verification",NA,NA
70
- hl7.fhir.uv.subscriptions_1.1.0,72,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#subscriptioncriteria-1,"The Subscription.criteria element is required (cardinality of 1..1), so any compatible implementation SHALL be able to read and/or write as necessary.",SHALL,Server,,,NA,NA,"1.1.01, 2.2.1.1.01, 2.2.2.1.01, 2.2.3.1.01","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_workflow-subscriptions_r5_backport_r4_server_interaction-subscriptions_r5_backport_r4_server_subscription_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction-subscriptions_r5_backport_r4_server_subscription_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction-subscriptions_r5_backport_r4_server_subscription_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction-subscriptions_r5_backport_r4_server_subscription_conformance"
65
+ hl7.fhir.uv.subscriptions_1.1.0,67,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-payload-content-1,Servers SHALL include information in notifications as described in this guide based on this value [in the extension backport-payload-content - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-payload-content.html].,SHALL,Server,,,NA,NA,"3.1.2.02, 3.2.2.02, 3.3.2.02","subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_full_resource_conformance"
66
+ hl7.fhir.uv.subscriptions_1.1.0,68,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-payload-content-1,Clients supporting this guide SHALL be able to write values in this [backport-payload-content - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-payload-content.html] extension.,SHALL,Client,,,1.3.01,subscriptions_r5_backport_r4_client-subscriptions_r4_client_workflow-subscriptions_r4_client_conformance_verification-subscriptions_r4_client_subscription_verification,NA,NA
67
+ hl7.fhir.uv.subscriptions_1.1.0,69,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#notification-entry-subscriptionstatus-1,Servers supporting this guide SHALL be able to generate a valid and correct R4 Backported R5 SubscriptionStatus resource for each notification. ,SHALL,Server,,,NA,NA,"1.2.01, 3.1.2.01, 3.1.2.02, 3.2.2.01, 3.2.2.02, 3.3.2.01, 3.3.2.02, 4.01, 4.02","subscriptions_r5_backport_r4_server-subscriptions_r4_server_workflow-subscriptions_r4_server_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_full_resource_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_handshake_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_heartbeat_conformance"
68
+ hl7.fhir.uv.subscriptions_1.1.0,70,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#notification-entry-subscriptionstatus-1,The status entry SHALL be the first entry of each notification bundle.,SHALL,Server,,,NA,NA,"1.2.01, 3.1.2.01, 3.1.2.02, 3.2.2.01, 3.2.2.02, 3.3.2.01, 3.3.2.02, 4.01, 4.02","subscriptions_r5_backport_r4_server-subscriptions_r4_server_workflow-subscriptions_r4_server_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_full_resource_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_handshake_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_heartbeat_conformance"
69
+ hl7.fhir.uv.subscriptions_1.1.0,71,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#notification-entry-subscriptionstatus-1,Clients supporting this guide SHALL be able to process a valid R4 Backported R5 SubscriptionStatus resource without errors.,SHALL,Client,,,"1.2.01, 1.2.02","subscriptions_r5_backport_r4_client-subscriptions_r4_client_workflow-subscriptions_r4_client_interaction_verification-subscriptions_r4_client_handshake_notification_verification, subscriptions_r5_backport_r4_client-subscriptions_r4_client_workflow-subscriptions_r4_client_interaction_verification-subscriptions_r4_client_event_notification_verification",NA,NA
70
+ hl7.fhir.uv.subscriptions_1.1.0,72,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#subscriptioncriteria-1,"The Subscription.criteria element is required (cardinality of 1..1), so any compatible implementation SHALL be able to read and/or write as necessary.",SHALL,Server,,,NA,NA,"1.1.01, 3.1.1.01, 3.2.1.01, 3.3.1.01","subscriptions_r5_backport_r4_server-subscriptions_r4_server_workflow-subscriptions_r4_server_interaction-subscriptions_r4_server_subscription_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction-subscriptions_r4_server_subscription_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction-subscriptions_r4_server_subscription_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction-subscriptions_r4_server_subscription_conformance"
71
71
  hl7.fhir.uv.subscriptions_1.1.0,73,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#subscriptioncriteria-1,"Compared with the core specification, this guide specifies that the [Subscription.criteria] element SHALL contain the canonical URL for the Subscription Topic.",SHALL,Server,,,NA,NA,,
72
72
  hl7.fhir.uv.subscriptions_1.1.0,74,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#subscriptioncriteria-1,Servers supporting this guide SHALL be able to read values in this [Subscription.criteria] element and process requests for subscription topics referenced by it.,SHALL,Server,,,NA,NA,,
73
73
  hl7.fhir.uv.subscriptions_1.1.0,75,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#subscriptioncriteria-1,"If a server does not support a requested topic [in the Subscription.criteria element] or will not honor the subscription otherwise, a server SHALL reject the subscription request.",SHALL,Server,,,NA,NA,,
74
- hl7.fhir.uv.subscriptions_1.1.0,76,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#subscriptioncriteria-1,Clients supporting this guide SHALL be able to write subscription topic URLs into this [Subscription.criteria] element.,SHALL,Client,,,1.3.01,subscriptions_r5_backport_r4_client-subscriptions_r5_backport_r4_client_workflow-subscriptions_r5_backport_r4_client_conformance_verification-subscriptions_r5_backport_r4_client_subscription_verification,NA,NA
74
+ hl7.fhir.uv.subscriptions_1.1.0,76,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#subscriptioncriteria-1,Clients supporting this guide SHALL be able to write subscription topic URLs into this [Subscription.criteria] element.,SHALL,Client,,,1.3.01,subscriptions_r5_backport_r4_client-subscriptions_r4_client_workflow-subscriptions_r4_client_conformance_verification-subscriptions_r4_client_subscription_verification,NA,NA
75
75
  hl7.fhir.uv.subscriptions_1.1.0,77,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/errors.html#handling-errors-as-a-server,A server SHALL…Increment the eventsSinceSubscriptionStart counter internally.,SHALL,Server,,,NA,NA,,
76
76
  hl7.fhir.uv.subscriptions_1.1.0,78,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/errors.html#handling-errors-as-a-server,A server SHALL…Update the status of the subscription internally.,SHALL,Server,,,NA,NA,,
77
77
  hl7.fhir.uv.subscriptions_1.1.0,79,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/errors.html#handling-errors-as-a-server,A server SHALL…Continue to respond to $status requests.,SHALL,Server,,,NA,NA,,
@@ -81,19 +81,19 @@ hl7.fhir.uv.subscriptions_1.1.0,82,https://hl7.org/fhir/uv/subscriptions-backpor
81
81
  hl7.fhir.uv.subscriptions_1.1.0,83,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/errors.html#using-the-events-operation,"Servers MAY choose to support the $events operation, as defined in this IG.",MAY,Server,,,NA,NA,,
82
82
  hl7.fhir.uv.subscriptions_1.1.0,84,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/errors.html#using-the-events-operation,"Servers which implement the operation MAY use implementation-specific criteria to restrict availability of events (e.g., most recent 10 events, events within the past 30 days, etc.).",MAY,Server,,,NA,NA,Not Tested,Not Tested
83
83
  hl7.fhir.uv.subscriptions_1.1.0,85,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/errors.html#using-the-events-operation,"During a recovery process, clients MAY try to retrieve missing events via the $events operation, which should allow processing to continue as normal.",MAY,Client,,,,,NA,NA
84
- hl7.fhir.uv.subscriptions_1.1.0,86,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscriptions,"In order to promote widespread compatibility, cross version extensions SHOULD NOT be used [clients should not put into Subscriptions they create] on R4 subscriptions to describe any elements also described by this guide",SHOULD NOT,Client,,,1.3.01,subscriptions_r5_backport_r4_client-subscriptions_r5_backport_r4_client_workflow-subscriptions_r5_backport_r4_client_conformance_verification-subscriptions_r5_backport_r4_client_subscription_verification,NA,NA
84
+ hl7.fhir.uv.subscriptions_1.1.0,86,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscriptions,"In order to promote widespread compatibility, cross version extensions SHOULD NOT be used [clients should not put into Subscriptions they create] on R4 subscriptions to describe any elements also described by this guide",SHOULD NOT,Client,,,1.3.01,subscriptions_r5_backport_r4_client-subscriptions_r4_client_workflow-subscriptions_r4_client_conformance_verification-subscriptions_r4_client_subscription_verification,NA,NA
85
85
  hl7.fhir.uv.subscriptions_1.1.0,88,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscriptions-and-fhir-versions,"Note that subscription notifications, by default, are made using the same FHIR version as the server. The Subscription.channel.payload element can be used [by clients] to specify a different FHIR version, using syntax and values defined by the MIME Type Parameter.",MAY,Client,,,Not Tested,Not Tested,NA,NA
86
86
  hl7.fhir.uv.subscriptions_1.1.0,90,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscriptions-and-fhir-versions,"Servers SHALL look for this [Subscription.channel.payload element] parameter during subscription negotiation and SHALL not accept requests for notification FHIR versions it cannot support (servers MAY reject or coerce, according to their policies)",SHALL,Server,,,NA,NA,,
87
87
  hl7.fhir.uv.subscriptions_1.1.0,92,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,Server may send notifications of type heartbeat at any time.,MAY,Server,,,NA,NA,Not Tested,Not Tested
88
- hl7.fhir.uv.subscriptions_1.1.0,93,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-definitions.html#root,"Subscription.channel.extension:heartbeatPeriod: If present, a 'hearbeat' notification (keepalive) is sent via this channel with an the interval period equal to this elements integer value in seconds. ",SHALL,Server,,,NA,NA,2.3.02,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_heartbeat_conformance
89
- hl7.fhir.uv.subscriptions_1.1.0,94,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-definitions.html#root,"Subscription.channel.extension:heartbeatPeriod: If not present, a heartbeat notification is not sent.",SHALL,Server,,,NA,NA,2.3.02,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_heartbeat_conformance
88
+ hl7.fhir.uv.subscriptions_1.1.0,93,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-definitions.html#root,"Subscription.channel.extension:heartbeatPeriod: If present, a 'hearbeat' notification (keepalive) is sent via this channel with an the interval period equal to this elements integer value in seconds. ",SHALL,Server,,,NA,NA,4.02,subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_heartbeat_conformance
89
+ hl7.fhir.uv.subscriptions_1.1.0,94,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-definitions.html#root,"Subscription.channel.extension:heartbeatPeriod: If not present, a heartbeat notification is not sent.",SHALL,Server,,,NA,NA,4.02,subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_heartbeat_conformance
90
90
  hl7.fhir.uv.subscriptions_1.1.0,95,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-definitions.html#root,"Subscription.criteria.extension:filterCriteria: When multiple filters are applied, evaluates to true if all the conditions are met; otherwise it returns false. (i.e., logical AND). ",SHALL,Server,,,NA,NA,,
91
91
  hl7.fhir.uv.subscriptions_1.1.0,96,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-definitions.html#root,Subscription.criteria.extension:filterCriteria: Keys can be either search parameters appropriate to the filtering resource or keys defined within the subscription topic.,SHALL,Client,,,,,NA,NA
92
92
  hl7.fhir.uv.subscriptions_1.1.0,97,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-definitions.html#root,"Subscription.channel.extension:timeout: If present, the maximum amount of time a server will allow before failing a notification attempt. ",SHALL,Server,,,NA,NA,,
93
93
  hl7.fhir.uv.subscriptions_1.1.0,98,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-definitions.html#root,"Subscription.channel.extension:maxCount: If present, the maximum number of triggering resources that will be included in a notification bundle (e.g., a server will not include more than this number of trigger resources in a single notification). Note that this is not a strict limit on the number of entries in a bundle, as dependent resources can be included.",SHALL,Server,,,NA,NA,,
94
- hl7.fhir.uv.subscriptions_1.1.0,99,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4-definitions.html,Parameters.parameter:topic.value[x]: This value SHOULD NOT be present when using empty payloads ,SHOULD NOT,Server,,,NA,NA,2.2.1.2.02,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_empty_conformance
95
- hl7.fhir.uv.subscriptions_1.1.0,100,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4-definitions.html,Parameters.parameter:topic.value[x]: This value … MAY be present when using id-only payloads,MAY,Server,,,NA,NA,2.2.2.2.02,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_id_only_conformance
96
- hl7.fhir.uv.subscriptions_1.1.0,101,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4-definitions.html,Parameters.parameter:topic.value[x]: This value … SHOULD be present when using full-resource payloads.,SHOULD,Server,,,NA,NA,2.2.3.2.02,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_full_resource_conformance
94
+ hl7.fhir.uv.subscriptions_1.1.0,99,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4-definitions.html,Parameters.parameter:topic.value[x]: This value SHOULD NOT be present when using empty payloads ,SHOULD NOT,Server,,,NA,NA,3.1.2.02,subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_empty_conformance
95
+ hl7.fhir.uv.subscriptions_1.1.0,100,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4-definitions.html,Parameters.parameter:topic.value[x]: This value … MAY be present when using id-only payloads,MAY,Server,,,NA,NA,3.2.2.02,subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_id_only_conformance
96
+ hl7.fhir.uv.subscriptions_1.1.0,101,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4-definitions.html,Parameters.parameter:topic.value[x]: This value … SHOULD be present when using full-resource payloads.,SHOULD,Server,,,NA,NA,3.3.2.02,subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_full_resource_conformance
97
97
  hl7.fhir.uv.subscriptions_1.1.0,102,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4-definitions.html,Parameters.parameter:eventsSinceSubscriptionStart.value[x]: The total number of actual events which have been generated since the Subscription was created (inclusive of this notification) - regardless of how many have been successfully communicated. This number is NOT incremented for handshake and heartbeat notifications.,SHALL,Server,,,NA,NA,,
98
98
  hl7.fhir.uv.subscriptions_1.1.0,103,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4-definitions.html,Parameters.parameter:notificationEvent.part:eventNumber.value[x]: The sequential number of this event in this subscription context.,SHALL,Server,,,NA,NA,,
99
99
  hl7.fhir.uv.subscriptions_1.1.0,104,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4-definitions.html,Parameters.parameter:notificationEvent.part:eventFocus.value[x]: MAY contain a reference to a non-FHIR object.,MAY,Server,,,NA,NA,Not Tested,Not Tested
@@ -106,7 +106,7 @@ hl7.fhir.uv.subscriptions_1.1.0,110,https://hl7.org/fhir/uv/subscriptions-backpo
106
106
  hl7.fhir.uv.subscriptions_1.1.0,111,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-status.html,"status Parameter: At the resource level, … In the absence of any specified status values, the server does not filter contents based on the status.",SHALL,Server,,,NA,NA,,
107
107
  hl7.fhir.uv.subscriptions_1.1.0,112,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-status.html,"return Parameter: The operation returns a bundle containing one or more subscription status resources, one per Subscription being queried. The Bundle type is ""searchset"".",SHALL,Server,,,NA,NA,,
108
108
  hl7.fhir.uv.subscriptions_1.1.0,113,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,Server may send notifications of type event-notification at any time.,MAY,Server,,,NA,NA,"",""
109
- hl7.fhir.uv.subscriptions_1.1.0,114,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#subscription,[Subscription Resource] Conformance Expectation: SHALL,SHALL,Server,,,NA,NA,2.1.01,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_capability_statement-subscriptions_r5_backport_r4_server_cs_conformance
109
+ hl7.fhir.uv.subscriptions_1.1.0,114,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#subscription,[Subscription Resource] Conformance Expectation: SHALL,SHALL,Server,,,NA,NA,2.01,subscriptions_r5_backport_r4_server-subscriptions_r4_server_capability_statement-subscriptions_r4_server_cs_conformance
110
110
  hl7.fhir.uv.subscriptions_1.1.0,115,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-events.html,"
111
111
  The [$events] operation returns a valid notification bundle, with the first entry being the subscription status information resource. The bundle type is ""history"".",SHALL,Server,,,NA,NA,,
112
112
  hl7.fhir.uv.subscriptions_1.1.0,116,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-events.html,"[the content input indicates the] Requested content style of returned data. Codes from backport-content-value-set (e.g., empty, id-only, full-resource).",SHALL,Client,,,,,NA,NA
@@ -114,7 +114,7 @@ hl7.fhir.uv.subscriptions_1.1.0,117,https://hl7.org/fhir/uv/subscriptions-backpo
114
114
  hl7.fhir.uv.subscriptions_1.1.0,118,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-events.html,"[The eventsSinceNumber input indicates] The starting event number, inclusive of this event (lower bound).",SHALL,Server,,,NA,NA,,
115
115
  hl7.fhir.uv.subscriptions_1.1.0,119,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-events.html,"[The eventsUntilNumber input indicates] The ending event number, inclusive of this event (upper bound).",SHALL,Server,,,NA,NA,,
116
116
  hl7.fhir.uv.subscriptions_1.1.0,120,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#summary,"
117
- [servers] SHOULD support [profile]: Backported R5 Subscription [NOTE: narrative says SHALL, resource says SHOULD, future versions correct the narrative to SHOULD]",SHOULD,Server,,,NA,NA,2.1.01,subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_capability_statement-subscriptions_r5_backport_r4_server_cs_conformance
117
+ [servers] SHOULD support [profile]: Backported R5 Subscription [NOTE: narrative says SHALL, resource says SHOULD, future versions correct the narrative to SHOULD]",SHOULD,Server,,,NA,NA,2.01,subscriptions_r5_backport_r4_server-subscriptions_r4_server_capability_statement-subscriptions_r4_server_cs_conformance
118
118
  hl7.fhir.uv.subscriptions_1.1.0,121,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#summary,SHALL support the $status operation,SHALL,Server,,,NA,NA,,
119
119
  hl7.fhir.uv.subscriptions_1.1.0,122,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#summary,MAY support the $events operation,MAY,Server,,,NA,NA,,
120
120
  hl7.fhir.uv.subscriptions_1.1.0,123,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#summary,MAY support the $get-ws-binding-token operation,MAY,Server,,,NA,NA,Not Tested,Not Tested
@@ -127,10 +127,10 @@ hl7.fhir.uv.subscriptions_1.1.0,129,https://hl7.org/fhir/uv/subscriptions-backpo
127
127
  hl7.fhir.uv.subscriptions_1.1.0,130,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#summary,Search Parameter Summary: SHOULD [support] status,SHOULD,Server,,,NA,NA,,
128
128
  hl7.fhir.uv.subscriptions_1.1.0,131,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4.html,[several SubscriptionStatus profile elements are flagged as must support],MAY,Server,,,NA,NA,Not Tested,Not Tested
129
129
  hl7.fhir.uv.subscriptions_1.1.0,132,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4.html,[several SubscriptionStatus profile elements are flagged as must support],MAY,Client,,,Not Tested,Not Tested,NA,NA
130
- hl7.fhir.uv.subscriptions_1.1.0,133,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHALL support the Subscription resource (...write).",SHALL,Server,,,NA,NA,"1.1.02, 2.2.1.1.02, 2.2.2.1.02, 2.2.3.1.02","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_workflow-subscriptions_r5_backport_r4_server_interaction-subscriptions_r5_backport_r4_server_notification_delivery, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction-subscriptions_r5_backport_r4_server_notification_delivery, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction-subscriptions_r5_backport_r4_server_notification_delivery, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction-subscriptions_r5_backport_r4_server_notification_delivery"
130
+ hl7.fhir.uv.subscriptions_1.1.0,133,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHALL support the Subscription resource (...write).",SHALL,Server,,,NA,NA,"1.1.02, 3.1.1.02, 3.2.1.02, 3.3.1.02","subscriptions_r5_backport_r4_server-subscriptions_r4_server_workflow-subscriptions_r4_server_interaction-subscriptions_r4_server_notification_delivery, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction-subscriptions_r4_server_notification_delivery, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction-subscriptions_r4_server_notification_delivery, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction-subscriptions_r4_server_notification_delivery"
131
131
  hl7.fhir.uv.subscriptions_1.1.0,134,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHALL support the Subscription resource (read...).",SHALL,Server,,,NA,NA,,
132
132
  hl7.fhir.uv.subscriptions_1.1.0,135,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-filter-criteria-1,Servers supporting this guide SHALL be able to read values in this [backport-filter-criteria - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-filter-criteria.html] extension.,SHALL,Server,,,NA,NA,,
133
133
  hl7.fhir.uv.subscriptions_1.1.0,136,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-filter-criteria-1,Servers supporting this guide...SHALL be able to apply filters [from the backport-filter-criteria - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-filter-criteria.html extension] as described by any Subscription Topics the server advertises support for.,SHALL,Server,,,NA,NA,,
134
134
  hl7.fhir.uv.subscriptions_1.1.0,137,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#profile-support-1,a conformant server…SHALL communicate all profile data elements that are mandatory by that profile’s StructureDefinition [for the R4/B Topic-Based Subscription profile],SHALL,Server,,,NA,NA,,
135
- hl7.fhir.uv.subscriptions_1.1.0,138,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#profile-support-1,a conformant server…SHALL communicate all profile data elements that are mandatory by that profile’s StructureDefinition [for the R4 Topic-Based Subscription Notification Bundle],SHALL,Server,,,NA,NA,"1.2.01, 2.2.1.2.01, 2.2.1.2.02, 2.2.2.2.01, 2.2.2.2.02, 2.2.3.2.01, 2.2.3.2.02, 2.3.01, 2.3.02","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_workflow-subscriptions_r5_backport_r4_server_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_full_resource_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_handshake_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_heartbeat_conformance"
136
- hl7.fhir.uv.subscriptions_1.1.0,139,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#profile-support-1,a conformant server…SHALL communicate all profile data elements that are mandatory by that profile’s StructureDefinition [for the R4 Backported R5 SubscriptionStatus],SHALL,Server,,,NA,NA,"1.2.01, 2.2.1.2.01, 2.2.1.2.02, 2.2.2.2.01, 2.2.2.2.02, 2.2.3.2.01, 2.2.3.2.02, 2.3.01, 2.3.02","subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_workflow-subscriptions_r5_backport_r4_server_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_empty_content-subscriptions_r5_backport_r4_server_empty_content_interaction_verification-subscriptions_r5_backport_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_id_only_content-subscriptions_r5_backport_r4_server_id_only_content_interaction_verification-subscriptions_r5_backport_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_event_notification-subscriptions_r5_backport_r4_server_full_resource_content-subscriptions_r5_backport_r4_server_full_resource_content_interaction_verification-subscriptions_r5_backport_r4_server_full_resource_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_handshake_conformance, subscriptions_r5_backport_r4_server-subscriptions_r5_backport_r4_server_coverage-subscriptions_r5_backport_r4_server_handshake_heartbeat-subscriptions_r5_backport_r4_server_heartbeat_conformance"
135
+ hl7.fhir.uv.subscriptions_1.1.0,138,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#profile-support-1,a conformant server…SHALL communicate all profile data elements that are mandatory by that profile’s StructureDefinition [for the R4 Topic-Based Subscription Notification Bundle],SHALL,Server,,,NA,NA,"1.2.01, 3.1.2.01, 3.1.2.02, 3.2.2.01, 3.2.2.02, 3.3.2.01, 3.3.2.02, 4.01, 4.02","subscriptions_r5_backport_r4_server-subscriptions_r4_server_workflow-subscriptions_r4_server_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_full_resource_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_handshake_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_heartbeat_conformance"
136
+ hl7.fhir.uv.subscriptions_1.1.0,139,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#profile-support-1,a conformant server…SHALL communicate all profile data elements that are mandatory by that profile’s StructureDefinition [for the R4 Backported R5 SubscriptionStatus],SHALL,Server,,,NA,NA,"1.2.01, 3.1.2.01, 3.1.2.02, 3.2.2.01, 3.2.2.02, 3.3.2.01, 3.3.2.02, 4.01, 4.02","subscriptions_r5_backport_r4_server-subscriptions_r4_server_workflow-subscriptions_r4_server_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_empty_content-subscriptions_r4_server_empty_content_interaction_verification-subscriptions_r4_server_empty_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_id_only_content-subscriptions_r4_server_id_only_content_interaction_verification-subscriptions_r4_server_id_only_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_notification_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_event_notification-subscriptions_r4_server_full_resource_content-subscriptions_r4_server_full_resource_content_interaction_verification-subscriptions_r4_server_full_resource_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_handshake_conformance, subscriptions_r5_backport_r4_server-subscriptions_r4_server_handshake_heartbeat-subscriptions_r4_server_heartbeat_conformance"
data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client/common/subscription_simulation_utils.rb CHANGED
@@ -19,7 +19,7 @@ module SubscriptionsTestKit
19
19
  def derive_handshake_notification(notification_json, subscription_url)
20
20
  notification_bundle = FHIR.from_contents(notification_json)
21
21
  subscription_status = update_subscription_status(notification_bundle, subscription_url, 'requested', 0,
22
- 'handshake')
22
+ 'handshake')
23
23
  subscription_status.parameter.delete(find_parameter(subscription_status, 'notification-event'))
24
24
  subscription_status.parameter.delete(find_parameter(subscription_status, 'error'))
25
25
  notification_bundle
@@ -33,8 +33,8 @@ module SubscriptionsTestKit
33
33
 
34
34
  def derive_status_bundle(notification_json, subscription_url, status_code, event_count, request_url)
35
35
  notification_bundle = FHIR.from_contents(notification_json)
36
- subscription_status = update_subscription_status(notification_bundle, subscription_url, status_code, event_count,
37
- 'query-status')
36
+ subscription_status = update_subscription_status(notification_bundle, subscription_url, status_code,
37
+ event_count, 'query-status')
38
38
  subscription_status.parameter.delete(find_parameter(subscription_status, 'notification-event'))
39
39
  subscription_status_entry = find_subscription_status_entry(notification_bundle)
40
40
  FHIR::Bundle.new(
@@ -56,7 +56,9 @@ module SubscriptionsTestKit
56
56
  end
57
57
 
58
58
  def find_subscription(test_session_id)
59
- request = requests_repo.tagged_requests(test_session_id, [SUBSCRIPTION_CREATE_TAG])&.find { |r| r.status == 201 }
59
+ request = requests_repo.tagged_requests(test_session_id, [SUBSCRIPTION_CREATE_TAG])&.find do |r|
60
+ r.status == 201
61
+ end
60
62
  return unless request
61
63
 
62
64
  begin
@@ -107,7 +109,7 @@ module SubscriptionsTestKit
107
109
  def update_subscription_status(notification_bundle, subscription_url, status_code, event_count, type)
108
110
  subscription_status_entry = find_subscription_status_entry(notification_bundle)
109
111
  subscription_status_entry.request = FHIR::Bundle::Entry::Request.new(method: 'POST',
110
- url: "#{subscription_url}/$status")
112
+ url: "#{subscription_url}/$status")
111
113
  subscription_status = subscription_status_entry&.resource
112
114
  set_subscription_reference(subscription_status, subscription_url)
113
115
  find_parameter(subscription_status, 'status')&.valueCode = status_code
@@ -130,6 +132,7 @@ module SubscriptionsTestKit
130
132
  end
131
133
 
132
134
  subscription.valueReference = FHIR::Reference.new(reference: subscription_url)
135
+ subscription
133
136
  end
134
137
 
135
138
  def find_parameter(subscription_status, parameter_name)
@@ -137,4 +140,4 @@ module SubscriptionsTestKit
137
140
  end
138
141
  end
139
142
  end
140
- end
143
+ end
data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client/workflow/conformance_verification/notification_input_payload_verification_test.rb CHANGED
@@ -11,9 +11,9 @@ module SubscriptionsTestKit
11
11
  include SubscriptionConformanceVerification
12
12
  include SubscriptionSimulationUtils
13
13
 
14
- id :subscriptions_r5_backport_r4_client_notification_input_payload_verification
14
+ id :subscriptions_r4_client_notification_input_payload_verification
15
15
  title '[USER INPUT VERIFICATION] Notification Bundle Input Conformance Verification for Payload Content'
16
- description 'This test verifies that the notification bundle from the test input meets the requirements '\
16
+ description 'This test verifies that the notification bundle from the test input meets the requirements ' \
17
17
  'of the payload indicated in the subscription created by the client under test.'
18
18
  input :notification_bundle
19
19
 
@@ -47,4 +47,4 @@ module SubscriptionsTestKit
47
47
  end
48
48
  end
49
49
  end
50
- end
50
+ end
data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client/workflow/conformance_verification/notification_input_verification_test.rb CHANGED
@@ -7,7 +7,7 @@ module SubscriptionsTestKit
7
7
  class NotificationInputVerificationTest < Inferno::Test
8
8
  include NotificationConformanceVerification
9
9
 
10
- id :subscriptions_r5_backport_r4_client_notification_input_verification
10
+ id :subscriptions_r4_client_notification_input_verification
11
11
  title '[USER INPUT VERIFICATION] Notification Bundle Input Conformance Verification'
12
12
  description %(
13
13
  This test verifies that the notification bundle provided by the tester is conformant
@@ -22,4 +22,4 @@ module SubscriptionsTestKit
22
22
  end
23
23
  end
24
24
  end
25
- end
25
+ end
data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client/workflow/conformance_verification/processing_attestation_test.rb CHANGED
@@ -7,7 +7,7 @@ module SubscriptionsTestKit
7
7
  class ProcessingAttestationTest < Inferno::Test
8
8
  include URLs
9
9
 
10
- id :subscriptions_r5_backport_r4_client_processing_attestation
10
+ id :subscriptions_r4_client_processing_attestation
11
11
  title 'Client Processes Event Notification'
12
12
  description %(
13
13
  This test asks the tester to attest that the event notification sent by Inferno
@@ -35,4 +35,4 @@ module SubscriptionsTestKit
35
35
  end
36
36
  end
37
37
  end
38
- end
38
+ end
data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_client/workflow/conformance_verification/subscription_verification_test.rb CHANGED
@@ -6,11 +6,11 @@ module SubscriptionsTestKit
6
6
  module SubscriptionsR5BackportR4Client
7
7
  class SubscriptionVerificationTest < Inferno::Test
8
8
  include SubscriptionConformanceVerification
9
- id :subscriptions_r5_backport_r4_client_subscription_verification
9
+ id :subscriptions_r4_client_subscription_verification
10
10
  title 'Client Subscription Conformance Verification'
11
11
  description %(
12
12
  This test verifies that the Subscription created by the client under test
13
- is conformant to the [R4/B Topic-Based Subscription
13
+ is conformant to the [R4/B Topic-Based Subscription
14
14
  profile](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription.html)
15
15
  and meets other requirements placed on it by the IG.
16
16
  )
@@ -25,4 +25,4 @@ module SubscriptionsTestKit
25
25
  end
26
26
  end
27
27
  end
28
- end
28
+ end