eHealth Infrastructure
8.0.0 - release Denmark flag

eHealth Infrastructure, published by Den telemedicinske infrastruktur (eHealth Infrastructure). This guide is not an authorized publication; it is the continuous build for version 8.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/fut-infrastructure/implementation-guide/ and changes regularly. See the Directory of published versions

CapabilityStatement: device

Official URL: http://ehealth.sundhed.dk/fhir/CapabilityStatement/device Version: 8.0.0
Active as of 2025-12-09 Computable Name: device

Raw OpenAPI-Swagger Definition file | Download

  • Implementation Guide Version: 8.0.0
  • FHIR Version: 4.0.1
  • Supported Formats: application/fhir+xml, xml, application/fhir+json, json, application/x-turtle, ttl, html/json, html/xml, html/turtle
  • Published on: 2025-12-09 02:07:22+0000
  • Published by: Den telemedicinske infrastruktur (eHealth Infrastructure)

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

This CapabilityStatement instantiates the CapabilityStatement http://hl7.org/fhir/uv/bulkdata/CapabilityStatement/bulk-data

FHIR RESTful Capabilities

Mode: server

Summary of System-wide Operations
ConformanceOperationDocumentation
SHALL$reindex
SHALL$migrate

Data migration

SHALL$export-poll-status

Operation for polling the status of a previously initiated FHIR Bulk Data System Level Export. A complete URL including the '_jobId' is returned in the 'Content-Location' response header when initiating the export. A 'GET' request to the polling location will return '202 Accepted' with a response header 'X-Progress' containing a status message for the progress of the export job. When the job has finished, the polling location will return '200 OK', and the contents of the body will be a JSON object providing metadata and links to the generated bulk data files. A 'DELETE' request can be used to cancel the export. If the export has already finished, the delete will return '404 Not Found', else the export job will be cancelled and a '202 Accepted' is returned with an operation outcome response.

Parameters

  • _jobId: the job ID for the Bulk Export job which was returned in the 'Content-Location' header when initiating the export
SHALL$export

FHIR Operation to initiate an export of data from a FHIR server. The type of resources returned can be restricted using the '_type' parameter, and the '_since' parameter can be used to restrict resources to be only included if changed since the supplied time. The FHIR server support invocation of this operation using the FHIR Asynchronous Request Pattern.

Initiation of export

The initiation of an export must specify the request header 'Prefer: respond-async', and will return '202 Accepted' with a polling location in the response header 'Content-Location'. The polling location is for the endpoint '$export-poll-status' and has the export job ID as parameter '_jobId'.

Parameters

  • _outputFormat: Optional parameter to specify the output format of the exported files. Default is 'application/fhir+ndjson'
  • _type: Optional parameter to specify a comma separated list of resource types to be included in the export. If not provided, all resource types will be included.
  • _since: Optional parameter to specify a time. Only resources that have been created or modified after this time will be included in the export (i.e., if Resource.meta.lastUpdated is later than the supplied _since time).
  • _typePostFetchFilterUrl: Optional parameter to apply filtering of resources for export. It is a string of comma-delimited FHIR REST search queries in the format [resourceType]?[parameters]. The filter will be applied on resources after being fetched from the database.
  • _exportId: Optional parameter to specify a client provided identifier for the export. Resulting exported files (Binary) will be labeled with the identifer in meta extension 'https://hapifhir.org/NamingSystem/bulk-export-identifier'

Polling status of export

Subsequent GET requests to the polling location will return '202 Accepted' with a response header 'X-Progress' containing a status message for the progress of the export job. When the job has finished, the polling location will return '200 OK', and the contents of the body will be a JSON object providing metadata and links to the generated bulk export data files.

Retrieving exported files

The JSON object returned when the export job is complete will contain a list of files (Binary resources) available for download. Each file can be retrieved using a standard HTTP GET request to the provided URL. The security context of the Binary resources resulting from the export is the user that initiated the export. The files can therefore only be retrieved by the same user.

Retention of exported files

The exported files are retained for a limited time after which they are deleted. The retention time is a server configuration with default 2 hours.

SHALL$meta
SHALL$get-resource-counts

Provides the number of resources currently stored on the server, broken down by resource type

SHALL$expunge

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

  • The relevant profiles (if any)
  • The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
  • The required, recommended, and some optional search parameters (if any).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)
Resource TypeProfileRV-RSUCSearches_include_revincludeOperations
Binaryhttp://hl7.org/fhir/StructureDefinition/Binaryyy*Device:location, Device:organization, Device:patient, DeviceMetric:parent, DeviceMetric:source, DeviceUseStatement:context, DeviceUseStatement:device, DeviceUseStatement:patient, DeviceUseStatement:subject
Devicehttp://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-deviceyyyyy_content, _has, _id, _language, _lastUpdated, _profile, _security, _tag, _text, device-name, identifier, location, manufacturer, model, organization, patient, status, type, udi-carrier, udi-di, urlDevice:location, Device:organization, Device:patient, DeviceMetric:parent, DeviceMetric:source, DeviceUseStatement:context, DeviceUseStatement:device, DeviceUseStatement:patient, DeviceUseStatement:subject$validate
DeviceMetrichttp://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-devicemetricyyyyy_content, _has, _id, _language, _lastUpdated, _profile, _security, _tag, _text, category, identifier, parent, qualityCategory, source, typeDeviceMetric:sourceDevice:location, Device:organization, Device:patient, DeviceMetric:parent, DeviceMetric:source, DeviceUseStatement:context, DeviceUseStatement:device, DeviceUseStatement:patient, DeviceUseStatement:subject
DeviceUseStatementhttp://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-deviceusestatementyyyyy_content, _has, _id, _language, _lastUpdated, _profile, _security, _tag, _text, context, device, identifier, patient, status, subject, timingDeviceUseStatement:deviceDevice:location, Device:organization, Device:patient, DeviceMetric:parent, DeviceMetric:source, DeviceUseStatement:context, DeviceUseStatement:device, DeviceUseStatement:patient, DeviceUseStatement:subject$validate
OperationDefinitionhttp://hl7.org/fhir/StructureDefinition/OperationDefinitiony*Device:location, Device:organization, Device:patient, DeviceMetric:parent, DeviceMetric:source, DeviceUseStatement:context, DeviceUseStatement:device, DeviceUseStatement:patient, DeviceUseStatement:subject

Base System Profile
Binary
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports vread, read.

Base System Profile
ehealth-device
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports update, search-type, vread, read, create.

Search Parameters
ConformanceParameterTypeDocumentation
SHALL_contentstring

Search the contents of the resource's data using a fulltext search

SHALL_hasstring

Return resources linked to by the given target

SHALL_idtoken

The ID of the resource

SHALL_languagestring

The language of the resource

SHALL_lastUpdateddate

Only return resources which were last updated as specified by the given range

SHALL_profileuri

Search for resources which have the given profile

SHALL_securitytoken

Search for resources which have the given security labels

SHALL_tagtoken

Search for resources which have the given tag

SHALL_textstring

Search the contents of the resource's narrative using a fulltext search

SHALLdevice-namestring

A server defined search that may match any of the string fields in the Device.udi.name or Device.type.coding.display or Device.type.text

SHALLidentifiertoken

Instance id from manufacturer, owner, and others

SHALLlocationreference

A location, where the resource is found

SHALLmanufacturerstring

The manufacturer of the device

SHALLmodelstring

The model of the device

SHALLorganizationreference

The organization responsible for the device

SHALLpatientreference

Patient information, if the resource is affixed to a person

SHALLstatustoken

active | inactive | entered-in-error | unknown

SHALLtypetoken

The type of the device

SHALLudi-carrierstring

UDI Barcode (RFID or other technology) string either in HRF format or AIDC format converted to base64 string.

SHALLudi-distring

The udi Device Identifier (DI)

SHALLurluri

Network address to contact device

 
Extended Operations
ConformanceOperationDocumentation
SHALL$validate
Base System Profile
ehealth-devicemetric
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports update, search-type, vread, read, create.

Search Parameters
ConformanceParameterTypeDocumentation
SHALL_contentstring

Search the contents of the resource's data using a fulltext search

SHALL_hasstring

Return resources linked to by the given target

SHALL_idtoken

The ID of the resource

SHALL_languagestring

The language of the resource

SHALL_lastUpdateddate

Only return resources which were last updated as specified by the given range

SHALL_profileuri

Search for resources which have the given profile

SHALL_securitytoken

Search for resources which have the given security labels

SHALL_tagtoken

Search for resources which have the given tag

SHALL_textstring

Search the contents of the resource's narrative using a fulltext search

SHALLcategorytoken

The category of the metric

SHALLidentifiertoken

The identifier of the metric

SHALLparentreference

The parent DeviceMetric resource

SHALLqualityCategorytoken

The device metric quality

SHALLsourcereference

The device resource

SHALLtypetoken

The component type

 
Base System Profile
ehealth-deviceusestatement
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports update, search-type, vread, read, create.

Search Parameters
ConformanceParameterTypeDocumentation
SHALL_contentstring

Search the contents of the resource's data using a fulltext search

SHALL_hasstring

Return resources linked to by the given target

SHALL_idtoken

The ID of the resource

SHALL_languagestring

The language of the resource

SHALL_lastUpdateddate

Only return resources which were last updated as specified by the given range

SHALL_profileuri

Search for resources which have the given profile

SHALL_securitytoken

Search for resources which have the given security labels

SHALL_tagtoken

Search for resources which have the given tag

SHALL_textstring

Search the contents of the resource's narrative using a fulltext search

SHALLcontextreference

Search by context

SHALLdevicereference

Search by device

SHALLidentifiertoken

Search by identifier

SHALLpatientreference

Search by subject - a patient

SHALLstatustoken

active | completed | entered-in-error +

SHALLsubjectreference

Search by subject

SHALLtimingdate

Period device was used

 
Extended Operations
ConformanceOperationDocumentation
SHALL$validate
Base System Profile
OperationDefinition
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports read.