#HealthShare

HealthShare Unified Care Record Fundamentals – In Person* June 22-26, 2026

*Please review the important prerequisite requirements for this class prior to   registering.

• Learn the architecture, configuration, and management of HealthShare Unified Care Record.
• This 5-day course teaches HealthShare Unified Care Record users and integrators the HealthShare Unified Care Record architecture and administration tasks. 
• The course also includes how to install HealthShare Unified Care Record. 
• This course is intended for HealthShare Unified Care Record developers, integrators, administrators and managers.

Hello,

Looking for some additional help, maybe someone who has experience with this before, in setting up and configuring the Web Gateway with Kerberos.

Have read through the documentation (at the link below) and it's a good start but seems there are some details missing, or I'm not clear on. 

Questions: 

• Is there a external enterprise Kerberos server required, or is this set up contained within the local server?
• Is there a step-by-step instructions on what to do and configure to successfully complete this?
• Are there there config changes necessary for Apache?

Hi Community,

In traditional InterSystems SQL, I can use the %NOINDEX keyword during a bulk INSERT to improve performance and then run BUILD INDEX %ALL afterward to populate the indices.

I am looking to implement a similar strategy for an InterSystems FHIR Server.

1. Is there a way to import/save FHIR resources while skipping the search table extraction (the FHIR version of %NOINDEX)?
2. Once the data is loaded, what is the correct programmatic way to "rebuild" the search tables?

Thank you!

Hi Community,

Interoperability metrics were enabled for a production using ##class(Ens.Util.Statistics).EnableSAMForNamespace(). However, after running DisableSAMForNamespace() and DisableStatsForProduction(), the metrics continue to appear in the endpoint output.

Is there a way to completely stop these interoperability metrics from displaying in the API metrics stream? Is there an additional step or cache clear required?

Good afternoon,

I have received a WSDL.

I have imported it successfully in HealthShare.

The external is requesting me to send messages with the following structure (using the auto-generated SOAP Bussiness Operation from the WSDL), as you see they need a custom http header titled "Appian-API-Key", as the following:

            curl --request POST \
              --url [ endpoint ] \
              --header 'Appian-API-Key:  << API KEY >> \
              --header 'Content-Type: application/xml' \
              --data '<?xml version='\''1.0'\'' encoding='\''utf-8'\''?>
            <soapenv:Envelope xmlns:soapenv='\''http://schemas.xmlsoap.org/soap/envelope/'\''>
              <soapenv:Body>
                <tns:acceptMessage xmlns:tns='\''http://ws.connectors.connect.mirth.com/'\''>
                <![CDATA[  Message  ]]>
                </tns:acceptMessage>
              </soapenv:Body>
            </soapenv:Envelope>'

Over the years, we keep monitoring Orphan Messages, and I have begun to notice the number of ACK/NCK's that do not match the Scheme in which the message was sent so it can't not align or signify that the message was OK. For example, if we send an ADT^A08 HL7 message to the vendor, and they send back a A08 instead of an ACK as the message type.

Currently our default is to have Save Replies on EnsLib.HL7.Operation set to IndexNotOk's.

Hi Community,

Stay ahead with content relevant to your role and goals with the InterSystems Learning Services newsletter!

See how to customize your journey! 👇

Hi!
We are deploying the iris image in a Kubernetes environment and the cluster state is "Hung" , looking the alerts endpoint we get 2 alerts:

[
  {
     "time":"2026-03-24T13:45:44.548Z",
     "severity":"2",
     "message":"System appears to have failed over from node a69a9f137593"
  },
  {
     "time":"2026-03-24T13:46:30.274Z",
     "severity":"2",
     "message":"Error: <PROTECT>KillAlive+1^%SYS.CDIRECT in SERVERS"
  }
]
Any idea / help where those are comming from and how to address them?

I have a daily service that consumes x number of files, each file name chronologically suffixed sequentially by _1, _2, etc. I only want to process the latest file.

How do I build a business rule so it will only process the last file?

READY is right around the corner, and this year the Application Services team from InterSystems will be hosting a CCR Users GroupMeeting during the conference!This will be held Wednesday, April 29^th during breakfast from 7:30 – 8:30 (breakfast will be served at the meeting room starting at 7:00am).

Introduction

In healthcare interoperability environments, InterSystems Health Connect typically contains critical components such as productions, business processes, operations, services, utility classes, routines, and other ObjectScript artifacts. Traditionally, many deployments of these components have been done manually, by copying classes, importing XML, or using administrative tools from the management portal.

Was wondering if anyone had a Dynamic way to see if a Global is still being used by a Class File. 

We have been monitoring our Global Size recently, and I am trying to find problematic Class files that are not being cleaned up or used appropriately. I have come across some globals that do not seem to have a Class attached to them anymore, and instead of deleting globals 1 by 1, I was looking for a way that we could dynamically do this since the globals have data that is stale in them.

Thanks

Scott

• HealthShare Unified Care Record Overview – Virtual  May 19-20, 2026
  • Overview of HealthShare Unified Care Record® architecture, data flows, consent, and notifications
  • This 2-day course provides an overview of HealthShare Unified Care Record®. It focuses on architecture, data flows, consent, alerts, user management and terminology.
  • This non-technical course provides an introduction to the product for those who do not need the detail provided in the 5-day HealthShare Unified Care Record Fundamentals class.

READY is right around the corner, and this year the Application Services team from InterSystems will be hosting a Embedded Git Users GroupMeeting during the conference!This will be held Thursday, April 30^th during breakfast from 7:30 – 8:30 (breakfast will be served at the meeting room starting at 7:00am).

We are very excited to launch a new AI powered CCR feature which should help our users save time and prevent calls to Support.  Today we are introducing the new CCR Transport Log Analyst (or CTLA) AI-Generated summary.  The goal of CTLA is to provide an analysis of errors that have occurred in the Transport Log for a specific CCR, and advise the user as to what steps could be taken to correct the situation, as well as what might have been done to prevent it in the first place. When there is an issue with integrating or deploying a CCR, all of the details are captured in the Transport Log.

• InterSystems EMPI (formerly HealthShare Patient Index) – Virtual  May 12-14, 2026
  • Configure, tune, and work with InterSystems EMPI, an Enterprise Master Person Index
  • This 3-day course teaches the installation, configuration, and use of InterSystems EMPI™ (formerly HealthShare® Patient Index). Starting with version 2025.1, HealthShare Patient Index has been renamed to InterSystems EMPI, but the core functionality remains the same.
  • The first half of the class focuses on person identification issues and the tools for reviewing records and record matches.

The 2026.1 release of InterSystems IRIS® data platform, InterSystems IRIS^® for Health, and InterSystems Health Connect™ is now Generally Available (GA). This is an Extended Maintenance (EM) release.

Hi Community,

Take a look at these new videos in online learning, and get familiar with new features and interfaces in the latest release of InterSystems® products. All videos are also available in the Learning Services YouTube channel.

Plus, check out a video for new ObjectScript developers, and a guide for HealthShare® users upgrading their deployments.

• Goal: Learn about enhancements to the interoperability UI in version 2026.1 of InterSystems products.