新しい投稿

検索

お知らせ
· 2026年1月16日

[Video] Innovations in FHIR Data Management

#FHIR #READY 2025 #ビデオ #Summit

Hey Community,

Enjoy the new video on InterSystems Developers YouTube:

⏯  Innovations in FHIR Data Management@ Ready 2025

Join us for an in-depth session on advancing FHIR data management by leveraging patient matching, clinical data enrichment, and AI decision support. We will explore how FHIR, MPIs, and AI have enhanced patient matching, streamlined interoperability and enabled comprehensive FHIR-based patient summaries at Méderi Hospital. Additionally, we’ll showcase AI-enabled clinical workflows and FHIR data mastering implementations at Stanford Health providing real-time AI responses for triage, CDS, care management, and operational planning to improve care quality.

Presenters:
🗣 @Elijah Cotterrell, Product Manager at InterSystems
🗣 @Kevin Kindschuh, Senior Sales Engineer at InterSystems
🗣 @Matías Fernández, Technical Specialist at InterSystems
🗣 @Bernardo Linarez, Senior Technical Lead at InterSystems
🗣 Satchi Mouniswamy, Sr. Director - Integration at Stanford Healthcare
🗣 Nikesh Kotecha, Head of Data Science at Stanford Health Care

Curious about best practices? Watch this and subscribe for more!

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

Building a Medical History Chatbot - FHIR, Vector Search and RAG for beginners

#初心者 #FHIR #Generative AI (GenAI) #Python #チュートリアル #Internal Tech Article Contest

Introduction

Earlier this year, I set about creating kit to introduce young techy folk at a Health Tech hackathon to using InterSystems IRIS for health, particularly focusing on using FHIR and vector search.

I wanted to publish this to the developer community because the tutorials included in the kit make a great introduction to using FHIR and to building a basic RAG system in IRIS. Its an all inclusive set of tutorials to show in detail how to:

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

Reviews on Open Exchange - #62

#Open Exchange

If one of your packages on OEX receives a review, you get notified by OEX only of YOUR own package.   
The rating reflects the experience of the reviewer with the status found at the time of review.   
It is kind of a snapshot and might have changed meanwhile.   
Reviews by other members of the community are marked by * in the last column.

I also placed a bunch of Pull Requests on GitHub when I found a problem I could fix.    
Some were accepted and merged, and some were just ignored.     
So if you made a major change and expect a changed review, just let me know.
 

# Package Review Stars IPM Docker *
1 JSON2Persistent Now also available in IPM 6.0 y y  
2 one-to-many-case The first of 2026 5.0 y y  
3 IRIS_dockerization promising composition 4.4   y  
4 GlobalsDB-NodeJS-Admin Historic artefact 3.8      
5 iris-jsonschema just partial working 3.8      
6 GlobalsDB-Admin-NodeJS Historic artefact #2 3.5      
7 Pivot partner posting        
8 DbVisualizer partner posting        
9 PIQXL Gateway partner posting        
10 Symedical partner posting        
11 Fhirgure partner posting        
12 iknowAV Another artefact        
13 OMNI-Lab partner posting        


NOTE:
If some review is not readable for you, it might still wait for approval by OEX admins.

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

Nouvel assistant CCR IA

#CCR #その他

CCR intègre désormais un « Assistant CCR » basé sur l'IA, disponible pour les bêta-testeurs. Cet assistant vous permet d'obtenir rapidement des réponses sur les flux de travail, la terminologie et les bonnes pratiques CCR. Chaque réponse inclut des références aux formations ICC pertinentes, facilitant ainsi l'approfondissement de chaque sujet. Prochainement, les liens pointeront directement vers la page du PDF de formation ICC ayant servi à générer la réponse.

Pour accéder à l'assistant, cliquez sur l'icône bleue « Ouvrir l'Assistant CCR » en bas à droite de l'application CCR. Les conversations sont conservées d'une session à l'autre, mais effacées à la déconnexion.

Vous pouvez donner votre avis sur chaque réponse en cliquant sur le pouce levé ou baissé et en ajoutant un commentaire facultatif. Vos commentaires sont précieux et nous aident à améliorer la qualité de nos réponses !

Pour tester l'Assistant CCR, accédez au menu Utilisateurs dans la barre latérale, cochez la case « Bêta-testeur » sous votre profil, puis cliquez sur Enregistrer. Vous pouvez vous désinscrire à tout moment en décochant la case.

Pour une démonstration rapide de l'assistant CCR en action, consultez la vidéo ci-dessus.

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

FHIR return code 201 or 200

#初心者 #ビジネスオペレーション #FHIR #HL7 #Health Connect

Needs some help with FHIR return code 200 or 201 when processing HL7 messages in HealthConnect.

Issue:

1. If FHIR code is 200 or 201, HealthConnect keep processing HL7 messages

2. If FHIR code is NOT 200 or 201, HealthConnect keep suspend the HL7 messages in the messages queue, then keep processing NEXT subsequent HL7 messages in the TEXT file if the FHIR code is 200 or 201

3. I am also using following "Reply Code Actions" in Operation settings (:?R=S,:?E=S,:~=S,:?A=C,:*=S,:I?=W,:T?=C)

Please advice if I have a "if condition check" for FHIR codes 200 or 201, what "Reply Code Actions" I should use? or any other logic to achieve 1,2,3 issues above.

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