National source record
Original product, substance, identifiers and source attributes.
MEDIMAPPER API
Bring medicine matching into your systems.
Bring national source records, shared substance identities and normalised product attributes into your own systems. Match results stay transparent, so internal search, master-data and research workflows can use the same evidence.
LOCAL RECORDS AND COMPARABLE LAYERS
Use the source data and the relationship between records.
The API preserves each national record, connects the active substance to a shared identity and calculates product relationships without collapsing products into one global item.
- National product records and local identifiers
- Shared active-substance identities and reference identifiers
- Original and normalised strength and pharmaceutical form
- Pack configurations and GTINs where available
- Manufacturer, supplier and brand information
- Prices and reimbursement context where available
- Source references and processing information
- Substance, presentation, pack and commercial-item match results
ONE SUBSCRIPTION, THREE ACCESS CHANNELS
Use the same licensed data through the interface, API or MCP.
Regional permissions, data-licensing terms and applicable fair-use limits apply across every access channel.
Platform
Search, compare and analyse medicine records in the Medimapper interface.
API
Bring national records, shared identities, normalised attributes and match results into your own systems.
MCP
Allow approved AI assistants and agents to query licensed Medimapper data through a controlled access layer.
CONCEPTUAL DATA MODEL
Keep local evidence and comparable values together.
Shared substance identity
An international identity connected through maintained evidence.
Normalised presentation
Comparable strength and pharmaceutical form alongside the original values.
Pack record
Pack size, configuration and commercial identifiers where available.
Comparison result
A dynamic relationship stating which level the available attributes support.
CONCEPTUAL JSON
Source and normalised values stay together.
This illustrative fragment explains the data model only. It is not an endpoint contract or production payload.
Conceptual example. Field names may differ in the production API.
{
"sourceRecord": {
"country": "FR",
"productName": "Doliprane 0.5 g",
"strength": "0.5 g",
"form": "comprimé",
"pack": "16 comprimés"
},
"normalised": {
"substance": "Paracetamol",
"strength": "500 mg",
"form": "tablet",
"packSize": 16
},
"comparison": {
"substanceMatch": true,
"presentationMatch": true,
"packMatch": false
}
}COMMON API WORKFLOWS
Use Medimapper as an international product-comparison layer.
Cross-market product search
Start with a local product, code or substance and retrieve related records in selected countries.
Master-data enrichment
Connect internal records to shared substance identities, normalised attributes and international reference identifiers.
Portfolio and market analysis
Compare national product presence, manufacturers, strengths, forms and packs.
Evidence-aware reporting
Preserve source fields and show which attributes support each comparison result.
Controlled AI access
Allow authorised assistants and agents to query licensed data through the Medimapper MCP layer.
FROM EVALUATION TO PRODUCTION ACCESS
Validate coverage and semantics before integrating.
01Define the workflow
Tell us which products, regions, data layers and internal decisions the integration must support.
02Review coverage
Confirm field availability, source depth, update information and material limitations for the required markets.
03Validate responses
Review real sample records, match semantics and the intended handling of source and normalised values.
04Agree access and usage
Confirm regions, authentication, fair-use limits, permitted use, support and data-licensing terms.
05Integrate with documentation
Implement against the production API documentation and versioned response contract.
WHAT TECHNICAL TEAMS NEED TO REVIEW
Make procurement and implementation questions visible early.
| Information | Availability |
|---|---|
| API documentation | Available on request |
| Authentication and access model | Available on request |
| Versioning and change policy | Available on request |
| Pagination and rate limits | Available on request |
| Data refresh and update commitments | Available on request |
| Permitted use and redistribution terms | Available on request |
| Security and privacy brief | Available on request |
| Onboarding and support model | Available on request |
DATA RESPONSIBILITY
An API response is evidence, not authorisation.
Your organisation remains responsible for validating results for the intended use and for every clinical, regulatory, quality, legal and commercial decision made with the data.
START WITH YOUR PRODUCTS