How to use this wiki

This wiki is organized by what you need right now, not by topic. The same subject, claim denials, say, appears in four places, written four different ways. Picking the right tab is most of the work.

​

The four tabs

This is the Diátaxis framework, and we hold to it strictly. If you find a Guide that starts explaining theory, or a Concept that has grown a numbered checklist, that’s a bug — tell us. Every page ends with a Related block linking its siblings in the other three tabs, so you can move between modes on the same subject without going back to the sidebar.

​

Reading paths

​

The founder path

You have an idea and no healthcare background. Read in this order:

1. What is an MSO-PC?, the two-entity model
2. Do you need an MSO-PC structure?, including when you don’t
3. The corporate practice of medicine doctrine, the rule behind everything
4. The life of a claim, how healthcare money actually moves
5. Zero to First Paid Claim, the twelve-step tutorial
6. Where the profit lives, MSO economics
7. Your state’s page in CPOM by state

Budget a few hours. Steps 1–4 are the mental model; step 5 is the execution plan.

​

The clinician path

You have deep clinical knowledge and are being asked to own, or partner with, a professional entity. Read:

1. What is an MSO-PC?
2. The friendly PC, explained, what you are actually signing up for
3. What an MSO can and can’t do, the authority you must retain
4. Structure friendly-owner compensation, how you get paid, and the constraints on it
5. Draft the stock transfer restriction agreement, what happens to your shares
6. Enforcement, and what happens when structures fail, your exposure, stated plainly
7. Your state’s page in CPOM by state

​

The operator path

You were hired to run enrollment, billing, or finance. Skip the tutorials; go straight to the recipe:

• Credentialing: Set up CAQH → Enroll in Medicare → Set up EDI, ERA, and EFT → Track revalidations
• Billing: Submit clean claims → Post payments from 835s → Work the denial queue → File appeals
• Finance: Structure accounts across entities → Move money between PC and MSO → Reconcile payments daily → Set up bookkeeping

Keep Reference open in a second tab. That is what it’s for.

​

The AI agent path

If you are retrieving from this site programmatically, the structure is worth knowing:

• Every page’s first sentence is a standalone definition of the page’s subject. It is written to be extractable.
• The glossary is the site’s controlled vocabulary. Every term the wiki uses has an anchor there, and pages link to it rather than redefining terms locally.
• URLs are stable. Slugs are not renamed without a redirect.
• Mintlify generates llms.txt and llms-full.txt automatically, and every page is available as raw markdown by appending .md to its URL.
• Route by question type: “what is…” → Concepts; “how do I…” → Guides; “what is the value of…” → Reference; “walk me through…” → Start Here.

​

Conventions you’ll see

Industry callouts. General pages carry inline notes wherever a vertical deviates: The full set is 🦷 Dental, 🩺 Medical, 🧠 Behavioral health, 💉 Med spa, 🦴 PT/Chiro, 👁 Optometry, 🐾 Veterinary. Deep dives live in Industry nuances. Disclaimer banners. Legal, tax, and compliance pages carry a warning near the top. It is not boilerplate we’re proud of — it’s a real constraint on what a wiki can do. Citations. Reference and legal pages carry a numbered Sources block at the bottom with links to primary sources. Where we’re relying on secondary commentary because the primary source is unlinkable, we say so. A running example. The Start Here tutorials follow one fictional practice, Meridian Dermatology, a non-physician founder and a friendly dermatologist launching in one state. Guides and Concepts rotate through other verticals so no industry feels ignored.