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 |
---|---|---|---|---|---|---|
irisGoogleChatSend messages powered by AI to Google Chat | D | Docker AI | 3.5 (1) | 12 Nov, 2024 | 19 | |
LabResultsVerification-hl7HL7 App to update reference range and find critical results | Docker IPM | 5.0 (1) | 12 Nov, 2024 | 815 | 13 | |
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 | ||||||
IRIS-MQTT for ManufacturingFirst-ever IRIS-integrated MQTT Broker - no middleware needed! | A | 0.0 (0) | 08 Oct, 2024 | 35 | ||
IRIS MQTT for HealthFirst-ever IRIS-integrated MQTT Broker - no middleware needed! | A | 0.0 (0) | 29 Sep, 2024 | 57 | ||
Healthcare HL7 XMLHealthcare HL7 XML (also known as ITB or Ensemble HL7 XML) is an application you can install in InterSystems Healthcare products to handle HL7 v.2.x messages in XML format. | A | Docker IPM | 5.0 (2) | 02 Sep, 2024 | 777 | 58 |
irisfirebaseFirebase module for InterSystems IRIS | D | Docker Python IPM | 5.0 (1) | 27 Jul, 2024 | 164 | 3 |
hl7v2-to-kafkaA simple IRIS interoperability application - transform HL7 and send it to Kafka | S | Docker IPM | 5.0 (1) | 30 Apr, 2024 | 160 | |
fhirproSupports the profiling of FHIR resources in HealthShare ODS | B | 5.0 (2) | 04 Apr, 2024 | 144 | ||
interoperability-integratedml-adapterAn IRIS Interoperability adapter to use ML models managed by IRIS IntegratedML | Docker IPM ML ML | 5.0 (1) | 25 Mar, 2024 | 248 | 38 | |
ETL Interoperability AdapterExtend EnsLib.SQL.OutboundAdapter to add batch batch and fetch support on JDBC connection for Ensemble and IRIS. | G | Docker IPM | 3.5 (1) | 25 Mar, 2024 | 554 | 28 |
irishealth-ensdemoInterSystems IRIS for Health ENSDEMO | R | Docker IPM | 4.5 (1) | 25 Mar, 2024 | 473 | 155 |
googlesheets-adapterInbound and Outbound adapters for Google Sheets | N | Docker | 0.0 (0) | 17 Mar, 2024 | 71 | |
iris-climatiq-adapterAn IRIS Interoperability adapter for using the Climatiq API | Docker IPM | 3.7 (3) | 13 Feb, 2024 | 202 | 15 | |
MTConnect-ObjectScriptAn ObjectScript Implementation for the MTConnect Standard. | P | Docker IPM | 4.3 (3) | 12 Feb, 2024 | 229 | 5 |
iris-fhirfyUsing IRIS and LLMs to help developers to convert raw data into FHIR | Docker Python IPM AI | 5.0 (1) | 03 Feb, 2024 | 509 | 1 | |
iris-healthtoolkit-serviceConvert HL7 to FHIR, CDA to FHIR, FHIR to HL7 as a Service | G | Docker IPM | 5.0 (3) | 23 Jan, 2024 | 991 | 8 |
swagger-validator-cliClient ObjectScript for swagger validator services | Docker IPM | 0.0 (0) | 15 Jan, 2024 | 271 | 259 | |
swagger-converter-cliClient library for swagger version converter. | Docker IPM | 0.0 (0) | 15 Jan, 2024 | 306 | 262 | |
presto-irisPresto InterSystems IRIS Connector | Docker Python | 5.0 (1) | 24 Nov, 2023 | 298 | ||
mercure-outboundadapterThis adapter allows you to send SSE events from IRIS using Mercu | N | Docker IPM | 0.0 (0) | 12 Nov, 2023 | 91 | |
workshop-firebaseFirebase adaptor | Docker IPM | 0.0 (0) | 04 Nov, 2023 | 107 | ||
Tracking-Patient-Care-Using-FHIRExample for related exercise on the InterSystems Learning site. | Docker IPM | 5.0 (1) | 04 Oct, 2023 | 182 | ||
Open API Client GenIRIS Interoperability Production generator from Swagger 2.0 specification. | Docker IPM | 5.0 (2) | 28 Sep, 2023 | 1.3k | 330 | |
EnsHelperIRIS Integration Extensions and Utilities | A | IPM | 5.0 (2) | 14 Jul, 2023 | 188 | 89 |
IRIS FHIR Transcribe Summarize ExportOpenAI Transcribe & Summarize. Google Docs & Sheets Integration | Docker Python IPM AI | 0.0 (0) | 06 Jul, 2023 | 479 | ||
IrisSapConnectorExample connection IRIS with SAP using RFC | D | Docker IPM | 0.0 (0) | 24 Jun, 2023 | 181 | 1 |
Telegram adapterTelegram adapter for InterSystems IRIS | N | Docker IPM | 5.0 (1) | 20 Jun, 2023 | 398 | 37 |
workshop-dicom-orthancFull example of a DICOM communication IRIS - PACS | Docker | 5.0 (1) | 10 Apr, 2023 | 229 | ||
iris-pubsubSimple local Publisher-Subscriber utility for InterSystems IRIS | A | Docker IPM | 5.0 (1) | 20 Feb, 2023 | 220 | 4 |
Custom ZenProxy%ZEN.proxyObject send numeric as String | D | Docker IPM | 3.8 (2) | 13 Feb, 2023 | 215 |