#FHIR

#North American Demo Showcase entry. 

>> Answer the question below to be entered in the raffle!

⏯️ Message Operational Data Store

Create an operational data store using the data flowing through your production. Create user-defined analytics tables based on fields and paths to their data from incoming documents with varying standards (FHIR, CDA, HL7v2, etc.).

Presenters: 
🗣 @Kwabena Ayim-Aboagye, Sales Engineer at InterSystems
🗣 @Christopher Carmichael, Sales Engineer at InterSystems
🗣 @Jeff Semmens, Senior Sales Engineer at InterSystems

#North American Demo Showcase entry. 

>> Answer the question below to be entered in the raffle!

⏯️ Health Galaxy: AI-Enabling Healthcare Applications

Health Galaxy creates an AI access point on top of any FHIR server, bringing healthcare into the AI future that has become a reality for many other industries. 

• AI access: Health Galaxy gives AI agents a single gateway into any healthcare system, so they can pull patient data, schedule appointments, and check insurance automatically instead of a human doing it manually. 
• Ease of use: You point it at an existing FHIR endpoint, click a button, and it generates an MCP endpoint automatically from the capability statement. 
• FHIR: Since we are using FHIR, we can leverage both the storage and exchange capabilities of InterSystems IRIS.

🗣 Presenter: @Zelong Wang, Sales Engineer at InterSystems 

Hi Developers,

We are happy to announce the new InterSystems online programming contest:

🏆 InterSystems Programming Contest: AI Agents for FHIR🏆

Duration: May 25 - June 14, 2026

Prize pool: $12,000

I am working on setting up OAUTH with FHIR and Microsoft Entra.  I have configured the Client and configured it in the FHIR Server successfully. However, I get 401 when authenticating with a token.   Looking at ^ISCLOG I see:
^ISCLOG("Data",9,0)="accessToken=<jwt token>, scope=, aud="
^ISCLOG("Data",10)=$lb(3,"OAuth2","[OAuth2.ServerDefinition:ValidateJWT]","171430","%SYS","2026-04-28 17:41:25.305549397","OAuth2.ServerDefinition.1","","zwKKakZZZx2")
^ISCLOG("Data",10,0)="JWT valid? sc=1"
^ISCLOG("Data",11)=$lb(3,"HSFHIRServer","[HS.FHIRServer.

In v2026.2 (currently available as a Developer Preview), we are adding a feature that can help in a FHIR Endpoint SMART/OAuth authorization - more out-of-the-box flexibility in audience value validation.

Hi, Community!

Are you gathering data for clinical research? See how InterSystems OMOP can help streamline your data preparation:

Using InterSystems OMOP to Transform FHIR Data

A very important feature for HL7 FHIR has been introduced with the release of v2026.1 - the support for SMART on FHIR v2 fine-grained granular Scopes.

This enables you to be much stricter and more accurate in the access you provide to the data in your FHIR repository.

Part of this new support is to refuse requests that don't match the scopes, but an even more interesting ability is to filter the results according to the provided scopes.