This page captures proposed architectures and workflows for supporting the CHW Interoperability Workflows.

Architectural Components

• Mobile App - This is the primary data entry point for the CHIS users.
• Central System - This central system is used to manage the mobile deployment, house all information collected, and ensure that the right information is synced with for the right users devices. Examples include CommCareHQ, OpenSRP Server, and CHT Core.
• Web Ui - This is the web interface with which users interact with the system. This Web Ui can be used for management of the system, health worker performance, basic reporting, and primary data collection.
• (Optional) Extract Transform Load (ETL) Tool - This is a tool that's responsible for extracting transactional information from the central system, normalizing it and loading it into the Data Warehouse.
• (Optional) Data Warehouse - This is a normalized data repository that is focused on providing performant analytics and reporting
• (Optional) Data Visualization Tools - These are tools that help end users make sense of information in the system with minimal programming involved. Tools in this category include Power BI, Tableau, and Superset
• Facility Based Electronic Medical Record System - A facility based electronic medical record system

Core Thoughts

• CHWs are often linked to working out of a centralized physical brick and mortar location where their management sits. This could be a district hospital, primary health facility, or other
• We often need to sync information with a facility based EMR to provide medical record continuity between the CHIS and facility based care

Point to Point FHIR Interoperability

HIE Mediated FHIR Interoperability