Part 09 · Practice Structure
Two-Hat Provider Guide · Part of 10
The two-hat model can be operated by solo providers or within group practice structures. Each setting has real advantages and real constraints. Providers entering the model benefit from understanding which structure fits their situation before they invest in setup that may not match the practice reality they actually want to build.
The solo provider scenario
A solo two-hat provider operates two distinct practices personally — the federal VA Community Care practice and the separate state cannabis evaluation practice — without partners or other clinicians in either. Most providers who explore the two-hat model do so initially as solo operators, often because the model fits within an existing solo federal practice they have already built.
The solo structure has clear advantages. The provider controls both practices entirely. The operational separation is easier to maintain because no other clinicians are operating in either practice. Decisions move quickly because they require only one person’s judgment. The financial structure is simpler because two single-clinician business entities are more straightforward than multi-clinician entities. And the patient relationship is uniformly with one provider, which carries a continuity benefit veterans often appreciate.
What the solo structure requires
Solo two-hat operation requires the provider personally to handle the administrative load of maintaining four-layer separation across two practices. Without partners or substantial support staff, the provider is the one ensuring documentation stays separate, billing flows correctly, scheduling is clean, and credentialing is maintained on both sides. This is workable, but it is real work, and providers underestimating it sometimes find themselves overwhelmed in the first six to twelve months.
The group practice scenario
Group practice structures for the two-hat model come in several variations. The cleanest version: a group practice where some clinicians operate only the federal VA Community Care side, some operate only the cannabis evaluation side, and some (the two-hat clinicians) operate both. The clear separation between roles within the group simplifies operational architecture — the federal practice has its clinicians, the cannabis evaluation practice has its clinicians, and the two-hat providers move between them under the same separation framework that solo providers maintain personally.
A messier version: a group practice where all clinicians are expected to do both. This structure creates harder operational separation because every visit in the practice requires clarity about which practice the clinician is in for that visit. The complexity multiplies with each additional clinician. Most established two-hat group practices have moved toward the cleaner structure, where role specialization within the group simplifies the separation.
The infrastructure that group practice provides
The most concrete advantage of group structure is shared infrastructure. A solo provider running the two-hat model personally handles or contracts every operational function: credentialing, billing, scheduling, EHR administration, compliance, malpractice management, financial accounting. A group practice pools these functions and amortizes the cost across multiple clinicians. The administrative cost per clinician drops meaningfully in group structure.
Specifically, group practice typically provides:
- Dedicated credentialing staff who handle the federal credentialing maintenance and the state cannabis registration renewal cycles
- Billing infrastructure that handles federal claims submission and the cash-pay cannabis evaluation transactions separately
- EHR administration that maintains the access controls and documentation separation across the two practices
- Compliance staff who track regulatory changes affecting both sides and update policies accordingly
- Front desk staff who can manage the two scheduling streams without confusion
- Practice management leadership that owns the overall operational separation as their job, not as a side responsibility
For a solo provider, each of these functions becomes the provider’s own work or a contracted service. The provider absorbs the administrative load directly or pays for it indirectly through service contracts.
The constraint side of group practice
Group practice has real constraints that solo operation does not. The most significant: shared liability across the group. When one clinician in a group practice makes a decision that creates regulatory or malpractice exposure, the group as a whole can face the consequences, depending on the entity structure and the specific facts. Solo providers carry their own risk entirely; group providers share risk with their partners.
Group practice also constrains individual provider decisions. A solo provider who decides to change something about how their cannabis evaluation practice operates can make the change immediately. A group provider proposing the same change has to navigate group governance, partner agreement, and operational consensus. The friction is meaningful for providers who value autonomy in how their practice is structured.
The structure that does not work
Group practices that attempt to operate the two-hat model without genuine operational separation — same EHR, same billing, same scheduling, same staff, just labeled differently — create the exact failure mode the model is designed to avoid. The separation has to be operationally real, not labeled. Groups that cannot or will not build the dual infrastructure tend to drift into mixing the two practices in ways that put the whole group at risk.
The hybrid: solo provider with shared infrastructure
A third structure has emerged in some two-hat practice settings: solo providers operating personally but sharing back-office infrastructure through a management services organization (MSO) or similar shared services arrangement. The clinical practice is solo; the operational infrastructure is shared. Credentialing, billing, scheduling, compliance, and other administrative functions are provided through the shared services arrangement, but the clinical entities and clinical decisions remain solo.
This structure can capture some of the infrastructure benefits of group practice while preserving the clinical autonomy of solo practice. It works best when the shared services arrangement is itself built around the two-hat structure — designed with the separation requirements in mind — rather than retrofit from a generic medical practice management model.
Choosing the structure
Providers evaluating which structure fits their situation can think about a few questions:
Question 1
How much administrative load can you personally absorb?
Solo operation works for providers comfortable with the administrative load that comes with personally running two separate practices. Providers who prefer to focus on clinical work and minimize administrative responsibility are usually better served by group or shared-infrastructure arrangements.
Question 2
What is the existing practice context?
A provider already running a solo federal practice is operationally close to running a solo two-hat practice; adding the cannabis evaluation side does not require fundamental restructuring. A provider in an existing group practice is operationally close to adding the two-hat capability within the group, if the group is willing to build the infrastructure. Starting from where you already are is usually easier than restructuring entirely.
Question 3
What is your risk tolerance?
Solo operation concentrates risk on one provider. Group practice spreads risk across partners but exposes each partner to others’ decisions. The right answer here depends on the provider’s confidence in their own judgment versus their willingness to share both control and risk with partners.
Question 4
What is your time horizon?
Solo practice can be entered and exited individually. Group practice involves longer commitments that are harder to unwind. Providers uncertain about their long-term commitment to the two-hat model are usually better served by starting solo or with shared-infrastructure arrangements that preserve more flexibility.
Mendry’s role across the structures
Mendry supports two-hat providers across all of these structures. For solo providers, Mendry provides the peer network, shared resources, and infrastructure templates that reduce the cost of doing this work alone. For group practices, Mendry provides operational frameworks, regulatory tracking, and inter-practice learning that single groups would have difficulty developing on their own. For hybrid arrangements, Mendry can serve as the shared infrastructure organization itself or as a complement to other shared-services arrangements.
The point of organizational support is not to replace the provider’s judgment about their own practice structure; it is to make whichever structure the provider chooses more workable than it would otherwise be. The two-hat model is operationally complex enough that solo providers without organizational support struggle to maintain it sustainably; small groups without shared learning frequently make the same mistakes that other small groups have already worked through; even larger practices benefit from access to regulatory and operational intelligence that develops faster across a network than within any single practice.