Open Health Stack use cases
Stay organized with collections
Save and categorize content based on your preferences.
OHS components make it easier to adopt FHIR. You can use them separately or
combine them to form the foundation of an end-to-end digital health platform.
FHIR-based Android apps
Using the Android FHIR SDK, developers can
build FHIR native Android applications quickly. The SDK is a modular set of
libraries designed to provide flexibility for a range of different use cases.
These include using:
Resources:
- Get started quickly with the SDC
codelab.
- Read about how developers are building mobile
solutions with OHS.
Enhancing privacy, leveraging SMART-on-FHIR
The FHIR Info Gateway is a stand-alone
reverse proxy that you can deploy in front of any application to enhance privacy
and make it easier to implement organizational access control policies. When
used together with an Android FHIR SDK powered application the Info Gateway can
also enhance sync operations, for example, to limit the patient data that a
specific health worker can download and access when working offline.
As a stand-alone proxy, the Info Gateway supports integration with SMART-on-FHIR
applications.
Resources:
FHIR Analytics Solutions
Due to the heavily nested structure of FHIR data, writing queries to generate
insights can be challenging. FHIR Data
Pipes simplify the problem with
an easily deployable and horizontally scalable pipeline that transforms FHIR
data into an SQL-on-FHIR
format, making it possible to
query FHIR Data via SQL.
FHIR Data Pipes can be helpful where FHIR is the source of the data to be
analyzed. Common scenarios for developers include:
- As an extension of a FHIR native mobile health solution - see foundations
for an end-to-end digital health
solution.
- As part of a stand-alone analytics solution that is leveraging FHIR - see
hybrid architecture example.
Resources:
Foundations for an end-to-end digital health solution
Using all of the OHS components together provides a foundation for developers to
build FHIR based platforms or solutions. By providing a number of core
features—like sync and offline capabilities—and reducing the technical
complexity of working with FHIR, developers can save significant time and focus
more on the value-add of their solutions.
Resources:
Hybrid Architecture Example
OHS component modularity lets developers pick and choose the pieces that best
help them solve specific problems.
There are many examples of where it could be beneficial to transition a part of
an existing system to FHIR while maintaining other parts of the solution as they
are. These include:
Non-FHIR data collection to FHIR based analytics: In this scenario, data
collected in a non-FHIR way is transformed into FHIR to enable the use of
the OHS FHIR Data Pipes for a common approach to generating insights from
FHIR data. To transform data, developers can use existing vendor APIs,
existing third party services such as the Global
Goods
approved OpenFn or leverage relevant open
source
projects.
FHIR Native app to Non-FHIR Systems: In this scenario, a FHIR native
mobile app built using the Android FHIR SDK is used for offline care
delivery with data synced to a FHIR Server. From the FHIR server developers
could implement integrations with existing systems, third party adapters or
custom code.
Resources:
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-07-23 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-07-23 UTC."],[[["\u003cp\u003eOpen Health Stack (OHS) components simplify FHIR adoption and can be used individually or combined for a comprehensive digital health platform.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can build offline-first Android FHIR apps using the Android FHIR SDK, featuring Structured Data Capture, FHIR Engine, and Workflow libraries.\u003c/p\u003e\n"],["\u003cp\u003eThe FHIR Info Gateway enhances privacy and access control for FHIR applications, supporting SMART-on-FHIR integration.\u003c/p\u003e\n"],["\u003cp\u003eFHIR Data Pipes streamline FHIR analytics by transforming data into an SQL-on-FHIR format for easier querying.\u003c/p\u003e\n"],["\u003cp\u003eOHS components offer modularity, allowing integration with existing systems in hybrid architectures for data transformation and app development.\u003c/p\u003e\n"]]],["The OHS (Open Health Stack) enables FHIR adoption through modular components. Developers can use the Android FHIR SDK to build FHIR-based apps, leveraging libraries for data capture, offline solutions, and clinical decision support. The FHIR Info Gateway enhances privacy and access control. FHIR Data Pipes transforms FHIR data into SQL for simplified analysis, supporting both end-to-end and hybrid solutions. These components enable building complete FHIR platforms or integrating FHIR into existing systems.\n"],null,["# Open Health Stack use cases\n\nOHS components make it easier to adopt FHIR. You can use them separately or\ncombine them to form the foundation of an end-to-end digital health platform.\n\nFHIR-based Android apps\n-----------------------\n\nUsing the [Android FHIR SDK](/open-health-stack/android-fhir), developers can\nbuild FHIR native Android applications quickly. The SDK is a modular set of\nlibraries designed to provide flexibility for a range of different use cases.\nThese include using:\n\n- the [Structured Data Capture\n Library](/open-health-stack/android-fhir/data-capture) in an existing application to enable data collection via FHIR,\n- the [FHIR Engine Library](/open-health-stack/android-fhir/fhir-engine) to build offline first solutions on FHIR and,\n- the advanced capabilities of the [Workflow\n Library](/open-health-stack/android-fhir/workflow) to enable CQL-based clinical decision support from WHO Smart Guidelines content.\n\n**Resources**:\n\n- Get started quickly with the [SDC\n codelab](/open-health-stack/codelabs/data-capture).\n- [Read](/open-health-stack/stories) about how developers are building mobile solutions with OHS.\n\nEnhancing privacy, leveraging SMART-on-FHIR\n-------------------------------------------\n\nThe [FHIR Info Gateway](/open-health-stack/fhir-info-gateway) is a stand-alone\nreverse proxy that you can deploy in front of any application to enhance privacy\nand make it easier to implement organizational access control policies. When\nused together with an Android FHIR SDK powered application the Info Gateway can\nalso enhance sync operations, for example, to limit the patient data that a\nspecific health worker can download and access when working offline.\n\nAs a stand-alone proxy, the Info Gateway supports integration with SMART-on-FHIR\napplications.\n\n**Resources**:\n\n- Explore the [FHIR app examples\n repository](https://github.com/google/fhir-app-examples) to see how the FHIR Info Gateway can be used with other OHS components.\n\nFHIR Analytics Solutions\n------------------------\n\nDue to the heavily nested structure of FHIR data, writing queries to generate\ninsights can be challenging. [FHIR Data\nPipes](/open-health-stack/fhir-analytics/data-pipes) simplify the problem with\nan easily deployable and horizontally scalable pipeline that transforms FHIR\ndata into an [SQL-on-FHIR\nformat](https://github.com/FHIR/sql-on-fhir), making it possible to\nquery FHIR Data via SQL.\n\nFHIR Data Pipes can be helpful where FHIR is the source of the data to be\nanalyzed. Common scenarios for developers include:\n\n1. As an extension of a FHIR native mobile health solution - [see foundations\n for an end-to-end digital health\n solution](#foundations_for_an_end-to-end_digital_health_solution).\n2. As part of a stand-alone analytics solution that is leveraging FHIR - [see\n hybrid architecture example](#hybrid_architecture_example).\n\n**Resources**:\n\n- Get started quickly with the [single machine deployment\n tutorial](https://github.com/google/fhir-data-pipes/wiki/Analytics-on-a-single-machine-using-Docker).\n- Explore the [FHIR app examples\n repository](https://github.com/google/fhir-app-examples) to see how the FHIR Data Pipes can be used with other OHS components.\n\nFoundations for an end-to-end digital health solution\n-----------------------------------------------------\n\nUsing all of the OHS components together provides a foundation for developers to\nbuild FHIR based platforms or solutions. By providing a number of core\nfeatures---like sync and offline capabilities---and reducing the technical\ncomplexity of working with FHIR, developers can save significant time and focus\nmore on the value-add of their solutions.\n\n**Resources**:\n\n- Explore the [FHIR app examples\n repository](https://github.com/google/fhir-app-examples) to see how all of the components can be used together.\n- [Read about how Ona has used OHS](/open-health-stack/stories/ona) to build OpenSRP FHIRCore.\n\nHybrid Architecture Example\n---------------------------\n\nOHS component modularity lets developers pick and choose the pieces that best\nhelp them solve specific problems.\n\nThere are many examples of where it could be beneficial to transition a part of\nan existing system to FHIR while maintaining other parts of the solution as they\nare. These include:\n\n1. *Non-FHIR data collection to FHIR based analytics* : In this scenario, data\n collected in a non-FHIR way is transformed into FHIR to enable the use of\n the OHS FHIR Data Pipes for a common approach to generating insights from\n FHIR data. To transform data, developers can use existing vendor APIs,\n existing third party services such as the [Global\n Goods](https://digitalsquare.org/blog/2023/2/16/digital-square-announces-new-software-global-goods-approved-through-notice-g)\n approved [OpenFn](http://openfn.org) or leverage relevant [open\n source\n projects](https://github.com/GoogleCloudPlatform/healthcare-data-harmonization).\n\n2. *FHIR Native app to Non-FHIR Systems*: In this scenario, a FHIR native\n mobile app built using the Android FHIR SDK is used for offline care\n delivery with data synced to a FHIR Server. From the FHIR server developers\n could implement integrations with existing systems, third party adapters or\n custom code.\n\n**Resources**:\n\n- Explore the [FHIR app examples\n repository](https://github.com/google/fhir-app-examples) to see how all of the components can be used together."]]
