MHD Release Notes 5.0

MHD Testing Release Notes 5.0

Upgrade to toolkit.properties

There is a new required property that controls the port used by the Proxy:

Proxy_Port=7297

Test Support for MHD actors

In the 5.0 release support is included to test the following actor configurations.

MHD Document Source - Provide Document Bundle transaction with Comprehensive Metadata

MHD Document Recipient/Responder with Comprehensive Metadata

• Provide Document Bundle transaction

• Find Document References transaction

• Retrieve Document transaction

• Testing is limited to implementations that offer both Recipient and Responder at one FHIR Base Address.

Secure connections not yet supported

ITI-66 Find Document Manifests is not yet supported

Some attributes are not translated from the Provide Document Bundle to Provide and Register transactions:

• hash

• languageCode

• legalAuthenticator

• sourcePatientInfo

• referenceIdList

Patient Resource server offers a very limited set of search terms

These capabilities will be expanded in future releases.

Known Bugs

Provide Document Bundle followed by FHIR READ of the Binary resource shows an size error of 1 for PDF document types. No error for text types. Not sure if the problem is in the client or the server.

Coding

Codes are translated in the combined MHD Document Recipient/XDS Document Source. The need for this translation has forced an upgrade to the codes.xml file format. The most important change is the adding of a system attribute. For a particular code, the code value is the same for XDS and MHD. In the above translation expects a coded value with code/system (MHD) and translates it to code/codingScheme (XDS). This also provoked a cleanup of the content of codes.xml.

Some users will not easily transition to the new codes.xml file content because it may be missing some codes it had before. To make the transition easier, toolkit now ships with two codes.xml files. The new/upgraded form (and content) is in the “default” environment. The old form and content is included in the “alternate” environment. To get these installed in your external cache, delete the environment directory in your external cache and restart tomcat which forces a full restart of toolkit. The missing environment directory will be noticed on start up and the updated version will be installed.

If the new version in default causes you problem you can switch to the alternate environment in the GUI or just move files in the external cache/environment/. Note that the simulators do not look to the external cache for codes.xml. They look to the toolkit internal copy at toolkitx/environment. So if you need to back out or change the codes reference used by simulators you need to alter this copy as well.

Major Deficiencies of this release

• No query tool

• No server support for Find Document Manifests

• Support for Minimal Metadata (on Comprehensive Metadata option for now)

• Document Recipient and Document Responder are combinded and need to be split