PHARMACY NETWORK CONNECTORS
ePrescription & Prescription Exchange
2 of 7Connect pharmacy systems, ePrescription networks, medication catalogues and fulfillment workflows across the medication pathway.
MedicationRequestSigned SnapshotFHIRNational ePrescriptionCancellationStatus SyncDispense
Standards-Based
Use FHIR MedicationRequest plus required national profiles.
Secure Exchange
Preserve signed/validated prescription snapshots.
Real-Time Synchronization
Synchronize prescribed, routed and dispensed states.
Multi-Country Support
Use country adapters for Luxembourg, France and future EU exchange.
Prescription Exchange Flow
1
Prescribe
Doctor creates, clinically validates and signs prescription
2
Exchange
National ePrescription infrastructure or direct pharmacy connector
3
Discover
Pharmacy retrieves/receives prescription
4
Accept
Validate prescription and availability
5
Dispense
Partial/full dispense recorded
6
Synchronize
Update patient record and source systems
Supported National ePrescription Systems
| Market | System / route | Capability | Status |
|---|---|---|---|
| Luxembourg | eSanté/CNS ecosystem | National ePrescription integration | Country adapter / subject to official onboarding |
| France | Prescription électronique / national services | National electronic prescription workflow | Country adapter / subject to official onboarding |
| EU | MyHealth@EU ePrescription/eDispensation | Cross-border exchange | Future / staged |
Prescription Data Model
| Concept | FHIR / Mediloop representation | Rule |
|---|---|---|
| Prescription | MedicationRequest | Immutable signed clinical snapshot after signing |
| Medication | Medication + terminology coding | Preserve original code + normalized mapping |
| Route | Pharmacy routing metadata | Patient choice / explicit routing |
| Dispense | MedicationDispense | Partial/full/corrected dispensing |
| Status | Workflow state + FHIR status | Map source statuses without losing originals |
Status & Synchronization
Use guarded prescription lifecycle transitions
Track source/national/pharmacy correlation identifiers
Use events for asynchronous acceptance/dispense updates
Reconcile missed callbacks and stale statuses
Prevent duplicate dispense updates with idempotency
Cancellation & Updates
Signed prescription corrections create controlled new version/amendment rather than silent edit
Propagate cancellation only when clinically and legally permitted
Preserve previous snapshot and reason
Handle already-dispensed items explicitly
Notify routed pharmacy and patient-facing workflow
Examples
fhirCopy
{
"resourceType":"MedicationRequest",
"status":"active",
"intent":"order",
"subject":{"reference":"Patient/123"},
"medicationReference":{"reference":"Medication/med-456"}
}Simplified FHIR example. National profiles, identifiers, signatures and required extensions must follow the applicable official specification.
Best Practices
Keep signed clinical snapshot immutable
Preserve national/external prescription identifiers
Use explicit routing and patient choice
Do not invent dispense information if pharmacy callback is delayed
Store source + normalized terminology
Test cancellation/partial dispense/retry scenarios
Developer Integration Surface
| Surface | Operation / resource | Use | Status |
|---|---|---|---|
| FHIR | MedicationRequest | Prescription semantics | FHIR |
| National adapter | publish / retrieve / cancel / status | Country ePrescription exchange | Country-specific |
| Pharmacy events | accepted / preparing / dispensed | Async synchronization | Connector |
| REST API | route / status / pharmacy handoff | Mediloop application workflow | Versioned when frozen |
Next Steps
Implement signed prescription output
Configure national/pharmacy adapter
Map statuses and identifiers
Test cancellation and duplicate events
Connect MedicationDispense reconciliation