smart_app_launch_test_kit 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: ae741dbca6b676c7c53c6be41a14f84292b4d620dbfecbf67f7472f5450c67fc
+  data.tar.gz: 4136c596fa810d8109c18df863e39eda7283c170a59c7441dc07e1bcb4ebdc1f
+SHA512:
+  metadata.gz: dfa9bd45de2c2b917347724b9a706dde71d1287dc48a3e49a86371b1106c42257084f78f989dcb737fba425594fbc11f4562b3aab7bf37710a40cdff3fccb116
+  data.tar.gz: ce2e0ed22fd192d88c5de32f334ada292ee5813b72c184eb9161f122d2cec82155ff6e83de19f8fe2c2d7a2ea0cd52b5c4adcdcefef0a668ff079abb7107776d

data/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright {yyyy} {name of copyright owner}
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/lib/smart_app_launch/app_launch_test.rb

@@ -0,0 +1,25 @@
+module SMARTAppLaunch
+  class AppLaunchTest < Inferno::Test
+    title 'EHR server redirects client browser to Inferno app launch URI'
+    description %(
+      Client browser sent from EHR server to app launch URI of client app as
+      described in SMART EHR Launch Sequence.
+    )
+    id :smart_app_launch
+
+    input :url
+    receives_request :launch
+
+    config options: { launch_uri: "#{Inferno::Application['inferno_host']}/custom/smart/launch" }
+
+    run do
+      wait(
+        identifier: url,
+        message: %(
+          Waiting to receive a request at
+          `#{config.options[:launch_uri]}` with an `iss` of `#{url}`.
+        )
+      )
+    end
+  end
+end

data/lib/smart_app_launch/app_redirect_test.rb

@@ -0,0 +1,61 @@
+module SMARTAppLaunch
+  class AppRedirectTest < Inferno::Test
+    title 'OAuth server redirects client browser to app redirect URI'
+    description %(
+      Client browser redirected from OAuth server to redirect URI of client
+      app as described in SMART authorization sequence.
+    )
+    id :smart_app_redirect
+
+    input :client_id, :requested_scopes, :url, :smart_authorization_url
+
+    output :state
+    receives_request :redirect
+
+    config options: { redirect_uri: "#{Inferno::Application['inferno_host']}/custom/smart/redirect" }
+
+    run do
+      assert_valid_http_uri(
+        smart_authorization_url,
+        "OAuth2 Authorization Endpoint '#{smart_authorization_url}' is not a valid URI"
+      )
+
+      output state: SecureRandom.uuid
+
+      oauth2_params = {
+        'response_type' => 'code',
+        'client_id' => client_id,
+        'redirect_uri' => config.options[:redirect_uri],
+        'scope' => requested_scopes,
+        'state' => state,
+        'aud' => url
+      }
+
+      oauth2_params['launch'] = launch if self.class.inputs.include?(:launch)
+
+      authorization_url = smart_authorization_url
+
+      authorization_url +=
+        if authorization_url.include? '?'
+          '&'
+        else
+          '?'
+        end
+
+      oauth2_params.each do |key, value|
+        authorization_url += "#{key}=#{CGI.escape(value)}&"
+      end
+
+      authorization_url.chomp!('&')
+
+      wait(
+        identifier: state,
+        message: %(
+          [Follow this link to authorize with the SMART
+          server](#{authorization_url}). Waiting to receive a request at
+          `#{config.options[:redirect_uri]}` with a state of `#{state}`.
+        )
+      )
+    end
+  end
+end

data/lib/smart_app_launch/code_received_test.rb

@@ -0,0 +1,31 @@
+module SMARTAppLaunch
+  class CodeReceivedTest < Inferno::Test
+    title 'OAuth server sends code parameter'
+    description %(
+      Code is a required querystring parameter on the redirect.
+    )
+    id :smart_code_received
+
+    output :code
+    uses_request :redirect
+
+    run do
+      code = request.query_parameters['code']
+      output code: code
+
+      assert code.present?, 'No `code` paramater received'
+
+      error = request.query_parameters['error']
+
+      pass_if error.blank?
+
+      error_message = "Error returned from authorization server. code: '#{error}'"
+      error_description = request.query_parameters['error_description']
+      error_uri = request.query_parameters['error_uri']
+      error_message += ", description: '#{error_description}'" if error_description.present?
+      error_message += ", uri: #{error_uri}" if error_uri.present?
+
+      assert false, error_message
+    end
+  end
+end

data/lib/smart_app_launch/discovery_group.rb

@@ -0,0 +1,229 @@
+module SMARTAppLaunch
+  class DiscoveryGroup < Inferno::TestGroup
+    id :smart_discovery
+    title 'SMART on FHIR Discovery'
+    description %(
+      # Background
+
+      The #{title} Sequence test looks for authorization endpoints and SMART
+      capabilities as described by the [SMART App Launch
+      Framework](http://hl7.org/fhir/smart-app-launch/conformance/index.html).
+      The SMART launch framework uses OAuth 2.0 to *authorize* apps, like
+      Inferno, to access certain information on a FHIR server. The
+      authorization service accessed at the endpoint allows users to give
+      these apps permission without sharing their credentials with the
+      application itself. Instead, the application receives an access token
+      which allows it to access resources on the server. The access token
+      itself has a limited lifetime and permission scopes associated with it.
+      A refresh token may also be provided to the application in order to
+      obtain another access token. Unlike access tokens, a refresh token is
+      not shared with the resource server. If OpenID Connect is used, an id
+      token may be provided as well. The id token can be used to
+      *authenticate* the user. The id token is digitally signed and allows the
+      identity of the user to be verified.
+
+      # Test Methodology
+
+      This test suite will examine the SMART on FHIR configuration contained
+      in both the `/metadata` and `/.well-known/smart-configuration`
+      endpoints.
+
+      For more information see:
+
+      * [SMART App Launch Framework](http://hl7.org/fhir/smart-app-launch/index.html)
+      * [The OAuth 2.0 Authorization Framework](https://tools.ietf.org/html/rfc6749)
+      * [OpenID Connect Core](https://openid.net/specs/openid-connect-core-1_0.html)
+    )
+
+    test do
+      title 'FHIR server makes SMART configuration available from well-known endpoint'
+      description %(
+        The authorization endpoints accepted by a FHIR resource server can
+        be exposed as a Well-Known Uniform Resource Identifier
+      )
+      input :url,
+            title: 'FHIR Endpoint',
+            description: 'URL of the FHIR endpoint used by SMART applications',
+            default: 'https://inferno.healthit.gov/reference-server/r4'
+      output :well_known_configuration,
+             :well_known_authorization_url,
+             :well_known_introspection_url,
+             :well_known_management_url,
+             :well_known_registration_url,
+             :well_known_revocation_url,
+             :well_known_token_url
+      makes_request :smart_well_known_configuration
+
+      run do
+        well_known_configuration_url = "#{url.chomp('/')}/.well-known/smart-configuration"
+        get(well_known_configuration_url, name: :smart_well_known_configuration)
+
+        assert_response_status(200)
+
+        assert_valid_json(request.response_body)
+
+        config = JSON.parse(request.response_body)
+        output well_known_configuration: request.response_body,
+               well_known_authorization_url: config['authorization_endpoint'],
+               well_known_introspection_url: config['introspection_endpoint'],
+               well_known_management_url: config['management_endpoint'],
+               well_known_registration_url: config['registration_endpoint'],
+               well_known_revocation_url: config['revocation_endpoint'],
+               well_known_token_url: config['token_endpoint']
+
+        content_type = request.response_header('Content-Type')&.value
+
+        assert content_type.present?, 'No `Content-Type` header received.'
+        assert content_type.start_with?('application/json'),
+               "`Content-Type` must be `application/json`, but received: `#{content_type}`"
+      end
+    end
+
+    test do
+      title 'Well-known configuration contains required fields'
+      description %(
+        The JSON from .well-known/smart-configuration contains the following
+        required fields: `authorization_endpoint`, `token_endpoint`,
+        `capabilities`
+      )
+      input :well_known_configuration
+
+      run do
+        skip_if well_known_configuration.blank?, 'No well-known configuration found'
+        config = JSON.parse(well_known_configuration)
+
+        ['authorization_endpoint', 'token_endpoint', 'capabilities'].each do |key|
+          assert config.key?(key), "Well-known configuration does not include `#{key}`"
+          assert config[key].present?, "Well-known configuration field `#{key}` is blank"
+        end
+
+        assert config['authorization_endpoint'].is_a?(String),
+               'Well-known `authorization_endpoint` field must be a string'
+        assert config['token_endpoint'].is_a?(String),
+               'Well-known `token_endpoint` field must be a string'
+        assert config['capabilities'].is_a?(Array),
+               'Well-known `capabilities` field must be an array'
+
+        non_string_capabilities = config['capabilities'].reject { |capability| capability.is_a? String }
+
+        assert non_string_capabilities.blank?, %(
+          Well-known `capabilities` field must be an array of strings, but found
+          non-string values:
+          #{non_string_capabilities.map { |value| "`#{value.nil? ? 'nil' : value}`" }.join(', ')}
+        )
+      end
+    end
+
+    test do
+      title 'Conformance/CapabilityStatement provides OAuth 2.0 endpoints'
+      description %(
+        If a server requires SMART on FHIR authorization for access, its
+        metadata must support automated discovery of OAuth2 endpoints.
+      )
+      input :url
+      output :capability_authorization_url,
+             :capability_introspection_url,
+             :capability_management_url,
+             :capability_registration_url,
+             :capability_revocation_url,
+             :capability_token_url
+
+      fhir_client do
+        url :url
+      end
+
+      run do
+        fhir_get_capability_statement
+
+        assert_response_status(200)
+
+        smart_extension =
+          resource
+            .rest
+            &.map(&:security)
+            &.find do |security|
+            security.service&.any? do |service|
+              service.coding&.any? do |coding|
+                coding.code == 'SMART-on-FHIR'
+              end
+            end
+          end
+            &.extension
+            &.find do |extension|
+              extension.url == 'http://fhir-registry.smarthealthit.org/StructureDefinition/oauth-uris'
+            end
+
+        assert smart_extension.present?, 'No SMART extensions found in CapabilityStatement'
+
+        oauth_extension_urls = ['authorize', 'introspect', 'manage', 'register', 'revoke', 'token']
+
+        oauth_urls = oauth_extension_urls.each_with_object({}) do |url, urls|
+          urls[url] = smart_extension.extension.find { |extension| extension.url == url }&.valueUri
+        end
+
+        output capability_authorization_url: oauth_urls['authorize'],
+               capability_introspection_url: oauth_urls['introspect'],
+               capability_management_url: oauth_urls['manage'],
+               capability_registration_url: oauth_urls['register'],
+               capability_revocation_url: oauth_urls['revoke'],
+               capability_token_url: oauth_urls['token']
+
+        assert oauth_urls['authorize'].present?, 'No `authorize` extension found'
+        assert oauth_urls['token'].present?, 'No `token` extension found'
+      end
+    end
+
+    test do
+      title 'OAuth 2.0 Endpoints in the conformance statement match those from the well-known configuration'
+      description %(
+        The server SHALL convey the FHIR OAuth authorization endpoints that are listed
+        in the table below to app developers. The server SHALL use both a FHIR
+        CapabilityStatement and A Well-Known Uris JSON file.
+      )
+      input :well_known_authorization_url,
+            :well_known_introspection_url,
+            :well_known_management_url,
+            :well_known_registration_url,
+            :well_known_revocation_url,
+            :well_known_token_url,
+            :capability_authorization_url,
+            :capability_introspection_url,
+            :capability_management_url,
+            :capability_registration_url,
+            :capability_revocation_url,
+            :capability_token_url
+      output :smart_authorization_url,
+             :smart_introspection_url,
+             :smart_management_url,
+             :smart_registration_url,
+             :smart_revocation_url,
+             :smart_token_url
+
+      run do
+        mismatched_urls = []
+        ['authorization', 'token', 'introspection', 'management', 'registration', 'revocation'].each do |type|
+          well_known_url = send("well_known_#{type}_url")
+          capability_url = send("capability_#{type}_url")
+
+          output "smart_#{type}_url": well_known_url.presence || capability_url.presence
+
+          mismatched_urls << type if well_known_url != capability_url
+        end
+
+        pass_if mismatched_urls.empty?
+
+        error_message = 'The following urls do not match:'
+
+        mismatched_urls.each do |type|
+          well_known_url = send("well_known_#{type}_url")
+          capability_url = send("capability_#{type}_url")
+
+          error_message += "\n- #{type.capitalize}:"
+          error_message += "\n  - Well-Known: #{well_known_url}\n  - CapabilityStatement: #{capability_url}"
+        end
+
+        assert false, error_message
+      end
+    end
+  end
+end

data/lib/smart_app_launch/ehr_launch_group.rb

@@ -0,0 +1,117 @@
+require_relative 'app_launch_test'
+require_relative 'app_redirect_test'
+require_relative 'code_received_test'
+require_relative 'launch_received_test'
+require_relative 'token_exchange_test'
+require_relative 'token_response_body_test'
+require_relative 'token_response_headers_test'
+
+module SMARTAppLaunch
+  class EHRLaunchGroup < Inferno::TestGroup
+    id :smart_ehr_launch
+    title 'SMART EHR Launch'
+
+    description %(
+      # Background
+
+      The [EHR
+      Launch](http://hl7.org/fhir/smart-app-launch/index.html#ehr-launch-sequence)
+      is one of two ways in which an app can be launched, the other being
+      Standalone launch. In an EHR launch, the app is launched from an
+      existing EHR session or portal by a redirect to the registered launch
+      URL. The EHR provides the app two parameters:
+
+      * `iss` - Which contains the FHIR server url
+      * `launch` - An identifier needed for authorization
+
+      # Test Methodology
+
+      Inferno will wait for the EHR server redirect upon execution. When the
+      redirect is received Inferno will check for the presence of the `iss`
+      and `launch` parameters. The security of the authorization endpoint is
+      then checked and authorization is attempted using the provided `launch`
+      identifier.
+
+      For more information on the #{title} see:
+
+      * [SMART EHR Launch Sequence](http://hl7.org/fhir/smart-app-launch/index.html#ehr-launch-sequence)
+    )
+
+    config(
+      inputs: {
+        client_id: {
+          name: :ehr_client_id,
+          title: 'EHR Launch Client ID',
+          description: 'Client ID provided during registration of Inferno as an EHR launch application',
+          default: 'SAMPLE_PUBLIC_CLIENT_ID'
+        },
+        client_secret: {
+          name: :ehr_client_secret,
+          title: 'EHR Launch Client Secret',
+          description: 'Client Secret provided during registration of Inferno as an EHR launch application'
+        },
+        requested_scopes: {
+          name: :ehr_requested_scopes,
+          title: 'EHR Launch Scope',
+          description: 'OAuth 2.0 scope provided by system to enable all required functionality',
+          type: 'textarea',
+          default: %(
+            launch openid fhirUser offline_access
+            patient/Medication.read patient/AllergyIntolerance.read
+            patient/CarePlan.read patient/CareTeam.read patient/Condition.read
+            patient/Device.read patient/DiagnosticReport.read
+            patient/DocumentReference.read patient/Encounter.read
+            patient/Goal.read patient/Immunization.read patient/Location.read
+            patient/MedicationRequest.read patient/Observation.read
+            patient/Organization.read patient/Patient.read
+            patient/Practitioner.read patient/Procedure.read
+            patient/Provenance.read patient/PractitionerRole.read
+          ).gsub(/\s{2,}/, ' ').strip
+        },
+        url: {
+          title: 'EHR Launch FHIR Endpoint',
+          description: 'URL of the FHIR endpoint used by EHR launched applications',
+          default: 'https://inferno.healthit.gov/reference-server/r4'
+        },
+        code: {
+          name: :ehr_code
+        },
+        state: {
+          name: :ehr_state
+        },
+        launch: {
+          name: :ehr_launch
+        }
+      },
+      outputs: {
+        launch: { name: :ehr_launch },
+        code: { name: :ehr_code },
+        token_retrieval_time: { name: :ehr_token_retrieval_time },
+        state: { name: :ehr_state },
+        id_token: { name: :ehr_id_token },
+        refresh_token: { name: :ehr_refresh_token },
+        access_token: { name: :ehr_access_token },
+        expires_in: { name: :ehr_expires_in },
+        patient_id: { name: :ehr_patient_id },
+        encounter_id: { name: :ehr_encounter_id },
+        received_scopes: { name: :ehr_received_scopes },
+        intent: { name: :ehr_intent }
+      },
+      requests: {
+        launch: { name: :ehr_launch },
+        redirect: { name: :ehr_redirect },
+        token: { name: :ehr_token }
+      }
+    )
+
+    test from: :smart_app_launch
+    test from: :smart_launch_received
+    test from: :smart_app_redirect do
+      input :launch
+    end
+    test from: :smart_code_received
+    test from: :smart_token_exchange
+    test from: :smart_token_response_body
+    test from: :smart_token_response_headers
+  end
+end