davinci_dtr_test_kit 0.9.0 → 0.11.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e84658427289327e910d38a2e24e50bfe15b0c7ae8096d358df3c45d30f6f6b5
-  data.tar.gz: 6ecc074de82b8e0533edcfd99cb9e42a82e74b5a3fe7779e19ba6403782f4cae
+  metadata.gz: e95ac1a81ec266133aa196823f9c4af450b6ff0c628b2ca9dccbb0fcd3b32863
+  data.tar.gz: d4ac1d46eadaa7f1067d07b4811e00803308f8d1c91cf9165f6e17534a280449
 SHA512:
-  metadata.gz: f97f96957563a2705899b6c3356ff127c8c5a55423730c26c69792ab441456acb3817245126008e764d867c6fea4a789a7bc9cb295c2d728910f98cd37798117
-  data.tar.gz: 399594d80b1d9e118abdae646fb308d221240debf4495f185f36f82e09c35d8326016d9039f68da0d1fef7c76e88bbe7c879f789127157b7ac405e29463b9191
+  metadata.gz: 22b65864b0795e2355b17d19b78d262524b29a9c0b1352603cd226a8d5c135a5bb0566c6c8449ce4ea0516ebedbee1e7a94965d7448e98a927b07716bd65c049
+  data.tar.gz: 0daaae716b201d20f99c768e5a7bc9d6ae997f953ab2d238862298ab00a39d82746b5e1a71537f13eeb09ea260c097955a22487405128aa5cbe9339cc1860fce

data/lib/davinci_dtr_test_kit/client_groups/dinner_static/dtr_dinner_questionnaire_package_request_test.rb

@@ -0,0 +1,97 @@
+require 'base64'
+require_relative '../../urls'
+
+module DaVinciDTRTestKit
+  class DTRDinnerQuestionnairePackageRequestTest < Inferno::Test
+    include URLs
+
+    id :dtr_dinner_questionnaire_package_request
+    title 'Invoke the DTR Questionnaire Package operation'
+    description %(
+      Inferno will wait for a DTR questionnaire package request from the client. Upon receipt, Inferno will generate and
+      send a response.
+    )
+    input :smart_app_launch, type: 'radio', title: 'SMART App Launch',
+                             description: 'How will the DTR SMART App launch?',
+                             options: { list_options: [{ label: 'Launch from Inferno', value: 'inferno' },
+                                                       { label: 'Launch from EHR', value: 'ehr' }] }
+    input :client_id
+    input :launch_uri, optional: true, description: 'Required if "Launch from Inferno" is selected'
+    input :smart_patient_id, optional: true, title: 'SMART App Launch Patient ID (Dinner Static)',
+                             type: 'text',
+                             description: %(
+                               Patient instance id to be provided by Inferno as the `patient` as a part of the SMART app
+                               launch.
+                             )
+    input :smart_fhir_context, optional: true, title: 'SMART App Launch fhirContext (Dinner Static)',
+                               type: 'textarea',
+                               description: %(
+                               References to be provided by Inferno as the `fhirContext` as a part of the SMART app
+                               launch. These references help determine the behavior of the app. Referenced instances
+                               may be providedin the "EHR-available resources" input.
+                             )
+    input :ehr_bundle, optional: true, title: 'EHR-available resources (Dinner Static)', type: 'textarea',
+                       description: %(
+                         Resources available from the EHR needed to drive the dinner static workflow.
+                         Formatted as a FHIR bundle that contains resources, each with an `id` property populated. Each
+                         instance present will be available for retrieval from Inferno at the endpoint
+                         `[fhir-base]/[resource type]/[instance id].`
+                       )
+
+    def example_client_jwt_payload_part
+      Base64.strict_encode64({ inferno_client_id: client_id }.to_json).delete('=')
+    end
+
+    run do
+      launch_prompt = if smart_app_launch == 'inferno'
+                        %(Launch the DTR SMART App from Inferno by right clicking
+                          [this link](#{launch_uri}?iss=#{fhir_base_url}&launch=#{launch_uri})
+                          and selecting or "Open in new window" or "Open in new tab".)
+                      else
+                        %(Launch the SMART App from your EHR.)
+                      end
+      inferno_prompt_cont = %(As the DTR app steps through the launch steps, Inferno will wait and respond to the app's
+                              requests for SMART configuration, authorization and access token.)
+
+      wait(
+        identifier: client_id,
+        message: %(
+          ### SMART App Launch
+
+          #{launch_prompt}
+
+          #{inferno_prompt_cont if smart_app_launch == 'inferno'}
+
+          Then, Inferno will expect the SMART App to invoke the DTR Questionnaire Package operation by sending a POST
+          request to
+
+          `#{questionnaire_package_url}`
+
+          A questionnaire package generated by Inferno will be returned.
+
+          ### Pre-population
+
+          Inferno will then wait for the client to complete Questionnaire pre-population. The client should make FHIR
+          GET requests using service base path:
+
+          `#{fhir_base_url}`
+
+          ### Request Identification
+
+          In order to identify requests for this session, Inferno will look for
+          an `Authorization` header with value:
+
+          ```
+          Bearer eyJhbGcmOiJub25lIn0.#{example_client_jwt_payload_part}.
+          ```
+
+          ### Continuing the Tests
+
+          When the DTR application has finished loading the Questionnaire,
+          including any clinical data requests to support pre-population,
+          [Click here](#{resume_pass_url}?client_id=#{client_id}) to continue.
+        )
+      )
+    end
+  end
+end

data/lib/davinci_dtr_test_kit/client_groups/dinner_static/dtr_questionnaire_response_save_test.rb

@@ -9,11 +9,11 @@ module DaVinciDTRTestKit
     description %(
       Inferno, acting as the EHR, will wait for a request to save the QuestionnaireResponse from the client.
     )
-    input :access_token
+    input :client_id
 
     run do
       wait(
-        identifier: access_token,
+        identifier: client_id,
         message: %(
           Complete the questionnaire, leaving the following items unmodified, because a subsequent test will expect
           their pre-populated values:

data/lib/davinci_dtr_test_kit/client_groups/dinner_static/dtr_smart_app_questionnaire_workflow_group.rb

@@ -1,4 +1,4 @@
-require_relative '../shared/dtr_questionnaire_package_request_test'
+require_relative 'dtr_dinner_questionnaire_package_request_test'
 require_relative '../shared/dtr_questionnaire_package_request_validation_test'
 require_relative 'prepopulation_attestation_test'
 require_relative 'prepopulation_override_attestation_test'
@@ -17,6 +17,7 @@ module DaVinciDTRTestKit
       demonstrate their ability to:
 
       1. Fetch the static questionnaire package
+         ([DinnerOrderStatic](https://github.com/inferno-framework/davinci-dtr-test-kit/blob/main/lib/davinci_dtr_test_kit/fixtures/dinner_static/questionnaire_dinner_order_static.json))
       2. Render and pre-populate the questionnaire appropriately, including:
          - fetch additional data needed for pre-population
          - pre-populate data as directed by the questionnaire
@@ -36,7 +37,7 @@ module DaVinciDTRTestKit
       run_as_group
 
       # Test 1: wait for the $questionnaire-package request
-      test from: :dtr_questionnaire_package_request
+      test from: :dtr_dinner_questionnaire_package_request
       # Test 2: validate the $questionnaire-package body
       test from: :dtr_questionnaire_package_request_validation
     end

data/lib/davinci_dtr_test_kit/client_groups/dinner_static/prepopulation_attestation_test.rb

@@ -9,19 +9,19 @@ module DaVinciDTRTestKit
     description %(
       Validate that pre-population of patient name information occurs as expected.
     )
-    input :access_token
+    input :client_id
 
     run do
       wait(
-        identifier: access_token,
+        identifier: client_id,
         message: %(
           I attest that the client application pre-populates the following questions with the respective values:
           - Last Name: Oster
           - First Name: William
 
-          [Click here](#{resume_pass_url}?token=#{access_token}) if the above statement is **true**.
+          [Click here](#{resume_pass_url}?client_id=#{client_id}) if the above statement is **true**.
 
-          [Click here](#{resume_fail_url}?token=#{access_token}) if the above statement is **false**.
+          [Click here](#{resume_fail_url}?client_id=#{client_id}) if the above statement is **false**.
         )
       )
     end

data/lib/davinci_dtr_test_kit/client_groups/dinner_static/prepopulation_override_attestation_test.rb

@@ -9,20 +9,20 @@ module DaVinciDTRTestKit
     description %(
       Validate that the user can edit a pre-populated item and replace it with another value.
     )
-    input :access_token
+    input :client_id
 
     run do
       wait(
-        identifier: access_token,
+        identifier: client_id,
         message: %(
           I attest that
 
           1. The client pre-populated an answer for question 'Location'.
           2. I have changed the answer to a different value.
 
-          [Click here](#{resume_pass_url}?token=#{access_token}) if the above statement is **true**.
+          [Click here](#{resume_pass_url}?client_id=#{client_id}) if the above statement is **true**.
 
-          [Click here](#{resume_fail_url}?token=#{access_token}) if the above statement is **false**.
+          [Click here](#{resume_fail_url}?client_id=#{client_id}) if the above statement is **false**.
         )
       )
     end

data/lib/davinci_dtr_test_kit/client_groups/dinner_static/rendering_enabled_questions_attestation_test.rb

@@ -10,19 +10,19 @@ module DaVinciDTRTestKit
       Validate that the rendering of the questionnaire includes only the "What would you like on..."
       question appropriate for the dinner selection, if made.
     )
-    input :access_token
+    input :client_id
 
     run do
       wait(
-        identifier: access_token,
+        identifier: client_id,
         message: %(
           I attest that the client application does not display any "What would you like on..."
           questions until I have selected a dinner choice and then only displays the
           "What would you like on..." question relevant for the dinner request:
 
-          [Click here](#{resume_pass_url}?token=#{access_token}) if the above statement is **true**.
+          [Click here](#{resume_pass_url}?client_id=#{client_id}) if the above statement is **true**.
 
-          [Click here](#{resume_fail_url}?token=#{access_token}) if the above statement is **false**.
+          [Click here](#{resume_fail_url}?client_id=#{client_id}) if the above statement is **false**.
         )
       )
     end

data/lib/davinci_dtr_test_kit/client_groups/resp_assist_device/dtr_questionnaire_package_group.rb

@@ -1,4 +1,4 @@
-require_relative '../shared/dtr_questionnaire_package_request_test'
+require_relative 'dtr_resp_questionnaire_package_request_test'
 require_relative '../shared/dtr_questionnaire_package_request_validation_test'
 
 module DaVinciDTRTestKit
@@ -10,7 +10,7 @@ module DaVinciDTRTestKit
     )
     run_as_group
 
-    test from: :dtr_questionnaire_package_request
+    test from: :dtr_resp_questionnaire_package_request
     test from: :dtr_questionnaire_package_request_validation
   end
 end

data/lib/davinci_dtr_test_kit/client_groups/resp_assist_device/dtr_questionnaire_rendering_attestation_test.rb

@@ -10,21 +10,21 @@ module DaVinciDTRTestKit
       Thist test provides the tester an opportunity to observe their client application following the receipt of the
       questionnaire pacakage and attest that the application renders the questionnaire.
     )
-    input :access_token
+    input :client_id
 
     run do
       load_tagged_requests QUESTIONNAIRE_PACKAGE_TAG
       skip_if request.blank?, 'A Questionnaire Package request must be made prior to running this test'
 
       wait(
-        identifier: access_token,
+        identifier: client_id,
         message: %(
           I attest that the client application displays the questionnaire and respects the following rendering style:
           - The "Signature" field label is rendered with green text
 
-          [Click here](#{resume_pass_url}?token=#{access_token}) if the above statement is **true**.
+          [Click here](#{resume_pass_url}?client_id=#{client_id}) if the above statement is **true**.
 
-          [Click here](#{resume_fail_url}?token=#{access_token}) if the above statement is **false**.
+          [Click here](#{resume_fail_url}?client_id=#{client_id}) if the above statement is **false**.
         )
       )
     end

data/lib/davinci_dtr_test_kit/client_groups/resp_assist_device/dtr_questionnaire_response_save_test.rb

@@ -9,11 +9,11 @@ module DaVinciDTRTestKit
     description %(
       Inferno, acting as the EHR, will wait for a request to save the QuestionnaireResponse from the client.
     )
-    input :access_token
+    input :client_id
 
     run do
       wait(
-        identifier: access_token,
+        identifier: client_id,
         message: %(
           Complete the questionnaire, leaving the following items unmodified, because a subsequent test will expect
           their pre-populated values:

data/lib/davinci_dtr_test_kit/client_groups/resp_assist_device/dtr_resp_questionnaire_package_request_test.rb

@@ -0,0 +1,95 @@
+require_relative '../../urls'
+
+module DaVinciDTRTestKit
+  class DTRRespQuestionnairePackageRequestTest < Inferno::Test
+    include URLs
+
+    id :dtr_resp_questionnaire_package_request
+    title 'Invoke the DTR Questionnaire Package operation'
+    description %(
+      Inferno will wait for a DTR questionnaire package request from the client. Upon receipt, Inferno will generate and
+      send a response.
+    )
+    input :smart_app_launch, type: 'radio', title: 'SMART App Launch',
+                             description: 'How will the DTR SMART App launch?',
+                             options: { list_options: [{ label: 'Launch from Inferno', value: 'inferno' },
+                                                       { label: 'Launch from EHR', value: 'ehr' }] }
+    input :client_id
+    input :launch_uri, optional: true, description: 'Required if "Launch from Inferno" is selected'
+    input :smart_patient_id, optional: true, title: 'SMART App Launch Patient ID (Respiratory Assist Device)',
+                             type: 'text',
+                             description: %(
+                               Patient instance id to be provided by Inferno as the `patient` as a part of the SMART app
+                               launch.
+                             )
+    input :smart_fhir_context, optional: true, title: 'SMART App Launch fhirContext (Respiratory Assist Device)',
+                               type: 'textarea',
+                               description: %(
+                                 References to be provided by Inferno as the `fhirContext` as a part of the SMART app
+                                 launch. These references help determine the behavior of the app. Referenced instances
+                                 may be providedin the "EHR-available resources" input.
+                               )
+    input :ehr_bundle, optional: true, title: 'EHR-available resources (Respiratory Assist Device)', type: 'textarea',
+                       description: %(
+                                 Resources available from the EHR needed to drive the respiratory assist device
+                                 workflow. Formatted as a FHIR bundle that contains resources, each with an `id`
+                                 property populated. Each instance present will be available for retrieval from
+                                 Inferno at the endpoint `[fhir-base]/[resource type]/[instance id].`
+                               )
+
+    def example_client_jwt_payload_part
+      Base64.strict_encode64({ inferno_client_id: client_id }.to_json).delete('=')
+    end
+
+    run do
+      launch_prompt = if smart_app_launch == 'inferno'
+                        %(Launch the DTR SMART App from Inferno by right clicking
+                          [this link](#{launch_uri}?iss=#{fhir_base_url}&launch=#{launch_uri})
+                          and selecting or "Open in new window" or "Open in new tab".)
+                      else
+                        %(Launch the SMART App from your EHR.)
+                      end
+      inferno_prompt_cont = %(As the DTR app steps through the launch steps, Inferno will wait and respond to the app's
+                              requests for SMART configuration, authorization and access token.)
+      wait(
+        identifier: client_id,
+        message: %(
+          ### SMART App Launch
+
+          #{launch_prompt}
+
+          #{inferno_prompt_cont if smart_app_launch == 'inferno'}
+
+          Then, Inferno will expect the SMART App to invoke the DTR Questionnaire Package operation by sending a POST
+          request to
+
+          `#{questionnaire_package_url}`
+
+          A questionnaire package generated by Inferno will be returned.
+
+          ### Pre-population
+
+          Inferno will then wait for the client to complete Questionnaire pre-population. The client should make FHIR
+          GET requests using service base path:
+
+          `#{fhir_base_url}`
+
+          ### Request Identification
+
+          In order to identify requests for this session, Inferno will look for
+          an `Authorization` header with value:
+
+          ```
+          Bearer eyJhbGcmOiJub25lIn0.#{example_client_jwt_payload_part}.
+          ```
+
+          ### Continuing the Tests
+
+          When the DTR application has finished loading the Questionnaire,
+          including any clinical data requests to support pre-population,
+          [Click here](#{resume_pass_url}?client_id=#{client_id}) to continue.
+        )
+      )
+    end
+  end
+end

data/lib/davinci_dtr_test_kit/client_groups/resp_assist_device/dtr_smart_app_questionnaire_workflow_group.rb

@@ -7,10 +7,11 @@ module DaVinciDTRTestKit
     id :dtr_smart_app_questionnaire_workflow
     title 'Respiratory Assist Device Questionnaire Workflow'
     description %(
-      This workflow validates that a DTR SMART App can perform a full DTR Questionnaire workflow using a canned
-      Questionnaire for a respiratory assist device order:
+      This workflow validates that a DTR SMART App can perform a full DTR
+      Questionnaire workflow using a canned Questionnaire
+      for a respiratory assist device order:
 
-      1. Fetch the questionnaire package
+      1. Fetch the questionnaire package ([RespiratoryAssistDevices](https://github.com/inferno-framework/davinci-dtr-test-kit/blob/main/lib/davinci_dtr_test_kit/fixtures/questionnaire_package.json))
       2. Render the questionnaire
       3. Pre-populate the questionnaire response
     )

data/lib/davinci_dtr_test_kit/docs/dtr_smart_app_suite_description_v201.md

@@ -52,64 +52,128 @@ validated with the Java validator using `tx.fhir.org` as the terminology server.
 
 ### Quick Start
 
-Inferno does not currently include the ability to launch the client. Therefore, clients
-must be manually configured to point to Inferno's simulated server endpoints. The endpoints
-can be inferred from the URL of the test session which will be of the form `[URL prefix]/dtr_smart_app/[session id]`: (NOTE: both currently use the same URL)
-- Payer Server Base FHIR URL: `[URL prefix]/custom/dtr_smart_app/fhir`
-- Light EHR Base FHIR URL: `[URL prefix]/custom/dtr_smart_app/fhir`
-
-In order for Inferno to associate requests sent to locations under these base URLs with this session,
-it needs to know the bearer token that the app will send on requests, for which 
-there are two options.
-
-1. If you want to choose your own bearer token, then
-    1. Select the "2. Basic Workflows" test from the list on the left (or other target test). 
-    2. Click the '*Run All Tests*' button on the right.
-    3. In the "access_token" field, enter the bearer token that will be sent by the client 
-       under test (as part of the Authorization header - `Bearer <provided value>`).
-    4. Click the '*Submit*' button at the bottom of the dialog.
-2. If you want to use a client_id to obtain an access token, then
-    1. Click the '*Run All Tests*' button on the right.
-    2. Provide the client's registered id "client_id" field of the input (NOTE, Inferno doesn't support the
-        registration API, so this must be obtained from another system or configured manually).
-    3. Click the '*Submit*' button at the bottom of the dialog.
-    4. Make a token request that includes the specified client id to the
-        `[URL prefix]/custom/dtr_smart_app/mock_auth/token` endpoint to get
-        an access token to use on the request of the requests.
-
-In either case, the tests will continue from that point. Further executions of tests under
-this session will also use the selected bearer token.
-
-Note: authentication options for these tests have not been finalized and are subject to change.
+This test suite can be run in two modes, each described below:
+1. [EHR launch mode](#ehr-launch)
+2. [Standalone launch mode](#standalone-launch)
+
+At this time, Inferno's simulation of the payer server that provides the questionnaires
+uses the same base server url and access token, and apps will need to be configured to
+connect to it as well. See the "Combined payer and EHR FHIR servers" section below for details.
+
+The DTR specification allows apps and their partners significant leeway in terms of
+what information is provided on launch and how that information gets used by the app
+to determine the `$questionnaire-package` endpoint and what details to submit as a
+part of that operation. Inferno cannot know ahead of time what data needs to be
+available for the app under test to successfully request, pre-populate, and render 
+a questionnaire. See the "`fhirContext` and available instances"
+section below for details on how to enable Inferno to meet the needs of your application.
+
+#### EHR Launch
+
+In this mode Inferno will launch the app under test using the SMART App Launch
+[EHR launch](https://hl7.org/fhir/smart-app-launch/STU2.1/app-launch.html#launch-app-ehr-launch)
+flow. 
+
+The tester must provide
+1. a `client_id`: can be any string and will uniquely identify the testing session.
+2. a `launch_uri`: will be used by Inferno to generate a link to launch the app under test.
+
+All the details needed to access clinical data from Inferno's simulated EHR are provided
+as a part of the SMART flow, including 
+- the FHIR base server URL to request data from
+- a bearer token to provide on all requests
+
+#### Standalone Launch
+
+In this mode the app under test will launch and on its own and reach out to Inferno to
+begin the workflow as described in the 
+[standalone launch section](https://hl7.org/fhir/smart-app-launch/STU2.1/app-launch.html#launch-app-standalone-launch).
+
+The tester must provide
+1. a `client_id`: can be any string and will uniquely identify the testing session.
+
+The app will then need to connect to Inferno as directed to initiate the SMART and DTR
+workflow. The FHIR base server url that app will connect to is 
+`[URL prefix]/custom/dtr_smart_app/fhir` where `[URL prefix]` comes from the URL of the
+test session which will be of the form `[URL prefix]/dtr_smart_app/[session id]`
 
 ### Postman-based Demo
 
 If you do not have a DTR SMART app but would like to try the tests out, you can use
-[this Postman collection](https://github.com/inferno-framework/davinci-dtr-test-kit/blob/main/config/DTR%20Test%20Kit.postman_collection.json)
+[this Postman collection](https://github.com/inferno-framework/davinci-dtr-test-kit/blob/main/config/DTR%20SMART%20App%20Tests%20Postman%20Demo.postman_collection.json)
 to make requests against Inferno. This does not include the capability to render the complete the
 questionnaires, but does have samples of correctly and incorrectly completed QuestionnaireResponses.
 The following is a list of tests with the Postman requests that can be used with them:
 
-- **2.1** *Static Questionnaire Workflow*: use requests in the `Static Dinner` folder
-  - **2.1.1.01** *Invoke the DTR Questionnaire Package operation*: submit request `Questionnaire Package for Dinner (Static)` while this test is waiting.
-  - **2.1.3.01** *Save the QuestionnaireResponse after completing it*: submit request `Save QuestionnaireResponse for Dinner (Static)` while this test is waiting. If you want to see a failure, submit request `Save QuestionnaireResponse for Dinner (Static) - missing origin extension` instead.
-- **3.1** *Respiratory Assist Device Questionnaire Workflow*: use requests in the `Respiratory Assist Device` folder
-  - **3.1.1.01** *Invoke the DTR Questionnaire Package operation*: submit request `Questionnaire Package for Resp Assist Device` while this test is waiting.
-  - **3.1.3.01** *Save the QuestionnaireResponse after completing it*: submit request `Save Questionnaire Response for Resp Assist Device` while this test is waiting. If you want to see a failure, submit request `Save Questionnaire Response for Resp Assist Device - unexpected override` instead.
+- **Standalone launch sequence**: use requests in the `SMART App Launch` folder during 
+  tests **1.1.1.01** or **2.1.1.01** to simulate the SMART Launch flow and obtain an access
+  token to use for subsequent requests. See the collection's Overview for details on the
+  access token's generation.
+- **1.1** *Static Questionnaire Workflow*: use requests in the `Static Dinner` folder
+  - **1.1.1.01** *Invoke the DTR Questionnaire Package operation*: submit request `Questionnaire Package for Dinner (Static)` while this test is waiting.
+  - **1.1.3.01** *Save the QuestionnaireResponse after completing it*: submit request `Save QuestionnaireResponse for Dinner (Static)` while this test is waiting. If you want to see a failure, submit request `Save QuestionnaireResponse for Dinner (Static) - missing origin extension` instead.
+- **2.1** *Respiratory Assist Device Questionnaire Workflow*: use requests in the `Respiratory Assist Device` folder
+  - **2.1.1.01** *Invoke the DTR Questionnaire Package operation*: submit request `Questionnaire Package for Resp Assist Device` while this test is waiting.
+  - **2.1.3.01** *Save the QuestionnaireResponse after completing it*: submit request `Save Questionnaire Response for Resp Assist Device` while this test is waiting. If you want to see a failure, submit request `Save Questionnaire Response for Resp Assist Device - unexpected override` instead.
+
+## Configuration Details
+
+### `fhirContext` and available instances
+
+Once they have launched, DTR SMART Apps obtain details that drive their retrieval of questionnaires
+and relevant clinical data from the payer and the EHR from [context that is passed with
+the access token](https://hl7.org/fhir/smart-app-launch/STU2.1/scopes-and-launch-context.html)
+provided by the EHR. Inferno cannot know ahead of time what information to provide and
+what instances to make available to direct the app under test to request and render a
+particular questionnaire.
+
+Therefore, use of this test suite requests that the tester provide this information so that the
+app can demonstrate its capabilities based on whatever business logic is present. These tests
+currently support two context parameters that contain references to instance in the EHR and provides
+testers with a way to provide those instances to Inferno so it can serve them to the app. These are
+controlled by the following inputs present on each group associated with a questionnaire:
+
+- **SMART App Launch Patient ID**: provide an `id` for the subject Patient FHIR instance.
+- **SMART App Launch `fhirContext`**: provide a JSON object containing FHIR references to instances
+  relevant to the DTR workflow, e.g. 
+  
+  ```
+  [{reference: 'Coverage/cov015'}, {reference: 'DeviceRequest/devreqe0470'}]
+  ``` 
+  This will be included under the `fhirContext` key of the token response.
+- **EHR-available resources**: provide a Bundle containing FHIR instances referenced in and from the
+  previous two inputs. Each instance must include an `id` element that Inferno will use in conjunction
+  with the `resourceType` to make the instances available at the `[server base url]/[resourceType]/[id]`.
+
+Each questionnaire workflow group description includes a link to the questionnaire package that Inferno will return
+(e.g., [here](https://github.com/inferno-framework/davinci-dtr-test-kit/blob/main/lib/davinci_dtr_test_kit/fixtures/dinner_static/questionnaire_dinner_order_static.json))
+where you can find `id` and `url` values and any other details needed to determine what inputs 
+will allow the app under test to work with that questionnaire. Note additionally that Inferno will always
+return that questionnaire in response to `$questionnaire-package` requests made during that test.
+
+These inputs can be cumbersome to create and if you have suggestions about how to improve this process
+while keeping the flexibility of Inferno to run with any app, submit a ticket 
+[here](https://github.com/inferno-framework/davinci-pas-test-kit/issues).
 
 ## Limitations
 
-The DTR IG is a complex specification and these tests currently validate SMART app
-configuration to only part of it. Future versions of the test suite will test further
+The DTR IG is a complex specification and these tests currently validate conformance to only
+a subset of IG requirements. Future versions of the test suite will test further
 features. A few specific features of interest are listed below.
 
 ### Launching and security
 
-The primary limitation on this test suite is that it requires the client under test
-to be manually configured to point to the Inferno endpoints and send a bearer token. 
-In the future, the tests will provide a mechanism for launching the application using
-the SMART app launch mechanism. To provide feedback and input on the design of this feature,
-submit a ticket [here](https://github.com/inferno-framework/davinci-pas-test-kit/issues).
+This test kit contains basic SMART App Launch cabilities that may not be complete. In particular,
+refresh tokens are not currently supported and scopes are not precise. To provide feedback and 
+input on the design of this feature and help us priortize improvements, submit a ticket 
+[here](https://github.com/inferno-framework/davinci-pas-test-kit/issues).
+
+### Combined payer and EHR FHIR servers
+
+At this time, the test suite simulates a single FHIR server that uses the same access token
+for both the payer server and the EHR server. Apps under test must use the FHIR server base url
+and access token identified during the SMART App Launch sequence when making requests
+to retrieve questionnaires.
 
 ### Questionnaire Feature Coverage
 

data/lib/davinci_dtr_test_kit/dtr_full_ehr_suite.rb

@@ -25,18 +25,42 @@ module DaVinciDTRTestKit
 
     version VERSION
 
-    # All FHIR validation requsets will use this FHIR validator
-    validator do
-      url ENV.fetch('VALIDATOR_URL')
+    links [
+      {
+        label: 'Report Issue',
+        url: 'https://github.com/inferno-framework/davinci-dtr-test-kit/issues'
+      },
+      {
+        label: 'Open Source',
+        url: 'https://github.com/inferno-framework/davinci-dtr-test-kit'
+      },
+      {
+        label: 'Download',
+        url: 'https://github.com/inferno-framework/davinci-dtr-test-kit/releases'
+      },
+      {
+        label: 'Implementation Guide',
+        url: 'https://hl7.org/fhir/us/davinci-dtr/STU2/'
+      }
+    ]
+
+    # Hl7 Validator Wrapper:
+    fhir_resource_validator do
+      igs 'hl7.fhir.us.davinci-dtr#2.0.1'
+
+      exclude_message do |message|
+        message.message.match?(/\A\S+: \S+: URL value '.*' does not resolve/)
+      end
     end
 
     allow_cors QUESTIONNAIRE_PACKAGE_PATH
 
-    record_response_route :post, TOKEN_PATH, 'dtr_auth', method(:token_response) do |request|
-      DTRFullEHRSuite.extract_client_id(request)
+    record_response_route :post, PAYER_TOKEN_PATH, 'dtr_full_ehr_payer_token',
+                          method(:payer_token_response) do |request|
+      DTRFullEHRSuite.extract_client_id_from_form_params(request)
     end
 
-    record_response_route :post, '/fhir/Questionnaire/$questionnaire-package', QUESTIONNAIRE_PACKAGE_TAG,
+    record_response_route :post, QUESTIONNAIRE_PACKAGE_PATH, QUESTIONNAIRE_PACKAGE_TAG,
                           method(:questionnaire_package_response) do |request|
       DTRFullEHRSuite.extract_bearer_token(request)
     end