Summary
| Advisory ID | Product & Versions Affected | Risk Category & Score | Explicit Requirements |
| IF-9396 | InterSystems IRIS® for Health InterSystems Health Connect™ versions: 2026.1.0 | System Stability Concern: 3 | Deployments with non-default path-prefixes will not serve FHIR Server UIs. |
Issue
- Deployments do not serve FHIR Server, bulk FHIR, FHIR SQL, or associated security user interfaces when using a non-default path prefix. For example, when using logical path configurations with Windows IIS, Apache, or other web servers.
- The most common situation where this occurs is when installing multiple deployments with a single web server or when applying custom logical paths from their web server to serve product UI pages.
Impact Assessment
Impacted configurations are unable to interact with FHIR Server features from the product UI. Existing APIs, the Terminal, and ObjectScript methods are unaffected.
This can affect both InterSystems IRIS for Health and Health Connect deployments on all supported operating systems with configurations from supported web servers (IIS, Apache, and Nginx).
Resolution
- InterSystems is creating a set of point releases to correct this issue: InterSystems IRIS for Health 2026.1.0.2 and Health Connect 2026.1.0.2 with general availability for both InterSystems IRIS for Health 2026.1.0.2 and Health Connect 2026.1.0.2 on April 14, 2026.
For More Information
If you have questions or need assistance, please contact the InterSystems Worldwide Response Center (WRC).