I Quit Healthcare Once. I'm Back to Reshape Credentialing.

I quit healthcare once.

I started out at a large hospital system in Health Information Management, and quickly learned that I was a small fish in a big pond. The problems I saw were enormous and the levers I could pull were tiny. I decided to move into the local community where I felt I could make a stronger and more direct impact. Over the years, I wore nearly every administrative hat a small clinic has. HIPAA compliance, medical billing and coding, insurance prior authorizations, claim denial appeals, scheduling, release of information. And I was good at it. I eliminated pain points, closed compliance gaps, and built stronger regulatory foundations. Everyone had clarity into each other's roles, understood how we were supporting each other as teammates, and what I built worked.

But it still wasn't enough.

Every fix I made was a drop in a bucket. The real problems, the ones that decide whether providers can treat patients, whether practices can grow, whether anyone gets paid on time, and whether the people holding it all together get the tools they need, lived at a systemic level way above me. I could win small. And win small I did, but I couldn't change the system. Eventually, I burned out trying.

So I left.

The seven years away

I spent the next seven years in operations, training, and product roles, solving problems I had real leverage over for the first time. And I said yes to everything. Every pilot program, every new project, every chance to learn from leaders who'd actually made change stick, whether on a five-person team or at a Fortune 100 organization.

I learned how to build training programs that actually prepare people for their real life daily work. How to write an SOP that gives murky processes clarity and helps people do their jobs without guessing what the rules are this week. How to pilot new software and gather feedback that improves it instead of just defending it. How to sit between engineering and the people who use the tools, and translate honestly in both directions.

At the time, I didn't think I was building toward anything in particular. I just knew I wanted to fix things, big or small, in whatever room I happened to be in. Now looking back, I realize none of it was incidental. Every project, every mentor, every side quest I took on, turned out to be a specific and unique tool I'd need in my toolbelt for the work I'm doing now.

Why credentialing, why now

When I met Dylan Avatar and the Credential Network team, I knew within the first call. This is what it's all been building towards. Healthcare. Compliance. Operations. Training. Product. 13 years of "this seems unrelated" was my journey leading me to Credential Network.

So with all this background, what do I see when I look at credentialing and the people behind the work?

Credentialing is one of the most foundational parts of healthcare, and it is by far the most complex, and the hardest to fix. Providers cannot treat patients and receive reimbursement for their services until they are credentialed. Providers flying around the country to provide emergency relief cannot offer disaster aid until they are credentialed at their destination. A health system can't grow, expand a service line, or open a new location until its providers are credentialed. Everything starts and ends with credentialing.

Why it's still this hard

Since this is such a crucial service that keeps the healthcare world running, we have obviously supplied the specialists who handle this work with the most cutting edge tools and technology, right? Wrong. Credentialing specialists spend their days working out of spreadsheets. With PDFs that are scanned and re-scanned. Faxes that became e-mail attachments and then became faxes again. Running on institutional knowledge that lives in senior team members' heads, who are on the cusp of retiring, and we haven't planned for what happens after they leave and take their knowledge with them.

People have been working on pieces of this for years, and that work matters. Healthtech hasn't been slow to modernize because nobody cared. It's been slow because the regulatory weight of ensuring PHI and PII are handled securely and properly at every step of the process is genuinely enormous. Getting it right is hard, and most innovators looked at the size of the problem and chose a less complex one to solve.

What makes Credential Network different is the ambition. We are building to fix it end to end. The whole shape of the problem. We're building it across the platform credentialing teams work in every day (CredComply), the AI partner that drafts, verifies, and chases the busywork alongside them (CredAssist), and the wallet providers carry with them between every job and license renewal (CredWallet). That is going to take time, and it is going to take honest input from the people doing this work. But you won't hear "we don't do that at Credential Network." You'll hear "we're already working on a solution for that," or "it's on our radar and we're working towards that." The question we ask isn't whether we can take something on. It's how we take it on well.

The conversation I want to have

If you're the credentialing specialist, the med staff coordinator, or the person who somehow inherited enrollment because the last person retired and someone had to fill the gap, I want to hear from you. All of it. The whole ugly truth.

I spend hours every week on calls with incredible people who do this work, from two-provider clinics to enterprise health systems, and I will tell you what I tell all of them. I am not here to nod politely and take notes. I want the petty stuff and the systemic stuff and everything in between. Tell me what ruins your day. Tell me what you've been banging your head against the wall about for years, wondering why can't somebody just… Tell me the thing you've stopped bringing up, because nothing ever came of it the last fifteen times you tried. Tell me what it would look like if someone handed you a magic wand and you got to design this work from scratch.

What you tell me doesn't disappear into a notebook somewhere. It becomes research, then ideation, then design, then Product Requirements, then a spot on our roadmap, and then an engineer starts cooking. That is the path from your shared frustrations to a new tool in your hands. I will get us as close to your dream scenario as the technology, the regulations, and the laws of physics will allow.

That's the work. And here's the rest. I hear you. I believe you. I've been there. And I'm spending every day finding solutions for you.