SolvingHealth — Strategic Architecture 2026

The Five Durable Verticals of Healthcare AI

When building software costs zero, five things become the only sources of durable value. SolvingHealth owns all five in healthcare.

Explore the architecture ↓
"Follow the money. Follow the risk. Follow the regulations. Create a model where patients and providers meet with ease and AI simplifies it all."
Founding Thesis, 2026
The thesis

The build layer has collapsed. Any developer can ship a healthcare app in hours. What they cannot ship: a CMS ACCESS attestation, a patient's Living Profile, a 50-state medical license, a physician's clinical judgment, or a professional corporation willing to be accountable to a medical board.

SolvingHealth is not competing with vibe coders. We are building the five things vibe coders can never replicate. Each entity in the ecosystem owns a specific durable vertical. The money flows are the economic expression. The legal structure is the compliance expression. The cooperative model is the cultural expression. Nothing is accidental.

Five durable verticals
๐Ÿ›ก๏ธ
Trust
SolvingHealth MSO
CMS ACCESS ยท HIPAA ยท umbrella insurance ยท safe harbor architecture
๐Ÿ“Š
Context
CareOS + ComfortCard
Living Profile ยท Omaha-to-FHIR ยท patient data gravity
๐ŸŒ
Distribution
Physician Platform
50-state license ยท $299/mo ยท cooperative network
๐ŸŽฏ
Judgment
Clinical Review
Physician reviews every LMN ยท cooperative values
โš–๏ธ
Liability
Altru.care PC
Physician signs ยท bills ยท is accountable

๐Ÿค– The Agentic Health Store

Why SolvingHealth is the healthcare equivalent of Shopify's Agentic Storefronts

In the agentic web, AI agents don't "google" for a doctor. They query structured APIs, verify trust signals, and route decisions to accountable humans. SolvingHealth is the store that AI health agents trust.

When a patient's AI agent needs to find care โ€” verify a physician is licensed, access health context with consent, route a clinical question to a human, check compliance, or initiate a care service โ€” it needs five things: machine-readable data, verified identity, clear terms, a human escalation path, and documented accountability. SolvingHealth provides all five through its FHIR API, NPI verification, safe harbor architecture, clinical review layer, and professional corporation structure.

๐Ÿ” Agent Discovery

FHIR R4 APIs via CMS ACCESS make every physician, service, and care plan machine-readable. AI agents can discover, verify, and interact programmatically.

โœ… AI Authority

NPI verification + CMS ACCESS attestation + umbrella insurance = the trust signal stack. AI agents verify SolvingHealth physicians the way payment agents verify Stripe merchants.

๐Ÿช Agentic Store

Structured service catalog: LMN review, CCM/RPM/RTM, companion care โ€” each with CPT codes, clear scope, pricing, and accountability chain. Machine-selectable, not human-persuasive.

๐Ÿ”„ Agent-to-Physician

AI drafts โ†’ physician reviews. The liability layer is the human escalation path every AI agent needs. Josh doesn't compete with AI โ€” he completes it.

๐Ÿ“‹ Protocol Compliance

FHIR is healthcare's ACP/UCP. CMS ACCESS is the certification that makes SolvingHealth agent-trustworthy. No FHIR API = invisible to AI agents.

๐Ÿชช ComfortCard = Agent ID

QR code health identity. When an AI agent needs patient context โ€” it scans the card, gets the Living Profile, routes care to the right physician. Machine-readable from day one.

Agentic viability checklist
RequirementWhy Agents Need ItSolvingHealthStatus
Machine-readable structured data Agents parse APIs, not web pages FHIR R4 via CMS ACCESS Building
Verified identity Agents need trust signals to route traffic NPI verification + CMS attestation Live (NPI) / Building (CMS)
Clear, unambiguous terms Agents skip ambiguous offers CPT codes, flat pricing, documented scope Defined
Human escalation path 86% of people require human decisions for important matters Josh reviews every LMN โ€” liability layer Architecture
Protocol compliance Agents only transact within verified protocols FHIR (healthcare ACP/UCP) Building
Insurance / accountability Enterprises require underwritten agent actions Umbrella malpractice + PC liability Structured
Consent infrastructure Agents need permissioned data access ComfortCard consent + HIPAA BAA chain Designed
Each vertical — who owns it and why
๐Ÿ›ก๏ธ

Trust — SolvingHealth LLC (MSO)

The verification layer for every clinical and financial transaction

SolvingHealth is to physician practices what Stripe is to e-commerce: the trust layer that makes every downstream transaction legitimate. CMS ACCESS attestation, HIPAA BAA chain, umbrella malpractice, AKS safe harbor architecture โ€” a physician subscribing for $299/mo immediately inherits CMS-grade compliance infrastructure they could never build alone.

In the agentic economy, trust is the routing layer. If an AI agent cannot verify a healthcare service, it will refuse to interact. SolvingHealth's CMS ACCESS / FHIR API is the trust signal that makes every enrolled physician discoverable and verifiable by AI health agents.

Certification
CMS ACCESS / FHIR API (ONC 170.315(g)(10))
Coverage
Umbrella malpractice for enrolled physicians
Compliance
HIPAA BAA ยท AKS safe harbors ยท Stark exceptions
Platform
$299/mo โ€” any MD/DO on our rails
๐Ÿ“Š

Context — CareOS + ComfortCard

The proprietary data that makes general AI specific to each person

An AI model without context is a chatbot. An AI model with a patient's Living Profile โ€” care history, family circle, advance directive, health goals, Omaha System assessments mapped to FHIR โ€” is a clinical teammate. CareOS is the context engine. ComfortCard is the card that carries it.

This is data gravity โ€” the same principle that makes Salesforce, Epic, and Palantir durable. Once a family's story lives in CareOS, switching costs are infinite. Every care visit, every story captured, every LMN reviewed adds to the Living Profile. Competitors start at zero.

Patient Record
Living Profile โ€” Omaha-to-FHIR R4 mapping
Identity
ComfortCard โ€” one card, your whole story
Clinical Data
CII/CRI scores, AmbientScribe, Video Assessment
IP
Omaha โ†’ FHIR mapping = genuine IP
๐ŸŒ

Distribution — Physician Platform + Cooperative Network

National from Day 1, local where it matters

Josh's 50-state license means LMN review, CCM/RPM/RTM billing, and clinical oversight operate nationally from day one. Any licensed physician subscribes for $299/mo and builds their own patient-facing brand on SolvingHealth's infrastructure. Altru.care was the first. There will be hundreds.

On the care side, co-op.care's cooperative model IS the distribution network. Caregivers who earn $25-28/hr W-2 + equity don't just work for co-op.care โ€” they ARE co-op.care. The ownership structure turns every caregiver into a distribution channel, every family into a referral source, and every ComfortCard into a gateway.

Physician Reach
50-state license โ†’ national Day 1
Platform
$299/mo โ†’ any MD/DO, any specialty
Care Network
Cooperative caregivers = owners + distributors
Patient Access
ComfortCard โ†’ LMN + HSA/FSA unlock
๐ŸŽฏ

Judgment — Clinical Review + Cooperative Values

The human decisions AI cannot make and the values it cannot hold

AI drafts the LMN. Josh reviews it. That 3-5 minute review is not a bottleneck โ€” it is the entire value proposition. In a world where AI can generate anything, the physician who says "this is clinically appropriate" is selling judgment. 86% of people believe important decisions should be made by a human. In healthcare, that number is higher.

The cooperative ownership model is a values decision, not a business optimization. When caregivers earn equity through labor hours, turnover drops from 77% to 15%. When "everyone earns, everyone owns, everyone benefits" is the operating principle, the culture becomes a moat that no competitor can replicate by writing better code.

Clinical Judgment
Every LMN reviewed by a licensed physician
Care Philosophy
Person-centered, not task-centered
Ownership Model
W-2 + equity โ†’ 77% โ†’ 15% turnover
Culture
Everyone earns. Everyone owns. Everyone benefits.
โš–๏ธ

Liability — Altru.care Professional Corporation

In healthcare, the person on the hook IS the moat

Altru.care PC signs LMNs. Bills Medicare. Holds the NPI. Stands before a medical board. This is the entity that says: "I am responsible for the clinical decisions made here."

This is why the MSO structure exists. SolvingHealth provides trust infrastructure, but it cannot provide clinical accountability โ€” Colorado CPOM law prohibits it. AI drafts documents as an administrative service; Josh's review is the clinical act. This separation is not a workaround โ€” it is the architecture. As AI gets better, the liability layer gets MORE valuable, because someone still has to be on the hook.

Entity
Colorado PC โ€” sole physician owner
Billing
Medicare CCM/RPM/RTM nationwide
Clinical Authority
CPOM-compliant โ€” all decisions are Josh's
NPI
Type 1 NPI enrolled under Altru.care PC
The integrated stack

A competitor at any single layer is competing with an integrated stack

Layer 5
โš–๏ธ Liability
Altru.care PC
Layer 4
๐ŸŽฏ Judgment
Josh + Cooperative
Layer 3
๐ŸŒ Distribution
Platform + Network
Layer 2
๐Ÿ“Š Context
CareOS + ComfortCard
Layer 1 โ€” Foundation
๐Ÿ›ก๏ธ Trust
SolvingHealth MSO
Three structural moats

๐Ÿ’ป Technology

CareOS + Omaha-to-FHIR + Autonomous LMN System + CMS ACCESS FHIR API. Hospital-grade data from home care. Pure Anthropic architecture.

โš™๏ธ Operations

We employ caregivers. We serve families. We bill Medicare. Our P&L is the proof. Operator, not vendor. Like Amazon built AWS for itself.

๐Ÿค Ownership

Cooperative equity = built-in retention. 77% โ†’ 15% turnover. The ownership structure is a moat code cannot replicate.

Revenue architecture

Every flow mapped to a vertical

StreamFrom โ†’ ToAmountVertical
ComfortCard subscriptionFamily โ†’ co-op.care LCAFlat monthlyContext
Companion careFamily โ†’ co-op.care LCA$400โ€“$12K/moDistribution
LMN review retainerSolvingHealth โ†’ Altru.care PCFixed monthlyJudgment
MSO fee (physician)Altru.care PC โ†’ SolvingHealth18% of collectionsTrust
MSO fee (care ops)co-op.care LCA โ†’ SolvingHealthFixed monthlyTrust
Physician subscriptionAny MD/DO โ†’ SolvingHealth$299/monthDistribution
Medicare CCM/RPM/RTMCMS โ†’ Altru.care PCPer codeLiability
Co-op equity (1% swipe)ComfortCard โ†’ equity pool1% of spendJudgment
SurgeonAccess foundingSurgeon โ†’ SolvingHealth$500 one-timeDistribution
The operator thesis

co-op.care builds technology to run its own care company. Not to sell to other agencies. Not to license as SaaS. The proof is our own P&L โ€” our retention numbers, our patient satisfaction, our Medicare rates, our HSA/FSA unlock volume.

Like Amazon built AWS for itself before offering it to the world, SolvingHealth builds the physician platform for Altru.care first. The internal proof point becomes the external sales argument. The $299/mo subscription is phase 2 distribution of phase 1 proof.

Health AI vendors like Ambience have the technology moat. We have three: Technology + Operations + Ownership. The intersection of all three is the competitive position no single-moat company can replicate.