PHARMACY NETWORK CONNECTORS
Routing, Discovery & Pharmacy Selection
3 of 7Connect pharmacy systems, ePrescription networks, medication catalogues and fulfillment workflows across the medication pathway.
Patient ChoiceDirectoryLocationCapabilitiesAvailabilityRoutingAudit
Patient Choice First
Respect preferred pharmacy and show transparent options.
Intelligent Routing
Suggest based on location, capabilities and availability.
Wide Network Coverage
Search community, group and hospital pharmacy networks.
Safe & Compliant
Audit routing while respecting national/data-protection rules.
How Pharmacy Routing Works
1
Prescription
Signed and ready for routing
2
Find Pharmacies
Directory, location and patient preferences
3
Evaluate Options
Capabilities, opening hours, services and availability
4
Select Pharmacy
Patient choice or transparent suggestion
5
Route Prescription
National network or direct API
6
Track Status
Acceptance, preparation and dispensing
Find Pharmacies
| Search dimension | Examples | Rule |
|---|---|---|
| Location | Distance, postal code, catchment | Never override patient choice solely for proximity |
| Services | Delivery, collection, language, accessibility | Directory capability |
| Prescription capability | ePrescription / specialty service | Must match prescription requirements |
| Availability | Current product availability | Use freshness/confidence metadata |
| Network state | Open / accepting / connector health | Do not route to unavailable endpoint |
Selection Criteria
Patient Preference
Default/preferred pharmacy and explicit selection.
Distance & Access
Location and accessibility preferences.
Availability
Medication/product availability and alternatives.
Fulfillment
Collection, delivery and service capabilities.
Routing Rules
Patient selection has priority when valid and operationally possible
Suggestions must be explainable and non-discriminatory
Do not disclose patient prescription details to candidate pharmacies before permitted routing
Handle closed/unavailable pharmacy with user-visible alternatives
Record why/when/to whom prescription was routed
Allow permitted rerouting with audit and notification
APIs & Examples
httpCopy
# Illustrative pharmacy discovery
GET /v1/pharmacies?lat=49.61&lng=6.13&service=eprescription&delivery=true
Authorization: Bearer <token>
# Illustrative route operation
POST /v1/prescriptions/{id}/route
{ "pharmacyId":"pharm_123" }Illustrative route names; final API contracts remain versioned implementation work.
Best Practices
Always expose clear patient choice
Treat ranking as assistive, not opaque clinical decision-making
Use authoritative pharmacy directory identifiers
Display availability freshness and connector status
Use explicit reroute/cancel semantics
Audit routing without leaking unnecessary clinical detail
Developer Integration Surface
| Surface | Operation / resource | Use | Status |
|---|---|---|---|
| Directory API | search pharmacies / capabilities | Discovery | Versioned when frozen |
| Routing API | route / reroute / cancel route | Prescription handoff | Versioned when frozen |
| Availability API | product availability per pharmacy | Optional decision input | Connector |
| Events | pharmacy.accepted / route.failed | Async tracking | Evolving |
Next Steps
Connect pharmacy directory
Define patient-visible filters
Implement transparent selection/routing
Test unavailable/failed/reroute cases
Add route audit and status events