FAQs

Find answers to common questions about the Chorus platform architecture, capabilities, and clinical integrations.

What types of devices are supported by Chorus?

Chorus primarily supports a range of cellular-enabled medical devices designed to capture physiological signals seamlessly. This includes cellular ECGs, blood pressure cuffs, blood glucose monitors, pulse oximeters, and body weight scales. Device compatibility can be expanded using our SMART on FHIR integration gateways.

Does Chorus replace electronic health record (EHR) systems?

No. Chorus is designed to complement existing electronic health record (EHR) systems (such as Epic or Cerner) by providing dedicated remote monitoring capabilities, device connectivity, and intensive physiological data analysis. The platform integrates back with EHR systems using standardized FHIR data exchange mechanisms.

How is patient data secured within the platform?

Chorus operates on a HIPAA-eligible AWS cloud environment. Patient data is protected through encryption at rest and in transit, strict Role-Based Access Control (RBAC), multi-factor authentication via AWS Cognito, and comprehensive, immutable audit logging.

Can clinicians override AI-generated insights?

Yes. Chorus employs a Human-in-the-Loop governance model. AI-assisted insights and stratifications are entirely advisory and require explicit clinician review and sign-off. Providers always maintain full authority to interpret physiological data and determine appropriate clinical actions.

How does Chorus support billing documentation?

Chorus leverages event-driven billing logic. It automatically links monitoring events, daily patient interactions, and provider review times to structured records (such as ChargeItem resources) that justify CPT codes like 99453, 99454, 99457, and 99091. These claim-ready records can be easily exported for use within your standard revenue cycle management systems.