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 |
---|---|---|---|---|---|---|
![]() Clinical Mindmap ViewerFHIR Clinical Mindmap Viewer | Docker IPM | 5.0 (1) | 04 Feb, 2024 | |||
![]() iris-fhirfyUsing IRIS and LLMs to help developers to convert raw data into FHIR | Docker Python IPM AI | 5.0 (1) | 03 Feb, 2024 | |||
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 | ||||||
Fhir-HepatitisC-PredictProcessing FHIR resources through FHIR SQL BUILDER will predict the probability of suffering from HepatitisC disease | s | IPM ML ML | 0.0 (0) | 02 Feb, 2024 | ||
![]() Health HarbourAn example of using InterSystems FHIR | A | Docker IPM | 5.0 (1) | 01 Feb, 2024 | ||
![]() ai-queryOur AI-driven eligibility query tool streamlines patient identification by leveraging FHIR data, making it easier to find patients with care gaps and suitable cohorts for clinical trials. It integrates with IRIS, handling requests across diverse data sources, asking clarifying questions, and executi | Docker AI | 5.0 (2) | 27 Jan, 2024 | |||
HL7-FHIR-Cohort-PopulationHL7 to FHIR Cohort Population | M | 5.0 (1) | 25 Jan, 2024 | |||
System-AlertsSystem Alerts | M | 5.0 (1) | 25 Jan, 2024 | |||
iris-healthtoolkit-serviceConvert HL7 to FHIR, CDA to FHIR, FHIR to HL7 as a Service | G | Docker IPM | 5.0 (3) | 23 Jan, 2024 | ||
![]() fhirserver-profile-based-validationA sample of calls (Postman Collection) to demonstrate FHIR Profile-based Validation Requests | N | 5.0 (1) | 11 Dec, 2023 | |||
![]() InterLangLangChain meets FHIR for personalized health plans | Z | Docker Python | 0.0 (0) | 27 Nov, 2023 | ||
![]() fhir-pexJava Application sending FHIR messages to Kafka topics. | F | Docker AI | 4.0 (1) | 26 Nov, 2023 | ||
workshop-fhir-adapterWorkshop with example of FHIR Adapter | Docker | 5.0 (2) | 12 Oct, 2023 | |||
![]() Tracking-Patient-Care-Using-FHIRExample for related exercise on the InterSystems Learning site. | Docker IPM | 5.0 (1) | 04 Oct, 2023 | |||
![]() FSLogInternal FHIR Server Log | Docker IPM | 4.5 (1) | 24 Sep, 2023 | |||
![]() FHIR-XMLToJSONConvert FHIR XML to JSON resource message structure | Docker IPM | 3.5 (1) | 22 Sep, 2023 | |||
iris-oauth-fhirFhir Oauth Sample | G | Docker Python | 0.0 (0) | 21 Jul, 2023 | ||
iris-fhir-generative-aiAn experiment to use generative AI and FHIR | Docker Python IPM AI | 0.0 (0) | 16 Jul, 2023 | |||
![]() FHIR - AI and OpenAPI ChainCall any FHIR API with natural language input. OpenAI. LangChain | Docker Python IPM AI | 0.0 (0) | 07 Jul, 2023 | |||
iris-fhir-python-strategyPython hooks on IRIS FHIR Repository/Facade | G | Docker Python | 0.0 (0) | 07 Jul, 2023 | ||
![]() IRIS FHIR Transcribe Summarize ExportOpenAI Transcribe & Summarize. Google Docs & Sheets Integration | Docker Python IPM AI | 0.0 (0) | 06 Jul, 2023 | |||
![]() FHIR EditorFHIR Editor | Docker | 5.0 (1) | 02 Jul, 2023 | |||
fhir-chatGPTA Virtual Healthcare chat Assistant | D | Docker AI | 0.0 (0) | 01 Jul, 2023 | ||
fhir-profile-validationValidating FHIR resources against profiles | D | Docker | 4.5 (1) | 30 May, 2023 | ||
workshop-smart-data-fabricLearn the main ideas involved in developing a Smart Data Fabric using InterSystems IRIS | A | Docker Python | 5.0 (1) | 26 Apr, 2023 | ||
iris-fhirsqlbuilderShowcase of the FHIR SQL Builder from IRIS | G | Docker Python | 5.0 (1) | 02 Feb, 2023 | ||
FHIR Interoperability examplesExample of using InterSystems IRIS or HealthShare Health Connect interoperability features for FHIR. Scenarios where forwarding requests and handling responses are required. | A | Docker IPM | 5.0 (1) | 17 Jan, 2023 | ||
![]() FHIRDrop-FHIRBoxA simple production that enables FHIR transaction bundles to be loaded into InterSystems® FHIR® Server via Box and Dropbox. | 0.0 (0) | 17 Jan, 2023 | ||||
![]() Medxnote MT for TrakCareConnect Microsoft Teams to TrakCare with Medxnote MT Chatbot | N | 0.0 (0) | 17 Jan, 2023 | |||
![]() Pregnancy Symptoms TrackerExample of using FHIR to track pregnancy symptoms | Docker IPM | 3.5 (1) | 08 Dec, 2022 | |||
![]() Dia-Bro-AppTo highlight IRIS for Health Integrational capabilities | D | 0.0 (0) | 04 Dec, 2022 |