Phreesia vs Cedar: Which One in 2026?
Phreesia and Cedar do not compete for the same hour of a medical practice's day. Phreesia is the product you put in front of the visit: the intake packet, the eligibility check, the copay at the window, the questionnaire the clinician needs before the rooming note. Cedar is the product you put after the claim: the digital statement, the residual balance, the payment plan, the billing conversation patients actually return. If your partner is asking "which patient-engagement platform," stop and name the queue that is failing. That is the decision. Neither vendor publishes a list price, so the commercial step is a quote that lists seats, modules, migration, and the interface into the chart — not a number you copy from a blog. When you are ready to map the handoff, use the pricing page.
How we evaluated
This page scores two jobs a medical practice already runs, not a feature checklist copied from a vendor site. The first job is access and intake: get a complete, current record into the chart before the clinician opens the encounter, collect what the patient can pay today, and keep the waiting room moving. The second job is patient-pay after the visit: send a bill a patient can understand, take payment without a phone tree, and keep residual balances from aging into collections. Phreesia is built for the first job. Cedar is built for the second. Treating them as substitutes is how a practice buys software for the queue that is already working and leaves the broken one in place.
US Tech Automations scored each product on the workflow a medical practice actually runs: appointment to intake, intake to eligibility, eligibility to time-of-service collection, visit to claim, claim to patient statement, statement to payment or plan, and plan to posting. A product that does not own a step is not marked down for missing a logo. It is marked as the wrong owner for that step. Pricing cells are "not published" because neither vendor sits in a public store with a figure we can date and link. Where a cell cannot be sourced, it stays "not published." We did not invent implementation weeks, client counts, or dollar amounts next to either name.
The money pressure around this choice is not a vendor list price. It is the volume of visits, the size of patient responsibility, and the administrative waste sitting between the card at the window and the statement that arrives later. Physician offices recorded 1.0 billion visits. That load, according to CDC, is 1.0 billion office visits in the National Ambulatory Medical Care Survey year those tables cover, or 320.7 visits per 100 persons, with 50.3% of visits made to primary care physicians. A medical practice that still runs intake on paper is putting that volume through a clipboard.
The other side of the ledger is what patients owe after insurance. According to CMS, national health spending grew 7.2% to $5.3 trillion in 2024, or $15,474 per person, and accounted for 18.0% of GDP. National health spending reached $5.3 trillion in 2024. Out-of-pocket spending is the slice a front desk and a billing office actually touch: according to CMS, out-of-pocket spending grew 5.9% to $556.6 billion in 2024, or 11 percent of total NHE. That is the pool Phreesia tries to collect at the visit and Cedar tries to collect after the claim. It is not a price for either product.
| Spending category | 2024 amount | Share or context | Growth |
|---|---|---|---|
| National health expenditures | $5.3 trillion | 18.0% of GDP | 7.2% |
| Medicare | $1,118.0 billion | 21% of NHE | 7.8% |
| Medicaid | $931.7 billion | 18% of NHE | 6.6% |
| Private health insurance | $1,644.6 billion | 31% of NHE | 8.8% |
| Out-of-pocket | $556.6 billion | 11% of NHE | 5.9% |
| Physician and clinical services | $1,109.7 billion | not published as a share on the fact sheet | 8.1% |
Source: CMS National Health Expenditure Fact Sheet, historical NHE 2024 (page last modified 24 June 2026).
Patient-pay tools exist because a large share of that out-of-pocket never clears on the first statement. U.S. adults owe at least $220 billion in medical debt. According to KFF, people in the United States owe at least $220 billion in medical debt, and 20 million people (nearly 1 in 12 adults) owe medical debt, with 14 million people (6% of adults) owing over $1,000. That is the operational failure a partner is asking you to fix: not "engagement," but unpaid patient responsibility that started as a copay, a deductible, or a balance after adjudication.
| Measure | Figure |
|---|---|
| Aggregate medical debt (conservative SIPP method) | at least $220 billion |
| Adults with medical debt | 20 million (nearly 1 in 12) |
| Adults owing over $1,000 | 14 million (6%) |
| Adults owing over $2,000 | 11 million |
| Adults owing over $5,000 | 6 million (2%) |
| Adults owing over $10,000 | 3 million (1%) |
| Adults with a disability who owe medical debt | 13% |
| Adults without a disability who owe medical debt | 6% |
| Black adults with medical debt | 13% |
| White adults with medical debt | 8% |
| Asian adults with medical debt | 3% |
| Women with medical debt | 9% |
| Men with medical debt | 7% |
| South Dakota adults with medical debt | 17.7% |
| Hawaii adults with medical debt | 2.3% |
| Average share of adults, 2019–2021 | 8.6% |
Source: Peterson-KFF Health System Tracker analysis of the Survey of Income and Program Participation, published 12 February 2024.
Administrative waste is the third pressure, and it is why intake and billing are being automated at all. According to CAQH, the 2025 Index findings reveal a $21 billion industry savings opportunity to reduce waste and ease burden. That figure is an industry savings opportunity, not a return you should write next to Phreesia or Cedar. Use it in the partner memo as the reason the practice is allowed to spend time on this choice, then go back to the two jobs.
We also scored privacy operations, because both products sit on registration data, insurance data, and payment data. According to HHS, OCR settled or imposed a civil money penalty in 152 cases resulting in a total dollar amount of $144,878,972.00 as of 31 October 2024, and private practices and physicians are the second most common type of covered entity named in complaints. A business associate agreement, a minimum-necessary design, and a documented access model are part of the buy, not a footnote after go-live.
| HIPAA enforcement measure (as of 31 October 2024) | Figure |
|---|---|
| Complaints received since April 2003 | 374,321 |
| Compliance reviews initiated | 1,193 |
| Cases resolved | 370,578 (99%) |
| Cases resolved with corrective action or technical assistance during investigation | 31,191 |
| Settlements or civil money penalties | 152 |
| Total dollar amount of settlements and civil money penalties | $144,878,972.00 |
| Investigations with no violation | 15,561 |
| Early technical assistance without a full investigation | 67,873 |
| Complaints not eligible for enforcement | 255,953 |
| Referrals to the Department of Justice | 2,419 |
Source: HHS Office for Civil Rights, Enforcement Highlights, current as of 31 October 2024 (content last reviewed 21 November 2024).
Visit volume is what the front desk feels on a Tuesday morning. | Ambulatory load | Figure | Context |
| --- | --- | --- |
| Adults with a visit in the past year | 85.2% | 2024 National Health Interview Survey |
| Children with a visit in the past year | 95.1% | 2024 National Health Interview Survey |
| Physician office visits | 1.0 billion | NAMCS 2019 national summary |
| Visits per 100 persons | 320.7 | NAMCS 2019 national summary |
| Share of visits to primary care physicians | 50.3% | NAMCS 2019 national summary |
Source: CDC NCHS FastStats, Ambulatory Care Use and Physician office visits.
Related reading for the same industry, without turning this page into a three-product bake-off, is the sealed-data ROI walkthrough for office supervisors. Use it when the partner asks how intake and billing automation shows up in hours, not in a vendor slogan.
Who Phreesia is actually for
Phreesia is for a medical practice whose broken queue is still in the lobby. The practice still hands a clipboard to a patient who already typed the same demographics into a portal last year. Eligibility is a printout someone interprets at the window. Copays are missed because the front desk cannot see a clean patient-pay amount before the patient is called back. Clinical questionnaires arrive after the clinician is in the room. Appointment reminders are a separate habit, not a step that feeds intake. If that paragraph is your Tuesday, you are shopping in Phreesia's job, not Cedar's.
The buyer is usually the operations lead or the office supervisor who owns cycle time from car-park to rooming, not the biller who owns days in A/R. Specialty groups with high deductible traffic feel this first: the visit is short, the patient-pay portion is not, and the only reliable collection point is the window. Independent practices that cannot staff a financial counselor at every site use intake as the counselor. Multi-site groups use it to stop each location inventing its own registration form.
What Phreesia is not: a replacement for the electronic health record, a patient-accounting system, or a post-claim statement platform. If your partner's complaint is "patients do not pay the bill we send two weeks later," you are describing Cedar's job. You can still need intake software. You should not pretend intake software will retire the statement.
US Tech Automations treats eligibility as a workflow step: the card is captured, the payer response lands, and the front desk only then quotes a copay or a deductible remainder. If that step is still a hallway conversation, Phreesia is the product whose job description matches. For a second look at how Phreesia sits next to a practice's charting stack, use this related Phreesia comparison for medical practices as adjacent reading, not as a third vendor on this page.
Ask the quote for locations, languages, intake modules, appointment messaging, eligibility, time-of-service payments, device versus mobile intake, and the interface that writes registration and coverage into the chart. Ask who owns failed eligibility and who posts the copay. If the vendor cannot name the posting path, you are buying a waiting-room tablet, not a collection step.
Who Cedar is actually for
Cedar is for a medical practice whose broken queue starts after the claim. The visit happened. Intake was good enough. The payer paid its portion. What remains is patient responsibility, and that remainder is where the practice is losing the room: paper statements that look like an EOB, a portal nobody logs into, a billing line that cannot offer a plan without a supervisor, and balances that age until they are someone else's collections file. If that paragraph is your month-end, you are shopping in Cedar's job.
The buyer is usually the revenue-cycle lead, the billing manager, or a partner who has stopped believing another statement cycle will change the yield. Groups that already collected the copay at check-in still need this product when the deductible remainder is the real balance. Practices that do hospital-adjacent procedures, or that send patients a bill only after adjudication, feel it more than a copay-only primary-care shop. A medical practice that already has a tolerable front door and an intolerable back door should not buy another intake tool to soothe the billing office.
What Cedar is not: a check-in system, a replacement for the practice management ledger, or a way to skip eligibility. If your partner's complaint is "we still do not know who is in the waiting room or what their plan will pay today," you are describing Phreesia's job. Digital statements will not register the patient.
Hospital price transparency rules are a nearby pressure, not a reason to pretend every medical practice is a hospital. According to the CMS hospital price transparency program, hospitals have been required since 1 January 2021 to post machine-readable files and a consumer-friendly display of shoppable services, and CMS has been tightening enforcement, including new 2026 requirements whose enforcement starts 1 April 2026. A medical practice that is not a hospital still has patients who want an estimate and a residual bill they can pay. Cedar's job lives in that after-care money conversation. Do not cite a hospital civil-money-penalty schedule as Cedar's price. It is not.
Ask the quote for statement volume, channels (portal, email, text, paper leftover), payment plans, financial-assistance screening, estimate workflows, language, and the posting file that has to hit the same encounter in the practice management system. Ask what happens to undeliverable digital bills. Ask who writes off small balances. If the vendor cannot name the posting path, you are buying a nicer PDF, not a collection step.
Side-by-side comparison
Read this table as a job map. "Built for this" means the product's primary work is that step. "not published" means we do not have a sourced, dated figure or a primary-job claim we can defend to a partner. Empty marketing language is not a cell.
| Workflow job | Phreesia | Cedar |
|---|---|---|
| Pre-visit intake and registration | Built for this | not published as the primary job |
| Eligibility check before rooming | Built for this | not published as the primary job |
| Time-of-service copay and outstanding-balance capture | Built for this | not the core after-claim job |
| Clinical questionnaires ahead of the note | Built for this | not published as the primary job |
| Appointment reminders tied to intake | Built for this | Practice still owns access |
| Digital patient statement after adjudication | not published as the primary job | Built for this |
| Payment plans on residual balances | not published as the primary job | Built for this |
| Financial-assistance or charity screening on the bill | not published as the primary job | Built for this |
| Estimate conversation after scheduling, before the claim | Partial overlap at the window | Closer to the post-visit bill and estimate job |
| Replacement for the electronic health record | No | No |
| Public list price | not published | not published |
| Seat or module price | not published | not published |
| Published implementation length | not published | not published |
| Published client count | not published | not published |
Source: vendor primary-job mapping for this comparison; price, volume, and timing cells are "not published" because neither product has a figure in the vendor store we can date and link.
The honest overlap is small. Both products talk to patients about money. Both need an interface to the chart and the ledger. Both will ask for a business associate agreement. That is where the similarity ends. Phreesia collects while the patient is still in the building. Cedar collects after the patient is at home and the payer has spoken. A practice that is failing at both still has to pick which fire is burning the partner's week, then sequence the other job later. Buying the wrong one first does not create a platform. It creates a second inbox.
Do not use a third logo to break a tie. If the charting stack is the actual question, park this page and read a sibling 2026 medical-practice stack comparison. This page stays a two-product decision.
Phreesia: what you gain and what you give up
You gain a defined owner for the pre-visit packet. Demographics, coverage, consents, and screeners can be completed on a phone before the patient stands at the window, which is the only way a busy Tuesday absorbs 1.0 billion national office visits worth of behavior at practice scale without adding a registrar. You gain a place to run eligibility as a step instead of as a hallway interpretation. You gain a chance to ask for the copay and the prior balance while the patient still wants to be seen. You gain a cleaner rooming packet for the clinician, which is the argument that usually moves a reluctant partner who does not care about billing yield.
You give up any fantasy that intake software will retire the statement. Deductible remainders, coinsurance after adjudication, and non-covered lines still become a bill. You give up a slice of front-desk muscle memory: the script at the window changes, the workaround of "we will bill you" has to be unlearned, and someone has to own exceptions when eligibility comes back messy. You give up a clean commercial comparison, because the number is a quote. You give up the option of treating devices, messaging, and payments as optional add-ons you will "phase in" without naming them in the statement of work — if those modules are how the job gets done, they belong in the quote or they will show up as a change order.
The operational con that partners under-weight is posting. A copay collected in intake that does not land on the encounter is not a collection. It is a patient-credit mess. US Tech Automations maps that posting path before go-live on purpose: intake payload, eligibility response, copay tender, and the ledger line have to be one step, not four inboxes. If you want that handoff drawn as an agentic workflow rather than a hallway, use the agentic workflows page as the picture of the spine, then come back to the quote.
The compliance con is the same data you were already collecting, now sitting with a business associate. Registration packets include identifiers, coverage, and sometimes payment details. Minimum necessary, access logs, and a break-glass story for the front desk are part of implementation. OCR's complaint mix is a reminder that private practices are not too small to show up in enforcement, not a prediction about this vendor.
Cedar: what you gain and what you give up
You gain a defined owner for the residual bill. The practice can send a statement a patient can actually read, take a card without staffing the phone, and offer a plan without a manager override on every account. You gain a place to put estimates and assistance screening next to the balance, which is the conversation patients are already having — just not with you. You gain a way to stop pretending that another paper cycle is a strategy. For a billing manager defending yield, that is the product.
You give up any fantasy that a better statement will fix a broken front door. Incomplete registration and skipped eligibility still become denied claims and surprise balances. You give up some control of tone: the practice's voice on the bill is now a configured template, and someone has to approve what the patient sees. You give up the same commercial comparison Phreesia withholds. The number is a quote, driven by statement volume, channels, plan logic, and posting. You give up a quiet month: statement vendors are visible to patients on day one, and the first cycle will generate the calls you were trying to reduce until the templates and the posting file are right.
The operational con that partners under-weight is the leftover paper and the undeliverable digital bill. Not every patient will use the channel you prefer. Dual-send for a cycle is operationally honest. Cutting paper to zero on the first statement run is how balances disappear from your view and not from the patient's. Posting is again the spine: a portal payment that does not match the encounter is a credit on the wrong account. Data extraction only helps if the statement, the payment, and the remittance still resolve to the same visit.
The compliance con is billing data plus collections conduct. Medical debt is already a household shock — KFF's broader poll definition on that same tracker brief found 41% of adults have health care debt when credit cards and family loans are included — and a digital bill that is aggressive, inaccurate, or sent to the wrong person becomes a complaint, not a collection. Configure assistance rules before you configure dunning. That is a practice policy choice, not a software skin.
What switching actually costs
Switching cost is not a list price, because there is not one. It is data, retraining, and the month you run two processes. Budget the quote around those three, then add the interface work your chart and ledger will demand.
Data for a Phreesia-shaped cutover is the intake library: demographics fields, coverage fields, consents, specialty questionnaires, appointment-message templates, and the map that writes those answers into the chart without creating duplicate patients. Someone has to decide which legacy form dies. Someone has to decide what happens when a patient refuses mobile intake and still needs to be seen that hour. Devices, if you use them, are inventory and infection-control, not a footnote. Data for a Cedar-shaped cutover is the statement library: balance types, plan rules, assistance rules, return-mail handling, and the posting file. Someone has to decide which residual balances move, which stay with the old statement vendor through their last cycle, and which are too small to chase. Moving a live A/R file in the middle of a statement cycle is how you double-bill.
Retraining is role-specific. Phreesia retrains the front desk and, to a lesser extent, the people who build questionnaires. The script at the window changes from "sign these papers" to "confirm what you already completed, then we collect what the eligibility response supports." Billers still need a one-hour tour so they stop reversing copays they do not recognize. Cedar retrains billers, posting staff, and whoever answers the billing line. The front desk needs a short tour so they stop promising a paper statement that will not come. Clinicians need almost none of either product, which is why they are the wrong people to own the selection committee.
The month it takes is a dual-run, not a weekend. For intake, that month is old forms still offered as fallback while mobile completion rates come up, with a daily huddle on abandoned packets and eligibility failures. For statements, that month is old paper or old portal still covering accounts that were already in flight, while new visits or newly adjudicated claims go through the new bill. Do not freeze both at once unless you have a staffed command room. A medical practice that tries to recut intake and patient billing in the same cycle is not being ambitious. It is stacking two go-lives on the same phone tree.
Migration questions that belong in the quote, because they are what usually drive the number: number of locations, number of users by role, which modules are in the first release, whether messaging is included, whether payments are included, who builds the interface, who owns testing, what happens to historical packets or historical statements, and whether training is in the statement of work or a separate line. If a salesperson answers those with a single bundle and no scope list, you do not have a quote yet. Ask again.
There is no published figure for either vendor's professional-services hours. Do not accept a blog's guess. Do not accept "roughly," "starting around," or "typically" as a substitute for a number. Those are figures. They are forbidden here because we cannot source them. The partner-safe sentence is: we will not print a price we cannot link, so we are sending a scoped request.
Privacy cutover is its own workstream. Access to intake or billing data has to be role-based on day one. Terminated staff have to lose both the old and the new tool. A practice that leaves the old statement portal live "just in case" has created a second copy of patient financial data with no owner. Close it when the dual-run ends.
Verdict: which one a medical practice should pick in 2026
Pick Phreesia if the failing queue is before the clinician opens the chart. Incomplete packets, eligibility theater at the window, missed copays, and questionnaires that arrive after rooming are intake failures. A medical practice with a tolerable billing yield and an intolerable lobby is not a Cedar buyer this year. Put the scoped request in front of operations, name locations and modules, and make posting of time-of-service payments a go-live criterion.
Pick Cedar if the failing queue is the residual bill. Patients who do not understand the statement, a billing line that cannot take a plan, and balances that age after a clean copay are patient-pay failures. A medical practice with a tolerable front door and an intolerable A/R is not a Phreesia buyer this year. Put the scoped request in front of revenue cycle, name statement volume and posting, and make the first cycle's undeliverable-bill handling a go-live criterion.
They are not close. The words "patient engagement" make them look close. The Tuesday workflow does not. If your partner is still asking which one is the platform, answer with the hour of the day. Morning lobby: Phreesia. After adjudication: Cedar. If you need both hours fixed, you still pick the fire that is in this quarter's partner meeting, then sequence the other. Do not force a single vendor to do the other vendor's job because the committee wanted one contract.
Who should pick the other one: the Cedar-shaped practice should pick Phreesia when the billing office is fine and the lobby is not, even if the original RFP said "patient payments." The Phreesia-shaped practice should pick Cedar when copays already clear at the window and the remaining pain is the bill at home, even if the original RFP said "patient access." Wrong-queue purchases are how these projects get described as "the software did not work" a year later.
Walk the two workflows against US Tech Automations only as a map of the handoff, then buy from the vendor that owns the queue. The commercial next step on our side is pricing for the spine between intake, eligibility, and posting — not a third patient-pay logo.
FAQs
Which product should a small medical practice buy first?
Buy Phreesia first if the front desk still builds the chart at the window and misses copays; buy Cedar first if the chart is fine and the residual bill is where money stalls. A small practice does not get a special published price from either vendor, so the first step is still a scoped quote, not a blog figure. Sequence the second job after the first queue is stable for a full statement cycle or a full intake month.
Can we run intake on Phreesia and statements on Cedar at the same time?
Yes, because they own different hours of the day, but only if posting is designed as one spine. Two patient-pay tools without a shared encounter key will create double-asks and unapplied credits. If you cannot staff that design, pick the failing queue and wait. US Tech Automations maps that spine as a workflow step so the copay, the residual plan, and the ledger land on the same visit.
How do we get a number if neither vendor prints a price?
Send a scoped request that lists locations, users by role, modules, interfaces, migration, training, and the dual-run month, then compare the quotes on that scope. Do not use "starting around" or a number you saw on another site. What usually drives the number is volume (visits or statements), modules (messaging, payments, plans, estimates), and who builds the interface. If those are not in writing, you are not looking at a price yet.
What happens to patient data if we switch off the current intake or statement tool?
Packets, statements, and payment history have to be exported or left readable for the retention period your policy already names, and the old portal has to close when the dual-run ends. Switching does not create a new legal retention clock; it creates a second copy you must either migrate or shut down. Ask the outgoing vendor for the export format before you sign the incoming quote. Ask the incoming vendor who loads history and what they will not load.
Does this choice replace our electronic health record?
No. Phreesia does not become the chart, and Cedar does not become the ledger. Both products fail if the interface cannot write registration, coverage, tenders, and posting back to the systems you already chart and bill in. If the chart is the actual selection fight, stop this comparison and use the sibling stack piece linked above. Keep this page for the intake-versus-statement decision.
Should billing or the front desk own the contract?
Front desk and operations should own a Phreesia-shaped contract; billing and revenue cycle should own a Cedar-shaped contract. Shared goals still belong in the statement of work: posting accuracy, exception handling, and who speaks to the patient when eligibility or a plan fails. A contract owned by the group that does not run the queue is how training gets skipped.
Where do estimates and the No Surprises conversation sit?
Estimates sit closer to Cedar's after-care money job and to any pre-service estimate workflow you already run, not inside a waiting-room tablet by default. Hospital price transparency enforcement is a CMS hospital program with 2021 start dates and 2026 updates; a medical practice still owes patients a number they can act on before a large residual lands. Put estimate ownership in the quote if that is part of the pain. Do not assume intake software will emit a good-faith estimate because it collected a copay.
Key Takeaways
Phreesia owns the lobby: intake, eligibility, questionnaires, and time-of-service collection. Cedar owns the residual bill: statements, plans, and after-claim patient pay. They are not close.
National health spending reached $5.3 trillion in 2024, and out-of-pocket spending was $556.6 billion, which is the pool both products try to collect from at different hours of the day.
U.S. adults owe at least $220 billion in medical debt, so a partner who wants "engagement" is actually asking which unpaid-patient-pay queue you will staff.
Print no list price for either vendor. Ask for a quote that names seats, modules, migration, interfaces, and the dual-run month. "Roughly" is still a figure.
Switching cost is data, retraining, and a month of dual-run. Posting is the spine. Two inboxes is not a go-live.
Private practices already show up in HIPAA complaint mix. A business associate agreement and a role-based access model are part of the buy.
If you need a map of the handoff, start at US Tech Automations pricing and keep this page as a two-product verdict, not a catalog.
About the Author

Helping businesses leverage automation for operational efficiency.