RPM Integration Questions Answered

Circadify outputs vital signs as HL7 FHIR R4 Observation resources with standard LOINC coding. Each scan session produces individual Observation resources for heart rate, heart rate variability, respiratory rate, SpO2, and autonomic stress index. Resources include patient references, device identifiers, and timestamps structured for direct ingestion by FHIR-capable EHR systems.

Circadify's FHIR Observation output is structured to align with Epic's and Cerner's standard FHIR R4 intake endpoints. Your integration team maps Circadify observation codes to your instance's flowsheet rows or result fields using standard FHIR resource mapping. No proprietary connectors or custom middleware is required, and most teams complete initial integration within one to two development sprints.

You can define threshold-based alerting rules per vital sign, per patient, or across patient panels. When a reading falls outside defined parameters, notifications route through your existing clinical communication infrastructure. Alert configurations support escalation tiers so urgent readings reach on-call providers while trend-based alerts go to care coordinators for scheduled follow-up.

All rPPG signal processing and vital sign computation occurs entirely on the patient's device. Only structured FHIR Observation payloads containing derived vital sign values transmit to your systems. No raw video, images, or biometric source data ever leaves the device. This architecture significantly reduces PHI exposure surface area and simplifies BAA scoping and security risk assessments.

Patients download the Circadify app and complete a brief enrollment flow. No peripheral hardware needs to be shipped, paired, or maintained. Patients scan using their existing smartphone camera, which eliminates device logistics entirely. Most health systems report patient onboarding completion rates significantly higher than hardware-dependent RPM programs because there is no equipment barrier.

Circadify generates timestamped, device-identified vital sign readings that support the documentation requirements for CMS RPM billing codes. Each reading includes device identifiers, patient references, and precise timestamps that your billing team can use to substantiate device setup (99453), monthly data transmission (99454), and clinical staff interaction time (99457, 99458) claims.