Skip to content

Release v1.1.4 and support for validator v1.0.79#294

Draft
karlnaden wants to merge 1 commit into
mainfrom
validator-v1.0.79-filters-for-5.0.1
Draft

Release v1.1.4 and support for validator v1.0.79#294
karlnaden wants to merge 1 commit into
mainfrom
validator-v1.0.79-filters-for-5.0.1

Conversation

@karlnaden

Copy link
Copy Markdown
Contributor

Summary

This PR includes release v1.1.4 including additional filters for the US Core Server v5.0.1 suite that address regressions introduced by the upgrade to validator version 1.0.79, specifically around the birthsex value set. The added filters remove errors related to valid codes, so only conformant system will continue to pass the v5.0.1 tests. All other US Core versions are unaffected.

Testing Guidance

The following instructions use the CRD Server v2.2.1 test suite's mock EHR capability to verify this functionality.

  1. Start a Da Vinci CRD Server v2.2.1 Test Suite session on inferno.healthit.gov
  2. Select the "Run Against the CRD Client Suite" preset.
  3. Run Group 1 "Discovery"
  4. Get an access token by running Group 2 "Hook Response Demonstration" without any changes to the inputs. Open the details for the request associated with Test 2.2.1 "Service request contains required fields" and pull out the "access_token" from the request body (will be a long base64 url encoded string). Save it for later use.
  5. Run Group 2 "Hook Response Demonstration" a second time with the following changes to inputs"
    • Require acknowledgement of completed hook requests?: select "Continue on user acknowledgement"
    • Mock EHR Data: use the Bundle provided below, which includes patients with all valid codes from the birthsex value set as well as an invalid code and some related resources.
  6. Once that test is waiting for requests, start the US Core test kit locally (including services) and create a US Core Server v5.0.1 session.
  7. Run Group 2.2 "Patient Tests" with the following inputs
  8. Run Group 2.3 "AllergyIntolerance Tests"
  9. Inspect the results:
  • Test 2.2.10 should FAIL with 3 errors related to the code "BAD". No other errors related to codes "M", "F", "ASKU", "OTH", or "UNK" should be present (though there may be some warnings)
  • Test 2.3.07 should PASS, indicating that errors were filtered during this check as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant