Keep up with latest product news
A clinician dashboard with AI triage questions that automate pre-checkup intake, built on InterSystems IRIS for Health.
QuestionnaireResponse%Embedding.OpenAI + VECTOR_COSINE)Encounter, SNOMED-coded ServiceRequest, LOINC/SNOMED Observations, and a Communication alert on escalationdocker compose up — boots IRIS, the agent, and the UI, and self-seeds demo data







Lowercased all the property names to work well with %JSON.Adaptor
LastUser->lastuser
CreatedAt->createdat
updatedat property introduced




Branch: main
This release resolves all issues identified during Open Exchange review and subsequent clean-environment validation. It includes fixes for the FHIR installation race condition, restoration of the runtime installation approach, and ObjectScript syntax compatibility improvements for non-interactive execution.
The original installation process executed:
HS.Util.Installer.Foundation.Install("FHIRSERVER")
followed immediately by:
HS.FHIRServer.Installer.InstallInstance(...)
Although Foundation.Install() starts the namespace/database creation process, it completes asynchronously through background jobs. On clean environments, the FHIR installer could execute before the FHIRSERVER namespace became available.
Fix:
Added an explicit polling loop to wait until the namespace exists before proceeding:
for {
quit:##class(%SYS.Namespace).Exists("FHIRSERVER")
hang 2
}
This guarantees that InstallInstance() only runs after the FHIR infrastructure is fully initialized.
An initial attempt to solve the race condition moved FHIR installation to Docker image build time.
During validation it was discovered that IRIS registers parts of the FHIR web application using the hostname present during image creation (buildkitsandbox). When containers later started with a different hostname, the /fhir/r4 endpoint became inaccessible and returned HTTP 404 responses.
Resolution:
The project returned to the runtime installation model while retaining the namespace readiness polling logic.
Changes:
docker-compose.yml
start.sh
README.md
config/iris/Dockerfile
Validation uncovered <SYNTAX> errors in:
config/iris/setup_fhir_post_install.sh
when ObjectScript was executed through:
iris session IRIS << 'EOF'
The original implementation used multi-line block syntax:
if condition {
...
} else {
...
}
This syntax is not reliably supported when commands are executed through stdin piping.
Fix:
Replaced block-style conditionals with equivalent single-line statements:
set fhirAppExists = ##class(Security.Applications).Exists("/fhir")
if 'fhirAppExists do ##class(Security.Applications).Create("/fhir", .props)
if 'fhirAppExists write "CSP application /fhir created",!
if fhirAppExists do ##class(Security.Applications).Modify("/fhir", .props)
if fhirAppExists write "CSP application /fhir already exists — updated.",!
This ensures compatibility across automated installation environments.
config/iris/install_fhir.txtconfig/iris/setup_fhir_post_install.shdocker-compose.ymlstart.shREADME.mdconfig/iris/DockerfileValidated from a completely clean environment:
docker-compose down -v
./start.sh
Results:
<SYNTAX> errors during installationGET /fhir/r4/metadata returns HTTP 200http://localhost:3000No manual migration steps are required.
For existing installations:
docker-compose down
docker-compose up -d
For a completely clean installation:
docker-compose down -v
./start.sh

