InterSystems FHIR Server 2026 Release Notes

Previously, there was no mechanism for deleting a FHIR package, which complicated efforts to update to a newer FHIR package version. Now, it is possible to remove packages, which makes it possible to effectively update them.

The out-of-the-box configuration for the OAuth Client now integrates with additional known FHIR servers, most notably Epic, reducing the need for customization during implementation. Integration is achieved using utility functions, built in to clients, to wrap necessary functionality into methods that are invoked prior to the FHIR request being sent out.

The HTML5 path routing standard has been adopted for routing to all FHIR Server UIs, to avoid conflicts with OpenConnect OAuth2 authentication redirects to these UIs.

Because not all FHIR servers support the use of the _count parameter in patient $everything requests, some Bulk FHIR Patient/$export processes were taking unreasonable time to execute, eventually resulting in errors. Now, a new Bulk FHIR Configuration setting, "Paginate Resource Export," allows you to specify whether the target FHIR server supports _count, avoiding these delays and errors.

Previously, the Basic:subject reference was omitted as a valid _revinclude for MedicationKnowledge resources, causing certain API queries to return an error message. This has been fixed.

Previously, during upgrades, saving a Bulk FHIR configuration forced a metadata/capability statement refresh by reaching out to the FHIR server. During upgrades where the FHIR server resides on the same instance as the BFC, these metadata fetches would time out.

BFC configs now include an "is_inactive" toggle, which allows the following when set:

• Saving "partial" or "draft" states of incomplete BFC configs

• Deactivation or temporary disabling of a BFC endpoint without the need to delete the entire endpoint.

"is_inactive" will also be used during upgrades according to this algorithm:

• Upgrade code makes the changes to configs, saves

• If the specific error is failure to retrieve the target FHIR server's metadata endpoint, it will just ignore the error, and upgrade continues, using the current capability statement.

• For any other error, it will toggle the "is_inactive" flag on, and save the config as inactive. It will also add an entry to the upgrade log with the name and endpoint of the BFC config that failed to save. This is the catch-all case. This ensures that BFC config upgrades cannot fail - At a minimum they will get updated and saved as inactive.

Previously, the "New" button was missing from the FHIR SQL Builder UI. This has been fixed.

Previously, searches with _include and _revinclude involving canonical references could return incomplete results. This has been fixed.

Previously, the "Download Logs" button did not perform download. This has been fixed.

Previously, issues with date-time data types caused errors when using $expand. These issues have been corrected.

Previously, if the 'meta' property was absent from exported resources, the resources would not be stored successfully in the data repository. The 'meta' property is no longer required in exported resources, and exported resources are stored as expected.