#FHIR

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.

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.

#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