PSS News
Updates, Answers & Practical Advice
Product updates, support guidance, common technical issues, and commentary from decades of working with medical practices and billing teams.
featured article
Why Phoenix?
Phoenix Wasn’t Built With Billing Second.
Most practice management software has to do a lot of things.
Scheduling. Patient information. Reporting. Clinical workflows.
And somewhere along the way, billing gets added to the list.
Phoenix was built differently.
Medical billing isn’t a module inside Phoenix.
It’s the foundation Phoenix was built on.
Forged From Decades of Medical Billing
For the last 26 years, we’ve worked inside the medical billing industry—supporting practices, billing services, legacy software users, clearinghouses, and the people responsible for actually getting claims paid.
We’ve seen what happens after a claim leaves the office. We’ve seen the rejections, the denials, the missing information, the payments that never get posted.
The claims nobody followed up on. The timely-filing deadlines that quietly pass, And we’ve spent years building tools to solve those problems.
Phoenix wasn’t introduced to medical billing.
Phoenix was born in it.
We Already Built the Pieces
Long before Phoenix, we were solving billing problems one at a time.
Validator was built to catch claim problems before they became rejections.
EZPost was built to make electronic remittance posting faster and more accurate.
EDI Insight gave billers more visibility into what was happening between the practice, clearinghouse, and payer.
Our reporting tools helped practices understand what was actually happening financially. Each tool solved a problem.
But eventually we had to ask:
Why are we building all of these tools around someone else’s software instead of building the software we actually want?
That question became Phoenix.
Built Around the Entire Revenue Cycle
Phoenix doesn’t treat submitting a claim as the finish line.
It’s just one step.
Patient Registration → Eligibility → Scheduling → Billing → Validation → Clearinghouse → Payment Posting → Follow-Up → Reporting
Those aren’t separate systems. They’re one continuous revenue cycle.
Phoenix is designed so the person doing the billing can see what needs attention before revenue disappears into a black hole.
Which claims are invalid? Rejected? Denied? Haven’t been paid? Which need follow-up? Which are approaching timely filing?
What happened to every claim?
That’s the question Phoenix is built to answer.
Built by People Who Actually Do This
Phoenix wasn’t designed from a checklist of what medical software is “supposed” to have.
It’s the product of 26 years spent working with the people who actually use it.
Physicians. Billers. Practice managers. Billing services. Support professionals.
We’ve watched people develop workarounds because their software couldn’t do what they needed, we’ve even BUILT some of these work arounds
We’ve watched billing teams jump between programs, clearinghouse websites, spreadsheets, reports, and handwritten notes just to keep track of their work.
We’ve built software to patch those gaps.
Phoenix is what happens when you stop patching the gaps and build the foundation correctly instead.
Your Practice Shouldn’t Have to Work Around Its Software
A small independent practice and a large billing service do not operate the same way.
Phoenix isn’t going to pretend they do.
Work queues, user permissions, saved searches, reporting, claim validation, payment posting, and multi-practice workflows are being designed around flexibility.
The philosophy is simple:
The software should adapt to the practice—not force the practice to adapt to the software.
That applies to infrastructure too.
Run Phoenix locally if you want control of your own environment.
Or choose our hosted option and let PSS handle much of the infrastructure, backups, updates, and technical burden behind it.
The same philosophy applies to clearinghouses.
Changing your practice management software shouldn’t mean surrendering every other choice your practice has made.
The Bigger Reason
There is one idea underneath everything we’re building:
Phoenix exists to help independent healthcare providers stay independent.
Independent practices already have enough working against them.
Their software shouldn’t be another obstacle.
A practice that can’t efficiently collect the money it has earned eventually loses the ability to remain independent—no matter how good the physician is at caring for patients.
That’s why billing isn’t an afterthought in Phoenix.
Getting practices paid is the foundation.
Built by a Small Team That Still Listens
Phoenix is being built by a small team, but the ideas behind it come from decades of listening to medical billers, practices, and the people actually doing the work.
Over the years, our founder participated in advisory groups for practice management software alongside other resellers and professionals who worked directly with customers every day.
That experience taught us an important lesson:
An advisory board only matters if the people building the software are willing to listen to it.
As software companies grow, change ownership, and become further removed from the people using their products every day, it can become increasingly difficult for real customer feedback to reach the people making product decisions.
We don’t want Phoenix to ever reach that point. We’re intentionally building it differently. We’re small enough to listen. Small enough to change direction when a medical biller tells us something doesn’t work.
And close enough to our customers to remember who the software is actually being built for.
The people using Phoenix should always have a voice in what Phoenix becomes.
So, Why Phoenix?
Because after 26 years in medical billing, we know where the bodies are buried. We’ve seen claims fail. We’ve seen where workflows break. We’ve seen where money gets left behind.
And we’ve spent decades building tools to fix those problems.
Phoenix brings those lessons together from the beginning.
Not billing added to practice management.
Practice management built from billing outward.
That’s Phoenix.
Ready for whats next?
See What Phoenix Was Built to Do.
Phoenix is being built for the people who live in the revenue cycle every day. If you want a closer look or you’re interested in being part of the upcoming beta, we’d love to hear from you.
09/01/2026 Phoenix Beta Launch
08/18/2026 Cybersecurity PSA – Is Your Backup Actually…
08/01/2026 Why Phoenix?
07/01/2026 Happy 4th of July!
03/01/2026 To All of Our EDI Insight Users
Subscribe to Our Newsletter!