開啟 Health Stack 用途
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
OHS 元件可讓您輕鬆採用 FHIR。您可以單獨使用，也可以合併使用，構成端對端數位健康平台的基礎。
以 FHIR 為基礎的 Android 應用程式
開發人員可以使用 Android FHIR SDK，快速建構 FHIR 原生 Android 應用程式。SDK 是一組模組化的程式庫，專為各種用途靈活設計。這些 API 包括：
資源：
強化隱私保護，運用 SMART-on-FHIR
FHIR Info Gateway 是獨立的反向 Proxy，可部署至任何應用程式之前，可加強隱私保護，並可讓您輕鬆實作機構存取權控管政策。與採用 Android FHIR SDK 的應用程式搭配使用時，資訊閘道也可以改善同步處理作業，例如限制特定健康工作者在離線工作時可以下載及存取的病患資料。
資訊閘道可做為獨立 Proxy，支援與 SMART-on-FHIR 應用程式整合。
資源：
FHIR 數據分析解決方案
由於 FHIR 資料高度巢狀結構，撰寫查詢來產生深入分析可能並不容易。FHIR 資料 Pipes 提供易於部署及水平擴充的管道，可將 FHIR 資料轉換成 SQL-on-FHIR 格式，進而簡化問題，讓您能夠透過 SQL 查詢 FHIR 資料。
FHIR 資料管道在處提供實用資源，其中 FHIR 是待分析資料的來源。開發人員的常見情境包括：
- 此為 FHIR 原生行動健康解決方案的延伸：參閱端對端數位健康解決方案的基礎。
- 做為使用 FHIR 的獨立數據分析解決方案的一部分，請參閱混合架構範例。
資源：
端對端數位健康解決方案的基礎
搭配使用所有 OHS 元件可為開發人員奠定基礎，建構 FHIR 式平台或解決方案。透過提供同步處理和離線功能等多種核心功能，並降低與 FHIR 合作的技術複雜度，開發人員可以省下大量時間，並將更多心力放在解決方案的附加價值上。
資源：
混合型架構範例
OHS 元件模組性可讓開發人員挑選及選擇最能協助他們解決特定問題的項目。
許多例子都有助於將現有系統的一部分轉換至 FHIR，同時維持解決方案的其他部分。這些服務包括：
將非 FHIR 資料收集作業傳送至 FHIR 式分析：在這個情境中，以非 FHIR 方式收集的資料會轉換為 FHIR，以便使用 OHS FHIR 資料管道，從 FHIR 資料產生深入分析。如要轉換資料，開發人員可使用現有的供應商 API、現有的第三方服務 (例如 Global
Goods 核准的 OpenFn)，或是利用相關的開放原始碼專案。
FHIR 原生應用程式到非 FHIR 系統：在這種情境中，使用 Android FHIR SDK 建構的 FHIR 原生行動應用程式會用於離線照護，以及與 FHIR 伺服器同步的資料。您可以從 FHIR 伺服器開發人員實作與現有系統、第三方轉接程式或自訂程式碼的整合。
資源：
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-07-25 (世界標準時間)。
[null,null,["上次更新時間：2025-07-25 (世界標準時間)。"],[[["\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."]]
