Examples of Good and Bad Requests

See Requests in Action

Some requests are routed. Others are not. That difference is the point.

Psychiatry, Adult ADHD

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

What Happened: Routed. The request named a specific type of care, included a timeframe, and gave a usable location. That's enough to find who fits.

Pediatric Speech Evaluation

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

What Happened: Routed. The request was clear about who needed care, what kind and when. Medixlinx had what it needed to find the right provider.

Veterinary Exam

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

What Happened: Routed. The request identified the animal, the need, the timeframe, and the location. All four were present and usable.

Too Broad to Route

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

What Happened: Not routed. The request described a symptom but didn't indicate what kind of care was being sought. Medixlinx needs more than a location and a general complaint to find an exact fit.

Area Not Yet Covered

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

What Happened: Not routed. The request was otherwise clear, but Medixlinx doesn't have provider coverage in that area. A well-formed request still won't route if the geography isn't supported.

Outside Scope

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

What Happened: Not routed. This isn't the kind of care need Medixlinx routes. It's health-related, but it doesn't fall within the scope of care requests the system handles.