eHealth Infrastructure
7.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 7.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: task

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

Raw OpenAPI-Swagger Definition file | Download

  • Implementation Guide Version: 7.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 03:12:12+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-RSUPCSearches_include_revincludeOperations
Binaryhttp://hl7.org/fhir/StructureDefinition/Binaryyy*ClinicalImpression:action, ClinicalImpression:assessor, ClinicalImpression:carePlan, ClinicalImpression:episodeOfCare, ClinicalImpression:finding-ref, ClinicalImpression:investigation, ClinicalImpression:patient, ClinicalImpression:previous, ClinicalImpression:problem, ClinicalImpression:subject, Task:based-on, Task:carePlan, Task:episodeOfCare, Task:focus, Task:owner, Task:part-of, Task:patient, Task:requester, Task:responsible, Task:subject
ClinicalImpressionhttp://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-clinicalimpressionyyyyy_content, _has, _id, _language, _lastUpdated, _profile, _security, _tag, _text, action, assessor, carePlan, date, decision, episodeOfCare, finding-code, finding-ref, identifier, investigation, patient, previous, problem, status, subjectClinicalImpression:previousClinicalImpression:action, ClinicalImpression:assessor, ClinicalImpression:carePlan, ClinicalImpression:episodeOfCare, ClinicalImpression:finding-ref, ClinicalImpression:investigation, ClinicalImpression:patient, ClinicalImpression:previous, ClinicalImpression:problem, ClinicalImpression:subject, Task:based-on, Task:carePlan, Task:episodeOfCare, Task:focus, Task:owner, Task:part-of, Task:patient, Task:requester, Task:responsible, Task:subject$validate, $set-measurement-validity
OperationDefinitionhttp://hl7.org/fhir/StructureDefinition/OperationDefinitiony*ClinicalImpression:action, ClinicalImpression:assessor, ClinicalImpression:carePlan, ClinicalImpression:episodeOfCare, ClinicalImpression:finding-ref, ClinicalImpression:investigation, ClinicalImpression:patient, ClinicalImpression:previous, ClinicalImpression:problem, ClinicalImpression:subject, Task:based-on, Task:carePlan, Task:episodeOfCare, Task:focus, Task:owner, Task:part-of, Task:patient, Task:requester, Task:responsible, Task:subject
Taskhttp://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-taskyyyyy_content, _has, _id, _language, _lastUpdated, _profile, _security, _tag, _text, authored-on, based-on, business-status, carePlan, category, code, episodeOfCare, focus, group-identifier, identifier, intent, modified, owner, part-of, patient, performer, period, priority, requester, resolvedTimingEnd, resolvedTimingServiceRequestVersionId, resolvedTimingStart, resolvedTimingType, responsible, restriction-category, status, subjectTask:based-on, Task:focus, Task:part-ofClinicalImpression:action, ClinicalImpression:assessor, ClinicalImpression:carePlan, ClinicalImpression:episodeOfCare, ClinicalImpression:finding-ref, ClinicalImpression:investigation, ClinicalImpression:patient, ClinicalImpression:previous, ClinicalImpression:problem, ClinicalImpression:subject, Task:based-on, Task:carePlan, Task:episodeOfCare, Task:focus, Task:owner, Task:part-of, Task:patient, Task:requester, Task:responsible, Task:subject$validate

Base System Profile
Binary
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports vread, read.

Base System Profile
ehealth-clinicalimpression
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports search-type, vread, read, patch, 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

SHALLactionreference

Action taken as part of assessment procedure

SHALLassessorreference

The clinician performing the assessment

SHALLcarePlanreference

CarePlan

SHALLdatedate

When the assessment was documented

SHALLdecisiontoken

Decision

SHALLepisodeOfCarereference

Encounter or Episode created from

SHALLfinding-codetoken

What was found

SHALLfinding-refreference

What was found

SHALLidentifiertoken

Business identifier

SHALLinvestigationreference

Record of a specific investigation

SHALLpatientreference

Patient or group assessed

SHALLpreviousreference

Reference to last assessment

SHALLproblemreference

Relevant impressions of patient state

SHALLstatustoken

draft | completed | entered-in-error

SHALLsubjectreference

Patient or group assessed

 
Extended Operations
ConformanceOperationDocumentation
SHALL$validate
SHALL$set-measurement-validity

This operation is used to invalidate or retract an invalidation of a Measurement.

Input

The input parameter is a ClinicalImpression resource with the following values:

  • status - The status of the ClinicalImpression must be completed.
  • investigation.item - Versioned reference to the Measurement that is to be invalidated or retracted.
  • investigation.item - Unversioned reference to the Measurement that is to be invalidated or retracted.
  • subject - Reference to the Patient .
  • episodeOfCare - Reference to the EpisodeOfCare that the Measurement is part of.
  • code - Should use MeasurementAssessment from http://ehealth.sundhed.dk/cs/clinicalimpression-codes.
  • finding.code - The finding code must be measurement-invalidated or measurement-invalidation-retracted.
  • decision - The decision code is required if finding.code is measurement-invalidated. The decision code must be invalidated-fulfills or invalidated-is-not-fulfillment.

Output

The operation returns the persisted ClinicalImpression:

  • clinicalImpression - The persisted ClinicalImpression resource with updated assessor values.

Operation side effects

  • The operation will update the status of the Measurement that is being invalidated or has the invalidation retracted to entered-in-error or completed respectively.
  • The operation will update the status to entered-in-error for any previous invalidation or invalidation retraction ClinicalImpression for the referenced Measurement, indicating that the previous ClinicalImpression is no longer used to represent the validity of the Measurement. The operation performs a search for any existing ClinicalImpression in the measurement validity cycle, and does not rely on/update the previous field on the input ClinicalImpression. If the input ClinicalImpression is for invalidation retraction, there must exist a ClinicalImpression invalidating the Measurement.
  • The operation will add an additional investigation with the code item-modified, referencing the Measurement version after the patch has been applied.
  • The operation will set assessor values (assessor, assessorOrganization and assessorOther). If the user is of type PRACTITIONER, assessor and assessorOrganization will be set. If the user is of type PATIENT, assessorOther will be set`.
Base System Profile
OperationDefinition
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports read.

Base System Profile
ehealth-task
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports search-type, vread, read, patch, 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

SHALLauthored-ondate

Search by creation date

SHALLbased-onreference

Search by requests this task is based on

SHALLbusiness-statustoken

Search by business status

SHALLcarePlanreference

Search by CarePlan

SHALLcategorytoken

Search by category

SHALLcodetoken

Search by task code

SHALLepisodeOfCarereference

Search by encounter or episode

SHALLfocusreference

Search by task focus

SHALLgroup-identifiertoken

Search by group identifier

SHALLidentifiertoken

Search for a task instance by its business identifier

SHALLintenttoken

Search by task intent

SHALLmodifieddate

Search by last modification date

SHALLownerreference

Search by task owner

SHALLpart-ofreference

Search by task this task is part of

SHALLpatientreference

Search by patient

SHALLperformertoken

Search by recommended type of performer (e.g., Requester, Performer, Scheduler).

SHALLperioddate

Search by period Task is/was underway

SHALLprioritytoken

Search by task priority

SHALLrequesterreference

Search by task requester

SHALLresolvedTimingEnddate

Resolved Timing end

SHALLresolvedTimingServiceRequestVersionIdtoken

Resolved Timing serviceRequestVersionID

SHALLresolvedTimingStartdate

Resolved Timing start

SHALLresolvedTimingTypetoken

Resolved Timing type

SHALLresponsiblereference

Search by responsible

SHALLrestriction-categorytoken

Search by restriction category

SHALLstatustoken

Search by task status

SHALLsubjectreference

Search by subject

 
Extended Operations
ConformanceOperationDocumentation
SHALL$validate