What the data supports. What it doesn't.
PharmaPath combines Google Maps lookup, FDA records, and optional user-submitted reports while keeping every claim inside a clear boundary.
Handled search inputs
Indexed server-sideMedication typeahead hits a normalized FDA-backed index plus a clearly isolated demo-only catalog, while location accepts freeform Google-backed searches such as city/state, ZIP, address, pharmacy name, and landmark queries.
Medication context
FDA evidenceListing, shortage, recall, and approval records stay separate so the access signal remains explainable instead of sounding like a stock feed.
Crowd layer
Separate by designUser-submitted reports can add context where available, but they never become proof of live inventory at a specific store.
Freeform location searches resolve through Google Places Autocomplete, Place Details, and Geocoding, then nearby pharmacy names, hours, ratings, and Maps links come from Google Places.
openFDA drug listing records shape the matched strengths, dosage forms, routes, active listing counts, and manufacturer breadth.
Approval history, application numbers, and formulation records.
Active, available, resolved, and discontinued shortage entries for matching presentations.
Recall and enforcement records tied to the matched medication family.
Signed-in users can submit fill reports. Those reports sit in a separate weighted layer and are not public-source inventory data.
What PharmaPath can state directly, and what still needs a call.
The app keeps live nearby discovery, medication-wide evidence, crowd input, and still-manual steps separate so the product never overstates store-level availability.
- Live nearby pharmacies
- FDA shortage, recall, and approval records
- Medication-wide access friction estimate
- Real-time shelf inventory at any specific store
- Guaranteed same-day pickup
- Insurance approval or copay outcome
Live route and integration checks from /api/health, kept here so the search views stay focused on patient and medication questions.