require_relative 'encounter/encounter_read_test' require_relative 'encounter/encounter_patient_search_test' require_relative 'encounter/encounter_id_search_test' require_relative 'encounter/encounter_identifier_search_test' require_relative 'encounter/encounter_class_patient_search_test' require_relative 'encounter/encounter_patient_status_search_test' require_relative 'encounter/encounter_patient_type_search_test' require_relative 'encounter/encounter_date_patient_search_test' require_relative 'encounter/encounter_provenance_revinclude_search_test' require_relative 'encounter/encounter_validation_test' require_relative 'encounter/encounter_must_support_test' require_relative 'encounter/encounter_reference_resolution_test' module USCoreTestKit class EncounterGroup < Inferno::TestGroup title 'Encounter Tests' short_description 'Verify support for the server capabilities required by the US Core Encounter Profile.' description %( # Background The US Core Encounter sequence verifies that the system under test is able to provide correct responses for Encounter queries. These queries must contain resources conforming to the US Core Encounter Profile as specified in the US Core v3.1.1 Implementation Guide. # Testing Methodology ## Searching This test sequence will first perform each required search associated with this resource. This sequence will perform searches with the following parameters: * patient * _id * date + patient ### Search Parameters The first search uses the selected patient(s) from the prior launch sequence. Any subsequent searches will look for its parameter values from the results of the first search. For example, the `identifier` search in the patient sequence is performed by looking for an existing `Patient.identifier` from any of the resources returned in the `_id` search. If a value cannot be found this way, the search is skipped. ### Search Validation Inferno will retrieve up to the first 20 bundle pages of the reply for Encounter resources and save them for subsequent tests. Each of these resources is then checked to see if it matches the searched parameters in accordance with [FHIR search guidelines](https://www.hl7.org/fhir/search.html). The test will fail, for example, if a Patient search for `gender=male` returns a `female` patient. ## Must Support Each profile contains elements marked as "must support". This test sequence expects to see each of these elements at least once. If at least one cannot be found, the test will fail. The test will look through the Encounter resources found in the first test for these elements. ## Profile Validation Each resource returned from the first search is expected to conform to the [US Core Encounter Profile](http://hl7.org/fhir/us/core/StructureDefinition/us-core-encounter). Each element is checked against teminology binding and cardinality requirements. Elements with a required binding are validated against their bound ValueSet. If the code/system in the element is not part of the ValueSet, then the test will fail. ## Reference Validation Each reference within the resources found from the previous tests must resolve. The test will attempt to read each reference found and will fail if any attempted read fails. ) id :us_core_311_encounter run_as_group def self.metadata @metadata ||= Generator::GroupMetadata.new(YAML.load_file(File.join(__dir__, 'encounter', 'metadata.yml'))) end test from: :us_core_311_encounter_read_test test from: :us_core_311_encounter_patient_search_test test from: :us_core_311_encounter__id_search_test test from: :us_core_311_encounter_identifier_search_test test from: :us_core_311_encounter_class_patient_search_test test from: :us_core_311_encounter_patient_status_search_test test from: :us_core_311_encounter_patient_type_search_test test from: :us_core_311_encounter_date_patient_search_test test from: :us_core_311_encounter_provenance_revinclude_search_test test from: :us_core_311_encounter_validation_test test from: :us_core_311_encounter_must_support_test test from: :us_core_311_encounter_reference_resolution_test end end