Most agencies I talk to already pay for an EMR, and most of those EMRs have a “referrals” or “intake” screen. So when someone suggests adding a home health CRM, the owner’s first reaction is fair: “Don’t we already have that?”
My short answer: your EMR is built to run care, and a CRM is built to win and keep referral relationships. If you have one liaison, a handful of referral partners and a clean intake process, your EMR’s referral tracking is probably enough. Once you have several people in the field, questions about which sources actually convert, or inquiries slipping through after hours, the EMR usually stops being the right place for that work. Here is how I would think it through.
What your EMR is actually built to do
An EMR (or the clinical and operational suite most agencies call their EMR) exists to document and deliver care correctly, then get paid for it. Depending on the vendor and your agency type, that usually means:
- Clinical documentation: assessments, visit notes, care plans and signatures.
- OASIS, where it applies: Medicare-certified home health agencies collect OASIS data as part of the comprehensive assessment, and CMS publishes the current instruments on its OASIS data sets page. Private-duty and non-medical personal care agencies generally don’t.
- Orders and authorizations: physician orders, plan-of-care sign-off, payer authorizations.
- Scheduling and visit verification: who goes where, when, and proof they were there. If you operate in Texas, the Texas EVV guide for agencies covers that side in detail.
- Billing: claims, remittances and denials, in many suites.
That is a lot of responsibility, and it is all about a person who is already a patient or about to become one. The EMR’s data model centers on the patient episode. That is exactly right for care, and it is also why EMRs tend to be awkward at the work that happens before a patient exists.
What a home health CRM does that an EMR doesn’t
A CRM centers on relationships instead of episodes. In home health, the most important relationships usually aren’t with patients at all. They are with the discharge planner at the hospital, the case manager at the skilled nursing facility, the physician’s office manager, and the family member who calls on a Sunday night.
A good home care CRM handles:
- Referral source management: facilities, physicians and individual contacts, with notes on who prefers what and who actually sends patients.
- Liaisons and field marketing: visit logs, territories, routes, in-service schedules and follow-up tasks for the people out in the community.
- The inquiry-to-admission pipeline: every inquiry, from first call to start of care or a documented reason it didn’t happen.
- Follow-ups: reminders to call a family back, thank a referrer, or check in with a quiet source.
- Relationship history: the full story of a partnership, which survives when a liaison leaves.
EMR vs CRM: who owns what
Here is how I split responsibilities when I map an agency’s systems.
| Responsibility | EMR / clinical system | CRM |
|---|---|---|
| Clinical documentation and OASIS | Owns it | Never |
| Orders, plan of care, authorizations | Owns it | Never |
| Scheduling, EVV, billing | Owns it | At most, read-only status |
| Patient demographics after admission | Owns it | Reference or link only |
| Referral source and contact records | Basic list, if any | Owns it |
| Liaison activity and territories | Rarely | Owns it |
| Inquiries that never admit | Often lost | Owns it, with a reason |
| Follow-up tasks with referrers and families | Limited | Owns it |
| Referral-to-admission reporting | Partial | Owns it, fed by EMR status |
The pattern is simple. Everything after “this person is our patient” belongs in the EMR. Everything before it, and every relationship around it, is CRM territory.
When your EMR’s referral tracking is enough
I don’t recommend adding a system just because it exists. Your EMR’s intake module is probably enough if most of these are true:
- One person, or a very small team, handles intake and marketing.
- You have a small, stable set of referral partners and you know them personally.
- Almost every inquiry is entered into the EMR the same day, including ones that don’t admit.
- You can already answer “where did last month’s admissions come from?” without a spreadsheet.
- Nobody is asking for liaison activity reports.
In that situation, the better investment is usually discipline, not software: a required “referral source” field, a standard list of non-admit reasons, and a weekly review. Configure what you already pay for before buying anything new.
Signs you’ve outgrown it and need a CRM
The need usually shows up as a set of recurring frustrations rather than one big failure. These are the ones I watch for:
You have multiple liaisons
Once two or three people are calling on facilities, you need to know who visited whom, what was promised and what happened next. EMRs aren’t designed to log a lunch-and-learn or a drop-in at a discharge planner’s office, so that history ends up in personal phones and notebooks, and it walks out the door when a liaison does.
You can’t answer referral-source ROI questions
If the owner asks “Is this hospital worth the time we spend there?” and the honest answer is a guess, you have a data problem. Answering it requires linking liaison effort to referrals to admissions, which crosses the line between the two systems.
After-hours inquiries disappear
Families call at night and on weekends. If those calls land in a voicemail box that someone checks Monday, some of those families have already chosen another agency. I wrote about fixing that specifically in handling after-hours calls at a home care agency. A CRM gives those inquiries a place to land, an owner and a timer.
You have no conversion data
If inquiries that don’t admit are never recorded, you can’t measure conversion at all. You only see the wins.
Buy, build or connect
Once you decide you need CRM capability, there are three broad routes. I covered the general version of this decision in custom CRM vs off-the-shelf. Here is how it plays out for home health specifically.
Buy: a healthcare CRM with a native EMR integration
Several CRMs are built for post-acute care and advertise integrations with common home health EMRs. The appeal is speed and a vendor who understands referral workflows. The trade-offs: per-seat pricing, integrations that may sync fewer fields than the demo suggests, and one more vendor to manage. Always ask exactly which fields sync, in which direction, and how often.
Connect: automation between the tools you have
Tools like Zapier and Make are excellent for moving data between systems, and I suggest them often for general business workflows (there are plenty of examples in automation ideas for small businesses). For anything carrying patient information, check first whether the platform will sign a Business Associate Agreement. Zapier, for example, states plainly that it isn’t HIPAA compliant and doesn’t sign BAAs, so it shouldn’t carry PHI. That limits general-purpose automation to non-PHI data, such as referral source activity, or pushes you toward healthcare-specific integration tools that do sign BAAs.
Build: a custom layer through the EMR’s API
If your EMR has a usable API, a custom layer can pull admission status into a CRM (commercial or custom) so conversion reporting happens automatically. This gives you the best fit and full ownership of the data model. The trade-offs are upfront cost, the need for someone to maintain it, and dependence on how good the vendor’s API really is.
All-in-one platforms
The fourth option is avoiding the split entirely. At Pinn.Media, my team built Pinn.Care as an ERP for home healthcare agencies that included HR, care coordination, caregiver matching, marketing and billing in one system, precisely because these pieces depend on each other. All-in-one removes integration work, but you accept one vendor’s view of every workflow. My guide to home healthcare agency software covers how to evaluate platforms like that.
The metrics that actually matter
A CRM earns its cost if it reliably answers a few questions:
- Referral-to-admission conversion: of all referrals and inquiries received, how many reached start of care? Track it overall, by source and by liaison.
- Time to first contact: how long from the moment an inquiry arrives until a person responds. This is the number that exposes after-hours gaps.
- Top referral sources: ranked by admissions, not by referral volume. A source that sends many referrals you can’t accept isn’t your best source.
- Non-admit reasons: no staff in that area, payer not accepted, patient chose another agency, patient needed a higher level of care. Each reason points to a different fix.
Notice that the first metric needs data from both systems: referrals from the CRM and admissions from the EMR. That is why the integration question matters more than the feature list.
HIPAA and data flow: where PHI should live
This is the part agencies most often get wrong, usually by accident. A referral that includes a patient’s name, diagnosis and discharge date is protected health information, and the moment it goes into a CRM, that CRM is holding PHI.
A few principles I design around:
- Keep clinical detail in the EMR. The CRM needs to know an inquiry exists, where it came from and whether it admitted. It rarely needs diagnoses, medications or visit notes.
- Apply minimum necessary. Under the HIPAA Privacy Rule, uses and disclosures of PHI are generally limited to the minimum necessary for the purpose, with exceptions such as disclosures to a provider for treatment. Marketing and referral analytics are not treatment, so design the CRM around the smallest data set that does the job.
- Get a BAA from any vendor that touches PHI. HHS guidance is clear that a cloud service provider that stores or processes ePHI is a business associate, even if the data is encrypted and the vendor can’t read it. That applies to your CRM, your automation tool, your phone system and any AI receptionist in the chain.
- Separate relationship data from patient data. Referral source records (the facility, the discharge planner, visit notes about the relationship) aren’t PHI. Patient inquiries are. Some agencies keep patient-level records only in the EMR and let the CRM work with IDs and statuses.
If a CRM vendor won’t sign a BAA, that doesn’t automatically rule it out, but it means no patient information goes into it. In practice, that is hard to enforce once intake staff start using it, so I usually steer agencies toward vendors that will sign.
Frequently asked questions
Do home health agencies need a CRM if they have an EMR?
Not always. A small agency with one intake person and a few steady referral partners can usually manage in the EMR’s intake module with good habits. A CRM becomes worth it when you have multiple liaisons, many referral sources, lost after-hours inquiries, or leadership asking which sources actually produce admissions. The trigger is complexity, not agency size alone.
What is the difference between a home care CRM and an EMR?
An EMR runs care: clinical documentation, OASIS where required, orders, scheduling, visit verification and often billing. A CRM manages relationships and growth: referral sources, liaison activity, the inquiry-to-admission pipeline and follow-ups. The EMR centers on the patient episode; the CRM centers on the people and organizations who send you patients.
Can I use Zapier to connect my EMR and CRM?
Only for data that isn’t protected health information. Zapier states that it isn’t HIPAA compliant and doesn’t sign Business Associate Agreements, so patient details shouldn’t pass through it. You can still automate non-PHI tasks, like logging liaison visits or syncing referral source contacts. For patient-level data, use a native integration or a tool that signs a BAA.
Does a home health CRM need a BAA?
If it will store or process any protected health information, yes. HHS treats a cloud vendor that maintains ePHI for a covered entity as a business associate, even if the data is encrypted. If a CRM holds only referral source and relationship data with no patient information, a BAA may not be required, but confirm with your compliance officer.
What home health referral tracking metrics should I watch?
Start with referral-to-admission conversion (overall, by source and by liaison), time to first contact for new inquiries, and top referral sources ranked by admissions rather than volume. Add non-admit reasons so you know why referrals didn’t convert. Those few numbers answer most of the questions owners actually ask about marketing and intake.
Want a second pair of eyes?
If you are trying to decide whether your EMR is enough, or you already have both systems and they don’t talk to each other, I’m happy to look at how referrals actually move through your agency and give you an honest read. Tell me about your setup, even if the answer turns out to be “configure what you already have.”
