Skip to main content

Upgrading Health Connect

Because Health Connect 2019.1 and later is powered by InterSystems IRIS, the process for upgrading Health Connect to a new major release or maintenance release is similar to upgrading the underlying InterSystems IRIS technology. Though all the steps may not apply to your Health Connect implementation, you should follow the upgrade process found in Upgrading InterSystems IRIS.

If you are upgrading from Health Connect 15.03 to Health Connect 2019.1 or later, see Upgrading from Health Connect 15.03.

Post-Upgrade Steps for Pre-2021.1 FHIR Endpoints

If you are upgrading from a version prior to 2021.1, the following steps that may be required depending upon on how you have customized your FHIR server. Perform these tasks in the following order:

  1. If your FHIR server uses custom subclasses, you must modify your architecture subclasses.

  2. If your FHIR endpoint uses custom search parameters, migrate them to a FHIR package and apply them to the endpoint.

Once you have completed these steps you can re-index the search tables.

Step 1: Modifying Architecture Subclasses

As part of the FHIR architecture that was introduced in Health Connect 2020.1, you can use a custom InteractionsStrategy to implement a custom FHIR server. If your FHIR server’s endpoint uses a custom InteractionsStrategy, including if it uses a subclass of the Resource Repository, complete the following steps:

  1. Complete the upgrade of your Health Connect instance.

  2. Using your IDE, do one of the following in your endpoint’s namespace:

    • If the InteractionsStrategy of your endpoint extended the Resource Repository (HS.FHIRServer.Storage.Json.InteractionsStrategy), create a subclass of HS.FHIRServer.Storage.Json.RepoManager.

    • If the InteractionsStrategy of your endpoint subclassed HS.FHIRServer.API.InteractionsStrategy directly, create a subclass of the HS.FHIRServer.API.RepoManager superclass.

  3. Add the following parameters to your subclass of the Repo Manager:

    • StrategyClass — Specifies the subclass of your InteractionsStrategy.

    • StrategyKey — Specifies the unique identifier of the InteractionsStrategy. This must match the value of the StrategyKey parameter in the InteractionsStrategy subclass.

  4. If your InteractionsStrategy subclass included custom code for the methods that manage the Service, you must move that logic to the new methods in the Repo Manager subclass that you created. Specifically, you must move custom code from the Create, Delete, Decommission, and Update methods to the corresponding methods in your Repo Manager subclass (CreateService, DeleteService, DecommissionService, and UpdateService ).

Re-Indexing Search Tables

Re-index any search tables that require it:

  1. In the Management Portal, navigate to Health > myFHIRnamespace > FHIR Configuration.

  2. Select the Server Configuration card.

  3. For each existing endpoint, select Reindex Now.

  4. When prompted, click Select All, and then select Reindex.


    This step may take some time to complete.

Upgrading from Health Connect 15.03

Health Connect 2019.1 was the first release of Health Connect that is powered by InterSystems IRIS. Because of this change in underlying technology, a special upgrade procedure is required when upgrading from a previous version of Health Connect. If you are upgrading to Health Connect 2019.1 or later from Health Connect 15.03, see the InterSystems IRIS In-Place Conversion Guide, which is available from the InterSystems WRC DocumentsOpens in a new tab page.

FeedbackOpens in a new tab