Home

Application Name	Developer	Made with	Rating	Last updated	Views	Installs
iris-medmatch An AI-powered patient matching engine built on InterSystems IRIS, utilizing Vector Search and Natural Language Processing (NLP) to find clinically similar patients across FHIR repositories	Ashok Kumar Thangavel	Docker Python	5.0 (1)	24 Feb, 2026	261
iris-queue-manager A robust, process-based queue manager designed for asynchronous	Ashok Kumar Thangavel	Docker	5.0 (1)	20 Feb, 2026	248
InterSystems Ideas Waiting to be Implemented Pull in all classes and tables called in a resource at export. I would like to see any utilized class, table, global variable, etc. that is utilized within a production component pulled into the export list when I export from that component. Right now, tables, XML message schemas, message classes, and others are not being pulled into the export list and it leads to missing classes when pushing components into production. It also requires a lot of extra documentation to be sure that all of the pieces I am building get moved as expected. V by Victoria Castillo 8 Votes 2 Comments Vote
DBdashboard Show free DB space as a DeepSee dashboard	Robert Cemper	Docker	5.0 (1)	25 Jan, 2026	203	3
irisfirebase Firebase module for InterSystems IRIS	D Daniel Aguilar	Docker Python IPM	5.0 (1)	27 Jul, 2024	334	4
journal-file-indexer IRIS Journal file indexer	Lorenzo Scalese	Docker IPM	5.0 (1)	27 Oct, 2023	1.6k	13
IRIS-REST-API-DATABASEMANAGER Create persistent Tables and Datas in Cache Database using REST API	L Lucas Bourré	Docker IPM	5.0 (1)	26 Feb, 2021	425	21

iris-medmatch

An AI-powered patient matching engine built on InterSystems IRIS, utilizing Vector Search and Natural Language Processing (NLP) to find clinically similar patients across FHIR repositories

Ashok Kumar Thangavel

Docker

Python

5.0 (1)

24 Feb, 2026

261

iris-queue-manager

A robust, process-based queue manager designed for asynchronous

Ashok Kumar Thangavel

Docker

5.0 (1)

20 Feb, 2026

248

InterSystems Ideas Waiting to be Implemented

Pull in all classes and tables called in a resource at export.

I would like to see any utilized class, table, global variable, etc. that is utilized within a production component pulled into the export list when I export from that component. Right now, tables, XML message schemas, message classes, and others are not being pulled into the export list and it leads to missing classes when pushing components into production. It also requires a lot of extra documentation to be sure that all of the pieces I am building get moved as expected.

V

by Victoria Castillo