What is wrong with the *inc file code below:

#define ArrayToString(%array,%out,%del)      set %out="" for { ##continue
                                                                                   set key=$order(%array("")) quit:key="" ##continue
                                                                                   set %out=%out_%del_key ##continue
                                                                               } quit

Compilation at calling classmethod as : Set tQStr = $$$ArrayToString(pQArray,tQStr,"##") brings error as:

I need to analyse and improve the performance on some old SQL statements.

One statement uses NVL in the WHERE clause (no wonder why it's slow) but I still have to improve the performance and the data really needs to be the same when returned.

SELECT *
FROM TOURHead, TOURFIND, SGNRFIND, TNRHead
WHERE TOURHead.cl = '123'
AND TOURHead.cl = TOURFIND.cl
AND TOURHead.TOURNR = TOURFIND.TOURNR
AND TOURFIND.cl =* SGNRFIND.cl
AND TOURFIND.SGNR    =* SGNRFIND.SGNR
AND TOURFIND.cl = TNRHead.cl
AND NVL(TOURFIND.TNR, SGNRFIND.TNR) = TNRHead.TNR;

Really hope someone can help me with this one.

I want to develop a REST API for uploading PDF files. I started with OPENAPI spec file. When I test, I get error 8727 referencing missing required parameter file.

"{"$c(13,10,9)"""errors"":[ {"$c(13,10,9,9,9)"""code"":8727,"$c(13,10,9,9,9)"""domain"":""%ObjectErrors"","$c(13,10,9,9,9)"""error"":""ERROR #8727: Parameter required: file."","$c(13,10,9,9,9)"""id"":""RESTRequired"","$c(13,10,9,9,9)"""params"":[""file"""$c(13,10,9,9,9)"]"$c(13,10,9,9)"}"$c(13,10,9)"],"$c(13,10,9)"""summary"":""ERROR #8727: Parameter required: file.

The recently published tutorial "Introduction to InterSystems Data Studio" inspired me to check out this product. And I think it’s an interesting look at how to manage a data fabric without deep-diving into complex code. It allows you to connect disparate data silos, transform the data through automated pipelines, and load it into a unified environment for analysis. So, I decided to write up an example of how you can use it. Basically, I'll walk you through the tutorial in case you don't have time to do it on your own. Though I would definitely suggest you actually follow the tutorial - it has lots of useful information.

To see how it works, I stepped into the shoes of a system administrator, logging in with the provided credentials to explore the interface. The layout centers on a few core pillars: defining where data comes from, cataloging its structure, and building automated "recipes" to move it into production.

And the very first step is to establish a connection to my data. 

Data privacy regulations such as GDPR, LGPD, and HIPAA demand that organizations know exactly where Personally Identifiable Information (PII) lives inside their databases. Yet in practice, most teams rely on manual inventories, tribal knowledge, or external scanning tools that require data to leave the database engine — a process that itself creates privacy and security risks.

This article presents an MVP that takes a different approach: it runs PII detection inside InterSystems IRIS using Embedded Python, analyzing data where it lives and never exporting it to an external process.

Sorry for the weird question, but mumps skills are very rusty.

Am trying to create globals dynamically, but with using names from an array. For example: 

S Names="A,B,Y,Z"
S A=$L(Names,"$")
F I=1:1:A D
//Create globals based on names from database
//^A,  ^B,  ^Y, ^Z etc..  

Hi Everyone,

We are looking for a way to disable production Business Services concurrently so that the whole process takes shorter amount time than just going sequentially in a loop and disable them one at a time (very slow). This is necessary for us to be able to stop all traffic to IRIS so that no data remains after we perform full production stop. 

Thank you!   

Many organizations that operate systems built on legacy technology stacks are facing significant support and maintenance complexities. They are eager to modernize, but the transition is usually prohibitively complex and expensive. These challenges apply to virtually any legacy tech, while InterSystems-based systems have their own unique nuances.

Key modernization challenges include:

• Refactoring massive amounts of code, including identifying and removing obsolete "dead code."
• Managing complex business logic accumulated organically over decades.

Hi everyone,

I’m thrilled to share that after several years of deep diving into the InterSystems IRIS data platform, I have finally summarized my project experiences into a new book IRIS (Data Platform) Programming Technical Guide. It is published by Beihang University Press, a prestigious central-level comprehensive publisher renowned for its leading role in aerospace, science, and technology publishing.

Writing this book was a significant engineering challenge for me. My goal was to bridge the gap between "understanding the syntax" and "building a production-ready project.

What was your READY experience like? 🎉
We’ve put together a bingo card — check out how many squares match your experience!

Mark the moments that happened to you or share them in the comments below.
And if you had a memorable READY moment that’s not on the card, tell us about it — we’d love to hear your story ✨

Hello, community.

I've been working with Intersystem Caché for two years, and right away I was excited about the rich ecosystem that Caché provides. However, I was disappointed with calls using #call, and I understand that it was a limitation of the time. Well, the frustration is that #call returns null by default, meaning an AJAX request is executed, but there's no hook to retrieve the return from that request. The only way to retrieve the data from that request is by building a callback on the server side using &js<>.

#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 

#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!

⏯️ AI Assistants for the Unified Care Record Powered by Gemini

In this demo, you will see how Gemini works directly with FHIR data, and how it leverages the harmonized dataset provided by InterSystems Unified Care Record. It also showcases multiple AI assistants helping multiple groups of users, e.g. clinicians, patients.

🗣 Presenter: @Simon Sha, Sales Architect at InterSystems

#North American Demo Showcase entry. 

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

⏯️ HL7 Validation Error Profiler: Rapid Insights into Batch HL7 Data Quality Issues

This demo highlights how HL7 validation logs can be transformed into scalable, actionable data quality insights using a lightweight application built on top of Health Connect.

• Batch ingestion and parsing of HL7 validation error logs into structured data
• Aggregation of errors by segment, field, and type to reveal systemic issues
• Interactive dashboard (Streamlit) for filtering, exploration, and root cause analysis
• Rapid identification of top error patterns across entire data feeds
• Natural language chatbot for intent-driven data investigation and querying
• PDF report generation for sharing clear, evidence-based feedback during data source onboarding 

Special thanks to @Henry Wojnicki for his contributions to designing and refining the application workflow.

🗣 Presenter: @Lynn Wu, Sales Engineer at InterSystems

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.

In our previous article, we explored the basics of unit testing in IRIS and the ways to apply it to a REST API. We even figured out how to test logic before finalizing network configurations and authentication, allowing us to focus solely on testing the API contents. Today, we will build upon that foundation and elevate our unit testing strategy by using another tool: %Populate .

At first glance, the %Populate class appears to be very simple. You can create a class that extends both %Persistent and %Populate and inherit a Populate method designed to generate randomized records.

For those of you that weren't at READY last week, you may have missed the exciting announcement that the Early Access Program for AI Hub is officially open. It was announced during an amazing demo from @Benjamin De Boe and @Jeff Fried, I recommend catching up with this demo when the recording is released!  I had the opportunity to play with AI Hub in advance, and thought I might share an introduction with the community.

Hi everyone,

I'm working on a requirement to generate and export medical reports to PDF using Logi Reports. The core requirement is that each generated PDF must be encrypted (password-protected), and the password needs to be dynamically set to the specific Patient's Date of Birth (DOB).

Currently, the report is populated using a Stored Procedure as its data source.

My questions are:

1. Is there a built-in way or API in Logi Reports to dynamically set the PDF export password using a field returned from my dataset (e.g., taking the Patient_DOB column from the Stored Procedure)?

#North American Demo Showcase entry. 

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

⏯️ AI-Assisted Rare and Complex Disease Detection

This demo shows how InterSystems Health Gateway can be used to pull in outside patient records from networks like Carequality, CommonWell, and eHealth Exchange, creating a more complete longitudinal view in a clinical viewer. That full record is then analyzed by AI to surface potential rare disease considerations with clear reasoning, helping clinicians see patterns they might otherwise miss.

Presenters: 
🗣 @Jesse Reffsin, Senior Sales Engineer at InterSystems
🗣 @Georgia Gans, Sales Engineer at InterSystems
🗣 @Annie Tong, Sales Engineer at InterSystems

Hi, Community!

Have you tried using serial objects in InterSystems IRIS? Explore some of the benefits and see how to start using them:

Using Serial Objects for Embedded Data Modeling

Hello everyone,

The Certification Team of InterSystems Learning Services is excited to announce the release of our new InterSystems IRIS SQL Professional exam. It is now available for purchase and scheduling in the InterSystems exam catalog. This exam is geared towards IRIS SQL experts, and it deals with a variety of advanced IRIS SQL topics that you can find in the exam page.

Hi Community,

We have some exciting news! It's time for the next InterSystems writing competition:

✍️ InterSystems Technical Article Contest 2026 ✍️

Write an article on any topic related to the InterSystems products and services.

🎁 Gifts for everyone: A special gift for each author participating in the competition!

Introduction

Today, coding assistants like Claude, GitHub Copilot and Cursor have transformed the way developers write code. However, these tools are limited by being isolated from the systems and data sources that developers work with daily. This limitation can be overcome through the Model Context Protocol (MCP), an open standard designed to connect AI assistants to external data sources and tools in a secure and standardized way.

In this review article, we'll explore the current state-of-the-art regarding the MCP within the InterSystems ecosystem.