Roger Healthcare
Ambient scribe for home health clinicians, built around the OASIS and the routine visit note, and distinguished from the rest of that segment by how much of the work happens before and during the visit rather than after it. Ahead of the encounter Roger pulls referral documents, attachments and schedules from the agency EHR, summarises what the company describes as hundreds of pages of discharge paperwork into a readable referral summary, and pre fills OASIS fields such as past medical history so the clinician arrives prepared. During the visit it listens ambiently and prompts the clinician about items they have not yet addressed, while they are still in the patient's home, which is compliance feedback at the point of care rather than a QA query days later. Afterwards the clinician can add sensitive or additional detail by dictation, and Roger combines the recordings with the referral information to complete the chart. The company is unusually direct about its integration mechanism, describing a proprietary robotic process automation system that syncs into the EMR in near real time without changing existing workflows. Most vendors in this lane describe RPA as integration; naming it is a candour worth noting, and it also tells a buyer exactly what kind of brittleness and audit trail questions to ask about. The underlying model is described as a multi stage pipeline trained on millions of rows of home health visit data, and the product handles the parts of the assessment that generic scribes struggle with, including wound measurements, medication reconciliation, the Plan of Care, and named OASIS items such as the M1800 series and GG functional scores. Multi language capture is supported. Roger Healthcare spun out of Cornell, pairing AI researchers with operators from the home health industry, and is based in the San Francisco Bay Area. New Day Healthcare, a home health organisation reported at 17,000 patients across six states, has deployed it company wide.
Capability Axes
Referral summarisation, chart pre fill, ambient capture, the real time prompting about missed items, and completion of the OASIS and routine notes are all model output. No human scribe tier, no coding services layer and no underlying EHR that the AI is a feature of. The company positions itself as a documentation platform sold to agencies, and the RPA sync is plumbing around the model rather than the product itself.
The oversight question here is not whether a human reviews but WHEN, and the ordering is the reason this is C rather than B. Roger's described sequence is that it fills out the entire chart in the agency EMR within minutes and the clinician then reviews the results without changing workflows. That is write first, review second. The pattern this index credits is the opposite, best shown by ModMed, where suggestions populate downstream workflows only once the provider approves. Two real mitigations belong alongside it. The OASIS is not submitted to CMS until the clinician signs it, so a draft sitting in the EMR is not yet a regulatory filing. And the real time prompting during the visit is a genuine oversight strength that most of the lane lacks entirely, catching omissions while the clinician is still with the patient and can still ask. No confidence threshold, abstention behaviour or escalation path is published.
Graded B for naming its architecture, which most of this lane will not do. Roger describes a multi stage AI pipeline trained on millions of rows of home health visit data, and separately names its EMR sync as a proprietary robotic process automation system. Both are real architectural statements that tell a buyer what they are getting and what to test. It also gives a concrete worked example of what domain training buys: when a patient says they walked to the mailbox yesterday, the system reads that as implying specific functional scores for ambulation, which is the kind of inference a general model would miss. Held at B because no model card, named model, accuracy figure or evaluation methodology exists, and the headline 80 percent time saving is described as proven without any study, denominator or comparator behind it.
One genuinely useful data point and no study behind it. New Day Healthcare, reported at 17,000 patients across six states, has rolled Roger out company wide, which is a named enterprise agency at real scale and is stronger than the anonymous testimonials most of this segment offers. Against that, the 80 percent time saving is asserted as proven with no cohort, baseline or method, and the remaining evidence is unattributed clinician quotes. On the standing precedent in this index that scale is not evidence, this stays at C. One thing a buyer should check directly: a competitor's own comparison page lists New Day Healthcare as ITS customer while Roger publishes a company wide rollout with the same agency. That may mean parallel evaluation, a switch, or different business units, but both vendors cannot be the sole documentation system there and the discrepancy is worth resolving with the agency rather than with either vendor.
Not assessed. No retention schedule, audio deletion commitment, encryption detail, de identification practice or statement on training use was located. Two aspects of this product make the gap worth pressing. The model is described as trained on millions of rows of home health visit data, and a buyer should establish whose data that was and on what basis. And the RPA layer holds credentials to the agency EMR in order to write into it, which is a different and broader access surface than a scribe that submits a note through an API.
Not assessed. No HIPAA statement, business associate agreement reference or compliance page was located in the retrieved materials, which is unusual for a product handling recorded patient encounters at enterprise agency scale. The absence is more likely a website gap than a compliance gap given the named enterprise deployment, but this index grades what is published and nothing was found. It should be the first item on a buyer's list.
Not assessed. No named or dated certification, audit report, penetration test or trust centre located. For a product whose integration works by automating the EMR interface under stored credentials, a health system or enterprise agency security review will want more here than for a typical scribe, and none of it is published.
Not a regulated medical device and none claimed or required. The regulatory weight in this product sits with CMS rather than FDA: OASIS items including the M1800 series and GG functional scores drive both quality reporting and case mix payment, so a scoring inference drawn from conversation lands in survey findings and payment integrity rather than in device oversight.
Mixed, with a real positive and a real gap. The positive is that Roger's compliance mechanism runs FORWARD rather than backward: it prompts the clinician about undocumented items while they are still in the home, which prevents an omission rather than querying it later, and reduces the QA back and forth the segment is built around. Its revenue framing stays on the right side of the coding gradient this index tracks, because the stated mechanism is throughput, serving more patients without adding staff, rather than coding intensity, and on the standing precedent that speed metrics are not coding metrics that does not belong on the gradient. The gap is disclosure. No fairness statement, subgroup analysis or accent and dialect performance breakdown was located despite multi language capture being sold as a feature, and the workforce in home health is among the most linguistically diverse in US healthcare.
Functionally deep and architecturally brittle, and the vendor says so plainly, which is the reason for the B rather than a lower grade. The sync is described as a proprietary robotic process automation system operating in near real time, and it works in both directions: pulling attachments, schedules and referral packets out of the EMR before the visit and filling in all fields of the chart after it. Reading referral documents out and writing the full assessment back is more than almost any RPA implementation in this lane attempts. The costs of that architecture are the standard ones and a buyer should price them in: RPA drives the user interface rather than a sanctioned data channel, so it breaks when the EMR changes its screens, and the audit trail shows an automated session rather than an integration. NO EMR IS NAMED. For a home health agency the systems that matter are WellSky, MatrixCare, HCHB, Axxess, Devero and Netsmart, and which of them are supported today is not published.
Not assessed. Delivered as a cloud service with an RPA connector into the agency EMR. No hosting region, residency option, sub processor detail or offline behaviour was located. Offline behaviour is a specific question for this product because the capture happens in patients' homes, and three vendors in this segment now address low connectivity explicitly while Roger does not.
Not assessed. No price, unit of pricing, tier structure or trial is published anywhere, and the only route in is a booked demo. This follows the house convention in this category of leaving the axis unrated rather than inventing a grade from an absence. The one price signal available is a customer testimonial stating that competing products were more expensive and did less, which is a positioning claim from an unnamed source rather than a disclosure.
Home health only, and deep within it. The product covers the comprehensive assessment rather than a summary of the conversation, and it names the instruments, which is this index's test for real domain depth as opposed to a template library: the OASIS including the M1800 series and GG functional scores, the Plan of Care, wound measurements and medication reconciliation, alongside routine visit notes. It explicitly targets the failure modes generic scribes hit in this setting, including reading a list of fifteen medications and handling regulatory forms. Multi language capture is supported, with no language count published. Held at B rather than A because coverage is one care setting in one country, with no hospice, no facility based care and no breadth beyond home health.
Pricing
Vendor-published figures are labeled as such. Figures labeled “Estimated” are derived from third-party sources and have not been confirmed by the vendor.
| Entry Price | Pricing Basis | BAA Tier | Implementation | Source |
|---|---|---|---|---|
|
Not published. Access is by booked demo only, with no price, tier or trial disclosed.
|
Not disclosed. Sold to home health agencies rather than to individual clinicians, and marketed to both large enterprises and smaller agencies, which implies negotiated agency level contracts. | No HIPAA statement or BAA reference located in published materials. Establish this first. | None published. Deployment requires connecting the RPA layer to the agency EMR, which the vendor describes as working without changing existing workflows, so a buyer should establish whether connector work for their specific EMR is included or scoped separately. | Vendor Published |
Five things to settle before signing. Which home health EMR is supported by name, since none is published and the whole product depends on the connector. Whether a business associate agreement exists and what it covers, since no HIPAA statement was found at all. What happens when the EMR changes its interface, because RPA drives the screens rather than an API and the maintenance burden of that sits somewhere. Whether the clinician reviews before or after the chart is written into the EMR, since the published sequence is that Roger fills the chart and the clinician then reviews the result. And what the model was trained on, since it is described as trained on millions of rows of home health visit data and the provenance of that corpus is not stated. Separately, verify the New Day Healthcare deployment directly: a competitor publishes a comparison page naming the same agency as its own customer, and the discrepancy is worth resolving with the agency rather than with either vendor.