The Operating Platform
How work moves to the center, and what stops it.
A capability list says what exists. This page is the mechanics underneath it: the rule that decides where a piece of work sits, the order anything is allowed to move in, what can be undone afterward, and where the rule says no.
The rule
Three filters decide where the work sits.
Every capability the platform could carry gets the same three questions in the same order. The first asks whether holding the work in one place actually executes better than every practice doing it separately. The second asks who is left holding the difference when the work is done differently from office to office. The third asks whether the work needs the doctor present, and it outranks the other two. A capability that fails a filter stays where it is, including the ones it would suit us to take.
| The filter | The question | What the answer decides |
|---|---|---|
| Leverage | Does one place doing this beat every practice doing it separately, or does one place only make it easier for the center to watch? | If the gain is visibility at the center rather than better execution in the office, the work stays in the office. |
| Exposure | When this is done differently from practice to practice, who ends up carrying the difference? | If the difference lands on one practice alone, legally, financially, or with a patient, the work moves onto shared rails and stops being optional. Compliance floors and data security sit here. |
| Presence | Does the work require the doctor to be in the room, with the patient or with the team? | If it does, it stays with the doctor whatever the first two filters said. This filter has the last word. |
The same three questions are put to capabilities we would like to run and to capabilities we would rather not. If a filter is being argued around instead of answered, that is the answer.
Sequence
How a capability actually arrives.
Reversal
Which of these could actually come back.
Usually comes back cleanly
- A reporting pack. The practice can return to its own numbers inside a month, provided the definitions were written down when they changed.
- A vendor agreement the practice is named on, rather than one it simply sits underneath.
- A workflow the center designed but the practice's own team still runs day to day.
- Anything where the practice's data can leave whole, in a format another system can actually read.
One-way doors, or close to it
- A core system that becomes the only place several years of the practice's history lives.
- Group-level agreements a single practice cannot be carved out of on its own terms.
- A definition change that rewrote how prior periods read, so the old reports and the new ones no longer compare.
- Any position the practice chose not to refill once the work moved to the center.
What the label measures
The DSO label describes who manages the back office, not who owns the practice.
The DSO label is used widely and defined narrowly. The ADA Health Policy Institute counts affiliation by whether an outside entity manages non-clinical functions, not by who owns the practice, so a dentist can be counted as DSO affiliated without anyone having sold equity.
The more useful point is what the definition leaves out. It is a measure of who manages. It does not reach who decides, which means no figure built on it will sort two platforms by the thing this page is about. That has to be read off the mechanics instead: the rule, the sequence, and the limits.
Limits
Where the rule says no.
Support is not conditioned on production. A capability the practice has does not get withdrawn because a month came in soft.
Uniformity is not one of the three filters. That another practice runs a system is not, by itself, a reason to move this one onto it.
Capabilities are not bundled. Declining one does not put another out of reach.
The center does not take on a capability it cannot staff. Work that moves to the center and then runs short-handed is worse than the version the practice was already running.
A capability does not move because the center wants better visibility into it. If the center wants a number, the center can ask for the number.
None of this is enforceable because a website says it. The partnership documents are where a limit becomes a limit, and terms are developed with each practice rather than published. So the useful question is which of these are written into yours, and what the documents say happens when one of them is crossed.
Ask how the platform would work in your practice.
Worth bringing: the capabilities you would want left alone, what you would need to see before letting one move, and which of the limits above you would want written down. Exact economics are developed privately, so ask for those directly.