Two systems hold two different populations
The EMR is the record of care. It holds Jess once Dana has seen her: the chart, the consent to treat, the photos, the treatment history, the visit dates and the checkout. The CRM is the record of the conversation. It holds Jess before she is a patient: the DM that asked about lips, the missed call, the form from the ad, and the follow-up Priya owes her. One population has a chart and the other has a thread. A practice that forces both into a system built for one of them ends up with leads inside a medical record or charts inside a sales pipeline; a system built for both is scored on both jobs.
What each holds, and the question each one answers
- The EMR holds the chart, the consents, the photos, the treatment history, the visit dates, the calendar and the checkout. It serves the provider, the medical director and the auditor, and its job is to answer what happened with this patient.
- The CRM holds the lead, the source, the conversation across phone, text, DM and email, the stage, the task owed and the person who owes it. It serves the front desk and the owner, and its job is to answer who is waiting on us.
- The overlap is the calendar and the contact details. Decide once which calendar is the calendar, and make it the one the provider works from.
Why a practice ends up running both
The EMR arrives with the first provider, because charting needs a record. The CRM arrives when the leads outgrow the front desk's memory: an ad campaign, a second channel, a coordinator who leaves and takes the follow-up list with them. Count the leads from last month with no next step written anywhere; that count is the gap the CRM fills. Count the patients treated last week whose consent you can pull in under a minute; that count is the job the EMR does.
Each job has one system that should own it
| The job | Which system | Why |
|---|---|---|
| Chart, consent to treat, photos, treatment history | EMR | It is the legal record of care, and the auditor reads it there |
| Lead capture, follow-up, the stage of each conversation | CRM | A lead is not a patient and has no chart to live in |
| The booking | The EMR calendar, written from the CRM | The provider works from one calendar; the CRM hands the booking to it |
| The comeback | Read from the EMR visit dates, sent through the system that holds the thread | Only the visit date says who is due; only the thread holds the reply |
| Consent to be texted | One field, readable by whichever system sends | Confirm with counsel what counts; keep the date and the wording |
| Revenue by treatment and provider | The EMR checkout export | The sale is rung up where the treatment was charted |
The comeback calendar reads from the visit date, which lives in the EMR
A comeback is timed from the last visit and the treatment's interval, and both of those live in the EMR. The CRM knows Jess asked about neurotoxin, tox from here on, in March; the EMR knows she was treated on the fourteenth and what she had. Build the due list from the EMR's visit dates, send the message through whichever system holds the thread, and write the reply back to that thread. A due list built from the CRM alone sends a comeback to leads who were never treated, and a list built from memory sends it late. The interval each treatment is planned around is your medical director's call; the method is in the reactivation guide.
Consent lives in two places, on purpose
Consent to treat is clinical and lives in the chart, attached to the visit it covers. Consent to be texted for marketing is a different record, and the common mistake is keeping it in the system that does not send. Record it once, with the date, the wording Jess saw and the channel she agreed to, in a field the sending system reads before every send. Which messages count as marketing and what consent each needs is for counsel to confirm; the texting rules are in the texting guide.
How to check your own split on Monday
- Pull ten leads from last month out of whatever holds them and write the next step owed on each. A blank means the CRM job is not being done.
- Pull ten patients treated last week and time how long it takes to open each consent. Over a minute means the EMR job is not being done.
- Open the calendar each provider works from and the calendar the front desk books into. If they differ, pick one by Friday.
- Find the field that holds texting consent and check that the system that sends can read it.
The growth system reads both and writes to neither chart
The growth system reads the EMR for the visit dates, the treatment and the calendar, and reads the CRM for the lead, the source and the thread. It writes a booking into the calendar with its note and writes the reply into the thread, and it writes into neither chart. The numbers come from both: new patients by source from the CRM, revenue by treatment and who is due from the EMR, on one page. Any system that touches patient health information signs the agreements your practice requires; confirm with counsel which ones.
What to do next
NorthCore's Run the whole practice solution reads your EMR and your CRM, books into the calendar, times the comeback from the visit dates and puts both sets of numbers on one page. Scoped in writing and covered by the promise on this site: results in 90 days, or we keep working until you have them.
