Pesquisar

Pergunta
· 21 hr atrás

How to design an efficient HL7-to-FHIR transformation pipeline in IRIS for Health?

I’m exploring best practices for building a real-time HL7 v2 to FHIR R4 transformation workflow in IRIS for Health.
Should this be handled purely through productions, or is it better to integrate a custom transformation service layer for version control and auditing?

Discussão (0)1
Entre ou crie uma conta para continuar
Artigo
· 21 hr atrás 9min de leitura

InterSystems IRIS for Health

 

Image

Image

Image

Introduction

In today’s digital-healthcare landscape, organizations face mounting challenges: gigantic volumes of clinical, administrative, and device-generated data; disparate proprietary systems; and demanding performance, interoperability, and analytics requirements. To meet these pressures, the platform InterSystems IRIS for Health has emerged as a purpose-built data platform tailored for the healthcare domain. (InterSystems Corporation)
This article explores the key features, benefits, use-cases, and considerations of IRIS for Health — ideal for healthcare software vendors, digital-health innovators, payers, providers and tech teams wanting a modern foundation.


What is IRIS for Health?

At its core, IRIS for Health is a comprehensive, cloud-first development and runtime platform designed specifically for healthcare applications. According to the vendor, it supports all major healthcare data standards (e.g., HL7 V2, HL7 FHIR, CDA, DICOM) and is built to handle very large scale workloads (billions of records globally) with analytics, transaction processing, interoperability, and rapid application development all in one. (assets.intersystems.com)

Key aspects include:

  • A unified platform combining data‐management (transaction + analytics), interoperability, and application services. (InterSystems Corporation)
  • Native support for healthcare standards: e.g., FHIR (Fast Healthcare Interoperability Resources), HL7 V2/V3, IHE, DICOM. (odbms.org)
  • Multi-model data handling: relational, object, and native storage models, enabling flexibility depending on the use case. (assets.intersystems.com)
  • API management, integration engine, transformation services (e.g., HL7 to FHIR) and out-of-the-box components to accelerate development. (dev-starthealth.intersystems.com)
  • Cloud and on-prem deployment options, high performance and scalability designed for large healthcare environments. (InterSystems Corporation)

In short: it’s a platform rather than just a single tool, aimed at developers and organizations building health-tech solutions rather than only at end-users.


Why this matters for healthcare

Healthcare organizations are increasingly dependent on integrating data across many systems: electronic health records (EHRs), laboratories, imaging, devices (IoT/IoHT), wearables, payers, research databases, etc. Traditional systems struggle with the velocity, variety, and volume of data—and with the need for real-time insights and interoperability.

IRIS for Health addresses several pains:

  • Interoperability and standards support: With built-in support for FHIR and legacy standards, it offers a bridge between older systems and modern architectures. (odbms.org)
  • Performance and scale: Built on a platform capable of handling billions of records and high throughputs. (InterSystems Corporation)
  • Development speed: The platform provides templates, tooling, and architecture that allow faster delivery of applications (e.g., FHIR servers, analytics apps, device data ingestion). Example: quickstart demos for HL7 message transformation. (dev-starthealth.intersystems.com)
  • Flexible data handling: The multi-model capability allows for relational queries, object access, and optimized native operations — useful when dealing with complex healthcare data. (assets.intersystems.com)
  • Support for analytics/AI/ML: Because the platform can act as a “smart data fabric”, it allows running analytics, machine learning, and other advanced data operations on top of the same infrastructure. (assets.intersystems.com)

For healthcare providers, software vendors, payers, and med-tech players, this means being able to build solutions that are more connected, scalable, and future-proof.


Key Features and Capabilities

Below is a breakdown of some of the standout features of IRIS for Health, and how they map to real-world needs:

Feature Description Why it matters
FHIR & Standards Engine Out-of-the-box support for FHIR repositories, transformation services, HL7 V2/V3, CDA, DICOM etc. (InterSystems Corporation) Enables interoperability, faster data exchange, and integration of legacy systems with modern standards.
Multi-model Data Platform Ability to use relational, object, native/multidimensional data models within one platform. (assets.intersystems.com) Provides flexibility: e.g., for high-volume time-series device data vs relational patient data.
Integration & Transformation Includes built-in message routing, transformation, API management, HL7 to FHIR conversion. (dev-starthealth.intersystems.com) Saves time and cost: rather than building integration pipelines from scratch.
Scalability and Performance Designed to handle massive data volumes, high concurrency, large labs/hospitals. (InterSystems Corporation) Critical for enterprise healthcare systems, cloud deployments, national/regional health networks.
Cloud-first / Hybrid Deployment Supports cloud infrastructure, containerization, distributed architecture. Example: in China, partner MediWay built cloud HIS on it. (hhmglobal.com) Enables modern deployment models, scalability, and flexibility (e.g., SaaS, regional health networks).
Analytics, AI/ML Support The platform provides hooks for analytics, machine learning, data fabrics. (assets.intersystems.com) Helpful for predictive care, population health, precision medicine, device data analysis.
Security, Audit, Data Governance Features like encryption at rest/in-motion, auditing of events, API management. (assets.intersystems.com) Healthcare data is highly regulated—these capabilities help with compliance and trust.

Use Cases in Healthcare

Here are several real-world scenarios where IRIS for Health is particularly well-suited:

  1. Clinical Interoperability & EHR Integration A hospital or health system using many disparate systems (lab, imaging, devices, EHR) needs to unify on a data layer, share data via FHIR, and build new apps for patient engagement, clinician decision-support, or research. IRIS for Health can serve as that unified platform.
  2. Digital Health / MedTech Applications Health-tech vendors building apps for remote monitoring, wearable data ingestion, IoT/IoHT (Internet of Healthcare Things) can leverage its ability to ingest device streams, map them to FHIR/other standards, store and analyze quickly.
  3. National or Regional Health Information Networks When multiple providers, labs, payers across a region need to exchange data, support research/population health, analytics and scale matter. IRIS for Health has been used in large-scale deployments (e.g., China, in partnership) for cloud HIS. (hhmglobal.com)
  4. Clinical Research & Real-World Evidence Platforms that need to ingest real-world healthcare data, transform it into research-friendly schemas (OMOP, i2b2) and then perform analytics or AI. The technology guide mentions support for OMOP and i2b2. (InterSystems Corporation)
  5. Migration from Legacy Systems Organizations moving from older systems (HL7 V2 pipelines, siloed databases) to modern, connected architectures can adopt IRIS for Health to facilitate transformation, data consolidation, new app development.

Benefits for Healthcare Organisations & Vendors

  • Faster time to market for applications: Developers don’t need to assemble many disparate components—it’s a unified platform.
  • Reduced complexity and operational burden: A common platform reduces the need for multiple point tools, middleware, and custom glue code.
  • Better data agility: Ability to access, transform, and exploit data more flexibly enables new use-cases (analytics, AI, device data).
  • Future-proofing: Support for the latest standards (FHIR, devices, cloud) positions organisations for next-gen digital health requirements.
  • Scalable infrastructure: Suitable for large organisations with high volume and concurrency requirements—reduces risk of system bottlenecks.
  • Improved interoperability & integration: Strong support for healthcare standards enables smoother data exchange, partner integrations, and cross-system workflows.

Considerations / Challenges

Of course, as with any powerful platform, there are some caveats and aspects to assess:

  • Cost & Licensing: Sophisticated enterprise platforms often come with significant licensing and operational costs. Organisations must weigh the business case.
  • Skill-set requirements: While IRIS for Health aims to streamline development, building advanced capabilities (analytics, device integration, FHIR transformations) still requires strong engineering resources.
  • Governance and data strategy: Moving to a unified platform demands clear data governance policies (who owns data, security, privacy, data provenance) especially in regulated healthcare environments.
  • Migration effort: Transitioning from legacy systems (multiple databases, older standards, siloed applications) into a new architecture can be lengthy.
  • Vendor lock-in risk: While the platform is rich, organisations should assess how portable their apps/data are across systems, and whether they may become too dependent on the vendor ecosystem.
  • Operational complexity at scale: While designed for scale, managing large distributed deployments, cloud/hybrid architectures, high-availability and disaster-recovery still involves sophisticated operations.

Thus, organisations should conduct a solid technology due diligence, define the scope of use (which parts of the ecosystem will ride on IRIS for Health), and plan for change-management, data migration, and skill readiness.


Why this is relevant for Indian / APAC Healthcare Market

For hospitals, healthcare networks and vendors in India and the broader Asia-Pacific region, IRIS for Health offers opportunities to leapfrog legacy limitations:

  • With the growing digital health initiatives (national health stacks, insurance coverage expansions, device/wearable adoption), the need for a platform that supports large scale, interoperability and diverse device data is increasing.
  • Many Indian healthcare organisations face data silos (lab systems, hospital systems, imaging, pharmacy) and struggle with integrating them. A unified platform helps address that.
  • Cloud-first or hybrid deployment can help reduce costs and improve scalability—important in regions where infrastructure may vary across tiers of hospitals.
  • For med-tech startups or digital-health vendors in India, building on a global health-optimized platform offers credibility, faster time-to-market and integration with global standards (which might help international expansion).
  • Given the prevalence of multi-language, multi-system, multi-device contexts in APAC, a platform built for heterogeneity is beneficial.

Summary & Outlook

In sum, InterSystems IRIS for Health is a compelling foundational platform for modern healthcare IT: it fuses data management, interoperability, analytics, and application-development capabilities in one solution. For organisations looking to build connected, scalable, standards-based health applications (whether at hospital, network, or vendor level), it is a strong contender.

Looking ahead, key areas to watch include:

  • Expansion in cloud-native / SaaS deployment models, particularly for regional health networks and startups.
  • Deeper integration with AI/ML and device/IoHT data streams (wearables, remote monitoring, real-time analytics).
  • Enhanced support for global interoperability initiatives (e.g., FHIR Bulk, research data models like OMOP) as health-data sharing becomes more cross-border.
  • Growing adoption in emerging markets (India, Asia-Pacific, Africa) where digital health transformation is accelerating, making scalability and standards support critical.

For any health-informatics team contemplating an overhaul of their data and application stack, or a digital-health vendor seeking a robust platform foundation, IRIS for Health merits serious evaluation.


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

¡Último webinar del año! Smart Supply Chain 360: Ver, Decidir, Actuar

¡Buenas a todos!

Vamos a cerrar el año por todo lo alto. Os invitamos a este webinar en español con @Pierre-Yves Duquesnoy "Smart Supply Chain 360: Ver, Decidir, Actuar" el jueves 27 de noviembre, a las 4:00 PM (CET).

   

Descubrid cómo InterSystems Supply Chain Orchestrator actúa como tejido conectivo inteligente entre vuestros sistemas ERP, WMS, TMS existentes, sin necesidad de "rip and replace".

Veréis en acción un chatbot inteligente con acceso directo a todos vuestros datos de supply chain, que comprende vuestro modelo de datos y actúa como asistente conversacional para la toma de decisiones en tiempo real. Podéis preguntarle sobre inventarios, analiza KPIs críticos, o solicita recomendaciones prescriptivas.

Incluye demo técnica mostrando APIs, modelo de datos extensible y análisis prescriptivo. Webinar dirigido a Arquitectos e ingenieros de soluciones, Data Analytics y Applications manager (ERP, WMS, TMS)

¡Os esperamos!

🗣 Ponente: Pierre-Yves Duquesnoy, Senior Sales Engineer en InterSystems 

➡️ Registro >>

Discussão (0)1
Entre ou crie uma conta para continuar
Artigo
· 21 hr atrás 6min de leitura

Nobody expects the Spanish Inquisidor!

¡Sí sí! ¡Adelante! No os habéis equivocado, estáis en vuestra querida Comunidad de Desarrolladores de InterSystems en español.

Os preguntaréis a qué viene el título de este artículo, pues muy sencillo, hoy estamos aquí reunidos para honrar al Inquisidor y elogiar la gran labor desempeñada por el mismo. 

Comunidad de Steam :: :: Nobody expects the Spanish Inquisition

Y bien, ¿quién o qué es el Inquisidor?

Perfecto, ahora que he captado vuestra atención, es momento de explicar que es el Inquisidor. El Inquisidor es una solución desarrollada con tecnología InterSystems para someter a inquisición los contratos públicos que diariamente son publicados en la plataforma https://contrataciondelestado.es/

Aunque la plataforma tiene un buscador habilitado para filtrar las licitaciones públicas este tenía varias limitaciones:

  • Es imposible realizar búsquedas por el título de la licitación.
  • La búsqueda por adjudicatarios depende de que conozcas la descripción exacta utilizada en el registro del mismo en el resultado de la licitación, la cual varía invariablemente de una a otra (me he encontrado a InterSystems escrito de 5 formas distintas).
  • Encontrar el organismo que ha publicado la licitación es digno de un libro de ¿Dónde está Wally en la Administración Pública?

Y ni qué decir tiene que es imposible sacar la más mínima estadística al respecto de las licitaciones.

¿Cómo funciona el Inquisidor?

Muy sencillo, la plataforma de contratación pública pone a disposición de la plebe, en una muestra de generosidad, descargas diarias de las licitaciones publicadas en la plataforma en formato XML de este estilo:

<entry>
        <id>https://contrataciondelestado.es/sindicacion/licitacionesPerfilContratante/13983936</id>
        <link href="https://contrataciondelestado.es/wps/poc?uri=deeplink:detalle_licitacion&amp;idEvl=Ag4n4m84LtCqb7rCcv76BA%3D%3D"/>
        <summary type="text">Id licitación: 2023/20; Órgano de Contratación: Parlamento de Andalucía; Importe: 99750 EUR; Estado: EV</summary>
        <title>Suministro de equipamiento para el trabajo de trabajo en movilidad del Parlamento de Andalucía.</title>
        <updated>2024-01-31T12:59:50.514+01:00</updated>
        <cac-place-ext:ContractFolderStatus>
            <cbc:ContractFolderID>2023/20</cbc:ContractFolderID>
            <cbc-place-ext:ContractFolderStatusCode listURI="https://contrataciondelestado.es/codice/cl/2.04/SyndicationContractFolderStatusCode-2.04.gc" languageID="es">EV</cbc-place-ext:ContractFolderStatusCode>
            <cac-place-ext:LocatedContractingParty>
                <cbc:ContractingPartyTypeCode listURI="http://contrataciondelestado.es/codice/cl/2.10/ContractingAuthorityCode-2.10.gc">2</cbc:ContractingPartyTypeCode>
                <cbc:ActivityCode listURI="http://contrataciondelestado.es/codice/cl/2.10/ContractingAuthorityActivityCode-2.10.gc">1</cbc:ActivityCode>
                <cbc:BuyerProfileURIID>https://contrataciondelestado.es/wps/poc?uri=deeplink:perfilContratante&amp;idBp=SI5CV24QS6s%3D</cbc:BuyerProfileURIID>
                <cac:Party>
                    <cbc:WebsiteURI>http://www.parlamentodeandalucia.es</cbc:WebsiteURI>
                    <cac:PartyIdentification>
                        <cbc:ID schemeName="DIR3">I00000175</cbc:ID>
                    </cac:PartyIdentification>
                    <cac:PartyIdentification>
                        <cbc:ID schemeName="NIF">S4133001J</cbc:ID>
                    </cac:PartyIdentification>
                    <cac:PartyIdentification>
                        <cbc:ID schemeName="ID_PLATAFORMA">20015840002647</cbc:ID>
                    </cac:PartyIdentification>

Tenéis acceso a los archivos desde esta URL.

El Inquisidor se conecta diariamente a la URL que descarga el fichero y lo mapea a su propia base de datos, extrayendo los datos más útiles de la misma, como es la descripción, el importe, fechas de publicación así como el ganador de la misma y el importe en el caso de estar adjudicadas.

Esta información puede ser consultada desde una aplicación de Angular desarrollada para tal efecto:

¿Que nos aporta InterSystems IRIS al Inquisidor?

Hasta ahora las funcionalidades presentadas no pueden ser más sencillas y podrían implementarse con cualquier tecnología, pero gracias a IRIS, no tenemos que contentarnos con esa funcionalidades básicas. Veamos cómo IRIS impulsa y mejora a nuestro Inquisidor.

Almacenamiento columnar para estadísticas

Actualmente la plataforma almacena 874534 licitaciones entre publicadas y adjudicadas (y creciendo). La explotación estadística de las mismas se podría ver afectada por el número de registros, pero gracias al almacenamiento de tipo columnar sobre la columna de importes de adjudicación el tiempo de búsqueda y de agregaciones se reduce dramáticamente.

Property Ganador As %String(MAXLEN = 200);
Property GanadorNIF As %String(MAXLEN = 200);
Property ImporteGanador As %Numeric(STORAGEDEFAULT = "columnar");
Property ImporteGanadorSinImpuestos As %Numeric(STORAGEDEFAULT = "columnar");

De tal forma que podremos buscar agilmente y con absoluta inmediatez los importes de adjudicaciones agregadas tanto por empresas ganadoras, organismo contratante y años de publicación.

Indexación de textos con %iFind

Las búsquedas por campos de texto pueden ser una auténtica tortura, al implicar consultas que hagan uso de "LIKE" así como de carácteres especiales "%" o "?" que pueden ralentizar la obtención de resultados ad aeternum. Esto no es un problema trabajando con IRIS gracias a la indexación con %iFind (más información aquí).

Index IndexTitulo On (Titulo) As %iFind.Index.Basic(INDEXOPTION = 0, LANGUAGE = "es");

Este tipo de índices permite indexar campos de texto que aceleran de forma dramática las búsquedas sobre los mismos ahorrando tiempos de procesamiento y sobre todo y lo más importante, no agotando nuestra paciencia.

Aquí podemos ver un ejemplo de búsqueda de adjudicaciones de contratos para la adquisición de embutidos y la cual ha tardado menos de 1 segundo:

Vectorización de títulos de licitaciones

En ocasiones es posible que no estemos totalmente seguros de la descripción usada para el título de las licitaciones, por ello hemos aprovechado las capacidades de almacenamiento vectorial de la base de datos para la vectorización de los títulos y permitir búsquedas basadas en proximidad vectorial, obteniendo resultados que se aproximen a la búsqueda realizada.

Property TituloVectorizado As %Vector(DATATYPE = "DECIMAL", LEN = 384);

Conclusiones

Como veis, lo que a priori puede ser una aplicación básica, gracias a InterSystems IRIS puede ser mejorada y optimizada al máximo haciendo uso de las múltiples funcionalidades y capacidades incluidas.

¿Cuellos de botellas o problemas de rendimiento en tus aplicaciones? ¡Echa un vistazo a InterSystems IRIS!

Asociado a este artículo tenéis la aplicación subida a GitHub. La aplicación hace uso de la versión Community de InterSystems IRIS, por lo que podréis hacer uso de la misma de forma gratuita, con la única limitación del tamaño de la base de datos.

Actualmente disponemos de una versión pública a la que podréis acceder (previa solicitud dejando un comentario en este artículo).

1 novo comentário
Discussão (1)2
Entre ou crie uma conta para continuar
Artigo
· Out. 31 20min de leitura

使用 Docker 运行 InterSystems IRIS 的分步指南 - 第 1 部分:从基础知识到自定义 Dockerfile

目录

  1. 本文目的
  2. 什么是容器,它们为什么对 IRIS 有意义
     2.1 容器和镜像简介
     2.2 为什么容器对开发者很有用
     2.3 为什么 IRIS 可以很好地与 Docker 配合使用
  3. 先决条件
  4. 安装 InterSystems IRIS 镜像
     4.1 使用 Docker Hub
     4.2 拉取镜像
  5. 运行 InterSystems IRIS 镜像
     5.1 启动 IRIS 容器
     5.2 检查容器状态
     5.3 在容器终端执行代码
     5.4 访问 IRIS 管理门户
     5.5 将容器连接到 VS Code
     5.6 停止或移除容器
     5.7 使用绑定挂载设置特定密码
     5.8 使用持久化 %SYS 卷
      5.8.1 可以使用持久化 %SYS 存储什么
      5.8.2 如何启用持久化 %SYS
  6. 使用 Docker Compose
     6.1 Docker Compose 示例
     6.2 运行 Docker Compose
  7. 使用 Dockerfile 运行自定义源代码
     7.1 Dockerfile 示例
     7.2 Docker Compose 示例
     7.3 了解层、镜像标记和构建与 运行时
     7.4 源代码和初始化脚本
     7.5 使用 Dockerfile 构建镜像
     7.6 在容器化 IRIS 终端中运行指令
  8. 结语和未来计划

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