Where patients come from, and which sources paid for anything.
The ad platform's knowledge of a patient ends at the form. The practice system's begins there. Everything in this section exists to join those two halves, which is why attribution is a property of the record rather than a report bolted onto it.
A source on every card
A lead, a consultation and a case are three states of one person. Every card names what produced them.
First-touch attribution
Credit goes to the source that started it, not the last thing clicked. Long consideration windows are the norm here, and last-click systematically misprices them.
Your ad accounts stay in your name
RootLogic reads the click ids your ads produce rather than taking custody of the account that produced them.
The click id survives to the outcome
Which is the whole difficulty. A booked and collected case can be handed back to the platform that produced it, so bidding optimizes toward patients who pay rather than toward whoever converts most cheaply.
Attribution on the booking itself
A self-serve booking writes its own attribution row at the moment it is made. A booking surface that drops the click id is a prettier version of the problem it replaced.
Call attribution
The click id travels with the phone call, so a booked consultation can be credited to the ad that caused it.
Source to revenue
Leads, qualified calls, consultations, procedures and collected revenue, per source, on one screen.
The sources that produced nothing
Shown rather than omitted, which is usually the more useful half.
Referral, organic and walk-in
The same reporting for practices that do not advertise. Which referral relationship is carrying the month is a question too.
Web chat you own
The widget is configured in RootLogic and embedded on your site. Transcripts land in your tenant, not a vendor's console.
The honest zero
Where a feed is not configured the screen says unconfigured. A coverage gap and a genuine zero look identical everywhere else in this category.
The phone, the thread and the calendar are one job here.
Most inquiries in elective medicine arrive as a phone call rather than a form. That is why the line is part of the product rather than a partner integration — a call nobody can attribute is a patient nobody can price.
Your own number
Ported in, and yours to take with you if you ever leave.
Extensions and handsets
Each on its own page, granted by role. A practice does not give the front desk the owner's view of the rate card.
Any SIP desk phone
Poly, Yealink, Grandstream, Cisco. Bring the handsets you already own or buy one outright from a reseller.
A softphone on a laptop
No hardware at all, for whoever does not sit at the front desk.
Usage at carrier cost
Five numbers or extensions and 2,000 talk minutes included. Past that, what the carrier charges us, itemized by line, with no markup and no bundle bought in advance.
Recording on the record
Held against the patient, not in a separate portal you log into.
Searchable transcripts
Attached to the same case as the quote and the payment.
A qualified verdict
Was this a real inquiry. Decided by rules you can read — direction, duration, disposition — rather than a score nobody can explain.
Scoring that carries its reasoning
A number without an explanation cannot be coached on, and a scoring system nobody can argue with is not worth having.
Coaching with a name on it
Per staff member, so the conversation is specific. Per source, so a campaign producing bad calls is visible.
What the analysis surfaces
Whether the consultation was actually asked for. Which objections went unanswered. Qualified calls nobody followed up. Questions nobody could answer.
One thread per patient
SMS, email and web chat in a single thread attached to the case, not to somebody's inbox.
Context without opening anything
Whoever picks up the thread sees the consultation, the quote and the last four messages.
A calendar per provider
Merged where it helps. Four views over one set of appointments.
Rooms, chairs and theatres as resources
A resource is a constraint on booking in its own right, so two appointments cannot take the same one. A video link counts as a resource too.
Deposits per service
A practice that charges for a surgical consultation usually does not charge for a touch-up. A free slot booked at midnight is a chair the practice paid for twice.
In person, virtual or phone
How the visit happens is recorded on the appointment, with the room link and its vendor, because a practice may bring its own. Blank means nobody recorded it, which is not the same as in person.
Reschedules that keep the case
The source, the history and the case survive the move.
Where a high-ticket month is made, and far more often lost.
The money is rarely lost at the top of the funnel. It is the consultation nobody called back, the quote nobody chased, the financing application nobody finished. Each of those is a stage with a clock on it here, because a follow-up list somebody maintains by hand decays in a fortnight.
One board
Leads, consultations and cases on a single board instead of three systems that disagree.
A clock on every card
A card sitting quietly for three weeks looks different from one that moved yesterday. Somebody opening it on Tuesday does not count as activity.
Columns that total money
Quoted value per column, so the board reads as revenue rather than volume.
Itemized quotes
Your fee schedule, your figure, your deposit.
A quote with a state
Tracked in three registers at once: where the case sits on the board, what the financing conversation did, and what the invoice it produced is doing.
Financing as a register
Six recorded outcomes instead of a conversation somebody remembers. Use the lenders you already use — we would rather say none are integrated than print a wall of logos.
Expiry that raises an alert
Against the coordinator who owns the case, not in a report nobody opens. The quote stays on the case.
Follow-up that exits on the event
A booking, a procedure, a reply, an inbound call or a stage change each end the sequence, all five defaulted on. Both production failures this design exists to prevent were exit failures, not send failures.
Case acceptance by provider
Accepted over presented. The number that most changes behavior once a practice can see it.
Time to decision
Days from presentation to acceptance, which tells you whether a follow-up sequence should run ten days or forty. Most practices guess.
Discount leakage
Quoted against collected, per provider. Small concessions made in the room are invisible monthly and substantial annually.
Revenue at risk
Open quoted value by expected decision week, so a slow month is visible three weeks before it closes.
A training library for cash-pay medicine
How to present a quote, how to run the financing conversation, and the follow-up call most coordinators avoid. The report shows the gap; the library closes it.
The clinical record the revenue side cannot proceed without.
RootLogic is not your chart and does not want to be. What sits here is what a consultation, a quote and a published photograph depend on: what the patient told you, what they agreed to, and what the result looked like from the angles you asked for.
Intake as fields
Landing on the record, not as a PDF somebody files.
Verbatim and append-only
What the patient said survives a later correction, and the record can say which is which.
A skipped question writes nothing
So an intake cannot blank something a coordinator typed.
A composed provider brief
Assembled from the answers deterministically, with no model behind it. The provider opens the visit with a brief rather than a transcript.
Resumable patient links
No app, no account, no password. Single use, expiring, autosaving as they go.
Outstanding intake, split two ways
Never opened and opened-then-abandoned are different problems. One is a message that may not have arrived.
Consent frozen at signature
Per clause, with a timestamp on each. Forty initials with forty timestamps answer what a single signature image cannot.
Every mark on its own row
IP address and browser captured per mark, in the order the patient made them. A correction is a new document, never an edit.
The rendered wording stored
Never re-rendered from the template, so a name corrected later cannot rewrite what was signed.
Template version stamped
Which wording a patient signed is answerable from the document itself.
Opened, completed, voided
Three separate timestamps. A voided document keeps the reason it was voided and stays readable.
Clause-level practice wording
Reword a clause and only that clause changes. You cannot add one, remove one or change its key, so a risk disclosure is not deletable through a text box.
Witness and physician blocks
Part of the document rather than a note about it, each carrying its own timestamp.
Named angle sets on a request
Which angles were asked for is an array on the request, so “how often do we ask for donor” is a query rather than a parse.
Patient photo uploads by link
A short-lived single-use credential, not an identifier. Requested, consumed and expired are three separate facts and none implies another.
One image per angle per session
A retake replaces rather than accumulating three crown shots nobody can put in order.
Allergies, with “nobody asked” kept separate from “none”
No known drug allergies is an assertion somebody made. An empty list is a question nobody put. They are different facts and they render differently.
Medications with an origin
Reported by the patient, prescribed here, or prescribed elsewhere. Who is responsible for a medication is part of the record rather than an inference.
Prescriber capability per provider
NPI, whether a DEA number is held, EPCS enrollment, the PDMP state and whether the provider is enrolled in it. Stored so a screen can refuse honestly instead of offering a button that fails at the pharmacy.
Interaction screening recorded
Which check ran, when, and what it said, so a chart can prove one happened. The database behind it is licensed clinical decision support and we do not ship one.
Good Faith Exam clearance
The clinician evaluation that gates injectables, with the examiner, their role, the modality, the outcome and its own expiry date. Not the Good Faith Estimate — same three letters, a different obligation, and never joined to it.
An append-only access log
Who opened what, when, from which address. A denied row is as important as a view, and there is no update or delete path, because a log somebody can edit is not a log.
A PDF matching what they saw
Running header and page breaks included, for every issued document.
Quote to invoice to deposit to bank, with the fee on a row you can open.
A deposit is not revenue until it lands. Every figure between the card and the bank account is itemized, and the merchant relationship stays with the practice, because a practice held through its card vault is a practice that cannot leave.
The accepted quote is the invoice
Without anybody retyping a line item or a price.
Six invoice states
Draft, awaiting payment, part paid, paid, void, written off. A balance is never a guess.
Deposits and card on file
Taken at the desk or from a link the patient can open.
Memberships
Recurring plans running against the same patient record.
Payouts with the settlement date
The date the money actually arrived, not the forecast.
Four figures per payout row
Payments, refunds, fees, deposited. They reconcile or the row says so.
Negative payouts represented
When refunds exceed charges the processor debits the account. A system that cannot show that quietly drops the day.
Processor fees itemized
Per payout, so every cent between the charge and the deposit sits on a row you can open.
Margin capped per transaction
An uncapped percentage earns thirty times more on a $12,000 surgical deposit than on a $400 treatment, for the same card and the same work. The cap is what stops that.
The merchant account is yours
In the practice's name, the same as your phone number and your ad accounts.
Card-on-file is portable
Stored credentials move at the processor level. We will not hold a practice through its card vault.
The subscription does not move with volume
Processing is billed separately. A good month should not make your software more expensive.
Good Faith Estimates
The No Surprises Act requires a written estimate for every self-pay patient, which here is every patient. It is issued from the quote rather than retyped, and it stores what it presented at issue, because the patient is holding a copy.
Superbills
Derived from the invoice and the catalog's codes, for the patient to submit for out-of-network reimbursement or to an HSA administrator. Without one the front desk types it in Word.
QuickBooks Online
Built around the date the money actually settled, rather than the date an invoice was raised.
Month to month
No termination fee.
The five sections are an arc, and the sixth closes it.
A practice spends eleven thousand dollars on Google Ads. The ad account reports ninety-four conversions. The front desk remembers a busy month. Neither system can say which of those ninety-four paid for anything.
The click that produced a twelve thousand dollar case and the click that produced nothing look identical to every other system in the building. Closing that is what makes these five one product rather than five. It is set out in full on Attribution.
Reporting looks backwards
Knowing which campaign produced revenue is half the value. The other half is telling the ad platform, so campaigns learn from outcomes instead of form fills.
Nobody else closes it natively
Not one platform serving elective medicine does, and not one names the return leg anywhere in its product. There is a small industry of bolt-ons that exist only to bridge the gap.
The reason is structural
A system that began as an electronic record treats marketing as a module at the edge. Closing the loop means owning the phone, the lead, the consultation, the quote and the payment from day one.
Which is why it is one price
Twelve modules designed together, not a suite that was acquired. One patient record, one thread per case, one set of numbers.
What is deliberately not in it.
RootLogic is the revenue side of the practice. The clinical material above is here because a consultation, a quote, a prescription and a published photograph need it, not because we are replacing a record system. Most practices keep the system they chart in, and that is the whole argument on Keep your chart.
Where a boundary has moved, this page says where it moved to rather than leaving the old sentence standing. Medications, allergies and prescriber capability are recorded here as of September 2026. The engine that would transmit a prescription is not built, and the two are named separately above.
- No claims submission — we do not bill insurance and are not going to. The superbill exists so the PATIENT can submit
- No interaction or contraindication database. That is licensed clinical decision support, and a screen that implies checking with nothing behind it is worse than no screen
- No electronic prescribing until there is a contracted vendor. A prescriber with no network account cannot transmit, and the record says so rather than offering a button that fails at the pharmacy
- No ambient clinical scribe
- No diagnostic output of any kind
- No website builder — RootLogic reads whatever your existing site produces
- No autonomous patient-facing messaging beyond web chat
Do we have to leave the system we chart in?
No, and most practices do not. That is the whole argument on Keep your chart.
How many users are included?
All of them. The price is per location.
Can we run two verticals in one account?
Yes. One tenant, one patient list, whichever packs are switched on.
What happens to our phone number?
You own it, and you take it with you if you ever leave.
Seven things on this page that would otherwise read as live.
They are not, and a product page that lists only what works is a product page nobody can check. Each one names which kind of not-yet it is: waiting on the data model, not built, gated per practice, or fenced in the schema until an agreement is signed.
Line-itemed treatment plans
In the data model. Each item carrying its own acceptance state. Lands when the plan object joins the data model. Quotes carry your figure and your deposit today.
Automatic intake dispatch
Not built. Sending intake by service type, and chasing anything unsigned on a schedule. A coordinator issues each link from the record today.
Sequence and reminder sending
Queued, no transport. The sequence engine resolves each message and writes it to the outbox. Until a transport is attached those rows hold pending transport, which is their honest state and is never rendered as sent. The exits are built and running.
Publishing consent on an image
Not built. Consent as a state on a photograph, with its scope and date, and a withdrawal that propagates. Named here because a marketing library you cannot prove is cleared is the asset every practice has and cannot use.
Timepoints on a photo set
Not built. Captures anchored to the procedure date, so a three, six and twelve month comparison assembles itself. Angles are recorded today; the timepoint is not.
Live card processing
Per practice. Activates after merchant onboarding, which is a decision the processor makes about your practice and not one we can make for you.
Ad platform connections
Not in the product. Spend and clicks read from Google Ads and Meta, and collected outcomes uploaded back to them. RootLogic captures the click id and carries it to the revenue; the connection that would import spend and upload conversions is not in the application.
The mobile app
In build. Native iPhone and iPad, carrying leads, conversations, pipeline and two-way calling. TestFlight from late November, App Store submission targeted for December. A softphone on a laptop works today.
Consent and imagery on a live practice
Gated in the schema. The database refuses a consent template, a signed document or a consultation photograph to a practice until our agreement covering patient data is in place. A fence in the schema rather than a policy in a document.