Version 5.0 Release Notes

Version 5.0 Release Notes

This covers the general release notes. For MHD release notes see MHD-Release-Notes-5.0.

New system selection display This is part of Find Documents/Get Documents/Retrieve style tools. The expanded offering of actor/transaction/option types has forced a new implementation of this selection mechanism.

New experimental system selection display for FHIR This is used in the new Submit Resource tool and the upgraded Simulator Log Viewer All systems are always shown (view does not change when selecting/de-selecting TLS) Each system represented by a toggle button Selected system is highlighted This new style is being evaluated and its use may be expanded in the future

New Simulator Log viewer UI Now has a new Look and feel. MHD Support has been added. Request Header, Request Body, Response Header, Response Body, and Log are now selectable as sub-tabs. XML and JSON are displayed pre-formatted. Bundle display includes display of index of components of the bundle and listing of References.

New Simulator Manager UI Now has a new display style. Multiple actors can be selected and deleted together. More detail is available in the display.

Upgraded Inspector UI Added advanced options tab where: metadata objects can be sorted by key attributes and the metadata attribute list for two objects of the same type can be displayed side-by-side.

New Conformance Test summary page A new display is presented when you first open the conformance tool. It can be navigated to from within the conformance tool using the three-bar icon in the upper left corner. Results are organized by Actor/Profile/Option in a grid display. Each Actor/Profile/Option combination is a point in the grid. Each combination shows a summary of untested/successful/failed tests as a three color bar. Red/green/white are used for failures/successes/untested tests - same colorization as rest of the tool. Clicking on an Actor/Profile/Option point navigates to the test collection.

Conformance Tool Tests are now organized in a hierarchy by Actor/Profile/Option. Support has been added for testing “source” actors, those actors that start their work by initiating a transaction. Tests for these actors have no “run” button. Instead they have a “validate” button with a different icon. Opening the conformance page for this actor/profile/option creates the necessary server(s) and publishes the endpoints. You use your system (the system under test or SUT) to send to these endpoints. After sending from your client, push the validate button and all the tests listed will validate recent inputs to see if they meet their requirements. Tests that turn red tell you that no transaction was found in the logs meeting the requirements of the test. If you open up the test, it will list the evaluation rules that were run and tell you what was missing or wrong. A future update will enable you to insert a marker in the logs. The significance of a marker is that all evaluations only look back to the most recent marker. This more easily allows you to update your software and try again without seeing the results of earlier efforts.

A reverse proxy has been added. See the MHD Release notes and MHD Testing Architecture sections for details.

New Submit Resource tool This is similar to the existing XDS submit tools. This tool allows the selection of a stock resource installed in toolkit and a FHIR server to send a CREATE operation to. In the case of PDB (MHD Provide Document Bundle) the tool sends a bundle/transaction.

The content for this tool resides in the External Cache in a directory named datasets. Inside that directory is a hierarchical structure:

datasets/
    set 1/
       resource type/
         xml or json files
       resource type/
         xml or json files
    set 2/

Any number of datasets can be installed in this directory. When version 5.0 toolkit is first launched it will create the datasets directory and populate it with some sample data. You can add your own.

Each “set” is an arbitrary collection of content. Future testing efforts will add data sets and you can create your own.

Within each dataset, each directory name identifies a resource type.

Inside the resource-named directories are XML or JSON files each containing a single resource of that type.

To use this tool, select a FHIR server (must be configured as a system in toolkit), navigate the content hierarchy in the UI (structured the same was as the above storage layout) and press the submit button. Log output will be presented. Also, once a resource is selected its source (JSON or XML) can be displayed in the tool.

Updated codes.xml file format FHIR uses a slightly different approach to coding. Instead of referring to code systems as an OID, FHIR uses a URI. To accommodate this each <Code> element in codes.xml has an added system attribute to carry this URI. There is also a deprecated attribute that will be used in the future.

You may or may not want to use the new format file. On toolkit startup it scans your External Cache. If it sees no environment directory then two environments are installed, default and alternate. The default environment codes.xml is in this upgraded format and contains what we believe are the proper translations (thank you to Steve Moore for providing the translations). The alternate environment contains the codes.xml file used last year. Both environments contain last year’s certificate.

If you do not want to use the new codes.xml file you need to take the following steps:

• Move/copy alternate/codes.xml to default/codes.xml in the External Cache.

• Move/copy alternate/codes.xml to default/codes.xml inside the toolkit war (toolkitx directory). This location is used by simulators instead of the external cache.

MHD testing facilities in toolkit depend on this upgraded codes.xml file and it will be used in the Cleveland Connectathon.

Bug Fixes MANY!

Coming in version 5.1

• Additional tooling to support MHD testing at Connectathon.

• New test suites for XPID and Metadata Update.

• Additional MHD tests and expanded facilities as time permits.