Skip to content

FHIR Packages and Profiles

This page tracks InterSystems support for FHIR profiles, conformance resources, implementation-guide packages, and capability statements.

User Interface

Add a FHIR Server dialog with namespace, name, FHIR R5, endpoint URL and Custom Packages selection.

Selecting endpoint packages. The Add a FHIR Server dialog includes a Custom Packages selector. This FHIR R5 example is from Luis Angel Pérez Ramos’s vendor-engineer tutorial, published 30 September 2025; the product build is unspecified. Package selection and profile validation remain separate operations. Select the image to open it at full size.

Supported Positioning

InterSystems documentation describes FHIR adaptations as profile and conformance-resource driven. Profiles are represented by StructureDefinition resources; other artifacts include SearchParameter, ValueSet, and CodeSystem resources; and implementation guides are commonly distributed as package-style collections.

Technical Shape

  • InterSystems FHIR endpoints can support FHIR packages of conformance resources, including more than one package on the same endpoint.
  • Package support controls what the server reports as supported and enables clients to search and use resources that claim conformance to the supported packages.
  • The documentation draws an important validation boundary: an InterSystems FHIR server does not automatically verify that an incoming resource conforms to a supported profile just because the client asserts that profile in resource metadata.
  • Supported-operations documentation adds that profile validation is currently designed to work with FHIR R4, with later releases targeting R5.
  • Clients can retrieve the server's CapabilityStatement through the endpoint metadata route to understand supported APIs, operations, search parameters, and resources.

Validation Configuration Boundary

The 2026-09-08 recheck confirms that the cloud operations documentation still describes R4-only profile validation and partial $validate support. It requires a profile snapshot; a request without an explicit profile checks the core resource schema. A successful core-schema check therefore does not demonstrate UK Core or GP Connect profile conformance.

IRIS for Health 2026.2 separately documents the FHIR_Validation_Server external server and Java 11 runtime configuration for profile validation. Its release notes add an optional structural-validation bypass for ingestion. Keep package installation, core structural checks, explicit profile validation, and the operation of the validation runtime separate in deployment evidence.

Evidence Status

Confidence is high for package/profile mechanics, the explicit non-automatic conformance-checking boundary, and the documented FHIR R4 profile-validation scope. This page is not proof that any specific UK national profile or GP Connect profile is installed, configured, validated, or assured in a customer deployment.

Remaining Follow-up Evidence

  • Product or deployment documentation naming specific UK FHIR packages, implementation guides, and validation settings.
  • Evidence for how profile conformance checking is handled in a named implementation.
  • Current GP Connect supplier or product documentation tying InterSystems endpoints to specific NHS profiles.