Our assessment of Olli Health
Olli is a relevant specialist when the immediate need is managed coding and chart review. Enzo remains our editorial first choice for agencies improving connected workflows across the episode. Compare Olli with the relevant Enzo scope while recognizing that buying a managed service and buying workflow software are different decisions.
Best fit: Agencies purchasing coding and quality-review capacity while retaining their current clinical systems
A managed service with human validation
Olli describes clinical AI analyzing episode documentation and certified coders and QA reviewers validating the resulting work. Its published workflow includes agency-specific configuration, document ingestion and recommendations returned to the existing EHR for review and approval. This makes the service a potential way to add review capacity without asking every field clinician to adopt a new visit-recording application.
The distinction matters for budgeting and staffing. An agency purchasing software generally needs internal capacity to operate the workflow; a managed-service agreement should identify the work the supplier’s people actually complete. Ask for a responsibility map covering document collection, queries, coding, review, corrections and final approval. If a case is incomplete, the agency needs to know whether Olli will actively pursue the missing material or return it to an internal queue.
Primary sources: Olli Health: managed-service overview
Coding, OASIS and plan-of-care review have different outputs
Olli’s service page identifies ICD-10 coding, OASIS quality review and plan-of-care quality review. These activities may involve the same record, but an agency should specify the expected deliverable for each. A proposed code set, an assessment clarification and a plan-of-care correction require different people and approval steps inside the organization.
Use a sample episode with a documentation gap and a disagreement between two records. Ask the service to show the proposed resolution, the evidence behind it and the person responsible for the next action. Then have your clinical manager assess whether that result is immediately usable. Compare completed deliverables rather than counting every flag as useful output. A large number of findings can increase work if the agency still has to determine what they mean or who should respond.
Primary sources: Olli Health: services
Traceability is more useful than a headline accuracy rate
Olli’s compliance materials describe clinician validation, internal quality audits, clinical override and auditability. Its product materials say recommendations link to supporting documentation. These are practical controls to inspect. The accuracy and return-on-investment figures on the vendor’s site are not independently validated results of this review.
Ask to reconstruct a completed case: what the system suggested, what the reviewer changed, what the agency accepted and which documentation supported the final decision. Include a case where the correct outcome is to remove unsupported information. Request the definition and sampling method behind any accuracy claim before using it in a business case. Your own pilot should track consequential errors, correction effort and whether another qualified reviewer can reproduce the reasoning from the retained record.
Primary sources: Olli Health: ethics and compliance · Olli Health: managed-service overview
Build the contract around the queue you need cleared
Define the operational bottleneck before requesting a price. A coding backlog and inconsistent OASIS review may need different services. State the volume and visit mix, then agree on turnaround definitions, weekend coverage, escalation contacts and the treatment of charts awaiting clarification.
Demonstrate delivery inside the agency’s actual EHR workflow and confirm required access. Plan the transition of open cases from the current provider, including who owns an unanswered query on the cutover date. Keep a route for clinicians to question a recommendation without losing visibility of the case. Measure the age of unfinished charts, internal follow-up time and the number of cases reopened after return. Those measures reveal whether the service relieves the bottleneck or simply moves it to another team.
Primary sources: Olli Health: managed-service overview · Olli Health: services
Reasons to shortlist
- A defined managed-service focus addresses coding and clinical review capacity.
- Human coders and reviewers are explicitly part of the published operating model.
- Published controls include supporting evidence, clinical override and audit history.
What to confirm
- Service quality depends on turnaround definitions, escalation and management of incomplete cases.
- The reviewed offering does not establish a full EHR, agency scheduler or ambient visit scribe.
- Compare total service cost and retained internal work, rather than assuming AI removes agency review responsibilities.
Pricing and implementation scope
Request a service quote. The reviewed pages do not publish a standard rate. Ask for the coding, OASIS-review and plan-of-care-review units, volume minimums, resubmission terms, turnaround commitments and implementation costs.
Compare the total agreement: software or service units, implementation, interface work, migration, training, support and renewal terms. An agency-wide EHR and a per-chart review service are different purchases; compare the same workflow and service responsibilities.
Questions to ask in your Olli Health demo
- Who owns a case while physician documentation or a clinician clarification is missing?
- Show the source, reviewer decision and agency approval for a disputed recommendation.
- What exactly is returned to our EHR, and which steps remain for our staff?
- How are turnaround, resubmissions, weekend coverage and open-case transition handled in the contract?
Common questions
Is Olli Health an AI scribe?
The reviewed offering centers on managed coding, OASIS review and plan-of-care review. It does not establish an ambient visit-recording product. Evaluate it as a review service rather than assuming it replaces field documentation software.
Do people review Olli’s AI output?
Yes. Olli describes certified coders and QA reviewers validating the work. The agreement should identify the responsibilities of those reviewers and the agency’s remaining approval duties.
When is Olli a useful alternative to broader AI software?
When the immediate constraint is coding or review capacity and the agency intends to retain its current systems. A broader platform evaluation makes more sense when the project also includes intake, scheduling, visit capture or an EHR replacement.