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 |
|---|---|---|---|---|---|---|
FHIR Simple Demo ApplicationFHIR Simple Demo Application | M | 2.5 (1) | 30 May, 2021 | |||
FHIR Pseudonymization ProxyFHIR pseudonymization proxy built with InterSystems IRIS for Health | M | Docker IPM | 5.0 (1) | 23 Jun, 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 | ||||||
![]() FHIR QuestionnairesFHIR Questions and Responses | Docker IPM | 5.0 (1) | 03 Dec, 2022 | |||
![]() FHIR EditorFHIR Editor | Docker | 5.0 (1) | 02 Jul, 2023 | |||
FHIR SQL Builder with Vector SearchFHIR SQL Builder with Vector Search Demo | F | Docker Python AI | 5.0 (2) | 22 Nov, 2025 | ||
FHIR Patient BrowserSimple Patient Browser app for FHIR server, using fhir.js library | A | Docker | 0.0 (0) | 17 Aug, 2020 | ||
FHIR-HL7v2-SQL-DemoThe FHIR repo can be query in SQL. | G | Docker | 5.0 (1) | 17 Apr, 2020 | ||
![]() fhir-chatbotA chatbot to query patient information using FHIR. | R | Docker | 0.0 (0) | 27 Aug, 2020 | ||
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 | ||
FHIR Data Studio ConnectorCommunity connector to Google Data Studio for FHIR | 0.0 (0) | 24 May, 2021 | ||||
fhir-integratedml-exampleAn example on how to use InterSystems IRIS for Health FHIR database to perform ML models througth InterSystems IRIS IntegratedML | Docker ML ML | 4.8 (3) | 01 Aug, 2021 | |||
FHIRaaS with OAuth 2.0This is a straightforward Angular app using the FHIR Accelerator Service as the Clinical Repository. It uses OAuth 2.0 as authorization and displays all patients and resources as JSON. | R | 0.0 (0) | 30 May, 2021 | |||
FHIRDemoWithAPIKeySimple FHIR application to retrieve patients and observations | P | 0.0 (0) | 16 Sep, 2021 | |||
![]() FhirgureHelping neurodiverse employees at book medical appointments. | J | 0.0 (0) | 21 Sep, 2021 | |||
fhir-scraperA simple python script to copy/scrap/crawl a FHIR repository. | G | Python | 4.0 (1) | 08 Oct, 2021 | ||
fhir-client-javaA simple example of a Fhir client in java | L | Docker | 0.0 (0) | 13 May, 2022 | ||
fhir-client-pythonA simple example of a Fhir client in python | L | Docker Python | 0.0 (0) | 13 May, 2022 | ||
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 | ||
fhir-client-netA simple example of a Fhir client in c# | L | Docker | 3.0 (1) | 13 May, 2022 | ||
![]() fhir-healthy-pregnancyApp online to record the information about the pregnancy | Docker | 3.5 (1) | 27 Nov, 2022 | |||
![]() 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 | ||||
![]() FHIR - AI and OpenAPI ChainCall any FHIR API with natural language input. OpenAI. LangChain | Docker Python IPM AI | 0.0 (0) | 07 Jul, 2023 | |||
fhir-orga-dtThis is a simple full python IRIS production that gather information from a csv, use a DataTransformation to make it into a FHIR object and then, save that information to a FHIR server. | L | Docker Python | 4.5 (1) | 17 Aug, 2022 | ||
fhir-profile-validationValidating FHIR resources against profiles | D | Docker | 4.5 (1) | 30 May, 2023 | ||
![]() FHIR-XMLToJSONConvert FHIR XML to JSON resource message structure | Docker IPM | 3.5 (1) | 22 Sep, 2023 | |||
fhir-chatGPTA Virtual Healthcare chat Assistant | D | Docker AI | 0.0 (0) | 01 Jul, 2023 | ||
FHIR-OCR-AIImage extraction text to fhir message | x | IPM AI | 0.0 (0) | 04 Feb, 2024 | ||
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 | ||
![]() fhir-pexJava Application sending FHIR messages to Kafka topics. | F | Docker AI | 4.0 (1) | 26 Nov, 2023 | ||
![]() fhirserver-profile-based-validationA sample of calls (Postman Collection) to demonstrate FHIR Profile-based Validation Requests | N | 5.0 (1) | 11 Dec, 2023 | |||