Home health AI documentation platform · Review

Apricot Review 2026

Apricot makes AI documentation software for home health clinicians that turns visit recordings and structured inputs into OASIS assessments and visit notes, with coding and QA help, inside the agency's existing EMR.

By · Published · Updated 3.9 Good
Products
Documentation, coding and QA
Pricing
Custom quote
Deployment
Managed integration with an existing EMR
Our rank
Tied #3 of 16 in skilled home health

Direct answer

Apricot makes AI documentation software for home health clinicians that turns controlled visit recordings, structured inputs and a post-visit debrief into OASIS and routine visit notes, with coding and QA assistance inside the agency’s existing EMR. Apricot prices by quote, connects through a managed EMR integration and is embedded in Netsmart’s CareFabric platform under a 2024 partnership. Apricot claims a SOC 2 Type II report without naming an auditor, is not a scheduling or billing system, and its published results, such as an 85% cut in documentation time at Choice Health at Home, come from Apricot itself.

Clinical AI Report editorial review · October 28, 2026

Key takeaways

  • Apricot turns clinician-controlled visit recordings, structured inputs and a post-visit debrief into OASIS and routine visit notes, with coding and QA assistance, for agencies keeping their existing EMR.
  • Apricot connects through a managed EMR integration, is embedded in Netsmart’s CareFabric platform under a 2024 partnership, and names Homecare Homebase as the EMR in its Choice Health at Home case study.
  • Apricot prices by custom quote for the proposed scope, publishes no standard rate and says most agencies are live in about a month.
  • Apricot claims a SOC 2 Type II report without naming an auditor or audit period, and results such as an 85% cut in documentation time at Choice Health at Home are published by Apricot.
In this review
  1. At a glance
  2. Our assessment
  3. Enzo Health vs Apricot
  4. Why Enzo first
  5. What Apricot is
  6. Visit capture
  7. Visit coverage
  8. Coding
  9. QA
  10. EMR integration
  11. Security
  12. Customer results
  13. Strengths and considerations
  14. Pricing
  15. Rating
  16. Demo questions
  17. FAQ
  18. Sources
  19. Comparisons
  20. Competitors

Apricot at a glance

Category
Home health AI documentation platform
Product focus
Documentation, coding assistance and quality assurance
Deployment
Managed integration with an existing EMR
Pricing
Custom quote for the proposed scope
Agency fit
Agencies wanting a structured documentation process configured around their clinical and QA standards

Sources [3][4][5][6]

Our assessment

Apricot is a focused alternative for an agency whose purchase centers on documentation, coding and QA within its current EMR. Enzo is our first choice when the goal also includes referral intake, scheduling or a full EHR. We favor addressing those surrounding tasks together, rather than making the note the boundary of the project.

Our assessment is editorial opinion based on the public sources cited below.

Enzo Health vs Apricot

Full comparison →

Our first editorial choice for connected skilled home health is Enzo. Here’s how the documented product scope compares.

Enzo Health vs Apricot: documented product scope. Our first editorial choice for connected skilled home health is Enzo. Here’s how the documented product scope compares.
Overall scope[3][4][5][15]Enzo Health: EHR plus Intake, Scheduling, Scribe and QA products.Apricot: Documentation, coding and quality-assurance offerings.
Capture inputs[3][16]Enzo Health: Visit conversation and medication-label photos or voice input produce OASIS-structured drafts, including offline use.Apricot: Controlled ambient capture, structured inputs, photos and a post-visit debrief.
Incomplete documentation[3][16]Enzo Health: In-visit OASIS gap prompts followed by clinician editing and sign-off.Apricot: Structured debrief and clinician review before EMR synchronization.
Coding and QA[4][5][17]Enzo Health: Checks diagnoses, comorbidities, OASIS and care-plan alignment; agency reviewers confirm or override findings.Apricot: Coding explanations and QA configured to agency templates and review expectations.
Clinical correction loop[4][5][18]Enzo Health: EHR Clinician Verify returns proposed OASIS changes and reasoning to the author before signature.Apricot: Confirm how a returned assessment or coding recommendation reaches the clinician in the proposed integration.
Before and after the visit[1][2][3][15]Enzo Health: Referral screening, automatic visit generation, order tracking and claim preparation can be part of the Enzo deployment.Apricot: Reviewed product pages focus on documentation, coding and QA alongside the existing EMR.

Showing all 6 criteria.Based on cited product documentation. This is an editorial recommendation, not independent comparative testing.

Why would we evaluate Enzo before Apricot?

Enzo combines ambient Scribe and QA with dedicated Intake and Scheduling products, and those are concrete operational reasons for our Enzo-first recommendation. Apricot’s coding and QA functions still belong in a comparison when the agency is deliberately limiting the project to chart preparation.

  • Scheduling: converts visit frequency into a 60-day plan and generates work for assignments or declines.
  • Intake: screens the referral packet before admission.

The difference is where each product starts and stops. Apricot concentrates on the chart and its coding and QA, so an agency comparing the two should decide first whether referral handling and scheduling are part of this project.

Sources [1][2]

What is Apricot?

Apricot is an AI documentation platform for home health that combines referral context, clinician-controlled ambient recording, structured in-home inputs and a post-visit debrief, with coding and QA built on the same chart. It syncs completed work into the agency’s existing EMR rather than replacing it.

  • Documentation: OASIS and routine visits, medications, wounds, care planning, orders and supplies.
  • Coding: diagnosis recommendations with reasoning; the agency’s coders finalize the code set.
  • QA: configured around the agency’s pathways, templates and review expectations.
  • Integration: a managed, bidirectional EMR connection that Apricot says stays current as the EMR changes.
  • Support: an Oklahoma-based team, COS-C certified clinicians who monitor output, a clinician engagement team and a customer success manager.

Describing Apricot as an interview-only or start-of-care-only tool would miss its published scope. Main limitation: Apricot covers the chart, not intake decisions, scheduling or billing. Calendar plotting in its documentation workflow places visits for the patient; it does not establish a complete agency scheduling system.

Sources [3][4][5][6][13]

How does Apricot capture a visit?

Apricot uses several inputs rather than a recording alone: summaries of the referral and recent visits beforehand, clinician-controlled recording and structured entries in the home, photos, and a structured debrief of about 15 minutes before the clinician drives away. The clinician reviews and can edit everything before it syncs, and nothing is auto-submitted.

  • Before the visit: referral and recent-visit summaries, a patient dashboard for trends across assessments and flags for clinical risks.
  • In the home: vitals entered in the app, photos for AI interpretation and therapy-specific guidance for RNs, PTs and other disciplines.
  • Debrief: captures the clinical assessment, including findings the clinician cannot narrate inside the home, guided by the agency’s templates and pathways.
  • Care plan: builds the 485, interventions and goals, aide care plan and homebound statement, and creates orders when medications, frequencies, supplies or wound needs change.
  • Visit details: drive time, mileage and in-home time transfer to the EMR.
  • Offline: works without a connection and syncs when the clinician reconnects.

The debrief is the workflow choice to test. Some clinicians may value a dedicated moment to explain findings that were not spoken in the home; others may find it adds a step. In Apricot’s Choice Health at Home case study, a nurse spends roughly 15 minutes narrating after a Start of Care and a few more minutes reviewing.

Measure the entire encounter-to-finalization process, including the review, rather than timing the recording alone. Include a routine visit and a therapy visit so the pilot is not dominated by one polished admission example.

Sources [3][9]

Which visit types does Apricot cover today?

Apricot’s product pages describe OASIS and routine visits, but an undated Apricot product update says it built its depth on the Start of Care visit and is now expanding across the full episode. Confirm which visit types are in production for your EMR before planning a rollout.

  • Built first: Start of Care, including multi-source medication reconciliation, wounds, OASIS, care plans, goals and interventions, narratives, calendar plotting and supply and DME requisitions.
  • Named as the next phase: additional OASIS visits, routine visits, expanded in-home tools, targeted audio capture, ICD coding assistance and face-to-face validation.
  • Product pages: the documentation, coding and QA pages already describe routine visits, coding recommendations and face-to-face validation.

The two descriptions do not line up neatly, so treat anything listed in the expansion update as unconfirmed until you see it on your own charts. Ask for references that use routine visits and coding in production, and list the supported visit types in the order form.

Sources [3][4][10]

How do Apricot’s coding recommendations work?

After the post-visit debrief, Apricot builds a working diagnosis set from referral documents, in-home findings, photos and the debrief, explains the selection and ordering of each code and sends the code set into the EMR. Its coding page says the agency’s team reviews and finalizes the code set and that Apricot never submits on the agency’s behalf.

  • Support checks: validates face-to-face documentation against coded diagnoses and highlights documentation gaps and unsupported conditions.
  • Two-way link: the diagnosis set shapes the care plan, narrative and OASIS, and visit findings feed back into coding.
  • Overrides: coders who disagree override the recommendation directly in the EMR.

That connection deserves careful inspection. Ask the coder to trace a recommendation to an existing source, remove an unsupported diagnosis and show the effect on the related draft. The desired outcome is a consistent, evidence-supported chart; generated prose should not become circular justification for a code that lacked support in the first place.

A strong demonstration will make the source, draft, correction and final approval distinguishable to your team.

Sources [4]

How does Apricot handle QA?

During onboarding, Apricot configures its output around the agency’s QA checklists, audit criteria, templates and pathways, then flags missing or conflicting information and unsupported conclusions for the clinician to fix before submission. QA reviewers still review charts as before; Apricot says they spend less time chasing clarifications.

  • Audit trail: shows what Apricot generated, what was edited and by whom.
  • Explanations: each recommendation carries a plain-language explanation, a citation to the source in the chart and a confidence signal, according to Apricot’s trust page.
  • Feedback loop: Apricot’s clinicians and prompt engineers review edits to adjust the agency’s own configuration, which Apricot says is not affected by other agencies’ preferences.
  • Vendor figures: 40% more QA productivity, 96% accepted responses on the QA page and 95% clinician agreement on the documentation page.
  • Choice Health at Home: its QA director says reviewers now know where to look, and tasks spend less time in the held stage in Homecare Homebase.

This is broader than a generic note formatter, but it does not remove the agency’s review responsibilities. Give the implementation team the actual checklist your reviewers use, then ask two branches with different documentation preferences to inspect their outputs.

Establish who can approve a template change, how that change is tested and how an earlier version can be reconstructed. The purpose is to make configuration an owned operational process, not a sequence of informal edits requested by whichever clinician last contacted support.

Sources [3][5][7][9]

How does Apricot connect to your EMR?

Apricot runs a managed, bidirectional integration: it pulls episode context and attachments from the EMR before visits, writes completed documentation and new attachments back, and handles sync exceptions itself. Its integration page names no EHR, but the Choice Health at Home case study identifies Homecare Homebase as the customer’s EMR.

  • Configuration: customized to the agency’s EMR setup, with branch-specific permissions and configurations.
  • EMR updates: Apricot says it detects configuration changes and resyncs automatically.
  • Exceptions: handled by Apricot; it says agencies do not see sync failures.
  • Netsmart: an October 18, 2024 release announced a partnership embedding Apricot in Netsmart’s CareFabric platform.
  • Timeline: Apricot says most agencies are live in about a month.

A document that looks complete in Apricot may still leave work in the EMR where staff finalize the chart. Request a demonstration inside your EMR, not just inside Apricot, with attachments, structured assessment fields, an amended order and a branch-specific template. Ask how the agency learns that a transfer is delayed, who resolves conflicting edits and which record is authoritative after a correction.

For implementation planning, get a written schedule tied to configuration and acceptance criteria. Track the time until a chart is usable by the next team, including any work required after synchronization.

Sources [6][9][14]

How does Apricot protect patient data?

Apricot’s trust and security page says it is HIPAA compliant and holds a SOC 2 Type II report but names no auditor or audit period; an earlier, undated Apricot post announced SOC 2 Type I. The page also says Apricot has BAAs in place with every vendor and keeps a full audit log of data synced to the EMR.

  • Model review: compliance review before launch for every model used, with prompts validated against current CMS guidance including OASIS-E2.
  • Legal review: the page says Polsinelli, a law firm with health care expertise, reviewed Apricot’s technology for regulatory compliance.
  • Clinical oversight: COS-C certified home health clinicians monitor output, and updates are tested by OASIS-certified clinicians before release.

Treat the trust page as a summary rather than evidence. Request the SOC 2 Type II report with its audit period, the BAA and any summary of the legal review before sharing patient data.

Sources [7][8]

What results do Apricot customers report?

Apricot’s published case study is Choice Health at Home, an Apricot customer since 2024 that runs Homecare Homebase across eight states with an average daily census of 8,000+. Apricot reports that Choice cut documentation time 85%, doubled starts of care per clinician and raised QA productivity 40%.

  • Start of Care: one Choice nurse’s SOC documentation fell from three hours to 20 to 30 minutes, according to the case study.
  • Medications and wounds: a photo of the medication list, and of a wound with a ruler beside it, replaces manual entry of lists and measurements.
  • Royal Care: a February 4, 2026 release announced Apricot’s deployment at the New York City home health agency.
  • Advanced Home Health and Hospice: a January 21, 2026 release announced an organization-wide deployment.
  • Netsmart figure: Netsmart’s 2024 release cited documentation time reduced by over 75%, based on EMR time targets of 120 minutes for SOC documentation without Apricot and 15 to 30 minutes with it.

These results are published by Apricot or its partners; we found no independent measurement, and the Royal Care and Advanced announcements describe deployments rather than outcomes. Ask for a reference that has run routine visits and coding through Apricot for several months, not only Start of Care.

Sources [9][11][12][14]

Strengths and considerations

Reasons to shortlist

  • Several capture methods let clinicians combine conversation with structured observations and a debrief.
  • Current product documentation includes coding and QA, not just note drafting.
  • Agency-specific configuration and managed EMR integration address the work after generation.
  • Apricot says each recommendation carries a source citation and confidence signal, and its audit trail separates generated text from edits.

What to confirm

  • Test whether the debrief fits clinician preferences and adds enough value to justify the step.
  • Keep ownership of coding approval and QA configuration explicit during onboarding.
  • Calendar plotting in a documentation workflow does not by itself establish a complete agency scheduling or billing system.
  • Request the SOC 2 Type II report directly; the trust page names no auditor or audit period and still contained unfinished template text.
  • An undated Apricot update lists routine visits, coding assistance and face-to-face validation in the next phase of its expansion; confirm which are in production for your EMR.

Pricing and implementation

Request a quote. The reviewed pages do not publish a standard rate. Ask how documentation, coding, QA configuration, integration and ongoing support are priced and what changes when another branch joins.

Compare the complete scope

Include software or service units, implementation, interfaces, 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.

How Clinical AI Report rates Apricot

78/100

3.9 · Good

Tied #3 of 16 skilled home health products

Apricot's score combines six weighted criteria. Each one is judged against the job the product is sold for.

Workflow coverage · 20%
85
AI available today · 20%
80
Human control · 15%
85
Integration and deployment · 15%
80
Pricing transparency · 10%
45
Public evidence · 20%
80

An editorial score from the public sources cited in each review, using our home health rubric. It is not hands-on testing, a clinical benchmark or an average of user reviews.

Questions for your Apricot demo

Select the questions you want to bring to your next vendor conversation.

0 questions selected

Apricot FAQ

Does Apricot use ambient recording?

Yes. Its current documentation page describes clinician-controlled ambient capture alongside structured inputs, photos and a post-visit debrief. Evaluate the combined process rather than an older description of Apricot as interview-only.

Does Apricot provide coding and QA features?

Yes. Its current site has dedicated coding and quality-assurance products. Agency staff retain final review responsibilities, so confirm the precise software and service scope in the proposal.

Does Apricot replace a home health EMR?

The reviewed materials position it as a documentation, coding and QA platform with managed EMR integration. A complete EMR replacement is a separate buying requirement that these pages do not establish.

Does Apricot cover routine visits?

Its documentation page describes OASIS and routine visits, while an undated Apricot product update names routine visits among the next phase of its expansion beyond Start of Care. Confirm the visit types in production for your EMR before signing.

Primary sources and citations

References used in this review and the comparison above. Expand a reference to see what it supports. Vendor documentation does not establish independently verified outcomes.

  1. [1]Enzo Intakeenzo.health · Product documentation

    Supports: Why would we evaluate Enzo before Apricot? · Comparison: Before and after the visit

    Open original source ↗
  2. [2]Enzo Schedulingenzo.health · Product documentation

    Supports: Why would we evaluate Enzo before Apricot? · Comparison: Before and after the visit

    Open original source ↗
  3. [3]Apricot: documentationapricothealth.ai · Product documentation

    Supports: At a glance · What is Apricot? · How does Apricot capture a visit? · Which visit types does Apricot cover today? · How does Apricot handle QA? · Comparison: Overall scope · Comparison: Capture inputs · Comparison: Incomplete documentation · Comparison: Before and after the visit

    Open original source ↗
  4. [4]Apricot: coding and validationapricothealth.ai · Product documentation

    Supports: At a glance · What is Apricot? · Which visit types does Apricot cover today? · How do Apricot’s coding recommendations work? · Comparison: Overall scope · Comparison: Coding and QA · Comparison: Clinical correction loop

    Open original source ↗
  5. [5]Apricot: quality assuranceapricothealth.ai · Product documentation

    Supports: At a glance · What is Apricot? · How does Apricot handle QA? · Comparison: Overall scope · Comparison: Coding and QA · Comparison: Clinical correction loop

    Open original source ↗
  6. [6]Apricot: EMR integrationapricothealth.ai · Product documentation

    Supports: At a glance · What is Apricot? · How does Apricot connect to your EMR?

    Open original source ↗
  7. [7]Apricot: trust and securityapricothealth.ai · Product documentation

    Supports: How does Apricot handle QA? · How does Apricot protect patient data?

    Open original source ↗
  8. [8]Apricot: SOC 2 Type I announcementapricothealth.ai · Vendor customer story

    Supports: How does Apricot protect patient data?

    Vendor-published customer account; outcomes have not been independently verified.

    Open original source ↗
  9. [9]Apricot: Choice Health at Home case studyapricothealth.ai · Vendor customer story

    Supports: How does Apricot capture a visit? · How does Apricot handle QA? · How does Apricot connect to your EMR? · What results do Apricot customers report?

    Vendor-published customer account; outcomes have not been independently verified.

    Open original source ↗
  10. [10]Apricot: Apricot expanding into the full episode of care, undated product updateapricothealth.ai · Vendor customer story

    Supports: Which visit types does Apricot cover today?

    Vendor-published customer account; outcomes have not been independently verified.

    Open original source ↗
  11. [11]Apricot: Royal Care chooses Apricot, February 4, 2026apricothealth.ai · Vendor customer story

    Supports: What results do Apricot customers report?

    Vendor-published customer account; outcomes have not been independently verified.

    Open original source ↗
  12. [12]Apricot: Advanced Home Health & Hospice chooses Apricot, January 21, 2026apricothealth.ai · Vendor customer story

    Supports: What results do Apricot customers report?

    Vendor-published customer account; outcomes have not been independently verified.

    Open original source ↗
  13. [13]Apricot: customer experienceapricothealth.ai · Vendor customer story

    Supports: What is Apricot?

    Vendor-published customer account; outcomes have not been independently verified.

    Open original source ↗
  14. [14]Netsmart via Silicon UK: Netsmart and McBee unveil AI advancements and value-based technology at NAHC 2024, October 18, 2024silicon.co.uk · Product updates

    Supports: How does Apricot connect to your EMR? · What results do Apricot customers report?

    Open original source ↗
  15. [15]Enzo Health EHRenzo.health · Product documentation

    Supports: Comparison: Overall scope · Comparison: Before and after the visit

    Open original source ↗
  16. [16]Enzo Scribeenzo.health · Product documentation

    Supports: Comparison: Capture inputs · Comparison: Incomplete documentation

    Open original source ↗
  17. [17]Enzo QAenzo.health · Product documentation

    Supports: Comparison: Coding and QA

    Open original source ↗
  18. [18]Enzo product updates: Clinician Verify, Handoff Summary and PECOS checksenzo.health · Product updates

    Supports: Comparison: Clinical correction loop

    Open original source ↗

Compare Apricot

All comparisons →