At InterSystems, we deeply appreciate the rapid innovation enabled by open-source development. Our team acknowledges the significant impact of the community's dedication, which has been a driving force behind the evolution of software and data technology.


| Application Name | Developer | Made with | Rating | Last updated | Views | Installs |
|---|---|---|---|---|---|---|
CoffeeCo Full Stack TutorialIRIS Coffee Company tutorial | R | Python | 3.0 (1) | 12 Aug, 2022 | ||
![]() ObjectScript KernelExecute ObjectScript in Jupyter Notebook | Docker Python | 5.0 (1) | 18 Jul, 2022 | |||
InterSystems Ideas Waiting to be ImplementedRPMShare - Database solution for remote patient monitoring (RPM) datasets of high density vitalsWhy Currently, patient home monitoring is a megatrend, promising to reduce readmission, and emergency visits and globally add years of health. Owing to US 21st Century act and Reimbursement Schedule from Medicare (up to 54 USD per month per patient) US market is flooded with RPM companies (over 100 for sure) providing primary physicians and hospitals the possibility to collect data from patients' homes, including blood pressure, blood sugar, weight, heart rate, and others. Most companies collect and store the data in free formats, creating an "unholy mess" of data, which has a very limited chance to be ever reused. The hospital only gets insights from single patient results as a dashboard concentrating on cases showing vitals going out of normal range. While research by scientific groups and several advanced companies shows that even data of medium accuracy could predict adverse events like heart failure weeks before happening. A project which is able to provide a federated environment for these new types of data, allowing patients and hospitals truly own data, connecting it to classic EHR, and making data readily available for AI/ML, a project like this is poised to conquer the US maket, with other markets following the trend. Who RPM Companies collecting the data will love the solution which will transfer the data from devices using FHIR, provide full security and compliance, and will include a multitude of routine functions for data analysis, and even data representation. They will stop creating hundreds of repositories of similar software code and concentrate on patient success. Hospitals will be able to have their own structured and standardized silos of data, they will have a chance to change RPM providers, and have a history of patient vitals. They will have EHR data and RPM data connected. Dashboards could be integrated into existing EMRs much easier and finally, they will be precious sources of integrated data for research. Patients will be able to reuse their data, have it analyzed by leading health tech companies, and enrich their vitals with even more data from wearables and other devices. Researchers will be able to analyze the data in the same cloud as it is stored, and by anonymizing datasets, with integrated EMR and RPM data, they could potentially assemble unprecedented volumes of data. AI/ML-ready datasets will boost the predictive power of digital health in only a few years from the first implementations of data collection. How HealthShare is already able to store and receive data in FHIR format, minor additions for hl7 standards are to be implemented and accepted by the community. In a way, RPMshare is a mini-version of HealthShare, if designed using an interoperability framework it could even have universal connection standards for existing devices. A secret sauce could be made from the integration of InterSystems solutions in anonymization and the IntegratedML package with RPMshare. To create immediate value and populate cloud service a consortium or partnership with existing RPM companies could be developed, where they will receive benefits of instrumentation and standardization and InterSystems will populate hundreds of thousands of years of observations (assuming companies already have tens of thousands of clients). In simple words, it is an Uber for RPM data. D 6Votes0Comments | ||||||
KozoKozo Page Builder | S | Docker IPM | 5.0 (2) | 15 Jul, 2022 | ||
![]() ObjectScript-Syntax-For-GitLabObjectScript highlight support for GitLab. | Docker | 5.0 (1) | 31 May, 2022 | |||
FIT REST Operation FrameworkAn IRIS Interoperability REST Operation Framework | Docker IPM | 4.5 (1) | 06 Jun, 2022 | |||
Benchmark time of response for messages in python and objectscriptBenchmark time of response for messages in python and objscript | L | 3.5 (1) | 30 May, 2022 | |||
wifis-connectWiFIS Connect is an application you can install in InterSystems Healthcare products to build your connection to WiFIS interoperability platform in SISCAT. | A | Docker | 5.0 (1) | 27 May, 2022 | ||
![]() iris-history-monitorIRIS History Monitor - For InterSystems IRIS is now available in Package Manager and using IRIS 2019.4 API and WS | Docker IPM | 4.2 (3) | 15 May, 2022 | |||
iris-docker-zpm-usage-templateThe simplest template to use InterSystems IRIS in Docker and with an arbitrary InterSystems Community Package | Docker | 5.0 (1) | 08 May, 2022 | |||
React-UI-GlobalApplication with toolkit for globals | E | Docker Python | 4.0 (1) | 08 Apr, 2022 | ||
dataset-financeDataset of Finance Transactions in a CSV file for SQL LOAD DATA | O | Docker IPM | 5.0 (1) | 15 Jan, 2022 | ||
IO-RedirectIO Redirect in ObjectScript | Docker IPM | 4.8 (2) | 15 Jan, 2022 | |||
![]() aoc-2021-uvgAdvent of code 2021 in objectscript classes | Y | Docker IPM | 5.0 (1) | 06 Jan, 2022 | ||
zap-api-scan-sampleAn example on how to scan your REST APIs on IRIS using the OWASP | Docker | 5.0 (1) | 05 Mar, 2023 | |||
iris-python-examplesEmbedded Python examples with notebook support. | G | Docker Python | 5.0 (2) | 13 Dec, 2021 | ||
![]() VSCode-ObjectScriptVSCode extension for InterSystems products | 4.9 (19) | 02 Dec, 2021 | ||||
global-logging-templateA simple objectscript global logging template | N | 3.5 (1) | 01 Dec, 2021 | |||
![]() Audit MediatorObject Script mediator to audit ObjectScript REST API requests | Docker IPM | 5.0 (1) | 01 Dec, 2021 | |||
![]() API Security MediatorInterSystems IRIS Declarative Security Rules for REST APIs | Docker IPM | 5.0 (1) | 30 Nov, 2021 | |||
LogSimple macros-driven logging system | E | Docker IPM | 4.0 (1) | 18 Feb, 2022 | ||
![]() IRIS Interoperability Message ViewerA new approach for the Interoperability Message Viewer | Docker IPM | 4.6 (4) | 20 Nov, 2021 | |||
secured-rest-apiBasic authentication and authorisation via REST API in IRIS | Docker IPM | 5.0 (1) | 15 Nov, 2021 | |||
csv2tableExample on how to import CSV to any existing table | Docker IPM | 4.5 (1) | 29 Sep, 2021 | |||
iris-analytics-for-moneyIRIS Analytics solution for money (not yet) | O | Docker IPM | 5.0 (1) | 12 Sep, 2021 | ||
![]() pop-song-analyticsPop Songs analytics from the last decades | Docker | 4.5 (1) | 11 Sep, 2021 | |||
integrated-ml-demoBackend in Python or ObjectScript | G | Docker Python ML ML | 5.0 (1) | 31 Aug, 2021 | ||
Example Backup TaskExample useful utilites | Docker IPM | 4.5 (1) | 24 Aug, 2021 | |||
fhir-openapi-genA code base for the processing and formulation of the openapi spec for fhir resources and profiles | C | Docker Python IPM | 3.0 (1) | 12 Aug, 2021 | ||
XList - for declarative and functional programmingExtended list for ObjectScript with support for declarative and functional programming | M | 4.0 (1) | 04 Aug, 2021 | |||
movieSample App to IRIS API Patterns | Docker IPM | 4.0 (1) | 03 Aug, 2021 | |||