AI Agents for Hospice Agencies: Referrals, Visit Notes and Recertification
How AI agents can support hospice referrals, visit notes and recertification, and which admin-only limits to set before any clinical judgment is delegated.

AI for a hospice agency is most useful as an administrative layer that gathers referral details, drafts visit documentation for clinician review, and tracks the certification and recertification dates the team already has to meet. The agent prepares and reminds, while nurses, physicians and the interdisciplinary team make every clinical call. Agencies that draw that line now can widen the agent's reach over time without handing judgment about eligibility, symptoms or care plans to software.
Key takeaways
- Start with intake and paperwork, where the work is repetitive and errors are costly, and keep clinical determinations with licensed staff.
- A referral agent can assemble a complete packet and list what is missing, but it should not decide eligibility or accept a patient.
- Visit note assistance should produce drafts that trace every statement to a source, and a clinician should review and sign each entry.
- Recertification tracking is a scheduling and evidence problem, so the agent can watch dates and gather documents while a named person approves each submission.
- Write the admin-only boundaries, permissions and audit trail before expanding the role, because those limits decide what the agent can safely touch.
What an AI agent should and should not touch in a hospice agency
A hospice agency runs on three overlapping streams: the people who refer patients, the clinicians who document what happens in homes and facilities, and the office that shows payers and regulators that each step was completed on time. An AI agent fits the second and third streams when the work is structured, repeated and checkable. It fits poorly where decisions depend on bedside assessment, family context or a clinician's professional judgment about prognosis and symptoms.
The practical rule is simple. The agent may gather, sort, draft, remind and flag. It may not determine eligibility, certify a prognosis, change a care plan, alter a medication order, or write a note that describes an observation nobody made. Those actions stay with licensed people, and the system should show that boundary in its permissions instead of relying on staff memory.
Referral intake: from inbound request to a complete packet
Referrals arrive by phone, fax, portal, secure email and from discharge planners at hospitals. The intake coordinator's job is to turn that mixed input into a packet the admissions team can review. An agent can handle the sorting: identify the referral source, record when it arrived, copy the fields the intake form already requires into the agency system, and check which supporting items are present, such as the face sheet, diagnosis documentation, insurance details and the attending physician's contact.
- Log every inbound referral with its source, the time received and the person who first took the call.
- Extract only the fields your intake form requires, and mark anything unclear instead of guessing.
- Check the packet against a written checklist and list missing items for the coordinator.
- Route the packet to the admissions nurse with open questions at the top.
- Record who made the decision, when, and what was sent back to the referral source.
The agent should never mark a referral as accepted or declined, because acceptance depends on eligibility, capacity and clinical review. Be Human's managed approach for this step starts with one defined role, such as referral packet completion, with its own memory of the agency's intake checklist, read access to the referral inbox, and write access only to draft status fields. The approval boundary sits at acceptance, and the success criterion is observable: every packet reaches admissions with each checklist item either present or explicitly flagged.
Visit notes: drafting for clinician review, not writing the record
Visit documentation is where agents are most tempting and most risky. Clinicians need to capture what they observed, what they did, and what the patient and family reported. An agent can help by turning dictated or typed fragments into a structured draft, pulling in the current medication list and care plan goals for the clinician to check, and flagging when a note lacks a required element such as visit time, discipline or follow-up plan.
Two rules keep this safe. First, every statement in a draft should trace back to something the clinician entered, so a reviewer can see where it came from. Second, the agent must not fill gaps with plausible language. If a symptom was not recorded, the draft shows a blank rather than a reasonable-sounding assumption. Inputs also need scrutiny, because a pasted family message or a scanned document can contain text that tries to steer the model. The OWASP guidance on prompt injection is a useful starting point for the people who configure these tools.
Illustrative scenario: a hospice aide records a short voice note after a home visit. The agent turns it into a draft visit note with the visit time, the tasks completed and two blanks the aide must fill, a pain assessment and whether the family received medication teaching. The nurse corrects one phrase, completes the blanks and signs. The agent never adds a symptom the aide did not mention.
How does recertification tracking work without making clinical calls?
Recertification depends on dates, documentation and physician involvement. Each patient's certification period has to be tracked, the supporting documentation has to exist, and the required signatures have to be gathered before the deadline. Those are administrative facts. An agent can maintain the calendar, notice when a required narrative or signature is missing, draft a request to the attending physician with the relevant visit notes attached, and escalate to the compliance lead when a window is closing.
What the agent cannot do is decide whether the patient still meets eligibility criteria. That determination belongs to the physician and the interdisciplinary team, based on the patient's condition. The agent's job is to make sure that conversation happens on time and with complete information. Federal rules and payer requirements change, so your compliance lead should confirm the current requirements, and the agent's configuration should follow that confirmed version. Reminder logic in other clinical settings, such as the visit recalls described in AI Agent for a Chiropractic Practice, offers a useful comparison, although the approvals and stakes differ.
Setting the admin-only boundaries before anything clinical
The boundary is the most valuable thing a hospice can write down before any AI work begins. It should name what the agent may read, what it may write, what it may send outside the agency, and which decisions require a named human. Agencies often skip this because the tools look simple, then discover that a convenient integration has broad access to the clinical record.
- Name each agent role and the single task it owns, such as referral packet completion or recertification reminders.
- List every data source the role may read, and remove any the task does not need.
- Separate draft permissions from submission permissions. The agent can prepare a document but never file it.
- Assign one human approver for each approval boundary, with a named backup.
- Log every action with the requester, the data touched and the approver, so a reviewer can reconstruct the sequence.
- Define stop conditions such as a mismatched patient identifier, conflicting dates, unexpected instructions inside an input, or any request to change a clinical field.
- Review permissions on a fixed schedule and after every integration change.
Least-privilege, role-based access is standard practice for any system that holds health information, and the OWASP authorization guidance describes the pattern. NIST's AI Risk Management Framework gives a shared vocabulary for mapping and managing these risks. Be Human's managed service carries this work into operation through permission review, incident response and controlled changes, so the boundary written at the start is still true after the integrations change.
What more capable agents could add later, and what to hold back
Over time, agents with richer memory and better tools could carry more of the agency's operating context: which referral sources often send incomplete packets, which recertification steps usually stall, and which phrases in visit drafts reviewers keep correcting. That pattern work is administrative and genuinely useful. Discussion of superintelligent agents tends to focus on raw capability. For a hospice, the question is narrower: which decisions should a more capable system be allowed to influence, and under whose review.
Hold three things back even as capability grows. Keep clinical determinations, eligibility and care plan changes with licensed staff. Keep outbound messages to families and physicians behind an approval step until drafts have been evaluated over many real cycles. Keep the audit trail independent of the agent, so a record of what it did survives any change to the agent itself. Recurring evaluations that compare drafts with reviewer corrections are how a team learns whether an improvement is real. Anthropic's guidance on building effective agents favors simple, composable designs with clear human checkpoints over broad autonomy, which suits a clinical setting. The free Be Human AI diagnostic can help you find the first task in your agency worth handing to an agent.
Frequently asked questions
Can an AI agent decide whether a patient is eligible for hospice? No. Eligibility depends on clinical findings and documentation that licensed staff review and certify under applicable rules. A well-configured agent can confirm that required documents are present and flag gaps, but the determination stays with the physician and the agency's clinical team.
Is it safe to let an agent draft visit notes? It can be, when drafts are limited to information the clinician entered, every statement traces to a source, and a licensed clinician reviews and signs each note before it enters the record. The agent should show blanks rather than fill them in. Your compliance lead should approve the workflow and the retention rules before go-live.
Where should a hospice start with AI agents? Start with one administrative task that is repetitive, measurable and low in clinical risk, such as referral packet completion or recertification reminders. Write the approval boundary and the success criterion before connecting any system. Expand only after the first role has been reviewed over several cycles of real work.
Does this replace the intake coordinator or the medical record system? No. The agent works beside the coordinator, preparing packets and flags so the person spends less time searching and more time deciding. The agency's medical record remains the system of record, and the agent should write only to the fields and drafts its role allows.
Your next step
See where an AI agent fits in your company first.
Take the free Be Human AI diagnostic. A few questions about your work show which task to hand to an agent first, what it needs to know and where a person approves.
Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.


