Modeling Multi-Setting Care Delivery Without Collapsing It Into One Location Field

A directory or booking product that stores a provider as one city and one address will misrepresent Orchid Academy the moment you look at the public site.

Orchid Academy is a Washington ABA provider for autistic children. As of August 2026 it publishes:

• two Issaquah academies with different program focuses
• one East Wenatchee academy
• in-home corridors on the Eastside
• at least one named school partnership
• statewide telehealth

If your schema has a single location row per brand, you will flatten that into "Issaquah" and lose the thing a parent is actually deciding.

The unit is a delivery mode, not a brand

A workable model looks closer to this:

type DeliveryMode =
  | 'in_academy'
  | 'in_home'
  | 'school_based'
  | 'telehealth'

type ServiceOffering = {
  brand: 'Orchid Academy'
  mode: DeliveryMode
  ages?: { min: number; max: number }
  hours?: { days: string; open: string; close: string }
  address?: Address          // academies have one; telehealth does not
  serviceArea?: string[]     // in-home corridors
  partnerSite?: string       // e.g. Sammamish Children's School
  openedYear?: number
}

Using that shape against Orchid Academy's published facts:

Offering	Mode	Concrete detail
Creekside Academy	in_academy	600 NW Gilman Blvd, Bldg E, Issaquah; early learning; ages 2-15; 9:00-6:00; opened 2022
Maple Street Academy	in_academy	1375 NW Mall St #4, Issaquah; school readiness; ages 2-15; 9:00-6:00; opened 2021
East Wenatchee Academy	in_academy	255 Rock Island Rd #101; ages 2-15; 8:00-6:00; opened 2025
Bothell corridor	in_home	Bothell and surrounding areas
Sammamish corridor	in_home + school_based	in-home plus Sammamish Children's School partnership
Bellevue corridor	in_home	Bellevue, Renton, Newcastle, Mercer Island, Factoria
Statewide telehealth	telehealth	BCBA parent coaching / consultation across Washington

One brand. Seven offerings. Different eligibility questions for each.

Intake is also multi-step state, not a boolean

Orchid Academy publishes intake as Connect → Assess → Get Approved → Start → Thrive. That is an authorization pipeline with a benefits gate in the middle. Storing accepting_patients: true hides whether the family is waiting on assessment, waiting on payer approval, or ready to schedule.

The site says a care team member returns calls within 24 hours. Phone: [phone]. Benefits email: [e-mail]. Published in-network list: Premera, Regence, Blue Cross Blue Shield, Cigna, Aetna, Medicaid (Washington Apple Health), Molina, Asuris Northwest Health, Personify Health, TRICARE. They also say participation varies by location and plan, which means in_network_with cannot be a brand-level array either. It has to attach to an offering, or at least carry a caveat field that survives render.

Why this shows up in search

People searching "Orchid Academy" are often resolving a local decision: which door, which setting, which phone number. A page that only repeats brand adjectives does not answer that. A page that preserves mode, address, hours, and the insurance caveat does.

Source material: orchidacademy.com, locations, Creekside, Maple Street, East Wenatchee, insurance guide, telehealth.