Nova postagem

Pesquisar

Anúncio
· 13 hr atrás

[Video] Vector Search Performance

Hey Community!

We're happy to share a new video from our InterSystems Developers YouTube:

     ⏯  Vector Search Performance @ Ready 2025

The session gives an overview of vector search benchmarking, comparing exact unindexed search with faster approximate nearest neighbor (ANN) methods. It highlights how to balance accuracy and performance by tuning recall, optimizing dimensionality, and keeping data in global buffers. Efficient indexing, proper resource management, and strong IRIS system maintenance are key to achieving the best performance.

🗣 Presenter: @Ray Wright , Principal Technology Architect, InterSystems

Enjoy watching, and subscribe for more videos! 👍

Discussão (0)1
Entre ou crie uma conta para continuar
Pergunta
· 16 hr atrás

Retrieve Segments (repeating) with a certain value using BPL

Hello, I am trying to get some fields from HL7 message and create a file using BPL.  The values I need are in a repeating segment (AIG).  Even in the repeating segment, I just want the iteration that has a certain field (AIG:3 populated).  With the help of documentation and community posts, I was able to create the BPL to loop through all of AIG and create the file.  But when I try to narrow the results even further (AIG:3 present), the process gets stuck.  I am not sure I am missing anything or have anything incorrectly set up.  Also, since the process gets stuck, it doesn't even seem to hit the 'Trace' step.  Below is our current BPL setup.

 

 

To Get the AIG Count to Loop through

Within the While Loop

Checking if AGI:3 has a value

request.GetValueAt("RGSgrp(1).AIGgrp(context.AIGitr).AIG:3)")'=""

Sample (trying to retrieve only lines in red)

RGS|1||1
AIS|1||1070002102^EXPLORATORY LAPAROTOMY|20260205100000|0|S|600|S||||
AIG|1|||7.221^Chest Instruments||||20260205100000|0|S|2580|S
AIG|2|||7.414^Defibrillator Paddles Internal Sm 4.5Cm||||20260205100000|0|S|2580|S
AIG|3|||7.695^Endo Scope Bronch Non Video Or||||20260205100000|0|S|2580|S
AIG|4|||7.1284^Major Set||||20260205100000|0|S|2580|S
AIG|5|||7.1466^Power Stryker Sternal Saw Trauma Room||||20260205100000|0|S|2580|S
AIG|6|||7.2914^Donor Network Instrument and Retractor Tray||||20260205100000|0|S|2580|S
AIG|7|||7.2928^Donor Network Sternal Retractors||||20260205100000|0|S|2580|S
AIG|8|||7.3066^Major Vascular Tray Number 1||||20260205100000|0|S|2580|S
AIG|9|||7.3283^Bin Scope Transport||||20260205100000|0|S|2580|S
AIG|10|||7.3360^Power Stryker Sternal Saw||||20260205100000|0|S|2580|S
AIG|11|||7.3458^Major Vascular Tray Number 2||||20260205100000|0|S|2580|S
AIG|12|||7.2914^Donor Network Instrument and Retractor Tray||||20260205100000|0|S|2580|S
AIG|13||900057^SYNTHES NEURO FIXATION PLATING SYSTEM|Implant Tray||||20260205100000||||
AIG|14||472^900880 BOTTOM TRAY RIGHT SIDE|Implant Tray||||20260205100000||||
AIG|15||900057^SYNTHES NEURO FIXATION PLATING SYSTEM|Implant Tray||||20260205100000||||

Final goal is to output lines with AIG:3 value and get a count of similar items.  In the example above 900057 will have a count of 2 and 472 will have a count of 1.  Any help is greatly appreciated.

Discussão (0)1
Entre ou crie uma conta para continuar
Anúncio
· 16 hr atrás

Bêta-testeurs recherchés pour notre prochain examen de certification InterSystems CCR EHR Application Specialist

Bonjour à la communauté InterSystems EHR,

InterSystems Certification développe actuellement un examen de certification pour les utilisateurs CCR Tier 2. Si vous correspondez à la description du candidat ci-dessous, nous aimerions que vous participiez au bêta-test de l'examen ! L'examen sera disponible pour les bêta-tests à partir du 27 janvier 2026.

Les bêta-tests prendront fin le 28 mars 2026.

Discussão (0)1
Entre ou crie uma conta para continuar
InterSystems Oficial
· Fev. 6

第三版 InterSystems IRIS、InterSystems IRIS for Health 和 HealthShare Health Connect 2026.1 开发人员预览版现已可用

 InterSystems IRIS® data platform, InterSystems IRIS® for Health, and HealthShare® Health Connect 2026.1 的第三次开发人员预览版已发布到 WRC 开发人员预览版网站容器可在我们的容器注册表中找到,其标签为latest-preview

这些开发人员预览版包括从 2026.1.0 开始放弃对 Mac Intel 的支持,以及将 Windows Server 2019 支持添加 2026.1.0。

初始文档可在以下链接中找到:

这些文档链接目前只是占位符,随着最终版本的推出和更多细节的分享,这些链接将不断更新。以下是 2026.1 文档的一些显著新增内容:

由于这是早期的开发人员预览版,一些内容仍在开发中,我们将在功能最终完成后提供完整的文档。我们感谢您在此阶段的耐心等待和反馈!

可用性和软件包信息

该版本为所有支持的平台提供了经典安装包,如需完整列表,请参阅 "支持的平台 "文档

安装包和预览密钥可从 WRC 的预览下载网站或通过 evaluation services website获取(勾选 "显示预览软件[Show Preview Software] "框)。

Discussão (0)1
Entre ou crie uma conta para continuar
Artigo
· Fev. 6 6min de leitura

Deploy IRIS Community Edition on the cloud: Part 2 Azure

 

Hello! 

In my last article, I went through a walkthrough on how you can try deploying InterSystems IRIS Community Edition, or IRIS for Health Community Edition for free on AWS. In this follow up, I will show the same for the next biggest cloud provider, Microsoft Azure. 

Like with AWS, Azure also provides a free offering on sign up, although its a bit less generous - you get $200 free credit to spend in the first month. This does mean you can once again try deploying IRIS Community edition for free on Azure, although I do recommend caution to avoid costly bills. 

Like with the previous article, this walks through the process for deploying the Community Edition on the cloud, however the process can be followed for a fully licenced version,  as there is a Bring Your Own Licence offering for IRIS and IRIS for Health. You can either use an existing license key for this, or contact sales for a new license. 

Walkthrough

Before starting you will need to sign in or create an account on Azure, and sign up for an Azure subscription (to enable billing). Then, head to the Azure Marketplace listing for IRIS Community (or IRIS for Health Community) and click Get it now

 

You will be prompted to sign in, and may also be asked for additional details like Country, Mobile number and workplace. Complete this and then click Get it now at the bottom of this form.

 

You will then be redirected to the Azure Portal. Click Start with a pre-set configuration to get started creating a deployment. If you'd rather select all the settings yourself, you can click Create to deploy without any default configuration.

 

After choosing to start with a pre-set configuration, you will be redirected to a page suggesting defaults for your use case. Choose your required use case, then click Continue to Create a VM, this choice will automatically pre-fill some of the configuration settings.

 

Choosing VM Settings

You will now enter the Create a virtual machine page. This is where you configure all of the settings for your virtual machine deployment.

There are tabs to choose settings under "Basics", "Disks" (storage), "Networking", "Management", "Monitoring", "Advanced Settings" and "Tags". This guide will discuss the settings under "Basics". For the other settings, you can either leave them as the default if you've started with a pre-set configuration, or select them in your own time. Many of these can be changed after deployment (for example limiting the connecting IP addresses).

Project Details 

Here you choose which Azure Subscription and Resource group is being used for the deployment, a resource group allows you to group related deployments (e.g. deployments for different services of a single project) for organization and billing purposes. You will need to create a resource group if you have not done so before. Click Create new and give a suitable name.

 

Instance Details 

The instance details controls the size, location and security settings of the instance. As you have clicked through the Azure portal, the image should have been pre-filled. Otherwise, you can selected through the marketplace dropdown.

There are several essentials to fill out in this section.

- Virtual Machine Name - Preferably use something easy to recognize for ease of management.

- Region - The closer the region is to your users, the less latency when accessing the machine. However, region choice will also affect availability of machines.

- Size - The performance specifications of the machine, including memory and number/type of processors available (CPUs, GPUs). The choice of size will depend on budget, required performance and availability in your selected region. As the InterSystems IRIS Community Edition itself limits the storage in the database and compute power used ( see the limits here), you will probably want to one of the smaller machines.

 

Authentication

Here you can choose how you authenticate when connecting to the machine. It's suggested that you use an SSH public/private key pair for this, but you can also use password authentication.You can also select a default username to access the machine.

You can leave all these settings as the default. If you choose to create a new SSH key, it will automatically be generated and downloaded when you deploy the machine.

 

Review + Create

Once you have set the,"Basics" check through the other tabs of settings and see if there is anything you would like to change from defaults. If not, select the Review + Create tab.

This tab will take a while to load, as it validates your selected settings. After validation has passed, you have to agree to the Terms for the final time, and will also see a summary of your selected settings.

When you are ready click Create to create your virtual machine.

 If you have selected to authenticate with an new SSH key as suggested, you will be greeted with a pop-up to generate and download this. Click Download private key and create resource.

 

Connect

It will take a couple of minutes for your deployment to launch, but you should end up with a screen saying "Your deployment is complete".

 

There are several settings which Azure recommends setting, which you may wish to do soon. However, to initially demonstrate connecting to the machine, click Go to resource. This will bring up the management dashboard for your deployed virtual machine.

 

On the left-hand side there is a panel to select different settings groups to view and edit machine settings. For now though, Select Connect from the panel across the top of the dashboard.

Via SSH

On Azure, Secure Shell (SSH) is the recommended method when connecting to the InterSystems IRIS Community Edition instance. You can connect via SSH from your local machine terminal or powershell.

 

From the connection panel you will clearly see the IP address of your instance, and an SSH command to use to connect to the instance. The SSH connection command required three things, the local path to your private key which was downloaded when you launched the instance, the username on the machine (default was azureuser unless you changed it in the Authentication step above) and the IP address of your instance.

ssh -i /path/to/key.pem username@xx.xx.xxx.xxx

ssh -i /home/keys/My-Iris-Instance_key.pem azureuser@12.34.567.899

On your first time connecting, you will be prompted if you are sure you want to continue connecting. Type "yes" and you will connect to the instance.

 

The first time you log in, you will need to reset the password from the default. To do this, run:

iris password

A prompt will tell you that the default credentials are:

- Username: _SYSTEM

- Password: SYS

And that this password is expired and needs to be changed. If like me, you prefer the other default username, SuperUser, that should also work with the same password

After this, you can start an IRIS terminal session with:

iris session iris

If you would like to copy files to the IRIS instance, you can use an SSH connection using scp, sftp or an sftp client like Filezilla. You can also copy files via Azure's Bastion service.

Via Management Portal

Once deployed, the Management Portal will be available at the IP address of your instance with :52773/csp/sys/UtilHome.csp appended on the end. The default credentials are:

- Username: _SYSTEM
- Password: SYS

These will need to be changed on first login, unless you have already changed them from the SSH connection.

Terminate Deployment

Remember to stop the deployment once you are done using it! To do so, navigate back to the Virtual Machine dashboard for your instance, and click Delete. You will be prompted for which components you want to delete. If you are completely finished using this deployment, select all of the components and click Delete to end all deployments.

 

Discussão (0)1
Entre ou crie uma conta para continuar