The questions we get, including the uncomfortable ones.

Nothing you couldn't do with enough staff and enough discipline. We run the parts that are easy to do badly: identifying who qualifies, holding enrolment until consent is documented correctly, counting distinct transmission days, assembling time logs, and refusing to prepare a claim for a month that didn't clear every requirement. The clinical judgment stays with your clinicians.

No. We read your chart through a standard export and get signed documents back into the record. There is no migration, no replacement, and no new system your clinicians have to work inside during a visit.

Nothing that reaches a patient, a chart, or a payer. It reads, ranks by acuity, and drafts — orders, outreach, and clinical notes. It cannot sign, diagnose, adjust medication, enrol a patient, or submit a claim. Those are enforced boundaries in the code, not guidelines.

Your physician or nurse practitioner, always. An order is a practitioner order; clinical staff can furnish monitoring and management under general supervision but cannot sign it. The console enforces that distinction by role.

Monitoring devices ship preconfigured and transmit over their own cellular connection, so readings arrive without depending on a patient's home network.

Running these programs at all creates exposure; running them without documentation is what turns exposure into repayment. Our answer is to hold claims rather than file optimistically, and to assemble an evidence file per patient-month as the work happens. How the gates work.

You do. We prepare, you submit. We never bill a payer, never take reassignment of benefits, and never sit between your practice and its money.

You do. As between us, the practice owns the patient records and the protected health information. If you leave, you get an export and we return or destroy the data at your direction.

We are a business associate and we expect to sign one — no patient data reaches our system before it is executed. On the broader question, we would rather show you the list than assert a word: what is built, what is committed, and what we don't have, including the certifications we lack.

An opaque internal token, an age, coded conditions, and the readings. No name, no date of birth, no Medicare Beneficiary Identifier, no address. Identity is stripped before anything leaves our boundary.

Some combinations are allowed and some are explicitly not, and the answer differs by program and by month. The engine checks for the conflicts rather than trusting anyone to remember them, and holds anything that would double-dip.