Questions From Implementers

Circadify runs on Android 8.0+ devices with a front-facing camera. It is optimized for the entry-level handsets commonly procured by global health programs — devices in the $50-150 range. No specialized sensors, accessories, or hardware modifications are required. If your CHWs already carry smartphones, they likely already have a compatible device.

All screening computation happens on the device itself. The rPPG algorithms, signal processing, and result generation run entirely locally. Results are stored in on-device storage and queued for sync. When the device next connects to Wi-Fi or mobile data — whether at a health facility, supervision point, or CHW home — queued data syncs automatically. There is no dependency on real-time connectivity for any screening function.

Yes. Screening outputs map to standard DHIS2 data elements. Your technical team configures the mapping once during deployment setup — defining which vital signs indicators correspond to which DHIS2 data elements and organization units. After that, synced screening data populates DHIS2 dashboards automatically. We also support flat-file export for programs using other HMIS platforms.

No. Circadify is a screening and pre-screening tool designed to identify individuals who should be referred for professional clinical evaluation. It does not diagnose any condition. Think of it as a triage layer — it helps CHWs identify who in a community needs to be seen at a facility, which is especially valuable where facility access is limited and health worker ratios are stretched thin.

The screening workflow is designed for a single orientation session — typically 30-60 minutes. The app provides visual step-by-step guidance in local languages, so CHWs do not need to memorize protocols. In field deployments, CHWs have successfully conducted independent screenings after one supervised practice session. The interface was designed with input from CHW program managers across multiple country contexts.

Screening data is processed and stored on-device until intentional sync. No data is transmitted to third-party servers. For research deployments, configurable data handling policies support IRB requirements including participant consent workflows, data minimization, and country-specific data residency rules. The architecture is designed to satisfy both Ministry of Health data governance frameworks and institutional review board protocols.