skills.rest
intersystems-community
intersystems-communityOFFICIAL
Explore all skills by this author →
WebsiteGitHub

irishealth-container

Configure IRIS Health and AI Hub container web server paths for Atelier REST.

27|10|Updated Apr 21, 2026
Search Tags:#docker containers#webgateway#intersystems irismod#FHIR R4#atelier REST#VSCode ObjectScript extension#IRIS health ai hub
One-click install
npx skills add https://github.com/intersystems-community/iris-agentic-dev --skill irishealth-container
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: irishealth-container
Source: https://github.com/intersystems-community/iris-agentic-dev/tree/main/light-skills/skills/irishealth-container
Command: npx skills add https://github.com/intersystems-community/iris-agentic-dev --skill irishealth-container

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents connection failures when you need to use IRIS Health (FHIR R4) and/or IRIS AI Hub containers with Atelier REST and the VSCode ObjectScript extension, especially when container editions differ in web server support.

Core Features & Use Cases

  • Web server edition split diagnostics: Ensures you route traffic to the correct port (52773 private web server) or through the required webgateway sidecar when Enterprise images disable the private web server.
  • VSCode ObjectScript extension configuration: Aligns extension settings (webServer host/port/pathPrefix, credentials, namespace) with Docker port mappings so the extension can talk to Atelier REST.
  • FHIR R4 container setup guidance (no ZPM, no network): Uses the pre-baked installation approach for the Health Share FHIR R4 endpoint and verifies readiness and resource availability.
  • Two-container architecture for AI Hub vs FHIR HTTP: Separates the health container (FHIR over HTTP) from the AI Hub container (AI services via DBAPI) to cover the different port/service capabilities.

Quick Start

Ask your AI assistant to help you configure VSCode ObjectScript to connect to Atelier REST using the correct container edition and port mapping for your IRIS health container.

Frequently Asked Questions about irishealth-container

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure VSCode ObjectScript to connect to Atelier REST on an IRIS health container?▼

Configure VSCode ObjectScript by aligning the extension's webServer host, port, pathPrefix, credentials, and namespace settings with your Docker port mappings to establish a reliable Atelier REST connection to the IRIS health container.

Why does my IRIS health container return a 404 or 403 error when accessing FHIR R4 endpoints?▼

FHIR R4 404 or 403 errors often occur due to incorrect web server path selection or missing CSP.ini configurations. Enterprise editions may disable the private web server on port 52773, requiring a webgateway sidecar to route traffic correctly.

Do I need a separate webgateway container for Enterprise IRIS health containers?▼

Yes, Enterprise IRIS images disable the private web server, requiring a webgateway sidecar to route traffic. Community editions include a private web server on port 52773, allowing direct local Docker access without an additional webgateway container.

How do I set up IRIS AI Hub and FHIR R4 HTTP capabilities in Docker containers?▼

Split AI Hub and FHIR R4 HTTP capabilities across two separate containers. Use the health container for FHIR over HTTP and a dedicated AI Hub container for AI services via DBAPI to cover the different port and service capabilities.

What causes a 500 error when connecting to IRIS AI Hub containers?▼

A 500 error when connecting to IRIS AI Hub containers usually indicates incorrect post-start configuration or Docker port mapping validation failures. Verify the specific post-start requirements and CSP.ini settings to ensure the AI Hub service is ready.

Can I use the pre-baked FHIR R4 installation without ZPM or a custom network?▼

Yes, you can use the pre-baked installation approach for the Health Share FHIR R4 endpoint without ZPM or a custom network. This setup verifies readiness and resource availability directly within the IRIS health container configuration.

Related Skills

Explore More Software Engineering Skills→
blockblock
49

docker-compose-dev

Orchestrate Proto Fleet development with Docker Compose base and override files.

Official
Intermediate
JinLee794JinLee794

azure-fhir-developer

Develop HL7 FHIR R4 applications on Azure with authentication and coding systems.

Community
Advanced
intersystems-communityintersystems-community
27

iris-vscode-objectscript

Configure VSCode ObjectScript development against InterSystems IRIS via Atelier REST.

Official
Intermediate
santoosaraujosantoosaraujo

mootdx

Fetch A-share OHLCV, intraday bars, and real-time quotes via TCP.

Community
Intermediate