subscriptions_test_kit 0.9.3 → 0.10.0

data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/common/interaction/subscription_conformance_test.rb

@@ -8,30 +8,29 @@ module SubscriptionsTestKit
       id :subscriptions_r4_server_subscription_conformance
       title '[USER INPUT VERIFICATION] Verify Subscription to Send to Server'
       description %(
-        The Subscription resource is used to request notifications for a specific client about a specific topic
-        Conceptually, a subscription is a concrete request for a single client to receive notifications per a single
-        topic. In order to support topic-based subscriptions in R4, this guide defines several extensions for use on the
-        [R4 Subscription resource](http://hl7.org/fhir/R4/subscription.html). A list of extensions defined by this guide
-        can be found on the
-        [Subscriptions R5 Backport IG's Artifacts page](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/artifacts.html#5).
-
         This test accepts a Subscription resource as an input and verifies that it is conformant to the
-        [R4/B Topic-Based Subscription profile](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription.html).
+        [R4/B Topic-Based Subscription profile](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription.html)
+        and that it is constructed to make supported notifications to Inferno's simulated
+        Subscriptions client.
 
-        The Subscription channel should have it's fields populated with the following information:
-          - The `endpoint` field must be set to
+        For the server to successfuly deliver notifications recognized by this test session, the Subscription `channel`
+        element should have it's subelements populated with the following information:
+        - The `endpoint` field must be set to
           `#{Inferno::Application['base_url']}/custom/subscriptions_r5_backport_r4_server#{SUBSCRIPTION_CHANNEL_PATH}`.
           The test will add the correct url to this field if it is not properly set.
-          - The `type` field must be set to `rest-hook`, as the Inferno subscription workflow tests use a `rest-hook`
+        - The `type` element must be set to `rest-hook`, as the Inferno subscription workflow tests use a `rest-hook`
           subscription channel to receive incoming notifications. The test will add the correct type to this field if it
           is not properly set.
-          - The `payload` field must be set to `application/json`, as Inferno will only accept resources in requests
-          with this content type.
-          - The `header` field must include the `Authorization` header with a Bearer token set to the inputted Inferno
-          access token.
+        - The `payload` element should be `application/fhir+json`. Inferno will update it to that value
+          unless the provided value is `application/json`, which Inferno also supports receiving as the
+          `content-type` HTTP header on notifications.
+        - The `header` element must include the `Authorization` header with a Bearer token set to the inputted Inferno
+          access token to direct the server to send that header to identify the notifications are for this session.
+          Inferno will add the entry if it is not present.
       )
 
       verifies_requirements 'hl7.fhir.uv.subscriptions_1.1.0@72',
+                            'hl7.fhir.uv.subscriptions_1.1.0@73',
                             'hl7.fhir.uv.subscriptions_1.1.0@86'
 
       input :subscription_resource,
@@ -54,17 +53,12 @@ module SubscriptionsTestKit
               sent to Inferno.
             )
 
-      output :updated_subscription, :subscription_topic
+      output :updated_subscription
 
       run do
         omit_if subscription_resource.blank?, 'Did not input a Subscription resource of this type.'
         subscription = subscription_verification(subscription_resource)
         no_error_verification('Subscription resource is not conformant.')
-
-        assert(subscription['criteria'].present?,
-               'The `criteria` field SHALL be populated and contain the canonical URL for the Subscription Topic.')
-        output subscription_topic: subscription['criteria']
-
         subscription = server_check_channel(subscription, access_token)
         output updated_subscription: subscription.to_json
       end

data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/common/interaction_group.rb

@@ -9,9 +9,9 @@ module SubscriptionsTestKit
       title 'Subscription Workflow Interaction'
       description %(
         Verify that the Subscription instance the tester provided is conformant, and then demonstrate the ability of the
-        server under test to accept a request for the creation of a FHIR Subscription instance and deliver a
-        notification for that Subscription. Inferno will act as a client, creating the Subscription and waiting for a
-        notification based on it.
+        server under test to accept a request for the creation of a FHIR Subscription instance and deliver
+        notifications for that Subscription. Inferno will act as a client, creating the Subscription and waiting for
+        notifications based on it.
       )
 
       run_as_group

data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/common/interaction_verification/notification_conformance_test.rb

@@ -6,7 +6,7 @@ module SubscriptionsTestKit
       include NotificationConformanceVerification
 
       id :subscriptions_r4_server_notification_conformance
-      title 'Subscription Notification Verification'
+      title 'Subscription Event Notification Verification'
       description %(
         As described in [Topic-Based Subscription Components](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscription-notifications),
         all notifications are enclosed in a Bundle with the type of history. Additionally, the first entry of the bundle
@@ -14,9 +14,11 @@ module SubscriptionsTestKit
         [Backport SubscriptionStatus Profile](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4.html)
         in FHIR R4.
 
-        This test takes the received notification bundle and ensures it is conformant to the
+        This test takes the received event notification bundle or bundles from the most recently successfully created
+        Subscription (from the just-run interaction test) and ensures they are conformant to the
         [R4 Topic-Based Subscription Notification Bundle](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-notification-r4.html)
-        profle.
+        profle. Note that other interactions like handshake and heartbeat notification are not verified as a
+        part of this test and those requests will not be associated with this test.
       )
 
       verifies_requirements 'hl7.fhir.uv.subscriptions_1.1.0@14',
@@ -37,36 +39,50 @@ module SubscriptionsTestKit
           subscription_requests =
             requests
               .select { |request| request.status == 201 }
-          skip_if subscription_requests.empty?,
-                  'No successful Subscription creation request was made in the previous test.'
+          skip_if subscription_requests.empty?, %(
+                    No successful Subscription creation request of type #{subscription_type}
+                    was made in the previous test.
+                  )
         else
           all_requests = load_tagged_requests('subscription_creation')
-          all_subscription_requests =
+          subscription_requests =
             all_requests
               .select { |request| request.status == 201 }
-          skip_if all_subscription_requests.empty?,
+          skip_if subscription_requests.empty?,
                   'No successful Subscription creation request was made in the previous test.'
-          subscription_requests = [all_subscription_requests.first]
         end
 
+        # select the most recent subscription to verify
+        # this test is run as part of the interaction group, so the most recent
+        # successfully created Subscription will be the one that came during
+        # the previoius interaction test
+        latest_subscription = nil
         subscription_requests.each do |subscription_request|
-          assert_valid_json(subscription_request.response_body)
-          subscription = JSON.parse(subscription_request.response_body)
+          if latest_subscription.blank? || latest_subscription.created_at < subscription_request.created_at
+            latest_subscription = subscription_request
+          end
+        end
 
-          requests = load_tagged_requests('event-notification', subscription['id'])
-          skip_if requests.empty?, 'No event-notification requests were made in a previous test as expected.'
+        assert_valid_json(latest_subscription.response_body)
+        subscription = JSON.parse(latest_subscription.response_body)
 
-          requests = requests.uniq(&:request_body)
-          requests.each do |request|
-            notification_verification(
-              request.request_body,
-              'event-notification',
-              subscription_id: subscription['id'],
-              status: 'active'
-            )
-          end
+        requests = load_tagged_requests('event-notification', subscription['id'])
+        skip_if requests.empty?, %(
+                  No event-notification requests were made for Subscription #{subscription['id']}
+                  in during the interaction.
+                )
+
+        requests = requests.uniq(&:request_body)
+        requests.each do |request|
+          notification_verification(
+            request.request_body,
+            'event-notification',
+            subscription_id: subscription['id'],
+            status: 'active'
+          )
         end
-        no_error_verification('Received event-notifications are not conformant.')
+
+        no_error_verification("Received event-notifications for Subscription #{subscription['id']} are not conformant.")
       end
     end
   end

data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/common/interaction_verification/notification_presence_test.rb

@@ -0,0 +1,56 @@
+module SubscriptionsTestKit
+  module SubscriptionsR5BackportR4Server
+    class NotificationPresenceTest < Inferno::Test
+      id :subscriptions_r4_server_notification_presence
+      title 'Notification Presence Verification'
+      description %(
+        This test identifies the most recent successfully created Subscription (from the just-run interaction test)
+        and checks that the server sent at least one notification to Inferno's notification endpoint
+        regarding that Subscription. This test does not check the types of these notifications or
+        whether they are conformant.
+      )
+
+      def subscription_type
+        config.options[:subscription_type]
+      end
+
+      run do
+        if subscription_type.present?
+          requests = load_tagged_requests('subscription_creation', subscription_type)
+          subscription_requests =
+            requests
+              .select { |request| request.status == 201 }
+          skip_if subscription_requests.empty?, %(
+                    No successful Subscription creation request of type #{subscription_type}
+                    was made in the previous test.
+                  )
+        else
+          all_requests = load_tagged_requests('subscription_creation')
+          subscription_requests =
+            all_requests
+              .select { |request| request.status == 201 }
+          skip_if subscription_requests.empty?,
+                  'No successful Subscription creation request was made in the previous test.'
+        end
+
+        # select the most recent subscription to verify
+        # this test is run as part of the interaction group, so the most recent
+        # successfully created Subscription will be the one that came during
+        # the previoius interaction test
+        latest_subscription = nil
+        subscription_requests.each do |subscription_request|
+          if latest_subscription.blank? || latest_subscription.created_at < subscription_request.created_at
+            latest_subscription = subscription_request
+          end
+        end
+
+        assert_valid_json(latest_subscription.response_body)
+        subscription = JSON.parse(latest_subscription.response_body)
+
+        requests = load_tagged_requests(subscription['id'])
+        assert !requests.empty?,
+               "No notifications were received from the server related to Subscription #{subscription['id']}."
+      end
+    end
+  end
+end

data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/common/interaction_verification_group.rb

@@ -1,4 +1,5 @@
 require_relative 'interaction_verification/notification_conformance_test'
+require_relative 'interaction_verification/notification_presence_test'
 
 module SubscriptionsTestKit
   module SubscriptionsR5BackportR4Server
@@ -6,13 +7,16 @@ module SubscriptionsTestKit
       id :subscriptions_r4_server_interaction_verification
       title 'Subscription Workflow Interaction Verification'
       description %(
-        Inferno takes the received event-notification Bundle and verifies that it is conformant to the
-        [R4 Topic-Based Subscription Notification Bundle](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-notification-r4.html)
-        profle.
+        Inferno will verify that the sever communicated at least one notification
+        (handshake, heartbeat, and/or event-notification) back to Inferno
+        related to the created Subscription and that that set of notifications
+        includes a conformant event-notification. Other types of notifications
+        are verified during other tests.
       )
 
       run_as_group
 
+      test from: :subscriptions_r4_server_notification_presence
       test from: :subscriptions_r4_server_notification_conformance
     end
   end

data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/common/subscription_creation.rb

@@ -16,6 +16,12 @@ module SubscriptionsTestKit
         field_path.reduce(subscription) { |obj, path| obj[path] }
       end
 
+      def normalize_value(value)
+        return value.deep_transform_keys(&:to_sym) if value.is_a?(Hash)
+
+        value
+      end
+
       def send_unsupported_subscription(subscription, unsupported_type, field_paths, subscription_field_old_values)
         fhir_operation('/Subscription', body: subscription)
 
@@ -27,7 +33,10 @@ module SubscriptionsTestKit
         altered_field = false
         field_paths.each_with_index do |field_path, index|
           subscription_field_new_value = get_new_subscription_value(new_subscription, field_path)
-          if subscription_field_new_value != subscription_field_old_values[index]
+          new_value = normalize_value(subscription_field_new_value)
+          old_value = normalize_value(subscription_field_old_values[index])
+
+          if new_value != old_value
             altered_field = true
             break
           end
@@ -56,7 +65,7 @@ module SubscriptionsTestKit
 
         fhir_operation('/Subscription', body: subscription, tags:)
         assert_response_status(201)
-        payload_type
+        json_parse(request.response_body)
       end
     end
   end

data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/event_notification/full_resource_content/full_resource_conformance_test.rb

@@ -54,11 +54,10 @@ module SubscriptionsTestKit
           requests = load_tagged_requests('event-notification', subscription['id'])
           skip_if requests.empty?, 'No event-notification requests were made in a previous test as expected.'
 
-          criteria_resource_type = subscription_criteria(subscription)
           requests = requests.uniq(&:request_body)
 
           requests.each do |request|
-            full_resource_event_notification_verification(request.request_body, criteria_resource_type)
+            full_resource_event_notification_verification(request.request_body, nil)
           end
         end
         no_error_verification('Received notification-events are not conformant.')

data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/event_notification/id_only_content/id_only_conformance_test.rb

@@ -52,11 +52,10 @@ module SubscriptionsTestKit
           requests = load_tagged_requests('event-notification', subscription['id'])
           skip_if requests.empty?, 'No event-notification requests were made in a previous test as expected.'
 
-          criteria_resource_type = subscription_criteria(subscription)
           requests = requests.uniq(&:request_body)
 
           requests.each do |request|
-            id_only_event_notification_verification(request.request_body, criteria_resource_type)
+            id_only_event_notification_verification(request.request_body, nil)
           end
         end
         no_error_verification('Received notification-events are not conformant.')

data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/event_notification_group.rb

@@ -6,12 +6,13 @@ module SubscriptionsTestKit
   module SubscriptionsR5BackportR4Server
     class EventNotificationGroup < Inferno::TestGroup
       id :subscriptions_r4_server_event_notification
-      title 'Backport Subscription Notification Verification'
+      title 'Backport Subscription Notification Payload Type Verification'
       description %(
         Verify that the received Notifications are conformant to the
         [R4 Topic-Based Subscription Notification Bundle](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-notification-r4.html)
-        profile, including additional requirements around the content type. This group contains tests for the three
-        options available when specifying the contents of a Notification: empty, id-only, and full-resource.
+        profile, including additional requirements around the payload type. This group contains tests for the three
+        options available when specifying the content level for event notification payloads:
+        `empty`, `id-only`, and `full-resource`.
       )
 
       input_order :url, :credentials, :access_token, :empty_subscription_resource,

data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/handshake_heartbeat/handshake_conformance_test.rb

@@ -13,6 +13,9 @@ module SubscriptionsTestKit
         endpoint. After a successful handshake notification has been sent and accepted, the server SHALL update the
         status to active. This test verifies that the incoming handshake request is a conformant
         [R4 Topic-Based Subscription Notification Bundle](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-notification-r4.html).
+
+        Note that all Subscriptions and the associated Handshake notifications received during previously-run tests
+        will be associated with this test and analyzed for conformance.
       )
 
       verifies_requirements 'hl7.fhir.uv.subscriptions_1.1.0@14',

data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/handshake_heartbeat/heartbeat_conformance_test.rb

@@ -11,6 +11,9 @@ module SubscriptionsTestKit
         When a Subscription is created for a REST Hook channel type, the server Server may send notifications of type
         heartbeat at any time. This test verifies that the incoming heartbeat request is a conformant
         [R4 Topic-Based Subscription Notification Bundle](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-notification-r4.html).
+
+        Note that all Subscriptions and the associated Heartbeat notifications received during previously-run tests
+        will be associated with this test and analyzed for conformance.
       )
 
       verifies_requirements 'hl7.fhir.uv.subscriptions_1.1.0@14',

data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/handshake_heartbeat_group.rb

@@ -7,7 +7,7 @@ module SubscriptionsTestKit
       id :subscriptions_r4_server_handshake_heartbeat
       title 'Backport Subscription Handshake and Heartbeat Notification Verification'
       description %(
-        Verify that the any received Handshake or Heartbeat Notifications are conformant to the
+        Verify that all Handshake ane Heartbeat Notifications received during previous tests are conformant to the
         [R4 Topic-Based Subscription Notification Bundle](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-notification-r4.html)
         profile.
       )

data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/subscription_rejection/reject_subscription_channel_endpoint_test.rb

@@ -0,0 +1,65 @@
+require_relative '../common/subscription_creation'
+
+module SubscriptionsTestKit
+  module SubscriptionsR5BackportR4Server
+    class RejectSubscriptionChannelEndpointTest < Inferno::Test
+      include SubscriptionCreation
+
+      id :subscriptions_r4_server_reject_subscription_channel_endpoint
+      title 'Server Handles Unsupported Subscription Channel Endpoints'
+      description %(
+        When processing a request for a Subscription a server SHOULD verify that the Subscription is supported and does
+        not contain any information not implemented by the server. If the Subscription is not supported, the server
+        should reject the Subscription create request, or it should attempt to adjust the Subscription. 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).
+
+        The test will pass if the server either
+        1. rejects the Subscription by responding with a non-201 response, or
+        2. updates the Subscription resource to remove or replace the unsupported value.
+      )
+
+      verifies_requirements 'hl7.fhir.uv.subscriptions_1.1.0@11'
+
+      input :subscription_resource,
+            title: 'Workflow Subscription Resource',
+            type: 'textarea',
+            description: %(
+              A Subscription resource in JSON format that Inferno will send to the server under test
+              so that it can demonstrate its ability to perform the Subscription creation and Notification
+              response workflow. The instance must be conformant to the R4/B Topic-Based Subscription profile.
+              Inferno may modify the Subscription before submission, e.g., to point to Inferno's notification endpoint.
+              This input is also used by the unsupported Subscription test as the base on which to add unsupported
+              element values to test for server rejection.
+            )
+      input :unsupported_subscription_channel_endpoint,
+            title: 'Unsupported Subscription Channel Endpoint',
+            description: 'An unsupported value for the `channel.endpoint` element to test for Subscription rejection.',
+            optional: true
+
+      run do
+        skip_if(unsupported_subscription_channel_endpoint.blank?, %(
+          Provide a value in the "Unsupported Subscription Channel Endpoint" input to run this test.))
+
+        assert_valid_json(subscription_resource)
+        subscription = JSON.parse(subscription_resource)
+
+        unsupported_info = {
+          'unsupported_title' => 'unsupported channel URL',
+          'field_path' => ['channel', 'endpoint'],
+          'field_value' => unsupported_subscription_channel_endpoint
+        }
+
+        field_name = unsupported_info['field_path'].last
+        outer_field_name = unsupported_info['field_path'].first
+        subscription_field = subscription[outer_field_name]
+        subscription_field[field_name] = unsupported_info['field_value']
+
+        send_unsupported_subscription(subscription, unsupported_info['unsupported_title'],
+                                      [unsupported_info['field_path']], [unsupported_info['field_value']])
+
+        no_error_verification('Unsupported Subscription creation error handling failures.')
+      end
+    end
+  end
+end

data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/subscription_rejection/reject_subscription_channel_payload_combo_test.rb

@@ -0,0 +1,76 @@
+require_relative '../common/subscription_creation'
+
+module SubscriptionsTestKit
+  module SubscriptionsR5BackportR4Server
+    class RejectSubscriptionChannelPayloadComboTest < Inferno::Test
+      include SubscriptionCreation
+
+      id :subscriptions_r4_server_reject_subscription_channel_payload_combo
+      title 'Server Handles Unsupported Subscription Payload for Channel Type'
+      description %(
+        When processing a request for a Subscription a server SHOULD verify that the Subscription is supported and does
+        not contain any information not implemented by the server. If the Subscription is not supported, the server
+        should reject the Subscription create request, or it should attempt to adjust the Subscription. 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).
+
+        The test will pass if the server either
+        1. rejects the Subscription by responding with a non-201 response, or
+        2. updates the Subscription resource to remove or replace the unsupported value.
+      )
+
+      verifies_requirements 'hl7.fhir.uv.subscriptions_1.1.0@13'
+
+      input :subscription_resource,
+            title: 'Workflow Subscription Resource',
+            type: 'textarea',
+            description: %(
+              A Subscription resource in JSON format that Inferno will send to the server under test
+              so that it can demonstrate its ability to perform the Subscription creation and Notification
+              response workflow. The instance must be conformant to the R4/B Topic-Based Subscription profile.
+              Inferno may modify the Subscription before submission, e.g., to point to Inferno's notification endpoint.
+              This input is also used by the unsupported Subscription test as the base on which to add unsupported
+              element values to test for server rejection.
+            )
+      input :unsupported_subscription_channel_payload_combo,
+            title: 'Unsupported Subscription Channel and Payload Combination',
+            description: %(
+              A channel (`channel.type`) and payload type (`content` extension under the `channel.payload` element)
+              combination not implemented by the server to test for Subscription
+              rejection. Provide as a JSON object with two keys as follows: {"channel": "channel_type",
+              "payload": "wrong_payload_type_for_this_channel"}.
+            ),
+            optional: true
+
+      run do
+        skip_if(unsupported_subscription_channel_payload_combo.blank?, %(
+          Provide a value in the "Unsupported Subscription Channel and Payload Combination" input to run this test.))
+
+        assert_valid_json(subscription_resource)
+        subscription = JSON.parse(subscription_resource)
+
+        assert_valid_json(unsupported_subscription_channel_payload_combo)
+        channel_payload_combo = JSON.parse(unsupported_subscription_channel_payload_combo)
+        channel_value = channel_payload_combo['channel']
+        payload_value = channel_payload_combo['payload']
+
+        if channel_value.blank? || payload_value.blank?
+          add_message('error', %(Channel and payload values are not populated correctly in unsupported channel and
+                                 payload combination input.))
+        else
+          subscription_channel = subscription['channel']
+          subscription_channel['type'] = channel_value
+          subscription_channel['payload'] = payload_value
+
+          channel_path = ['channel', 'type']
+          payload_path = ['channel', 'payload']
+
+          send_unsupported_subscription(subscription, 'unsupported channel and payload combination',
+                                        [channel_path, payload_path], [channel_value, payload_value])
+        end
+
+        no_error_verification('Unsupported Subscription creation error handling failures.')
+      end
+    end
+  end
+end

data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/subscription_rejection/reject_subscription_channel_type_test.rb

@@ -0,0 +1,68 @@
+require_relative '../common/subscription_creation'
+
+module SubscriptionsTestKit
+  module SubscriptionsR5BackportR4Server
+    class RejectSubscriptionChannelTypeTest < Inferno::Test
+      include SubscriptionCreation
+
+      id :subscriptions_r4_server_reject_subscription_channel_type
+      title 'Server Handles Unsupported Subscription Channel Types'
+      description %(
+        When processing a request for a Subscription a server SHOULD verify that the Subscription is supported and does
+        not contain any information not implemented by the server. If the Subscription is not supported, the server
+        should reject the Subscription create request, or it should attempt to adjust the Subscription. When
+        processing a request for a Subscription a server SHOULD validat that the channel type is known
+        and implemented by the server.
+
+        The test will pass if the server either
+        1. rejects the Subscription by responding with a non-201 response, or
+        2. updates the Subscription resource to remove or replace the unsupported value.
+      )
+
+      verifies_requirements 'hl7.fhir.uv.subscriptions_1.1.0@10'
+
+      input :subscription_resource,
+            title: 'Workflow Subscription Resource',
+            type: 'textarea',
+            description: %(
+              A Subscription resource in JSON format that Inferno will send to the server under test
+              so that it can demonstrate its ability to perform the Subscription creation and Notification
+              response workflow. The instance must be conformant to the R4/B Topic-Based Subscription profile.
+              Inferno may modify the Subscription before submission, e.g., to point to Inferno's notification endpoint.
+              This input is also used by the unsupported Subscription test as the base on which to add unsupported
+              element values to test for server rejection.
+            )
+      input :unsupported_subscription_channel_type,
+            title: 'Unsupported Subscription Channel Type',
+            description: %(A value for the `channel.type` element that is not implemented by the server to test for
+                           Subscription rejection.),
+            optional: true
+
+      run do
+        skip_if(unsupported_subscription_channel_type.blank?, %(
+          Provide a value in the "Unsupported Subscription Channel Type" input to run this test.))
+
+        assert_valid_json(subscription_resource)
+        subscription = JSON.parse(subscription_resource)
+
+        unsupported_info = {
+          'unsupported_title' => 'unsupported channel type',
+          'field_path' => ['channel', 'type'],
+          'field_value' => unsupported_subscription_channel_type
+        }
+
+        field_name = unsupported_info['field_path'].last
+        outer_field_name = unsupported_info['field_path'].first
+        subscription_field = subscription[outer_field_name]
+        subscription_field[field_name] = unsupported_info['field_value']
+
+        subscription_field[field_name] = unsupported_info['field_value']
+
+        send_unsupported_subscription(subscription, unsupported_info['unsupported_title'],
+                                      [unsupported_info['field_path']], [unsupported_info['field_value']])
+
+        no_error_verification('Unsupported Subscription creation error handling failures.')
+      end
+    end
+  end
+end

data/lib/subscriptions_test_kit/suites/subscriptions_r5_backport_r4_server/subscription_rejection/reject_subscription_cross_version_extension_test.rb

@@ -0,0 +1,59 @@
+require_relative '../common/subscription_creation'
+
+module SubscriptionsTestKit
+  module SubscriptionsR5BackportR4Server
+    class RejectSubscriptionCrossVersionExtensionTest < Inferno::Test
+      include SubscriptionCreation
+
+      id :subscriptions_r4_server_reject_subscription_cross_version_extension
+      title 'Server Handles Unsupported Cross-Version Extensions'
+      description %(
+        When processing a request for a Subscription a server SHOULD verify that the Subscription is supported and does
+        not contain any information not implemented by the server. If the Subscription is not supported, the server
+        should reject the Subscription create request, or it should attempt to adjust the Subscription. Since the FHIR
+        R5 is currently under development, there are no guarantees these extensions will meet the requirements of
+        this guide. In order to promote widespread compatibility, cross version extensions SHOULD NOT be used
+        on R4 subscriptions to describe any elements.
+
+        The test will pass if the server rejects the Subscription by responding with a non-201 response.
+      )
+
+      input :subscription_resource,
+            title: 'Workflow Subscription Resource',
+            type: 'textarea',
+            description: %(
+              A Subscription resource in JSON format that Inferno will send to the server under test
+              so that it can demonstrate its ability to perform the Subscription creation and Notification
+              response workflow. The instance must be conformant to the R4/B Topic-Based Subscription profile.
+              Inferno may modify the Subscription before submission, e.g., to point to Inferno's notification endpoint.
+              This input is also used by the unsupported Subscription test as the base on which to add unsupported
+              element values to test for server rejection.
+            )
+
+      run do
+        assert_valid_json(subscription_resource)
+        subscription = JSON.parse(subscription_resource)
+
+        unsupported_info = {
+          'unsupported_title' => 'cross-version extensions',
+          'field_path' => ['_criteria'],
+          'field_value' => { 'extension' => [{
+            url: 'http://hl7.org/fhir/5.0/subscriptions-backport/StructureDefinition/backport-filter-criteria',
+            valueString: 'Encounter.patient=Patient/123'
+          }] }
+        }
+
+        field_name = unsupported_info['field_path'].last
+        subscription[field_name] = unsupported_info['field_value']
+
+        fhir_operation('/Subscription', body: subscription)
+        if request.status == 201
+          add_message('error', %(
+            Sending a Subscription with #{unsupported_info['unsupported_title']} should be rejected.))
+        end
+
+        no_error_verification('Unsupported Subscription creation error handling failures.')
+      end
+    end
+  end
+end