Encontrar

InterSystems 官方
· 11 hr 前

InterSystems Platforms Update Q4-2025

#InterSystems 官方

In review of the previous quarter, several notable developments were highlighted that remain relevant for this quarter’s report.

  • Beginning with 2025.3, OpenSSL 3 will be standard across supported platforms; SUSE 15 sp6 becomes the required OS for organizations utilizing SUSE.
  • For 2025.3, revised minimum CPU specifications will take effect.
  • Windows Server 2016 will not be supported in 2025.3.

For those newly acquainted with these communications, this update provides details about recent enhancements as well as anticipated changes based on current information; however, future projections remain uncertain and the content should not be interpreted as a definitive product roadmap.

InterSystems IRIS Production Operating Systems and CPU Architectures

Minimum Supported CPU Architecture

In 2024, InterSystems introduced a minimum supported CPU architecture for all Intel- & AMD-based servers that allows us to take advantage of new CPU instructions to create faster versions of IRIS.  IRIS 2025.3 will update that list to require the x86-64-v3 microarchitecture level, which requires the AVX, AVX2, BMI, and BMI2 instructions.

  • For users with Intel-based systems, this means that Haswell and up will be required.
  • For users with AMD-based systems, this means that Excavator and up will be required while Piledriver & Steamroller will not be supported.

Are you wondering if your CPU will still be supported?  We published a handy article on how to look up your CPU’s microarchitecture in 2023.

 

Red Hat Enterprise Linux

  • Recent Changes
    • RHEL 10 - Red Hat released RHEL 10 on May 20th.  We released a version of IRIS 2025.1.0 that supports RHEL 10 on June 20th.
      • IRIS 2025.2 and up will support RHEL 9 & 10, which means that we stopped supporting RHEL 8.
    • RHEL 9.6 – We have completed Minor OS Certification for 9.6 with no problems found.
  • Further reading: RHEL Release Page

 

Ubuntu

  • Upcoming Changes
    • Ubuntu has announced Ubuntu 26.04 will be released April 23, 2026.  We are planning to release IRIS support for the OS about a month thereafter.
  • Recent Update
    • Ubuntu 24.04.2 has just been released and minor OS certification has completed successfully.
  • Further Reading: Ubuntu Releases Page

 

SUSE Linux

  • Upcoming Changes
    • SUSE 16 was released earlier this month.  InterSystems is planning to add support for the platform with IRIS 2026.1
    • IRIS 2025.3+ will require SUSE Linux Enterprise Server 15 SP6 or greater – SLES 15 sp6 has given us the option to use OpenSSL 3 and, to provide you with the most secure platform possible, we’re going to change IRIS to start taking advantage of it.

Further Reading: SUSE lifecycle

 

Oracle Linux

  • Upcoming Changes
    • We’ve started testing Oracle Linux 10.  If history is to be our guide, it should work just fine with any version of IRIS that supports RHEL 10.
  • Further Reading: Oracle Linux Support Policy

 

Microsoft Windows

  • Previous Updates
    • Windows Server 2025 is now supported in IRIS 2025.1 and up.
  • Upcoming Changes
    • IRIS 2025.3+ will no longer support Windows Server 2016 & 2019.
  • Further Reading: Microsoft Lifecycle

 

AIX

  • Upcoming Changes
    • IBM released new Power 11 hardware in July.  Unfortunately, our equipment has been back logged.  I’ll let you know when we have performance test reports ready.
  • Further Reading: AIX Lifecycle

 

Containers

  • Upcoming Changes
    • We anticipate changing the container base image to Ubuntu 26.04 with either the IRIS 2026.2 or 2026.3 release.  That’s still a long ways off, but we’ll let you know when it’s locked in.

 

InterSystems IRIS Development Operating Systems and CPU Architectures

MacOS

  • Upcoming Changes
    • IRIS 2026.1 will end support for MacOS on Intel-based systems.  Apple has been phasing out support for the Intel-based machines and they’ve announced their intention to drop support for all remaining Intel-based macs in 2026.
  • Recent Changes
    • IRIS 2025.1 adds support for MacOS 15 on both ARM- and Intel-based systems.

 

InterSystems Components

  • Recent Releases
    • InterSystems API Manager 3.10 has been released.  Users of earlier versions of the API manager will need an updated IRIS license key to use version 3.10.
    • InterSystems Kubernetes Operator 3.8 has been released.

Caché & Ensemble Production Operating Systems and CPU Architectures

  • Previous Updates
    • A reminder that the final Caché & Ensemble maintenance releases are scheduled for Q1-2027, which is coming up sooner than you think.  See  Jeff’s excellent community article for more info.

InterSystems Supported Platforms Documentation

The InterSystems Supported Platforms documentation is the definitive source information on supported technologies.

 

… and that’s all folks.  Again, if there’s something more that you’d like to know about, please let us know.

讨论 (0)1
登录或注册以继续
文章
· 15 hr 前 阅读大约需 4 分钟

Connecting C# to InterSystems IRIS via ODBC

#ODBC #InterSystems IRIS

For developers building external applications, especially those using familiar technologies like C#, ODBC (Open Database Connectivity) is a crucial, standardized bridge to any relational database, including InterSystems IRIS. While InterSystems offers its own native ADO.NET provider, the ODBC driver is often the most straightforward path for integration with generic database tools and frameworks.

Here is a step-by-step guide to getting your C# application connected to an IRIS instance using the ODBC driver, focusing on DSN-less connection string.

Step 1: Install the InterSystems IRIS ODBC Driver

The InterSystems ODBC driver is installed by default when you install InterSystems IRIS on a Windows machine.

  • If IRIS is on the same machine: The driver is already present.
  • If IRIS is on a remote server: You must download and install the standalone ODBC client driver package for your client operating system (Windows, Linux, or macOS) and bitness (32-bit or 64-bit) from WRC website if you're a client or by installing Client components and copying ODBC driver.

Once installed, you can verify its presence in the ODBC Data Source Administrator tool on Windows (look for the InterSystems IRIS ODBC35 driver).

Step 2: Define the DSN-less Connection String

Instead of creating a pre-configured Data Source Name (DSN) in the Windows administrator tool, we’ll use a DSN-less connection string. This is cleaner for deployment because your application carries all necessary connection details.

The format specifies the driver name and the server parameters:

Driver={InterSystems IRIS ODBC35};
server=127.0.0.1;
port=1972;
database=USER;
uid=_System

Note:

  • The Driver Name (InterSystems IRIS ODBC35 or sometimes InterSystems ODBC) must exactly match the name registered in your local ODBC Data Source Administrator.
  • Port is the IRIS Superserver port (often 1972).
  • Database is the target Namespace in InterSystems IRIS (e.g., USER or your custom application namespace).
  • The default UID is _System with the password SYS. Always change these defaults in a production environment.

Step 3: Implement the Connection in C#

In your C# project, you will need to reference the System.Data.Odbc namespace to work with the generic .NET ODBC provider.

Here is a minimal C# example that establishes a connection, executes a simple query against a default table, and displays the result.

using System.Data;
using System.Data.Odbc;

public class IrisOdbcExample
{
    public static void Main()
    {
        // 1. Define the DSN-less connection string
        string connectionString =
            "DRIVER={InterSystems IRIS ODBC35};" +
            "Server=127.0.0.1;Port=1972;Database=USER;" +
            "UID=_System;PWD=SYS;";

        // 2. Define the SQL Query (Example: querying the default Sample.Person table)
        string sql = "SELECT ID, Name FROM Sample.Person WHERE ID < 5";

        using (OdbcConnection connection = new OdbcConnection(connectionString))
        {
            try
            {
                connection.Open();
                Console.WriteLine("Connection successful!");

                using (OdbcCommand command = new OdbcCommand(sql, connection))
                using (OdbcDataReader reader = command.ExecuteReader())
                {
                    while (reader.Read())
                    {
                        Console.WriteLine($"ID: {reader["ID"]}, Name: {reader["Name"]}");
                    }
                }
            }
            catch (OdbcException ex)
            {
                // 3. Handle specific ODBC errors (e.g., wrong password, port blocked)
                Console.WriteLine($"ODBC Error: {ex.Message}");
            }
            catch (Exception ex)
            {
                Console.WriteLine($"General Error: {ex.Message}");
            }
            // The connection is automatically closed at
            // the end of the Using block.
        }
    }
}
 
Setting up DSN

Next Steps

This DSN-less approach provides flexibility and avoids client-side configuration bloat. For high-performance C# applications, you may consider the native InterSystems ADO.NET Provider. But for quick integrations and tool compatibility, an ODBC connection is a reliable choice.

❗Always remember to use parameterized queries in production code to prevent SQL injection vulnerabilities.

讨论 (0)1
登录或注册以继续
文章
· 17 hr 前 阅读大约需 5 分钟

OMOP Odyssey - Vibing Synthea Modules for OMOP

#数据库 #FHIR #Generative AI (GenAI) #Prompt Engineering #InterSystems IRIS for Health

Vibe the Module, Not the Data


While working with the FHIR to OMOP Service, I've seen good FHIR synthetic data being created using commercial LLM's etc, custom tailored for ConditionOnset with the typical amazement on return, but witnessed some questionable trust first hand on a call.  This approach also falls short generating gigantic payloads so I can go back to my interests on the backend and ensure smooth data transition.

So imposters syndrome quickly surfaced after a couple day hiatus at the 2025 OHDSI Collaborator Showcase out in New Brunswick last October, so a new approach to generating data was in order for any possibility to being invited to cocktail parties with these folks, so I leaned into the work of the pros over at Mitre Corporation that brought us Synthea.

I Immediately noticed a module for the complex Sickle Cell Disease did not exist in the modules folder in the Synthea Repo, but have always known I was afforded the opportunity to write one, but this task would be definitely need da ifferent brain that the OHDSI community seems to have in abundance, but I do not.

The Vibe

Not a huge fan of this term, but it fits the distraction for sure with lack of another term... so given that Synthea Modules generate data based on a "ConditionOnset" lets create a Sickle Cell Disease module and generate a 1m population FHIR Bulk Export from it.

{
  "type": "ConditionOnset",
  "target_condition": "sickle cell disease"
}

Prompt #1 - Do My Job for Me

 
Quick Disease Profile for a first-pass SCD module
 
Synthea Module Design

Prompt #2 - Sure

 
Things that May be Weak, Race Incidence and Chronic Complications

The SCD Module

LGTM! The module that was created cited sources from the CDC almost exclusively, but here it is if you want to take a look at it, also visualized with the synthea visualization utility.

🔗 https://github.com/sween/synthea/blob/43325b191185301a668062ed0bb75a2cf1... 


Run

Lets grab the generator, some associated cheat codes, load up our module, and rip the Synthetic Bulk FHIR Export to a zip file.

git clone https://github.com/synthetichealth/synthea
cd synthea

Now, lets steal @Dmitry Zasypkin 's ndjson fixer utility from his repo.  This patches the generated ndjson references for processing.

https://raw.githubusercontent.com/dmitry-zasypkin/synthea-ndjson/refs/heads/main/patch-synthea-ndjsons.sh

Enable bulk fhir in the synthea.properties file.

Also helpful to only care about FHIR Resources relevant to the OMOP CDM

Then drop the generated SCD module in the modules folder.


Now run a -p 1m population synthetic generation for the State of Michigan for SCD

Somewhere in all the terminal noise and cpu fans, you should see that your module was loaded and then off to generate the ndjsons

In just under an hour, we are now run the patch-synthea-ndjsons.sh across the generated data...

And zip it all up to bulk fhir export format...

And here is what it looks like on disk if curious on the sizes

Load

Upload the bulk fhir payload to the S3 bucket

Let the OMOP service do its thing...

Attestation

Although this is generally hand waving to validate the data, lets just see if after transformation if SCD concepts are present in the data.

Now lets see if anybody has Sickle Cell Diseases in the synthetic data.

FAQ

Did you use AI for any of this?

I used my computer.

 Is the data accurate?

Its synthetic.

 Will you get invited to any cocktail parties at the next OHDSI Symposium?

Probably not, this is an oversimplification of complicated observational dataset, but not meant to be offensive.

 Any closing statements?

Just vibing this module, even with the 3 prompts, I gained even further appreciation for the complex challenges the OHDSI community solves with this observational data.

讨论 (0)1
登录或注册以继续
公告
· 18 hr 前

We Want to Hear Your Feedback on the Latest InterSystems IRIS Release!

#版本 #InterSystems 想法门户

Hi Community,

With the General Availability of the 2025.3 release of InterSystems IRIS® data platform, InterSystems IRIS® for Health™, and HealthShare® Health Connect, we are now collecting your ideas for improvement. 

If the new release inspired you or highlighted opportunities to enhance the developer experience, please share your suggestions on the InterSystems Ideas Portal - every idea is reviewed by our product teams and can influence future releases.

💡 Have an idea for improvement?

Submit it to the Ideas Portal - we’d love to hear your thoughts.

🐞 Think you’ve found a bug?

If what you discovered looks more like a defect than an idea, please report them via our standard bug-reporting channels so our teams can investigate it promptly:

Thank you for helping us make our products better with every release. Your feedback truly drives innovation!

讨论 (0)1
登录或注册以继续
公告
· 19 hr 前

[Video] Documentation Templates and Rules

#新手 #视频 #HealthShare #InterSystems IRIS for Health #学习门户

Hi, Community!

If you need to help providers meet a payer's documentation requirements, see how the Documentation Templates and Rules (DTR) module of the InterSystems Payer Services ePrior Authorization solution can help:

Documentation Templates and Rules

https://www.youtube.com/embed/SKZ_pz6GkUY?utm_source=youtube&utm_medium=social&utm_campaign=SKZ_pz6GkUY
[这是一个嵌入式链接，但由于您拒绝了访问嵌入式内容所需的 Cookie，您无法直接在网站上进行查看。要查看嵌入式内容，您需要在 Cookie 设置中接受所有 Cookie。]

讨论 (0)1
登录或注册以继续