Examples of Exact-Fit Care Routing

Request: “I’m looking for a psychiatrist who evaluates adult ADHD. I need to see them tomorrow. I live near 11231.”

Validation: Pass — adult psychiatric evaluation need with a specific diagnostic focus.

Decision: Routed

Why: The request includes a clear care concern, the time signal, a usable geography, and a defined specialty target.

Request: “My shoulder has been hurting for a while and I want someone nearby. We live in 11231.”

Validation: Fail — musculoskeletal concern identified, but no routing-grade service target is present.

Decision: Not Routed

Why: A valid ZIP code does not overcome structural ambiguity. The request is too broad for exact-fit routing.

Request: “I need a pediatric speech evaluation this Friday for my six-year-old. We’re near 11201.”

Validation: Pass — pediatric evaluation request with a defined service need and usable location signal.

Decision: Routed

Why: The request includes age context, a clear care need, and the specificity required for provider routing.

Request: “My dog needs an exam tomorrow. I’m in 10005.”

Validation: Pass — species-specific veterinary request with a defined service need.

Decision: Routed

Why: The request includes a clear animal-care need, a usable geography, and the time signal required for routing.

Request: “I need an in-person visit for knee pain this Friday in 99999.”

Validation: Fail — the request includes time, condition, and location, but the geography is unsupported.

Decision: Not Routed

Why: A request can be structurally complete and still fail when Medixlinx coverage or aligned provider presence does not exist there.

Request: “I need whitening strips tomorrow in 10019.”

Validation: Fail — the request is location-usable but does not clearly present a routeable care need.

Decision: Not Routed

Why: Not every health-adjacent request qualifies as valid Medixlinx intake for exact-fit routing.