#InterSystems Demo Games entry

⏯️ MyVitals: Connecting Wearable Health Data to EHRs with InterSystems

MyVitals is a Personal Health Device Hub that bridges the gap between wearable health devices and clinical workflows. In this demo, we show how healthcare organizations can enroll patients, collect real-time data from personal devices via mobile apps, and seamlessly integrate that information into EHR systems using FHIR, HL7, and InterSystems technology. Built on IRIS for Health and FHIR repositories, MyVitals turns disconnected wearable data into actionable clinical insights—securely, efficiently, and at scale.

Presenters:
🗣 @Alberto Fuentes, Sales Engineer, InterSystems
🗣 @Pierre-Yves Duquesnoy, Senior Sales Engineer, InterSystems
🗣 @Luis Angel Pérez Ramos, Sales Engineer, InterSystems

https://www.youtube.com/embed/2O0KZ__todk
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

Hey Community,

Enjoy the new video on InterSystems Developers YouTube:

⏯ SMART on FHIR: FHIR Server - OAuth Config

https://www.youtube.com/embed/CKhwj_nP678
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

I am seeking work with InterSystems HealthConnect/Cache. My experience is working with Rules and DTLs, plus message search, and export of components.With 10 years of dedicated expertise in SOA and ESB platform development, I have successfully designed and implemented enterprise-level integration solutions for large organizations, driving significant improvements in system interoperability and business efficiency.I have actively developed and supported HL7 V2/V3 、FHIR、XML/JSON interfaces.I reside in China.

You send an HTTP request and get back an HTTP error but with an HTML error page which you didn't expect... what's happening?... 🤔

Specifically for example, perhaps you tried to READ a FHIR Resource (e.g. /Patient/123) and you get back a 404 error page, even though with other Patient IDs, you get back the Resource payload, so "the page" definitely does exist... why should you be getting a 404 error page? 🙄

Introduction

In a previous article, I presented the IRIStool module, which seamlessly integrates the pandas Python library with the IRIS database. Now, I'm explaining how we can use IRIStool to leverage InterSystems IRIS as a foundation for intelligent, semantic search over healthcare data in FHIR format.

This article covers what I did to create the database for another of my projects, the FHIR Data Explorer. Both projects are candidates in the current InterSystems contest, so please vote for them if you find them useful.

You can find them at the Open Exchange:

• IRIStool and Data Manager
• FHIR Data Explorer

In this article we'll cover:

• Connecting to InterSystems IRIS database through Python
• Creating a FHIR-ready database schema
• Importing FHIR data with vector embeddings for semantic search

Hi, Community!

Do you have HL7® V2 messages that you need to convert to the HL7® FHIR® format for better integration and analysis? See how the InterSystems FHIR Transformation Service can help:

Using the FHIR Transformation Service with AWS HealthLake

https://www.youtube.com/embed/ggf6yuV0FxE?utm_source=youtube&utm_medium=social&utm_campaign=ggf6yuV0FxE
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

#InterSystems Demo Games entry

⏯️ Being READY to Tackle Healthcare Enterprise Challenges in a Few Clicks

Managed Cloud Solutions to Help Streamline Your Health Services.

This demo showcases composing several InterSystems Managed Cloud Services to solve various use-cases.

The video is actually built of 6 short chapters (each ~2.5 minutes long) showing each part of the story, demoing a different service.

You can watch each "chapter" individually if you're interested in a specific service, but there is value in viewing the whole composition and observing the full flow.

• 0:00 Health Connect Cloud - Medical Device MQTT - HL7v2 for Hospital Operation Systems
• 2:29 FHIR Server & FHIR Transformation Service - HL7v2 to FHIR & Repository for Regulation & Exchange
• 5:21 FHIR SQL Builder - Providing standard relational access to FHIR data
• 7:22 "FHIR IntelliChat" (see note below) - Natural human language chat with FHIR Server
• 9:37 OMOP Solution - FHIR to OMOP transformation & OMOP database with OHDSI tools compliance
• 12:54 InterSystems Data Studio for Health - Creating a multi data/app sources fabric

[Note the "FHIR IntelliChat" part is not an actual formal InterSystems service, it is just a demonstration of a possibility (based on this solution by @José Pereira) ]

Presenters:
🗣 @Tani Frankel, Sales Engineer Manager, InterSystems
🗣 @Keren Skubach, Senior Sales Engineer, InterSystems
🗣 @Ariel Glikman, Sales Engineer, InterSystems

https://www.youtube.com/embed/MM7GS4z3W5Y
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

Hey Developers,

Watch the video from our Tech Video Challenge:

⏯ HL7-to-FHIR integration using InterSystems IRIS

https://www.youtube.com/embed/Cm7cT26ANeo
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

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.

Hello Community!

We're excited to announce that the FHIR France Meetup is making a comeback... in person at SantExpo 2025!

📅 Dates: May 21, 2025, starting at 7:00 PM

📌 Location: Halles d'Issy - Biltoki, 1 Rue Rouget de Lisle, Issy-les-Moulineaux, Paris, France

We are hiring! 100% Remote W2 Contract | 3-6+ Months (numerous extensions likely)

Two Roles:
🔹InterSystems Engineer
🔹Epic Bridges Certified/InterSystems Engineer

Having solid experience with the below:

As I am iterating through the FHIR JSON Response from a Patient Search, I am running into an issue where the extracted values are not being popualted into the Response object that I have created. If I do a $$$LOGINFO on them they will show up in the Object log, however if I try the following for example I get an error.

Hi, Community!

Need a more efficient way to exchange health data? See how InterSystems Payer Services can help:

Automate Prior Authorization and Data Exchange with InterSystems Payer Services

https://www.youtube.com/embed/zP2m4hz2Opw?utm_source=youtube&utm_medium=social&utm_campaign=zP2m4hz2Opw
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

Dear InterSystems-Maintainer Team,

I am currently conducting a comparative evaluation of FHIR clients as part of my
bachelor thesis in health informatics. One of my evaluation criteria is the response
time to support inquiries.

Therefore, I would like to kindly ask the following question as part of my analysis:
How can I read and write custom FHIR extensions using your client library?

If available, could you point me to any documentation or examples?

Many thanks for your time and support!