PHARMACY NETWORK CONNECTORS
Pharmacy Directory, Medication Catalogue & Product Resolution
4 of 7Connect pharmacy systems, ePrescription networks, medication catalogues and fulfillment workflows across the medication pathway.
Pharmacy DirectoryMedication CatalogueATCSNOMED CTGTIN / SKUGenericsMSIS
Multiple Data Sources
Connect national, pharmacy, wholesaler and PMS sources.
Standardized With MSIS
Normalize medication terminology through MSIS.
Clinical ↔ Commercial Mapping
Link clinical concepts to presentations, packs and product identifiers.
Up-to-Date & Reliable
Version and reconcile source data for safe dispensing.
Catalogue Ecosystem
1
National Medication Sources
Regulatory/national medication data
2
Pharmacy Directories
Pharmacies, groups and services
3
Wholesaler Catalogues
Products, packs, commercial identifiers
4
PMS Catalogues
Local products and stock keys
5
Connector Layer
Sync, dedupe and source provenance
6
MSIS
Clinical medication semantics and equivalence
Directory & Catalogues
| Source | Data | Authority |
|---|---|---|
| Pharmacy directory | Pharmacy identity, location, capabilities | Directory/organization source |
| Clinical medication terminology | Substance/medication concept | Clinical terminology source via MSIS |
| Commercial product catalogue | Presentation, pack, GTIN/SKU, market status | National/wholesaler/PMS source |
| PMS catalogue | Local product ID and dispense keys | Local pharmacy system |
Product Resolution
1
Clinical Medication
Prescribed medication concept
2
Normalize
ATC/SNOMED/national code mappings
3
Resolve Products
Strength, form, pack and market
4
Evaluate Equivalence
Generic/biosimilar/substitution relationships under rules
5
Concrete Product
GTIN/SKU/local PMS item
Data Mapping & Standards
| Layer | Examples | Purpose |
|---|---|---|
| Clinical | SNOMED CT / ATC / national clinical codes | Meaning of medication |
| Product | GTIN / national pack codes / SKU | Concrete commercial product |
| Local | PMS product ID | Pharmacy operational reference |
| FHIR | Medication / MedicationRequest | Interoperable representation |
APIs & Examples
httpCopy
# Illustrative product resolution
POST /v1/pharmacy/catalogue/resolve
Authorization: Bearer <token>
{
"medicationCode":{"system":"http://www.whocc.no/atc","code":"A10BA02"},
"market":"LU",
"pharmacyId":"pharm_123"
}Resolution must preserve original codes and return mapping/provenance/confidence. Commercial product sources remain market/provider-specific.
Best Practices
Do not use a commercial SKU as the clinical medication identity
Preserve all original codes and data-source versions
Record mapping/equivalence provenance
Treat substitution as a governed clinical/pharmacy rule, not simple string matching
Reconcile discontinued/replaced packs
Monitor catalogue freshness
Developer Integration Surface
| Surface | Operation / resource | Use | Status |
|---|---|---|---|
| Catalogue API | search / resolve product | Medication→product workflow | Planned/versioned |
| FHIR | Medication | Clinical medication representation | FHIR |
| MSIS | normalize / map terminology | Clinical semantic equivalence | Semantic service |
| PMS/wholesaler adapter | catalogue sync | Commercial/local product data | Provider-specific |
Next Steps
Inventory medication/product sources
Define clinical-vs-commercial identifiers
Build mappings through MSIS
Connect market/PMS catalogues
Validate generics/substitution/versioning