davinci_pas_test_kit 0.15.2 → 0.16.0

data/lib/davinci_pas_test_kit/client/v2.0.1/pas_client_must_support_group.rb

@@ -7,6 +7,7 @@ require_relative 'workflows/pas_client_request_bundle_validation_test'
 require_relative 'workflows/pas_client_response_bundle_validation_test'
 require_relative 'workflows/pas_client_inquire_request_bundle_validation_test'
 require_relative 'workflows/pas_client_inquire_response_bundle_validation_test'
+require_relative '../client_input_descriptions'
 
 module DaVinciPASTestKit
   module DaVinciPASV201
@@ -14,54 +15,55 @@ module DaVinciPASTestKit
       id :pas_client_v201_must_support
       title 'Must Support Elements'
       run_as_group
-      description %(
-        During these tests, the client will show that it supports all PAS-defined profiles and the must support
-        elements defined in them. This includes
+      description DaVinciPASTestKit.must_support_group_description('v2.0.1', 'da-vinci-pas-v201')
 
-        - The ability to make prior authorization submission and inquiry requests that contain all
-          PAS-defined profiles and their must support elements.
-        - The ability to receive in responses to those requests all PAS-defined profiles and their
-          must support elements.
+      # The must support response inputs already belong to pas_client_v201_gather_must_support
+      # (the wait test below); declaring them here too, before the receive group is defined,
+      # propagates them onto the bundle validation tests in that group as well, so they can tell
+      # whether a tester-provided response was used - see
+      # PasClientResponseBundleValidationTest/PasClientInquireResponseBundleValidationTest
+      # #failed_entities_description.
+      input :ms_submit_responses, optional: true
+      input :ms_inquire_responses, optional: true
 
-        Clients under test will be asked to make additional requests to Inferno demonstrating coverage
-        of all must support items in the requests. Clients must also demonstrate that they can handle
-        all response must support elements. Because Inferno's mocked responses do not include all must
-        support elements, testers will need to provide responses that include examples of all must
-        support elements for Inferno to respond with.
-
-        Note that Inferno will consider requests made during the workflow group of tests, so only
-        profiles and must support elements not demonstrated during those tests need to be submitted
-        as a part of these.
-      )
+      input_order :ms_submit_responses,
+                  :ms_inquire_responses,
+                  :client_id,
+                  :session_url_path
 
       # Combined receive group - single wait test for both submit and inquire
       group do
         id :pas_client_v201_must_support_receive
-        title 'Demonstrate Must Support Coverage'
-        description %(
-          Submit $submit and $inquire requests demonstrating coverage of must support elements.
-          Optionally, provide response bundles for Inferno to use when responding. Inferno will
-          verify both the requests received and the responses provided.
-        )
+        title MUST_SUPPORT_RECEIVE_GROUP_TITLE
+        description MUST_SUPPORT_RECEIVE_GROUP_DESCRIPTION
         run_as_group
 
         test from: :pas_client_v201_gather_must_support
-      end
-
-      # $submit Bundle Conformance Validation
-      group do
-        title '$submit Bundle Conformance'
-        description %(
-          Verify that the $submit request bundles sent by the client are conformant
-          and that the $submit response bundles provided for Inferno to send back
-          are conformant.
-        )
-        run_as_group
+        test from: :pas_client_v201_response_attest,
+             id: :pas_client_v201_response_attest_ms_submit_inquire,
+             title: MUST_SUPPORT_SUBMIT_INQUIRE_ATTEST_TITLE,
+             description: MUST_SUPPORT_SUBMIT_INQUIRE_ATTEST_DESCRIPTION,
+             config: { options: {
+               workflow_tag: MUST_SUPPORT_WORKFLOW_TAG,
+               no_requests_ok: true,
+               multiple_requests_ok: true,
+               attest_message: MUST_SUPPORT_SUBMIT_INQUIRE_ATTEST_MESSAGE
+             } } do
+          verifies_requirements 'hl7.fhir.us.davinci-pas_2.0.1@41'
+        end
 
         test from: :pas_client_v201_request_bundle_validation_test,
-             config: { options: { workflow_tag: MUST_SUPPORT_WORKFLOW_TAG } }
+             config: { options: { workflow_tag: MUST_SUPPORT_WORKFLOW_TAG, no_requests_ok: true,
+                                  multiple_requests_ok: true } }
         test from: :pas_client_v201_response_bundle_validation_test,
-             config: { options: { workflow_tag: MUST_SUPPORT_WORKFLOW_TAG } }
+             config: { options: { workflow_tag: MUST_SUPPORT_WORKFLOW_TAG, no_requests_ok: true,
+                                  multiple_requests_ok: true } }
+        test from: :pas_client_v201_inquire_request_bundle_validation_test,
+             config: { options: { workflow_tag: MUST_SUPPORT_WORKFLOW_TAG, no_requests_ok: true,
+                                  multiple_requests_ok: true } }
+        test from: :pas_client_v201_inquire_response_bundle_validation_test,
+             config: { options: { workflow_tag: MUST_SUPPORT_WORKFLOW_TAG, no_requests_ok: true,
+                                  multiple_requests_ok: true } }
       end
 
       # $submit Request Must Support (fail when errors detected)
@@ -70,22 +72,6 @@ module DaVinciPASTestKit
       # $submit Response Must Support (skip when errors detected)
       group from: :pas_client_v201_submit_response_must_support
 
-      # $inquire Bundle Conformance Validation
-      group do
-        title '$inquire Bundle Conformance'
-        description %(
-          Verify that the $inquire request bundles sent by the client are conformant
-          and that the $inquire response bundles provided for Inferno to send back
-          are conformant.
-        )
-        run_as_group
-
-        test from: :pas_client_v201_inquire_request_bundle_validation_test,
-             config: { options: { workflow_tag: MUST_SUPPORT_WORKFLOW_TAG } }
-        test from: :pas_client_v201_inquire_response_bundle_validation_test,
-             config: { options: { workflow_tag: MUST_SUPPORT_WORKFLOW_TAG } }
-      end
-
       # $inquire Request Must Support (fail when errors detected)
       group from: :pas_client_v201_inquire_must_support
 

data/lib/davinci_pas_test_kit/client/v2.0.1/pas_client_pended_group.rb

@@ -13,10 +13,10 @@ module DaVinciPASTestKit
       include UserInputResponse
 
       id :pas_client_v201_pended_group
-      title 'Pended Workflow'
+      title 'Pended Response'
       description %(
-        During these tests, the client will initiate a prior authorization
-        request and show it can respond appropriately to a 'pended' decision, including
+        During these tests, the PAS client will initiate a prior authorization
+        request and show it can react appropriately to a 'pended' decision, including
         waiting for a notification that an update has been made
         and making an inquiry request to retrieve the final result.
       )
@@ -31,15 +31,15 @@ module DaVinciPASTestKit
                   :session_url_path
 
       group do
-        title 'Perform the pended workflow'
+        title 'Perform the pended scenario'
         description %(
-          All interactions for the pended prior authorization request workflow
-          between Inferno and the client under test will be performed during this test
+          All interactions for the pended prior authorization request scenario
+          between Inferno and the PAS client will be performed during this group
           including
-          - A `$submit` request from the client to Inferno where Inferno returns a pended response.
+          - A `$submit` request from the PAS client to Inferno where Inferno returns a pended response.
           - A notification that the prior authorization decision has been finalized from Inferno
-            to the client under test.
-          - An `$inquire` request from the client to Inferno where Inferno returns an approved response.
+            to the PAS client.
+          - An `$inquire` request from the PAS client to Inferno where Inferno returns an approved response.
         )
 
         test from: :pas_client_v201_pended_submit_test
@@ -53,17 +53,19 @@ module DaVinciPASTestKit
         test from: :pas_client_v201_response_bundle_validation_test,
              config: { options: { workflow_tag: PENDED_WORKFLOW_TAG } }
         test from: :pas_client_v201_response_attest,
-             title: 'Check that the client registers the request as pended (Attestation)',
+             title: 'Check that the PAS client registers the request as pended',
              description: %(
-              This test provides the tester an opportunity to observe their client following
+              During this test, the tester will observe the PAS client following
               the receipt of the pended response and attest that users are able to determine
               that the response has been pended and a decision will be forthcoming.
              ),
              config: { options: {
                workflow_tag: PENDED_WORKFLOW_TAG,
-               attest_message: "I attest that following the receipt of the 'pended' response to the submitted " \
-                               'claim, the client system indicates to users that a final decision on request ' \
-                               'has not yet been made.'
+               operation_tag: SUBMIT_TAG,
+               multiple_requests_ok: true,
+               attest_message: "I attest that the PAS client did not error when handling the 'pended' " \
+                               'response to the submitted claim and that it indicated to users that a final decision ' \
+                               'on the request had not yet been made.'
              } }
       end
 
@@ -73,7 +75,7 @@ module DaVinciPASTestKit
         test from: :subscriptions_r4_client_notification_input_verification,
              title: 'Tester-provided event notification Bundle is conformant',
              description: %(
-               This test checks that the notification Bundle sent to the client, which will be either
+               This test checks that the notification Bundle sent to the PAS client, which will be either
                the tester-provided notification Bundle in the **Claim updated notification JSON** input
                or mocked by Inferno based on details in the Subscription and submitted Claim, is conformant
                to Subscription Backport IG requirements.
@@ -87,10 +89,10 @@ module DaVinciPASTestKit
         test from: :subscriptions_r4_client_notification_input_payload_verification,
              title: 'Tester-provided event notification Bundle matches the Subscription',
              description: %(
-               This test checks that the notification Bundle sent to the client, which will be either
+               This test checks that the notification Bundle sent to the PAS client, which will be either
                the tester-provided notification Bundle in the **Claim updated notification JSON** input
                or mocked by Inferno based on details in the Subscription and submitted Claim, matches the details
-               requested in the Subscription provided during the **2.1** "PAS Subscription Setup" tests.
+               requested in the Subscription provided during the "Subscription Setup" tests.
              ),
              simulation_verification: true,
              config: {
@@ -102,9 +104,9 @@ module DaVinciPASTestKit
         # and testers have to demonstrate and attest that their systems work, which will require some
         # correspondence.
         test from: :subscriptions_r4_client_event_notification_verification,
-             title: 'Client accepts the "claim updated" event notification',
+             title: 'PAS client accepts the "claim updated" event notification',
              description: %(
-               This test checks that the client responds appropriately to the event notification request.
+               This test checks that the PAS client responds appropriately to the event notification request.
              )
       end
 
@@ -116,15 +118,19 @@ module DaVinciPASTestKit
         test from: :pas_client_v201_inquire_response_bundle_validation_test,
              config: { options: { workflow_tag: PENDED_WORKFLOW_TAG } }
         test from: :pas_client_v201_response_attest,
-             title: 'Check that the client registers the request as approved (Attestation)',
+             title: 'Check that the PAS client registers the request as approved',
              description: %(
-              This test provides the tester an opportunity to observe their client following
+              During this test, the tester will observe the PAS client following
               the receipt of the inquiry response with a final decision and attest that users
               are able to determine that the response has been approved in full.
              ),
              config: { options: {
                workflow_tag: PENDED_WORKFLOW_TAG,
-               attest_message: "I attest that the client system displays the submitted claim as 'approved' meaning that the user can proceed with ordering or providing the requested service." # rubocop:disable Layout/LineLength
+               operation_tag: INQUIRE_TAG,
+               multiple_requests_ok: true,
+               attest_message: 'I attest that the PAS client did not error when handling the `$inquire` ' \
+                               "response and displays the submitted claim as 'approved' meaning that the " \
+                               'user can proceed with ordering or providing the requested service.'
              } }
       end
     end

data/lib/davinci_pas_test_kit/client/v2.0.1/pas_client_registration_group.rb

@@ -12,8 +12,8 @@ module DaVinciPASTestKit
       id :pas_client_v201_registration
       title 'Client Registration'
       description %(
-        Register the client under test with Inferno's simulated PAS Server,
-        including configuration of the system under test to make requests against
+        Register the PAS client with Inferno's simulated PAS Server,
+        including configuration necessary to make requests against
         Inferno's simulated PAS endpoints and enable authentication and authorization of PAS requests.
       )
       run_as_group

data/lib/davinci_pas_test_kit/client/v2.0.1/pas_client_subscription_setup_group.rb

@@ -8,8 +8,8 @@ module DaVinciPASTestKit
       id :pas_client_v201_subscription_setup
       title 'Subscription Setup'
       description %(
-        These tests verify that the client can create a Subscription instance
-        that will tell the Payer how to notify the client when pended claims
+        These tests verify that the PAS client can create a Subscription instance
+        that will tell the Payer how to notify the PAS client when pended claims
         are updated.
       )
       run_as_group

data/lib/davinci_pas_test_kit/client/v2.0.1/pas_client_workflows_group.rb

@@ -6,9 +6,9 @@ module DaVinciPASTestKit
   module DaVinciPASV201
     class PASClientWorkflowsGroup < Inferno::TestGroup
       id :pas_client_v201_workflows
-      title 'PAS Workflows'
+      title 'PAS Scenarios'
       description %(
-        The workflow tests verify that the client can participate in complete end-to-end prior
+        The scenario tests verify that the PAS client can participate in complete end-to-end prior
         authorization interactions, initiating requests and reacting appropriately to the
         responses returned.
       )

data/lib/davinci_pas_test_kit/client/v2.0.1/workflows/pas_client_inquire_request_bundle_validation_test.rb

@@ -1,14 +1,16 @@
 require_relative '../../../cross_suite/pas_bundle_validation'
+require_relative '../../client_bundle_validation_helper'
 
 module DaVinciPASTestKit
   module DaVinciPASV201
     class PasClientInquireRequestBundleValidationTest < Inferno::Test
       include DaVinciPASTestKit::PasBundleValidation
+      include DaVinciPASTestKit::ClientBundleValidationHelper
 
       id :pas_client_v201_inquire_request_bundle_validation_test
-      title 'Inquire Request Bundle is valid'
+      title '$inquire request Bundles have the correct structure and content'
       description %(
-        This test verifies the conformity of the client's request body to the
+        This test verifies the conformity of each of the PAS client's `$inquire` request bodies to the
         [PAS Inquiry Request Bundle](http://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-pas-inquiry-request-bundle.html)
         structure. It also checks that other conformance requirements defined in the [PAS Formal
         Specification](https://hl7.org/fhir/us/davinci-pas/STU2/specification.html),
@@ -37,30 +39,22 @@ module DaVinciPASTestKit
                             'hl7.fhir.us.davinci-pas_2.0.1@125', 'hl7.fhir.us.davinci-pas_2.0.1@126',
                             'hl7.fhir.us.davinci-pas_2.0.1@127', 'hl7.fhir.us.davinci-pas_2.0.1@128'
 
-      def request_type_tag
-        INQUIRE_TAG
+      def operation_name
+        'inquire'
       end
 
-      def workflow_tag
-        config.options[:workflow_tag]
+      def message_direction_name
+        'request'
       end
 
-      run do
-        if workflow_tag.present?
-          load_tagged_requests(request_type_tag, workflow_tag)
-        else
-          load_tagged_requests(request_type_tag)
-        end
-        skip_if !request.present?, 'No inquire requests received.'
+      def ig_version
+        '2.0.1'
+      end
 
-        validate_pas_bundle_json(
-          request.request_body,
-          'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/profile-pas-inquiry-request-bundle',
-          '2.0.1',
-          'inquire',
-          'request_bundle',
-          message: 'The Bundle provided for the Claim/$inquire operation is invalid:'
-        )
+      run do
+        failed = non_conformant_bundles
+        assert failed.empty?,
+               "Non-conformant request Bundles detected: #{failed.join(', ')}. Check messages for issues found."
       end
     end
   end

data/lib/davinci_pas_test_kit/client/v2.0.1/workflows/pas_client_inquire_response_bundle_validation_test.rb

@@ -1,21 +1,21 @@
 require_relative '../../../cross_suite/pas_bundle_validation'
 require_relative '../../user_input_response'
-require_relative '../../response_generator'
+require_relative '../../client_bundle_validation_helper'
 
 module DaVinciPASTestKit
   module DaVinciPASV201
     class PasClientInquireResponseBundleValidationTest < Inferno::Test
       include DaVinciPASTestKit::PasBundleValidation
       include UserInputResponse
-      include ResponseGenerator
+      include DaVinciPASTestKit::ClientBundleValidationHelper
 
       id :pas_client_v201_inquire_response_bundle_validation_test
-      title 'Inquire Response Bundle is valid'
+      title '$inquire response Bundles have the correct structure and content'
       description %(
-        **USER INPUT VERIFICATION**: This test verifies input provided by the tester instead of the system under test.
+        This test verifies input provided by the tester instead of the PAS client.
         Errors encountered will be treated as a skip instead of a failure.
 
-        This test verifies the conformity of the inquire response sent by Inferno, which will have been
+        This test verifies the conformity of each `$inquire` response sent by Inferno, which will have been
         either:
         - the response body provided by the tester in the corresponding input, or
         - created by Inferno from the $inquire Bundle.
@@ -33,8 +33,11 @@ module DaVinciPASTestKit
         to the bound ValueSet. Quantity, Coding, and code element bindings will
         fail if their code/system are not found in the valueset.
 
-        Note that because X12 value sets are not public, elements bound to value
-        sets containing X12 codes are not validated.
+        Note that:
+        - To ensure that the PAS client is driving its behavior only based on standard
+          PAS information, custom extensions are not allowed within the responses.
+        - Because X12 value sets are not public, elements bound to value
+          sets containing X12 codes are not validated.
 
         **Limitations**
 
@@ -46,12 +49,16 @@ module DaVinciPASTestKit
       )
       simulation_verification
 
-      def request_type
+      def operation_name
         'inquire'
       end
 
-      def workflow_tag
-        config.options[:workflow_tag]
+      def message_direction_name
+        'response'
+      end
+
+      def ig_version
+        '2.0.1'
       end
 
       def target_user_input
@@ -63,26 +70,19 @@ module DaVinciPASTestKit
         end
       end
 
-      run do
-        load_tagged_requests(workflow_tag, INQUIRE_TAG)
-        skip_if requests.empty?, 'No responses to verify because no inquire requests were made.'
-        message = if workflow_tag == MUST_SUPPORT_WORKFLOW_TAG
-                    'Invalid must support response bundle provided:'
-                  elsif user_inputted_response? target_user_input
-                    "Invalid response generated from provided input '#{input_title(target_user_input)}':"
-                  else
-                    'Invalid response generated from the submitted claim:'
-                  end
+      def failed_entities_description
+        if user_inputted_response? target_user_input
+          "built from tester-provided response in '#{input_title(target_user_input)}'"
+        else
+          'generated from the submitted claim'
+        end
+      end
 
-        validate_pas_bundle_json(
-          request.response_body,
-          'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/profile-pas-inquiry-response-bundle',
-          '2.0.1',
-          request_type,
-          'response_bundle',
-          skips: true,
-          message:
-        )
+      run do
+        failed = non_conformant_bundles
+        skip_if failed.present?,
+                "Non-conformant response Bundles #{failed_entities_description}: #{failed.join(', ')}. " \
+                'Check messages for issues found.'
       end
     end
   end

data/lib/davinci_pas_test_kit/client/v2.0.1/workflows/pas_client_pended_submit_test.rb

@@ -3,6 +3,7 @@ require_relative '../../client_input_descriptions'
 require_relative '../../user_input_response'
 require_relative '../../../cross_suite/pas_bundle_validation'
 require_relative '../../session_identification'
+require_relative '../../subscription_setup_requirement'
 
 module DaVinciPASTestKit
   module DaVinciPASV201
@@ -11,15 +12,16 @@ module DaVinciPASTestKit
       include SessionIdentification
       include UserInputResponse
       include PasBundleValidation
+      include SubscriptionSetupRequirement
 
       id :pas_client_v201_pended_submit_test
-      title 'Client submits a claim and reacts to a pended response'
+      title 'PAS client submits a claim and reacts to a pended response'
       description %(
-        Inferno will wait for a prior authorization submission request
-        from the client. Upon receipt, Inferno will respond with the
+        During this test, Inferno will wait for a prior authorization submission request
+        from the PAS client. Upon receipt, Inferno will respond with the
         provided pended response. Subsequently, Inferno will send a
         notification that the claim has been finalized and expect the
-        client under test to send a follow-up inquiry.
+        PAS client to send a follow-up inquiry.
       )
       verifies_requirements 'hl7.fhir.us.davinci-pas_2.0.1@58', 'hl7.fhir.us.davinci-pas_2.0.1@62',
                             'hl7.fhir.us.davinci-pas_2.0.1@67', 'hl7.fhir.us.davinci-pas_2.0.1@70',
@@ -27,14 +29,14 @@ module DaVinciPASTestKit
                             'hl7.fhir.us.davinci-pas_2.0.1@153', 'hl7.fhir.us.davinci-pas_2.0.1@202',
                             'hl7.fhir.us.davinci-pas_2.0.1@203'
 
-      config options: { accepts_multiple_requests: true }
+      config options: { accepts_multiple_requests: true, submit_enabled: true, inquire_enabled: true }
       input :notification_bundle,
             title: 'Claim updated notification JSON',
             type: 'textarea',
             optional: true,
             description: %(
               If provided, this JSON will be sent as the notification for the
-              PAS Subscription to tell the client that a decision has been made on the pended claim.
+              PAS Subscription to tell the PAS client that a decision has been made on the pended claim.
               Before sending, Inferno will update the provided notification with details that the tester cannot
               know ahead of time, including timestamps corresponding to the notification trigger time, and the id of
               the triggering ClaimResponse if Inferno mocks that ClaimResponse because it is not provided by the
@@ -69,8 +71,8 @@ module DaVinciPASTestKit
             optional: true,
             title: 'Client Notification Access Token',
             description: %(
-              The bearer token that Inferno will send on requests to the client under test's rest-hook notification
-              endpoint. Not needed if the client under test will create a Subscription with an appropriate header value
+              The bearer token that Inferno will send on requests to the PAS client's rest-hook notification
+              endpoint. Not needed if the PAS client will create a Subscription with an appropriate header value
               in the `channel.header` element. If a value for the `authorization` header is provided in
               `channel.header`, this value will override it.
             )
@@ -92,13 +94,7 @@ module DaVinciPASTestKit
       inquire_respond_with :inquire_json_response
 
       run do
-        load_tagged_requests(SUBSCRIPTION_CREATE_TAG)
-        skip_if requests.empty?, # NOTE: subscription needed ahead of time to support notification generation
-                %(
-                  Pended workflow tests cannot proceed because no Subscription exists to receive notifications
-                  for pended claims. Run the _PAS Subscription Setup_ tests to provide a Subscription for use
-                  in delivering notifications before re-running the pended workflow tests.
-                )
+        require_unmodified_subscription
 
         if user_inputted_response? :pended_json_response
           assert_valid_json pended_json_response,
@@ -141,42 +137,55 @@ module DaVinciPASTestKit
         wait(
           identifier: wait_identifier,
           timeout: 600,
-          message: %(
-            **Pended Workflow Test**:
+          message: <<~MESSAGE
+            **Pended Scenario Test**:
 
-            1. Submit a PAS request to
+            Inferno will wait while the tester uses the PAS client to complete the following steps:
 
-            `#{submit_endpoint}`
+            1. Submit a PAS request to Inferno's `$submit` endpoint. Inferno will return a pended response.
+            2. Within 5-10 seconds, Inferno will send a notification indicating that the ClaimResponse has
+               been finalized to the endpoint provided on the Subscription during the _Subscription Setup_ tests.
+            3. Once the notification has been received, submit a PAS inquiry request to Inferno's `$inquire`
+               endpoint. Inferno will return an approval response.
 
-            If the optional '**#{input_title(:pended_json_response)}**' input is populated, it will
-            be returned, updated with current timestamps. Otherwise, a pended response will
-            be generated by Inferno using the received Claim.
+            Inferno will later ask testers to attest that the PAS client marked the request as pended after
+            step 1 (submit) and before step 2 (notification), so testers should check their PAS client's state
+            between these steps in order to faithfully answer the attestation.
 
-            2. Within 5-10 seconds, Inferno will send a notification indicating that the ClaimResponse has been
-               finalized. If the optional '**#{input_title(:notification_bundle)}**' input is populated
-                Inferno will send it as a notification. Otherwise, a notification will be generated
-                from Inferno. In either case, the notification will be delivered to the endpoint provided on the
-                Subscription during the _PAS Subscription Setup_ tests.
+            [Click here](#{confirmation_url}) once the PAS client has completed these steps.
 
-            3. Once the notification has been received, submit a PAS inquiry request to
+            ### Endpoints
 
-            `#{inquire_endpoint}`
+            - $submit: `#{submit_endpoint}`
+            - $inquire: `#{inquire_endpoint}`
 
-            If the optional '**#{input_title(:inquire_json_response)}**' input is populated, it will
-            be returned, updated with current timestamps. Otherwise, an approval response will
-            be generated by Inferno using the received Claim.
+            ### Authentication and Identification
 
-            Note that Inferno will ask testers to attest to correct behavior of the system between these steps,
-            i.e., that the system marked the pended prior auth request appropriately after step 1 (submit) but
-            before step 2 (notification). Thus testers should check their system state as appropriate in order
-            to be able to faithfully answer the attestations.
+            #{auth_description_for_wait(client_id)}
 
-            Once the client has completed these steps,
-            [click here to complete the test](#{confirmation_url})
-            and continue Inferno's evaluation of the interaction.
-          )
+            ### Responses
+
+            #{response_description_for_wait(user_inputted_response?(:pended_json_response),
+                                            input_title(:pended_json_response),
+                                            '$submit')}
+
+            #{response_description_for_wait(user_inputted_response?(:inquire_json_response),
+                                            input_title(:inquire_json_response),
+                                            '$inquire')}
+
+            #{notification_description_for_wait}
+          MESSAGE
         )
       end
+
+      def notification_description_for_wait
+        if notification_bundle.present?
+          "Inferno will send the content of the '**#{input_title(:notification_bundle)}**' input as the " \
+            'notification, updated with current timestamps.'
+        else
+          'Inferno will send a notification generated from the pended response.'
+        end
+      end
     end
   end
 end