Skip to content

Version 2.2.1 - Initial MHDv4.0.1 List support
Compare
Choose a tag to compare
@skbhaskarla skbhaskarla released this 24 Sep 17:52
· 352 commits to master since this release
v2.2.1
82ad5f9

The downloadable zip file contains NIST FHIR Toolkit v2.2.1 and NIST XDS Toolkit v7.7.0.
Installation information can be found here: https://github.com/usnistgov/asbestos/wiki/Installation-Guide-v2.2.x

Multiple MHD Version support
Channel configuration can be limited to certain MHD version(s). Test Collections are filtered based on the channel configuration and only those that meet the MHD version level are displayed. By default, channels are not restricted and all Test Collections are displayed. At the moment all existing tests from previous releases are available and three new Minimal Metadata Test Collection MHD v4.0.1 server tests are available. The three new tests are: 1) 1_Prerequisite_Single_Document_with_Binary, 2) Missing_DocumentReference_with_reference, and 3) Missing_SubmissionSetTypeList. More tests will be added in a future release.

PDB Validations
Inspector tool now has a drop to perform PDB Validations based on the MHD version. Click Inspect Request and select the PDB Validations drop down option. This feature only works if the request is an HTTP POST and has PDB content.

NIST FHIR(r) Toolkit (Asbestos) v2.2.1 Bug fixes and improvements:

#82 Upgrade HAPI...
#157 Tests for Document Addendum, Document Transformation
#159 MHD 4.0.1 Canonical URLs (Applies to MHDv4 Test Collections only)
#160 MHD 4.0.1 - DocumentManifest has been replaced by List (Applies to MHDv4 Test Collections only)
#161 Integrate XDS Toolkit v7.7.0
#163 Support multiple versions of MHD
#164 Java 9+ runtime support

Known Issues:

  1. Root directory README.html has an incorrect release number. The correct release number is v2.2.1. The installation guide also points to an older installation guide hosted on the GitHub project page. The older installation guide has been updated with a link to v2.2.1 to help navigate to the proper page. See #165.
  2. Do not restrict a channel to the MHDv3.x version in the channel configuration, there is a bug which will cause a null pointer exception when the channel receives a PDB. By default, channels are not restricted to a MHD version. So, not selecting the MHD3.x MHD version will simply use the bundle profile to determine the MHD version. See #174.
Assets 3
Loading