Getting Started
Overview
The Nompd API provides Norwegian healthcare treatment group and reimbursement data in a simplified REST format. Data is sourced from the national FHIR APIs and kept up to date via nightly synchronization.
Prerequisites
The API has two authentication options (see Authentication):
- API key — for the
/api/v1/*endpoints. Contact the Nompd team to request a key. - HelseID (DPoP) — for the
/api/v2/*endpoints. You need access to HelseID and a client with thenhn:nompd/apiscope.
This quickstart uses the v1 endpoints and an API key.
Your First Request
v1 requests require an X-API-KEY header:
curl https://nompd-api.example.com/api/v1/treatment-group \
-H "X-API-KEY: your-api-key"
Response
{
"currentVersion": 5,
"entries": [
{
"data": {
"id": "4077eb19-b094-4712-89b1-c3b5a021ef8d",
"name": "Natalizumab",
"description": "Rangering av natalizumab s.c og i.v formulering",
"diseaseGroup": "MS",
"jurisdictions": [
{
"system": "urn:oid:2.16.578.1.12.4.1.102",
"code": "100022",
"display": "Helse Nord RHF"
}
],
"validityPeriod": {
"start": "2025-05-01",
"end": "2027-04-30"
},
"reviewDate": "2025-04-10",
"indications": [
{
"coding": [
{
"system": "urn:oid:2.16.578.1.12.4.1.1.7110",
"code": "G35",
"display": "Multippel sklerose"
}
],
"text": "Multiple sclerosis"
}
],
"treatmentAlternatives": [
{
"rank": 1,
"treatmentId": "6d3c0e9f-dd3f-49e6-8c6c-c3ef1ccdfa1a",
"name": "Natalizumab (Tysabri)",
"description": null,
"products": [
{
"reference": null,
"type": "FEST/LegemiddelPakning",
"identifier": {
"system": "FEST/Varenummer",
"value": "166028"
},
"display": null
}
]
}
]
},
"version": 5,
"lastChanged": "2025-04-10T08:30:00Z",
"isDeleted": false
}
]
}
Key Concepts
currentVersion— The server's current data version. Store this value to use with diff queries later.entries— Array of data items, each wrapped with per-document metadata.version— The version when this specific item last changed. Useful for tracking individual updates.lastChanged— Timestamp of last modification.isDeleted— Alwaysfalsewhen fetching withoutsince-version. Relevant when using diff queries (see Versioning and Diff).
Available Endpoints
| Method | Endpoint | Description |
|---|---|---|
GET |
/api/v1/treatment-group |
Treatment groups (API key). Supports ?since-version=N for incremental updates and optional filters. |
GET |
/api/v1/treatment-group/{id} |
Treatment group (API key) |
GET |
/api/v1/reimbursement-group |
Reimbursement authorizations (API key). Supports ?since-version=N for incremental updates and optional filters. |
GET |
/api/v1/reimbursement-group/{id} |
Reimbursement group (API key) |
GET |
/api/v2/treatment-group |
Treatment groups (HelseID DPoP). Same data and queries as v1. |
GET |
/api/v2/treatment-group/{id} |
Treatment group (HelseID DPoP) |
GET |
/api/v2/reimbursement-group |
Reimbursement authorizations (HelseID DPoP). Same data and queries as v1. |
GET |
/api/v2/reimbursement-group/{id} |
Reimbursement group (HelseID DPoP) |
Next Steps
- API Reference — Full endpoint documentation
- Versioning and Diff — How to fetch only changes
- Data Models — Field descriptions and code systems
- Authentication — API keys (v1) and HelseID with DPoP (v2)