Skip to content
This repository has been archived by the owner on Jan 23, 2024. It is now read-only.

Inferno Program Edition v1.6.0
Compare
Choose a tag to compare
@arscan arscan released this 12 May 15:14
· 173 commits to main since this release
v1.6.0P
cec401e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

The Inferno Program Edition v1.6.0 release contains test updates that reflect additional guidance provided in the 2015 Cures Update CCG v1.4, as well as a number of updates to tests based on bug reports and community feedback. This release may result in some systems that previously passed to now fail due to additional search tests.

Notice: This release migrates to an alternate data persistence library because the previous library is no longer maintained. This library uses a different database schema, and therefore users that upgrade Inferno in the same directory will not have access to previous test results after upgrading to v1.6.0.

Updates in this version include:

  • Include checks for POST-based searches, in addition to the existing checks for GET-based searches, because support for POST-based searches is required in the base FHIR specification. This update may cause systems that previously passed to now fail.
  • Update the "Limited Scope" tests to no longer require the system under test to demonstrate the ability to deny "offline_access" scopes, as clarified in the CCG update.
  • Update language in the "Visual Inspection and Attestation" test to clarify that the system under test needs to inform the user when "offline_access" scopes are being granted.
  • Allow systems to use "user-level" scopes for non-Patient compartment, non-USCDI resources in the "Standalone Patient App" tests, as clarified in the CCG update.
  • Fix issue where entering a Implantable Device Type Code would cause a search test to incorrectly fail systems.
  • Fix issue where the Multi-Patient tests would incorrectly fail systems that included charset or other additional information in the Content-Type header.
  • Enable the ability to use Postgres by configuration when deployed in a shared environment for increased stability. Please review the README for information on how to enable this configuration.
  • Migrate from DataMapper to ActiveRecord because DataMapper is no longer maintained and is not receiving security updates.
  • Migrate to Ruby v2.7 and update the versions of many of the libraries being used in Inferno.
Assets 3