HealthRecordCommunity
FHIR🌏 International🏛 InterSystemsEnriched

IRIS for Health FHIR Repository Stops Responding After Upgrade and How to Fix It

IRIS For Health FHIR Repository stops responding after upgrade to

The IRIS For Health FHIR Repository encountered operational issues following an upgrade to version 2023.6.1.

May 23, 2025InterSystems

Summary

InterSystems discovered that its FHIR repository started returning an Error 500 after migrating to a new container-based environment. The issue was traced back to PROTECT violations in specific namespaces, which were resolved by modifying Web Application settings and implementing token retrieval logic.

Key Players

IRIS For HealthFHIR

Details

InterSystems encountered an issue where the FHIR Repository began responding with an Error 500 after rolling out a new container based on `containers.intersystems.com/intersystems/irishealth:2023.1`. The root cause was identified as PROTECT violations within the new HSSYSLOCALTEMP namespace and database used by the FHIR components. While an initial fix involved adding “%DB_HSSYSLOCALTEMP” to the Web Applications handling FHIR requests, custom code required access to the JWT Bearer token from the client's `AdditionalInfo` element (

Technology Note

FHIR(Fast Healthcare Interoperability Resources)は医療データ交換の国際標準。このエントリの関連技術: FHIR

📰
Read Original Article
community.intersystems.com
→

Original content copyright by respective publishers