Specialty DSOs: Orthodontics, Oral Surgery and Pediatrics

What should specialty DSOs prove before you compare offers?

Ask the group to turn its support promise into an office-level plan. “Specialty expertise” may describe a brand, a leadership team, or a service you can actually use. Those are different things. A useful proposal identifies the work, the provider, the location, the start date, and how the practice gets help when the service fails.

Start with the needs of the practice being sold or acquired. An orthodontic office with long courses of care may ask different questions from an oral surgery office that needs a particular setting and team. A pediatric practice may need support that fits family communication and its actual care model. Do not infer those needs from the specialty label alone.

The ADA's January 2021 guide describes business-services agreements with widely varying administrative scope. Use the actual agreement to establish what is promised. ADA business-services guide.

This guide evaluates the service a specialty network proposes to deliver. The DSO overview explains the broader model, while the DSO offer comparison addresses the buyer choice. Neither a recognized name nor a larger purchase headline proves that a promised service will reach your office.

Separate a service promise from its evidence

Build a short schedule of the support you expect to receive. Ask for a named responsible role, a backup route, and evidence of actual readiness. A brochure may be enough to open the discussion. It is not the final basis for a transition plan.

Keep a distinction between access to a service and an obligation to deliver it. A group might offer a shared resource subject to availability. Your office may need a firm commitment for a specific date. Have counsel and the operating team resolve that gap before treating the resource as confirmed.

What changes when the specialty is orthodontics?

Focus on who owns each unresolved handoff question. A treatment course may span the change in ownership. Your review should identify the receiving clinician, the relevant records, and the person who resolves business questions about payments and remaining work. Do not let central billing and local care teams assume that the other has taken responsibility.

The AAO's July 2017 contract questions include the handling of unfinished treatment, collected fees and transitions between doctors. This dated checklist supports asking those questions; it is not current legal advice. AAO contract questions.

For a proposed network arrangement, walk through a hypothetical unresolved case using no real patient details. Ask where the exception enters the system, who can act, and how completion is recorded. The aim is to test the route through the business, not to prescribe treatment or decide a patient's course of care.

The orthodontic practice transition guide examines balances and remaining obligations. Bring its findings into the support agreement. Do not repeat that calculation as proof that the network can deliver the required service. A payment reconciliation and a workable service route answer different questions.

What changes for oral and maxillofacial surgery?

Test a proposed coverage arrangement against the actual office. A list of surgeons in the network says little about which clinician can work at this site, on this date, under the reviewed arrangements. Obtain the relevant site and provider evidence through qualified clinical and legal reviewers before using the plan in a transaction budget.

AAOMS's office-evaluation material distinguishes its component-society process from state licensing-board requirements and recognizes differences among states. A society process is not a substitute for checking the applicable state requirements. AAOMS office-evaluation material.

Ask the group to show how its support team tracks unresolved readiness items. A report labeled complete should identify what was checked, the office involved, and the person who accepted it. If an item remains open, the plan should show which proposed service depends on it. Do not describe an unavailable service as ready merely because equipment is present.

Use the oral surgery transition guide for the separate practice-level review. Here, the issue is whether the larger organization has accepted a specific support duty and can perform it within the reviewed plan.

What changes for pediatric practices?

Ask how the support model serves the office's actual patients and care setting. The proposal should explain the division of work between local staff and central teams. Test who answers an unresolved family-facing business question, who routes it to the responsible professional, and who confirms that it has been resolved.

AAPD's guidance, revised in 2023, addresses personnel, facilities, documentation and quality assurance when clinicians choose office-based deep sedation or general anesthesia with anesthesia providers. This limited setting needs its own qualified review. AAPD anesthesia-provider guidance.

That source does not imply that every pediatric practice uses that care model. Do not build a service requirement around a capability the office does not need. Equally, if the proposed business plan depends on it, identify the actual prerequisites instead of relying on a network-wide description.

The pediatric practice guide addresses household, payer and transition details. Use those findings to write a specific request for support. Keep authority over care, consent and patient information within its separately reviewed process.

Worked case: enough sessions can still leave offices uncovered

The following scheduling exercise is entirely invented. It tests a support promise, not clinical capacity, patient throughput, revenue or legal eligibility. Assume qualified reviewers have already accepted each permitted office-provider arrangement. The listed slots include all needed preparation and travel. No person can serve two offices in the same slot.

One specialist has eight distinct, nonoverlapping session slots, labeled S1 through S8, during a supplied planning cycle. Offices A and B each request three sessions. Office C requests two. A session is a defined business scheduling block; no treatment time or number of patients is implied.

The totals look balanced: eight requests and eight slots. But A and B need six sessions between them and can use only the same four slots. C can use two of the other four. At most six requests can be filled under these exact rules, leaving two unfilled.

One feasible assignment gives A slots S1, S2 and S3; B slot S4; and C slots S5 and S6. Slots S7 and S8 remain unused because neither A nor B can use them. This is an example assignment, not a recommended order of preference among offices or patients.

The shortfall exists because availability does not match need. Adding the numbers hides that constraint. Ask the network to identify a feasible assignment before accepting a statement that it has enough total coverage. The same test can be done with dates and reviewed availability in a real planning file.

Test flexibility and disruption as separate cases

First change only B's flexibility. Allow B to use S7 and S8 as well as S1 through S4. All other base rules stay fixed. A can use S1, S2 and S3, B can use S4, S7 and S8, and C can use S5 and S6. All eight requests now fit.

The added flexibility does not create more specialist time. It lets the existing time meet the stated needs. In a real plan, check what permits that change and whether the office can sustain it. Do not assume a scheduling change is costless or clinically suitable because the teaching case allows it.

For the disruption case, restore B's original limits and remove S4. A and B can fill only three requests in S1 through S3; C can still fill two. The maximum is five. This branch does not also include the flexibility change. It tests how the original plan responds to one lost slot.

These results do not show how to prioritize actual care. The appropriate professionals must make that decision. They show why a business promise needs a feasible calendar and a response to disruption, rather than a total number of providers or sessions.

Turn the support plan into an acceptance record

Before closing, give each required service a clear readiness test. The test should show what evidence makes the service usable and who can accept it. Avoid vague labels such as “integrated” when the office still lacks access, an assigned contact, or a confirmed date.

For a systems task, a completed ticket may be useful evidence. For a staffing task, identify the actual arrangement and its start status. For a clinical service, rely on the qualified review appropriate to the work. Do not substitute one kind of evidence for another merely to mark the overall project complete.

Also define the exception route after launch. Who receives a request? Who has authority to resolve it? When does an unresolved matter reach the next responsible person? A service can be easy to request yet difficult to complete if no one owns the final step. Record the closure, not just the initial referral to another team.

Compare cost only after the service is defined

Ask which support costs replace an existing expense and which are added. Obtain the actual fee basis, included tasks, exclusions and proposed local staffing plan. An attractive fee is hard to assess if the practice must still buy the service elsewhere or retain the same staff work.

Keep promised savings separate from the current operating case. If a support plan depends on hiring, systems changes or a later contract, show that dependency. The practice should not be valued as though all hoped-for benefits already exist. Use the financing guide to organize any funding implications of the supported plan.

Likewise, compare the service proposal alongside the seller's actual post-sale role. A group might centralize one task while asking the seller to keep doing another. Write down both. A smooth handoff requires agreement on who performs the work, not just which party receives the fee or owns the practice.

Protect confidentiality while testing the plan

Keep initial outreach seller-blind. Obtain an NDA before identifying the practice to a prospective buyer, then release authorized business evidence in stages that fit the support review. Involve staff when their actual scheduling, systems or handoff duties require participation, with the owner agreeing the scope and communication plan.

Commercial confidentiality does not settle patient-information access or replace required notices. Use appropriate privacy and clinical processes for those matters. An early service test can use fictional examples or aggregate work descriptions without exposing a patient's information. Do not send identifiable records through a booking form.

Common mistakes and summary

Avoid assuming a specialty brand guarantees local capacity. Do not count a recruiting plan as confirmed coverage, a shared contact as a completed service, or unused sessions as interchangeable with the sessions an office needs. Ask what the proposal can deliver under the actual constraints before assigning it value.

A specialty DSO proposal should connect each promised service to a responsible party, usable evidence and a feasible schedule. The invented case shows why balanced totals can still leave offices without the requested sessions. Compare the service and its cost after the relevant professionals have reviewed the operating plan. Bring the proposal and its unresolved support questions to a confidential planning call with Jason Taken at HedgeStone.