davinci_plan_net_test_kit 0.11.1 → 0.12.1

data/lib/davinci_plan_net_test_kit/generator/templates/suite.rb.erb

@@ -1,4 +1,3 @@
-require 'inferno/dsl/oauth_credentials'
 require_relative '../../version'
 require_relative '<%= capability_statement_file_name %>'
 <% group_file_list.each do |file_name| %>require_relative '<%= file_name %>'
@@ -13,15 +12,15 @@ module DaVinciPlanNetTestKit
 
         ## Scope
 
-        These tests are a **DRAFT** intended to allow Plan Net server implementers to perform 
-        preliminary checks of their servers against Plan Net IG requirements and [provide 
-        feedback](https://github.com/inferno-framework/davinci-plan-net-test-kit/issues) 
-        to ONC on the tests. Future versions of these tests may validate other 
+        These tests are a **DRAFT** intended to allow Plan Net server implementers to perform
+        preliminary checks of their servers against Plan Net IG requirements and [provide
+        feedback](https://github.com/inferno-framework/davinci-plan-net-test-kit/issues)
+        to ONC on the tests. Future versions of these tests may validate other
         requirements and may change the test validation logic.
 
         ## Test Methodology
 
-        Inferno will act as a client and make a series of requests to the 
+        Inferno will act as a client and make a series of requests to the
         server under test. The responses will be checked for conformance to the Plan
         Net IG requirements individually and used in aggregate to determine whether
         required features and functionality are present.
@@ -30,10 +29,10 @@ module DaVinciPlanNetTestKit
         `tx.fhir.org` as the terminology server.
 
         ## Running the Tests
-        
+
         ### Quick Start
 
-        The tests are designed to be runnable with a single input from the user: 
+        The tests are designed to be runnable with a single input from the user:
         the base FHIR URL of the server under test. To run in this mode:
         1. Click the `RUN ALL TESTS` button in the upper right
         2. Provide the URL for the server in the first "FHIR Endpoint (required)" input
@@ -41,10 +40,10 @@ module DaVinciPlanNetTestKit
         4. Wait for Inferno to run the tests (will take several minutes)
         5. Expand tests with failures to determine the reason
 
-        If you would like to try out the tests but don't have a Plan Net server implementation, 
-        you can use the publicly available reference implementation available at URL 
+        If you would like to try out the tests but don't have a Plan Net server implementation,
+        you can use the publicly available reference implementation available at URL
         https://plan-net-ri.davinci.hl7.org/fhir. Select this endpoint by using that URL as the
-        "FHIR Endpoint (required)" input or prepopulating it by selecting the 
+        "FHIR Endpoint (required)" input or prepopulating it by selecting the
         `Da Vinci Plan Net Reference Server` preset in the upper left. Note that this
         system is not currently expected to pass all of the tests.
 
@@ -53,8 +52,8 @@ module DaVinciPlanNetTestKit
         - Additional data within the system under test, e.g., to demonstrate all Must Support elements.
         - Fixes to the system under test.
 
-        Note that this mode requires that the server support parameterless searches against 
-        Plan Net resource types (e.g., `GET [FHIR Endpoint]/InsurancePlan`), which are not required 
+        Note that this mode requires that the server support parameterless searches against
+        Plan Net resource types (e.g., `GET [FHIR Endpoint]/InsurancePlan`), which are not required
         by the Plan Net IG. If your server does not support these searches, or some returned instances
         will not conform to Plan Net profiles, see the *Instance Gathering* section under
         *Test Configuration Details* below for how to disable these searches and direct the tests
@@ -62,8 +61,8 @@ module DaVinciPlanNetTestKit
 
         ### Running Groups Individually
 
-        Each test group listed on the left can be run individually using the `RUN TESTS` 
-        button in the upper right of the group page. However, note that running 
+        Each test group listed on the left can be run individually using the `RUN TESTS`
+        button in the upper right of the group page. However, note that running
         them individually requires additional inputs so that Inferno can find appropriate values for searches
         (see *Determination of Search Values When Running Single Groups* below for details).
 
@@ -74,60 +73,59 @@ module DaVinciPlanNetTestKit
 
         ### Authentication
 
-        The Plan Net IG requires that "A conformant Plan-Net service SHALL NOT 
-        require a directory mobile application to send consumer identifying information 
+        The Plan Net IG requires that "A conformant Plan-Net service SHALL NOT
+        require a directory mobile application to send consumer identifying information
         in order to query content." A simple way to ensure this is to not require authentication,
         which is safe because the information in scope does not include PHI. Thus, the
         tests do not send authentication details by default.
 
-        If a server under test requires authentication information to be sent, an access token 
-        may be provided using the "OAuth Credentials - Access Token" input. When populated, 
+        If a server under test requires authentication information to be sent, an access token
+        may be provided using the "OAuth Credentials - Access Token" input. When populated,
         requests to the server will include an HTTP header of the form `Authorization: Bearer [access token]`.
 
         ### Instance Gathering
 
         Inferno needs to identify instances of each profile to use to validate conformance to
-        structural and search API requirements. Inferno will use one or a combination of the 
+        structural and search API requirements. Inferno will use one or a combination of the
         following two approaches as directed by the inputs.
 
         #### Parameterless searches (default)
-        
-        Inferno will use a search against the base resource type without any search 
-        parameters (`GET [FHIR Endpoint]/[Resource Type]`) to identify instances of each profile. 
+
+        Inferno will use a search against the base resource type without any search
+        parameters (`GET [FHIR Endpoint]/[Resource Type]`) to identify instances of each profile.
         This behavior can be controlled using the following inputs:
         - "Use parameterless searches to identify instances?": if the server under test does not support
           parameterless searches, this can be set to `No` to disable parameterless searches.
-        - "Maximum number of instances to gather using parameterless searches (required)" and 
-          "Maximum pages of results to consider when using parameterless searches (required)": if fewer 
-          instances (e.g., to improve performance) or more instances (e.g., to improve Must Support 
+        - "Maximum number of instances to gather using parameterless searches (required)" and
+          "Maximum pages of results to consider when using parameterless searches (required)": if fewer
+          instances (e.g., to improve performance) or more instances (e.g., to improve Must Support
           element coverage) should be gathered, these inputs can be adjusted to tune the number
           of instances that Inferno will gather using parameterless searches.
-        
+
         #### Specific instance ids
-        
-        Inputs of the form "ids of [profile] instances" can be used by the user to specify particular 
+
+        Inputs of the form "ids of [profile] instances" can be used by the user to specify particular
         instances for Inferno to gather for use in testing. Inferno will perform a read on each provided id
-        to gather the instances. When parameterless searches are not used, all inputs of this form must be populated. 
+        to gather the instances. When parameterless searches are not used, all inputs of this form must be populated.
         When instance ids are provided in addition to parameterless searches, instances provided by the user
         are prioritized for use in determining search values for search tests.
-        
+
         ### Determination of Search Values When Running Single Groups
 
-        Validation of search parameters requires Inferno to identify values that are expected 
-        to return instances. By default, Inferno does this by examining gathered instances of each profile 
+        Validation of search parameters requires Inferno to identify values that are expected
+        to return instances. By default, Inferno does this by examining gathered instances of each profile
         to identify search values that should return results when performed against the server under
         test. For `_revinclude` and reverse chaining tests, Inferno needs access to instances of other profiles
-        in order to determine appropriate search values. When test groups are run individually, Inferno will not 
-        have access to instances identified while running other groups. Thus, when running at the group level, 
+        in order to determine appropriate search values. When test groups are run individually, Inferno will not
+        have access to instances identified while running other groups. Thus, when running at the group level,
         two additional inputs are required to allow the tests to identify appropriate search values:
-        - "[target profile] instance ids referenced in [referencing profile].[reference element]": 
-          used by `_revinclude` tests on [target profile] when run as a group to identify 
+        - "[target profile] instance ids referenced in [referencing profile].[reference element]":
+          used by `_revinclude` tests on [target profile] when run as a group to identify
           instances of the [target profile] that have instances of [referencing profile] that reference it.
-        - "'[constraining element]' value from a [referencing profile] instance with '[reference element]' populated": used by reverse chaining tests 
-          on the [target profile] referenced in the [reference element] element when run as a single group 
+        - "'[constraining element]' value from a [referencing profile] instance with '[reference element]' populated": used by reverse chaining tests
+          on the [target profile] referenced in the [reference element] element when run as a single group
           to identify the value to use when performing the reverse chain search.
       )
-      version VERSION
 
       VALIDATION_MESSAGE_FILTERS = [
         %r{Sub-extension url 'introspect' is not defined by the Extension http://fhir-registry\.smarthealthit\.org/StructureDefinition/oauth-uris},
@@ -146,6 +144,14 @@ module DaVinciPlanNetTestKit
 
       id :<%= suite_id %>
 
+      requirement_sets(
+        {
+          identifier: 'hl7.fhir.us.davinci-pdex-plan-net_1.1.0',
+          title: 'DaVinci PDEX Plan Net',
+          actor: 'Server'
+        }
+      )
+
       fhir_resource_validator do
         igs '<%= ig_identifier %>'
 
@@ -167,9 +173,13 @@ module DaVinciPlanNetTestKit
           url: 'https://github.com/inferno-framework/davinci-plan-net-test-kit/issues'
         },
         {
-          label: 'Source Code',
+          label: 'Open Source',
           url: 'https://github.com/inferno-framework/davinci-plan-net-test-kit'
         },
+        {
+          label: 'Download',
+          url: 'https://github.com/inferno-framework/davinci-plan-net-test-kit/releases'
+        },
         {
           label: 'Implementation Guide',
           url: '<%=ig_link %>'
@@ -179,10 +189,13 @@ module DaVinciPlanNetTestKit
       input :url,
         title: 'FHIR Endpoint',
         description: 'URL of the FHIR endpoint'
-      input :smart_credentials,
+      input :smart_auth_info,
         title: 'OAuth Credentials',
-        type: :oauth_credentials,
-        optional: true
+        type: :auth_info,
+        optional: true,
+        options: {
+          mode: 'access'
+        }
       input :no_param_search,
         title: 'Use parameterless searches to identify instances?',
         type: 'radio',
@@ -208,10 +221,10 @@ module DaVinciPlanNetTestKit
         title: 'Maximum pages of results to consider when using parameterless searches',
         default: '20',
         description: 'Only used with parameterless searches. A higher number will gather more instances for the tests, if they are available. The test will not consider further pages once the maximum number of instances has been reached.'
-      
+
       fhir_client do
         url :url
-        oauth_credentials :smart_credentials
+        auth_info :smart_auth_info
       end
 
       group from: :<%= capability_statement_group_id %>

data/lib/davinci_plan_net_test_kit/must_support_test.rb

@@ -14,198 +14,7 @@ module DaVinciPlanNetTestKit
     def perform_must_support_test(resources)
       skip_if resources.blank?, "No #{resource_type} resources were found"
 
-      missing_elements(resources)
-      missing_slices(resources)
-      missing_extensions(resources)
-
-      handle_must_support_choices if metadata.must_supports[:choices].present?
-
-      if (missing_elements + missing_slices + missing_extensions).length.zero?
-        pass
-      end
-
-      skip "Could not find #{missing_must_support_strings.join(', ')} in the #{resources.length} " \
-           "provided #{resource_type} resource(s)"
-    end
-
-    def handle_must_support_choices
-      missing_elements.delete_if do |element|
-        choices = metadata.must_supports[:choices].find { |choice| choice[:paths]&.include?(element[:path]) }
-        is_any_choice_supported?(choices)
-      end
-
-      missing_extensions.delete_if do |extension|
-        choices = metadata.must_supports[:choices].find { |choice| choice[:extension_ids]&.include?(extension[:id]) }
-        is_any_choice_supported?(choices)
-      end
-
-      missing_slices.delete_if do |slice|
-        choices = metadata.must_supports[:choices].find { |choice| choice[:slice_names]&.include?(slice[:name]) }
-        is_any_choice_supported?(choices)
-      end
-    end
-
-    def is_any_choice_supported? (choices)
-      choices.present? &&
-      (
-        choices[:paths]&.any? { |path| missing_elements.none? { |element| element[:path] == path } } ||
-        choices[:extension_ids]&.any? { |extension_id| missing_extensions.none? { |extension| extension[:id] == extension_id} } ||
-        choices[:slice_names]&.any? { |slice_name| missing_slices.none? { |slice| slice[:name] == slice_name} }
-      )
-    end
-
-    def missing_must_support_strings
-      missing_elements.map { |element_definition| missing_element_string(element_definition) } +
-        missing_slices.map { |slice_definition| slice_definition[:name] } +
-        missing_extensions.map { |extension_definition| extension_definition[:id] }
-    end
-
-    def missing_element_string(element_definition)
-      if element_definition[:fixed_value].present?
-        "#{element_definition[:path]}:#{element_definition[:fixed_value]}"
-      else
-        element_definition[:path]
-      end
-    end
-
-    def exclude_uscdi_only_test?
-      config.options[:exclude_uscdi_only_test] == true
-    end
-
-    def must_support_extensions
-      if exclude_uscdi_only_test?
-        metadata.must_supports[:extensions].reject{ |extension| extension[:uscdi_only] }
-      else
-        metadata.must_supports[:extensions]
-      end
-    end
-
-    def missing_extensions(resources = [])
-      @missing_extensions ||=
-        must_support_extensions.select do |extension_definition|
-          resources.none? do |resource|
-            resource.extension.any? { |extension| extension.url == extension_definition[:url] }
-          end
-        end
-    end
-
-    def must_support_elements
-      if exclude_uscdi_only_test?
-        metadata.must_supports[:elements].reject{ |element| element[:uscdi_only] }
-      else
-        metadata.must_supports[:elements]
-      end
-    end
-
-    def missing_elements(resources = [])
-      @missing_elements ||=
-        must_support_elements.select do |element_definition|
-          resources.none? do |resource|
-            path = element_definition[:path] #.delete_suffix('[x]')
-            value_found = find_a_value_at(resource, path) do |value|
-              value_without_extensions =
-                value.respond_to?(:to_hash) ? value.to_hash.reject { |key, _| key == 'extension' } : value
-
-              (value_without_extensions.present? || value_without_extensions == false) &&
-                (element_definition[:fixed_value].blank? || value == element_definition[:fixed_value])
-
-            end
-
-            # Note that false.present? => false, which is why we need to add this extra check
-            value_found.present? || value_found == false
-          end
-        end
-
-      @missing_elements
-    end
-
-    def must_support_slices
-      if exclude_uscdi_only_test?
-        metadata.must_supports[:slices].reject{ |slice| slice[:uscdi_only] }
-      else
-        metadata.must_supports[:slices]
-      end
-    end
-
-    def missing_slices(resources = [])
-      @missing_slices ||=
-        must_support_slices.select do |slice|
-          resources.none? do |resource|
-            path = slice[:path] # .delete_suffix('[x]')
-            find_slice(resource, path, slice[:discriminator]).present?
-          end
-        end
-    end
-
-    def find_slice(resource, path, discriminator)
-      find_a_value_at(resource, path) do |element|
-        case discriminator[:type]
-        when 'patternCodeableConcept'
-          coding_path = discriminator[:path].present? ? "#{discriminator[:path]}.coding" : 'coding'
-          find_a_value_at(element, coding_path) do |coding|
-            coding.code == discriminator[:code] && coding.system == discriminator[:system]
-          end
-        when 'patternCoding'
-          coding_path = discriminator[:path].present? ? discriminator[:path] : ''
-          find_a_value_at(element, coding_path) do |coding|
-            coding.code == discriminator[:code] && coding.system == discriminator[:system]
-          end
-        when 'patternIdentifier'
-          find_a_value_at(element, discriminator[:path]) { |identifier| identifier.system == discriminator[:system] }
-        when 'value'
-          values = discriminator[:values].map { |value| value.merge(path: value[:path].split('.')) }
-          find_slice_by_values(element, values)
-        when 'type'
-          case discriminator[:code]
-          when 'Date'
-            begin
-              Date.parse(element)
-            rescue ArgumentError
-              false
-            end
-          when 'DateTime'
-            begin
-              DateTime.parse(element)
-            rescue ArgumentError
-              false
-            end
-          when 'String'
-            element.is_a? String
-          else
-            element.is_a? FHIR.const_get(discriminator[:code])
-          end
-        when 'requiredBinding'
-          coding_path = discriminator[:path].present? ? "#{discriminator[:path]}.coding" : 'coding'
-          find_a_value_at(element, coding_path) {|coding| discriminator[:values].include?(coding.code) }
-        end
-      end
-    end
-
-    def find_slice_by_values(element, value_definitions)
-      path_prefixes = value_definitions.map { |value_definition| value_definition[:path].first }.uniq
-      Array.wrap(element).find do |el|
-        path_prefixes.all? do |path_prefix|
-          value_definitions_for_path =
-            value_definitions
-              .select { |value_definition| value_definition[:path].first == path_prefix }
-              .each { |value_definition| value_definition[:path].shift }
-
-          find_a_value_at(el, path_prefix) do |el_found|
-            child_element_value_definitions, current_element_value_definitions =
-              value_definitions_for_path.partition { |value_definition| value_definition[:path].present? }
-
-            current_element_values_match =
-              current_element_value_definitions
-                .all? { |value_definition| value_definition[:value] == el_found }
-
-            child_element_values_match =
-              child_element_value_definitions.present? ?
-                find_slice_by_values(el_found, child_element_value_definitions) : true
-
-            current_element_values_match && child_element_values_match
-          end
-        end
-      end
+      skip { assert_must_support_elements_present(resources, nil, metadata:) }
     end
   end
 end

data/lib/davinci_plan_net_test_kit/requirements/davinci_plan_net_test_kit_requirements.csv

@@ -0,0 +1,65 @@
+Req Set,ID,URL,Requirement,Conformance,Actors,Sub-Requirement(s),Conditionality,Not Tested Reason,Not Tested Details
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,1,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#privacy-considerations-1,A conformant Plan-Net service SHALL NOT require a directory mobile application to send consumer identifying information in order to query content.,SHALL NOT,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,2,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#privacy-considerations-1,A directory mobile application SHALL NOT send consumer identifiable information when querying a Plan-Net service.,SHALL NOT,Client,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,3,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#health-plan-api-requirements,Health Plan API actors SHALL be capable of populating all Must Support data elements as part of the query results.,SHALL,Server,,,,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,4,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#health-plan-api-requirements,"In situations where information on a particular Must Support data element is not present and the minimum cardinality is 0 , the Health Plan API actors SHALL NOT include the data elements in the resource instance returned as part of the query results.",SHALL NOT,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,5,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#health-plan-api-requirements,In situations where information on a particular data element is not present and the minimum cardinality is >0 SHALL send the reason for the missing information using values (such as nullFlavors) from the value set where they exist or use the dataAbsentReason extension.,SHALL,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,6,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#application-requirements,Application actors SHALL be capable of processing resource instances containing the Must Support data elements without generating an error or causing the application to fail.,SHALL,Client,,,Not Tested,Client testing currently out of scope
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,7,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#application-requirements,Application actors SHOULD be capable of displaying the data elements for human use or storing the information for other purposes.,SHOULD,Client,,,Not Tested,Client testing currently out of scope
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,8,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#application-requirements,"When querying Health Plan API actors, Application actors SHALL interpret missing Must Support data elements within resource instances as data not present in the Health Plan API actors system.",SHALL,Client,,,Not Tested,Client testing currently out of scope
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,9,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#application-requirements,Consumer App actors SHALL be able to process resource instances containing Must Support data elements asserting missing information.,SHALL,Client,,,Not Tested,Client testing currently out of scope
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,10,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/CapabilityStatement-plan-net.html#behavior,Support json source formats for all Plan-Net interactions.,SHALL,Server,,,,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,11,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/CapabilityStatement-plan-net.html#behavior,Implement the RESTful behavior according to the FHIR specification.,SHALL,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,12,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/CapabilityStatement-plan-net.html#behavior,Support all profiles defined in this Implementation Guide.,SHALL,Server,,,,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,13,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/CapabilityStatement-plan-net.html#behavior,Return the following response classes: (Status 401/4xx): unauthorized request,SHALL,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,14,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/CapabilityStatement-plan-net.html#behavior,Return the following response classes: (Status 403): insufficient scope,SHALL,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,15,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/CapabilityStatement-plan-net.html#behavior,Return the following response classes: (Status 400): invalid parameter,SHALL,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,16,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/CapabilityStatement-plan-net.html#behavior,Return the following response classes: (Status 404): unknown resource,SHALL,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,17,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/CapabilityStatement-plan-net.html#behavior,Return the following response classes: (Status 410): deleted resource.,SHALL,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,18,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/CapabilityStatement-plan-net.html#behavior,Identify the Plan-Net profiles supported as part of the FHIR meta.profile attribute for each instance.,SHALL,Server,,,Not Tested,Not intended by IG authors
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,19,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/CapabilityStatement-plan-net.html#behavior,Support the searchParameters on each profile individually,SHALL,Server,,,,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,20,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/CapabilityStatement-plan-net.html#behavior,Support the searchParameters on each profile...in combination.,SHALL,Server,,,Not Tested,Caveat: partial because full scope prohibitively expensive
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,21,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/CapabilityStatement-plan-net.html#behavior,Support forward...chaining on all search parameters that specify the 'chain' property,SHALL,Server,,,,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,22,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/CapabilityStatement-plan-net.html#behavior,Support...reverse chaining on all search parameters that specify the 'chain' property,SHALL,Server,,,,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,23,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/CapabilityStatement-plan-net.html#behavior,Support xml source formats for all Plan-Net interactions.,SHOULD,Server,,,Not Tested,XML format not supported by Inferno
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,24,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/CapabilityStatement-plan-net.html#behavior,A server SHALL reject any unauthorized requests by returning an HTTP 401 unauthorized response code.,SHALL,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,25,https://hl7.org/fhir/us/davinci-pdex-plan-net/CapabilityStatement-plan-net.json,"For each resource type and profile, a Plan Net server SHALL support the read interaction",SHALL,Server,,,,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,26,https://hl7.org/fhir/us/davinci-pdex-plan-net/CapabilityStatement-plan-net.json,"For each resource type and profile, a Plan Net server SHOULD support the vread interaction",SHOULD,Server,,,Not Tested,Low priority
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,27,http://hl7.org/fhir/us/davinci-pdex-plan-net/CapabilityStatement-plan-net.html#resource--details,[For each resource] A Server SHALL be capable of supporting the following _includes [list],SHALL,Server,,,,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,28,http://hl7.org/fhir/us/davinci-pdex-plan-net/CapabilityStatement-plan-net.html#resource--details,[For each resource] A Server SHALL be capable of supporting the following _revincludes: [list],SHALL,Server,,,,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,29,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/index.html#relation-to-us-core-and-other-igs,"The Network profile is based on USCore Organization, since there was no contradiction between the USCore profile and the Plan-Net requirements. However, the NPI and CLIA identifier types, which are Must-Support, are clearly intended for provider organizations only and are not expected to be populated for other organization types.",None,Server,,,,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,30,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#client-detection-of-updates-directory-content,Each profile in this guide requires that the lastUpdate timestamp be provided as part of the profile's data content.,None,Server,,,Not Tested,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,31,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#client-detection-of-updates-directory-content,Clients that cache query results can track additions or modifications to directory content through queries that filter content using the _lastUpdated search parameter.,None,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,32,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#representing-and-searching-provider-directory-data,"The Plan-Net design is based around the following types of searches….
+- Search: General Search
+- Example: Pharmacy
+- Focal Resource and Field: HealthcareService.category, HealthcareService.specialty
+- Qualifications of Search: Location, network",None,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,33,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#representing-and-searching-provider-directory-data,"The Plan-Net design is based around the following types of searches….
+- Search: Provider by Name
+- Example: Joe Smith
+- Focal Resource and Field: Practitioner.name
+- Qualifications of Search: Location, network, specialty, role/priviledges",None,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,34,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#representing-and-searching-provider-directory-data,"The Plan-Net design is based around the following types of searches….
+- Search: Organization by Name
+- Example: Montgomery Cardiology or CVS
+- Focal Resource and Field: Organization.name
+- Qualifications of Search: Location, network, specialty",None,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,35,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#representing-and-searching-provider-directory-data,"The Plan-Net design is based around the following types of searches….
+- Search: Provider by Specialty
+- Example: Cardiologist
+- Focal Resource and Field: PractitionerRole.specialty
+- Qualifications of Search: Location, network, name",None,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,36,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#representing-and-searching-provider-directory-data,"The Plan-Net design is based around the following types of searches….
+- Search: Organization by specialty
+- Example: Compounding Pharmacy
+- Focal Resource and Field: OrganizationAffiliation.specialty
+- Qualifications of Search: Location, network, name",None,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,37,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/implementation.html#searching-for-active-practictioners-and-organizations,"Sample query to search for currently active Practitioners (replace date in query with current date):
+http://davinci-plan-net-ri.logicahealth.org/fhir/PractitionerRole?_include=PractitionerRole:date=ge2021-10-25
+
+Sample query to search for currently active Organizations (replace date in query with current date):
+http://davinci-plan-net-ri.logicahealth.org/fhir/OrganizationAffiliation?_include=OrganizationAffiliation:date=ge2021-10-25",None,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,38,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/StructureDefinition-plannet-Network.html#implementation-guidance,"When the contact is a department name, rather than a human (e.g., patient help line), include a blank family and given name, and provide the department name in contact.name.text.",None,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,39,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/StructureDefinition-plannet-Organization.html#implementation-guidance,"When the contact is a department name, rather than a human (e.g., patient help line), include a blank family and given name, and provide the department name in contact.name.text.",None,Server,,,Not Verifiable,
+hl7.fhir.us.davinci-pdex-plan-net_1.1.0,40,http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/StructureDefinition-plannet-Practitioner.html#implementation-guidance,"When the value set for the coded concept in qualification is insufficient, the qualification can be provided in the text field of the codeableConcept.",None,Server,,,Not Verifiable,