Open Health Stack 用例
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
OHS 组件有助于更轻松地采用 FHIR。您可以单独使用它们,也可以将它们组合起来构成端到端数字健康平台的基础。
基于 FHIR 的 Android 应用
借助 Android FHIR SDK,开发者可以快速构建 FHIR 原生 Android 应用。SDK 是一组模块化库,旨在为一系列不同的用例提供灵活性。其中包括使用:

资源:
利用 SMART-on-FHIR 加强隐私保护
FHIR 信息网关是一个独立的反向代理,您可以将其部署在任何应用的前面,以加强隐私保护并更轻松地实施组织访问权限控制政策。当与由 Android FHIR SDK 提供支持的应用结合使用时,信息网关还可以增强同步操作,例如限制特定健康工作器在离线工作时可以下载和访问的患者数据。
作为独立代理,Info Gateway 支持与 SMART-on-FHIR 应用集成。

资源:
FHIR 分析解决方案
由于 FHIR 数据结构高度嵌套,因此编写查询来生成数据分析可能非常困难。FHIR DataPipes 通过可轻松部署且可水平扩缩的流水线来简化问题,该流水线可将 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 服务器,开发者可以实现与现有系统、第三方适配器或自定义代码的集成。
资源:
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-25。
[null,null,["最后更新时间 (UTC):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."]]