Healthcare · Full Build-Out
Retail Pharmacy Chain
One Patient Record, Every Store
A customer calls asking to transfer 30 days of maintenance meds to your downtown location. This page walks through building that in SmartLite from scratch — the record types, the fields, the relationships, the automation, and what staff actually do with it every day.
About & Business Case #
The everyday problem #
"A customer calls asking to transfer 30 days of maintenance meds to our downtown location. Today that means three unlinked store systems and twenty minutes on hold. We need one customer record, not three."
Each store location running its own separate system means the same patient looks like three different strangers, depending on which counter they walk up to. Refill reminders get missed, prescription history gets re-asked at every visit, and a simple transfer between stores turns into a phone-tag exercise.
What good looks like
One patient record that every store location can see. Refill reminders that go out on their own. Clinical notes that only pharmacists can read — nobody else, not even other store staff.
What you're building #
Three pieces work together: the standard Lead/Contact/Account records SmartLite already has, one new custom record type for tracking prescriptions, and a handful of automation and security rules layered on top.
| Record type | Kind | What it holds |
|---|---|---|
| Lead | Standard (built-in) | A person who just signed up for refill reminders or walked in as a new customer, before they're fully on file |
| Contact | Standard (built-in) | The patient, once they're a confirmed customer |
| Account | Standard (built-in) | The prescriber's practice, e.g. "Riverside Family Practice" — kept separate from the patient so many patients can share one prescriber |
| Prescription | Custom (you build it) | Drug, dosage, refill date, prescribing physician, and diagnosis notes — linked to the patient |
Business outcome #
- One patient record follows the customer across every store — nobody re-asks "have you been here before?"
- Refill reminders go out automatically, lifting adherence without a single manual phone call
- Clinical notes stay locked to the Pharmacist Profile only — other store staff never see them
Implementation #
Step-by-step build #
Do these six pieces in order — each one builds on the last. Total time: roughly 30–40 minutes the first time through.
1 Capture the patient automatically #
name, "Phone" → phone, "Preferred Store" → store_location__c (you'll create this field — see step 3 for how to add a custom field).Every sign-up now creates a Lead automatically — no front-desk staff member has to retype it.
2 Convert once, link to the right prescriber #
3 Build the Prescription record type #
prescription__c).| Field label | Type | Links to / notes |
|---|---|---|
| Patient | LOOKUP | Related object: Contact — connects each Prescription to the patient it belongs to |
| Drug Name | TEXT | e.g. "Lisinopril 10mg" |
| Dosage | TEXT | e.g. "Once daily" |
| Refill Date | DATE | Drives the automatic reminder in step 4 |
| Prescribing Physician | LOOKUP | Related object: Account — connects to the prescriber's practice |
| Diagnosis Notes | TEXT | Sensitive — locked down in step 5 |
Why two lookup fields
The Patient lookup and the Prescribing Physician lookup are what make this a connected record instead of a floating spreadsheet row — open any Patient and you'll see every Prescription linked to them, and vice versa.
4 Automate the refill reminder #
5 Lock down clinical notes #
Field-level, not just page-level
This hides the field everywhere — record pages, reports, and exports — not just off the default screen. That's what makes it a real safeguard rather than a suggestion.
6 Build the daily pull-list report #
How to Use #
Day-to-day: front-desk staff #
Day-to-day: pharmacists #
Day-to-day: store manager #
What to try next
Once this is running smoothly, look at the Reports and Notifications trails to build more views on top of the same Prescription data.