PHARMACY NETWORK CONNECTORS
Monitoring, Reconciliation, Audit / APIs & SDK / Production Readiness
7 of 7Connect pharmacy systems, ePrescription networks, medication catalogues and fulfillment workflows across the medication pathway.
MonitoringConnector HealthReconciliationAuditAPIs & SDKCertificationProduction
End-to-End Visibility
Monitor prescription→dispense→fulfillment across the network.
Data Integrity
Reconcile prescriptions, stock and dispense evidence.
Audit & Compliance
Maintain immutable/correlated audit history.
Production Ready
Use sandbox, certification and go-live checklists.
Operational Overview
Connected Pharmacies
Active pharmacy/group connector count and health.
Prescription Volume
Received/routed/accepted transactions.
Synchronization Rate
Successful status/dispense reconciliation.
Response Time
PMS/network dependency latency.
Connector Health
| Dependency | Health signals | Action |
|---|---|---|
| PMS | Availability, last sync, errors, latency | Alert + reconcile stale state |
| ePrescription network | Auth/cert/submit/retrieve health | National support runbook |
| Catalogue/stock | Freshness and sync lag | Disable stale availability when threshold exceeded |
| Delivery provider | Webhook/status latency | Reconcile active shipments |
Reconciliation
1
Prescription
Expected routed clinical order
2
PMS State
Accepted/prepared/dispensed evidence
3
Inventory
Reservation and stock movement
4
Compare
Identifiers, quantities, product and status
5
Exception
Missing/conflicting/late data
6
Resolve
Automated/manual resolution with audit
Audit Trail
Correlation ID across prescription, route, reservation, dispense and fulfillment
Actor/system and tenant for each Mediloop action
Original source payload/reference retained according to policy
Mapping/product-resolution version
Patient choice/routing decision evidence
Manual exception resolution and reason
APIs & SDK Examples
httpCopy
# Illustrative pharmacy status
GET /v1/pharmacies/{id}/status
Authorization: Bearer <token>
# Standard FHIR dispense query
GET /fhir/MedicationDispense?subject=Patient/123&_sort=-whenHandedOverPharmacy REST and SDK operation names are illustrative until frozen. FHIR behavior depends on the published Mediloop FHIR implementation.
Testing & Certification
Sandbox with synthetic prescriptions and pharmacies
PMS connector validation
National ePrescription conformance/approval where required
End-to-end partial/substitution/cancel scenarios
Performance/load and webhook retry testing
Certificate/credential lifecycle tests
Production Readiness
Required connectors tested and approved
Monitoring/alerting/reconciliation configured
Identity/access controls reviewed
Audit and retention validated
Go-live/rollback plan approved
Support contacts/runbooks configured
Best Practices
Monitor connector freshness, not just HTTP uptime
Reconcile prescriptions, stock and dispenses regularly
Use idempotency and correlation IDs
Keep patient choice and clinical decisions auditable
Avoid letting stale stock drive routing
Resolve exceptions promptly with source-of-truth evidence
Common Use Cases
Operational pharmacy-network dashboard
Automated prescription/dispense reconciliation
Exception management
Regulatory audit evidence
Multi-pharmacy oversight
Production connector support
Developer Integration Surface
| Surface | Operation / resource | Use | Status |
|---|---|---|---|
| Pharmacy API | directory / route / stock / status | App-facing workflows | Versioned when frozen |
| FHIR | MedicationRequest / MedicationDispense | Clinical interoperability | FHIR |
| SDK | Typed pharmacy operations | Developer productivity | Published versions only |
| Webhooks/events | status / dispense / delivery / failures | Async integration | Evolving |
| Operations API | health / reconciliation / audit | Production operations | Planned/versioned |
Next Steps
Complete end-to-end sandbox tests
Validate national/PMS conformance
Enable health and reconciliation alerts
Run go-live checklist
Launch gradually and monitor exceptions