DIPS FHIR (OpenDIPS)
Category: EHR & Practice Mgmt
Node id: dips-fhir
Standards: GDPR, Norway-PDA, HelseID
DIPS AS (NO) hospital EHR via OpenDIPS partner program. Tier 2 — partner-program access. Dominant Norwegian hospital EHR (~73% share).
What it does
- FHIR R4 search and read
- Patient lookup via Norwegian fødselsnummer
- Encounter history retrieval
- Hospital-scoped routing
Use cases
- Aggregate Norwegian inpatient encounters into a national EHDS pipeline
- Pull DIPS data for population analytics
Runtime
- Performance tier:
variable
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
resource_id | text | No | |
patient_id | text | No | |
fnr | text | No | Norwegian fødselsnummer |
family_name | text | No | |
given_name | text | No |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | |
metadata | json | No | |
success | boolean | No |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| DIPS Base URL | dips_base_url | string | Yes | |||
| Operation | operation | enum | No | search | search, read, patient_search, encounter_history | |
| Resource Type | resource_type | string | No | Patient |
Auth
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Client ID | client_id | secret | Yes | |||
| Client Secret | client_secret | secret | Yes |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Hospital ID | hospital_id | string | No | X-DIPS-HospitalId routing header | ||
| FNR System OID | fnr_system | string | No | urn:oid:2.16.578.1.12.4.1.4.1 | ||
| Search Parameters | search_params | json | No |
Errors
| Code | Description |
|---|---|
DIPS_AUTH_FAILED | OAuth2 token request failed |
DIPS_REQUEST_FAILED | HTTP request to DIPS failed |
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..