新しい投稿

查找

ダイジェスト
· 2026年1月20日

InterSystems Open Exchange Annual Newsletter 2025

Hello and welcome to the InterSystems Open Exchange Annual Newsletter 2025.
General Stats:
174 new apps in 2025
6,717 downloads in 2025
1,101 applications all time
44,992 downloads all time
3,484 developers joined

Top applications of the year
This rating includes only applications that have been published this year. The popularity of applications depends on various metrics such as views, bookmarks, ZPM installation rate, releases, reviews, and clicks on the Download button on the app page.
Top applications of all time
This rating includes applications that have been published since Open Exchange went online. The popularity of applications depends on various metrics such as views, bookmarks, ZPM installation rate, releases, reviews, and clicks on the Download button on the app page.
Top developers of all time
 

A developer's rating is affected by factors such as publishing apps, entering contests, writing reviews, and releasing updates.

If you want to see the top developers based just on the number of apps they've published, you can find them here.
2025 at a GlanceInterSystems Open Exchange
記事
· 2026年1月20日 4m read

Capturing and Sharing Patient-Level Measure Reports via FHIR Using Da Vinci Risk Adjustment with HealthShare

Overview

Organizations that need to capture, store, and share patient-level quality or risk adjustment measure results via FHIR can do so by extending HealthShare SDA and enabling transformation to the FHIR MeasureReport resource.

This article describes how to configure HealthShare to support the Da Vinci Risk Adjustment (RA) Implementation Guide by enabling storage and FHIR-based exchange of MeasureReport resources for individual patients or members.

The outcome of this configuration is the ability to persist MeasureReport data in SDA and expose it via FHIR R4 in compliance with the Da Vinci RA profile.

 

Solution Summary

This solution introduces a custom SDA3 container to store MeasureReport data for each patient and configures HealthShare to transform that data into a FHIR R4 MeasureReport resource.

The deliverables include:

  • A custom SDA container and related supporting classes
  • A custom DTL to transform SDA to FHIR
  • Configuration updates to register and enable the transformation
  • A test patient to validate end-to-end functionality

Once completed, HealthShare will:

  • Store MeasureReport data per patient in SDA
  • Automatically use the custom container
  • Expose the MeasureReport through the FHIR R4 endpoint in ODS

Implementation Steps

1. Download, Import and Compile Custom Code

Download MeasureReportCode.xml from GitHubhttps://github.com/smckennaisc/hs-measurereports-example/

Import and compile the contents of MeasureReportCode.xml into HSCUSTOM namespace in the following HealthShare environments:

  • Registry
  • Edge Gateway
  • ODS/FHIR Gateway
  • Clinical Viewer

Note: Applies to HealthShare v2025.1

Included Components in file

i. Custom SDA Container

  • HS.Local.SDA3.ZContainer.cls

ii. Custom SDA3 MeasureReport Classes

  • HS.Local.SDA3.ZMeasureReport.cls
  • HS.Local.SDA3.ZMeasureReportGroup.cls
  • HS.Local.SDA3.ZMeasureReportExtension.cls
  • HS.Local.SDA3.Streamlet.ZMeasureReport.cls
  • HS.Local.SDA3.CodeTableDetail.ZMeasureReportCategory.cls
  • HS.Local.SDA3.CodeTableDetail.ZGroupCode.cls
  • HS.Local.SDA3.CodeTableDetail.ZccRemark.cls

iii. Custom DTL

  • HS.Local.FHIR.DTL.SDA3.vR4.MeasureReport.MeasureReport

2. Register the Custom SDA Container

 

In HSREGISTRY, add the following Configuration Registry entry:

\CustomSDA3Container = HS.Local.SDA3.ZContainer

This ensures that HealthShare uses the custom SDA container when processing SDA3 data.


3. Enable the SDA-to-FHIR Transformation

 

In HSODS, update the following global:

set ^HS.XF.Transform("SDA3","vR4", "HS.Local.SDA3.ZMeasureReport", "HS.Local.FHIR.DTL.SDA3.vR4.MeasureReport.MeasureReport") = 1 

This explicitly enables the transformation from the custom SDA3 MeasureReport container to the FHIR R4 MeasureReport resource.


4. Update XFTransform.xml

 

Locate XFTransform.xml in the instance directory:

/dev/fhir/gbl/
  • You may need to temporarily set the file to read/write.

Add the following XML node after the SDA4 and vR4 nodes and before HS.SDA3.Address (typically around line 7):

<Node> <Sub>HS.Local.SDA3.ZMeasureReport</Sub> <Node> <Sub>HS.Local.FHIR.DTL.SDA3.vR4.MeasureReport.MeasureReport</Sub> <Data>1</Data> </Node> </Node>

This step ensures the transformation is recognized during runtime.


Testing and Validation

 

Download and Load Test SDA Data


Validate via FHIR API

Using Postman or another API testing tool, issue the following requests:

Query by Patient and Profile

https://<your-host>/csp/healthshare/hsods/fhir/r4/MeasureReport ?patient=100000012 &_profile=http://hl7.org/fhir/us/davinci-ra/StructureDefinition/ra-measurereport 
  • Replace <your-host> with your HealthShare URL
  • Replace 100000012 with the patient’s MPIID

Query All MeasureReports

https://<your-host>/csp/healthshare/hsods/fhir/r4/MeasureReport 

Expected Result:

  • A single MeasureReport resource should be returned

Validate in Clinical Viewer (CV)

 

  • Look up the patient “Test MeasureReport” in HealthShare's Clinical Viewer
  • Confirm the SDA record includes the custom MeasureReport container

Outcome

After completing these steps, your HealthShare environment will be capable of:

  • Persisting patient-level MeasureReport data in SDA
  • Transforming SDA data into a FHIR R4 MeasureReport resource
  • Sharing MeasureReport resources via FHIR in alignment with the Da Vinci Risk Adjustment Implementation Guide

This enables standards-based risk adjustment reporting and interoperability with downstream analytics, payers, and regulatory systems

 

Note: This article was edited using ChatGPT for grammar and readability.

ディスカッション (0)1
続けるにはログインするか新規登録を行ってください
記事
· 2026年1月20日 2m read

Small VS Code features that will boost your productivity

The official InterSystems VS Code extensions are packed with features that make developing with InterSystems products a breeze. Today I'd like to highlight some small but useful features that you may have missed.

Show All Class Members

You can view all members of the current class, including inherited members, with the click of a button. Just click on the class icon in the top-right corner of the editor window and a filterable list of all members will appear. Clicking on one will reveal it in an editor tab.

  

Show Plan

Using SQL in your ObjectScript code is a popular way to take advantage of InterSystems IRIS's powerful multi-model capabilities. However, writing performant SQL queries can be a challenge. That's why InterSystems added the ability to view the execution plan of SQL statements with one click right from your editor tab. Just click the Show Plan button above class queries and Embedded SQL statements and a webview displaying ther execution plan will appear beside your code.

 

Open InterSystems Document

A neat feature of VS Code is that it allows you to have multiple root folders open at once. It's also common to have many files in each folder, which makes navigating to a file using the explorer UI cumbersome at times. While VS Code has commands for quickly opening a file by name, that is usually different than the InterSystems name for the document (for example, the file path for User.Test.cls will often be /User/Test.cls). In response to this discrepancy, InterSystems added a command to open a file using the InterSystems name for it. After selecting a workspace folder, a file explorer picker is shown. Users can browse for the file to open using it, or enter the name directly in the text box and press Enter. The command accepts dots for package separators and the short form for %Library classes.

 

Open Error Location

When trying to identify the cause of an error, a good first step is go to the source. If you have the error location handy, VS Code has a command that will open the exact line for you, even if it's in a generated routine that isn't in your workspace folder. From the command palette, type Open Error Location... and run the command. A text box will appear that accepts a location in an INT routine in the form label+offset^routine. Submitting the form will open that location in an editor tab if the source code exists. A user can then use the View Other command to open the equivalent line in the higher level source file if applicable.

 

As always, feedback and issues reports can always be made on GitHub. Thanks for reading and happy coding!  

ディスカッション (0)1
続けるにはログインするか新規登録を行ってください
お知らせ
· 2026年1月20日

Innovaciones en la gestión de datos FHIR

Hola comunidad,

Disfrutad del nuevo vídeo en el YouTube de InterSystems Developers:

⏯ Innovaciones en la gestión de datos FHIR en Ready 2025

Acompañadnos en una sesión en profundidad sobre cómo avanzar en la gestión de datos FHIR aprovechando la identificación de pacientes, el enriquecimiento de datos clínicos y el soporte de decisiones con IA. Exploraremos cómo FHIR, los MPI y la IA han mejorado la identificación de pacientes, agilizado la interoperabilidad y permitido resúmenes completos de pacientes basados en FHIR en el Hospital Méderi. Además, mostraremos flujos de trabajo clínicos habilitados por IA e implementaciones de gobierno de datos FHIR en Stanford Health que proporcionan respuestas de IA en tiempo real para triaje, soporte a la decisión clínica, gestión de la atención y planificación operativa, con el fin de mejorar la calidad asistencial.

Presentadores:

🗣 @Elijah Cotterrell, Product Manager en InterSystems
🗣 @Kevin Kindschuh, Senior Sales Engineer en InterSystems
🗣 @Matías Fernández, Especialista Técnico en InterSystems
🗣 @Bernardo Linarez, Senior Technical Lead en InterSystems
🗣 Satchi Mouniswamy, Director Senior de Integración en Stanford Healthcare
🗣 Nikesh Kotecha, Responsable de Ciencia de Datos en Stanford Health Care

¿Tenéis curiosidad por las mejores prácticas? ¡Vedlo y suscribíos para más!

ディスカッション (0)1
続けるにはログインするか新規登録を行ってください
Job
· 2026年1月20日

Développeur d’Applications – Santé

InterSystems recherche un développeur d’Applications – santé.

Le développeur participera à la planification, au développement, à la maintenance et aux tests de nos logiciels (systèmes d’information hospitalier : TrakCare et IntelliCare). Il est responsable de la création de logiciels robustes et de la vérification que les solutions répondent à toutes les exigences. Le poste inclut également la production de documentation technique et la participation à l’ensemble du cycle de vie du développement logiciel.

Le poste est basé à Montpellier, France.

  • Le développeur intégrera une équipe R&D française à taille humaine et collaborera avec des équipes R&D internationales.
  • Le développeur travaillera avec des membres de plusieurs départements (Support, Implémentation, Ventes) et collaborera étroitement avec des profils techniques et non techniques de l’équipe Scrum afin de livrer les développements dans un cadre Agile.
  • L’innovation et la créativité sont des atouts et des qualités fortement encouragés.

Vous êtes encouragé(e) à postuler si vous :

  • Avez une forte capacité d’analyse et de résolution : vous aimez travailler sur des problématiques humaines à fort impact en relevant des défis techniques complexes.
  • Êtes enthousiaste : vous contribuez activement au sein d’une équipe transverse aux côtés d’experts métier.
  • Curieux(se) : vous avez soif d’apprendre et de perfectionner votre expertise.

Principales Responsabilités :

  • Concevoir des structures objets, des schémas SQL et des workflows applicatifs
  • Utiliser une partie des technologies propriétaires de l’entreprise (voir : https://www.intersystems.com/fr/produits/ )
  • Concevoir l’interface utilisateur dans le respect des normes applicables
  • Planifier, développer (code et tests unitaires), tester et documenter les programmes
  • Aider à l’investigation et à la résolution d’erreurs logicielles (support niveau 2)
  • Participer à des implémentations techniques sur site si nécessaire
  • Se tenir informé(e) de l’évolution des fonctionnalités des applications
  • Se tenir informé(e) des évolutions des outils de programmation, des systèmes d’exploitation et des technologies associées
  • Se tenir informé(e) des évolutions des standards d’échange de données applicables
  • Participer aux sessions de formation produit afin de se familiariser avec les fonctionnalités et workflows de base

Expérience et qualifications requises :

  • 2 à 5 ans d’expérience dans des environnements de développement d’applications à grande échelle
  • Excellente connaissance du cycle de vie du développement logiciel
  • Compétences techniques : SQL – langage de développement orienté objet

Souhaité :

  • Expertise démontrée dans le développement d’applications web et/ou d’applications client riches : Angular, JavaScript
  • Expérience en intégration de données et systèmes d’information hospitaliers
  • Connaissance des technologies InterSystems fortement appréciée
  • Linux

Formation souhaitée :

  • Master en informatique ou expérience équivalente
  • Diplôme d’ingénieur

>> appliquer ici <<

ディスカッション (0)0
続けるにはログインするか新規登録を行ってください