eHealth Infrastructure
3.4.1 - 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 3.4.1 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

Resource Profile: ehealth-goal

Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-goal Version: 3.4.1
Active as of 2025-03-06 Computable Name: ehealth-goal

Introduction

Describes the intended objective(s) for a patient, group or organization care, for example, weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc.

Scope and Usage

In scope of the eHealth infrastructure Goals are used together with reference ranges to configure triaging based on relative values.

This use is indicated by setting the code reference-value in Goal.description. This is currently the only type of Goal used in the infrastructure, but other types may be added in the future.

A Goal must have a startDate and optionally a target.dueDate or dueDuration to specify during which period the Goal applies.

Goal.addresses must reference exactly one serviceRequest containing the reference ranges that the Goal supports.

Goal.target.measure must contain an observation code indicating which type of observation the Goal is intended for.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Goal 0..* Goal Describes the intended objective(s) for a patient, group or organization
dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources
dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
dom-5: If a resource is contained in another resource, it SHALL NOT have a security label
dom-6: A resource should have narrative for robust management
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
ele-1: All FHIR elements must have a @value or children
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
... lifecycleStatus ?!Σ 1..1 code proposed | planned | accepted | active | on-hold | completed | cancelled | entered-in-error | rejected
Binding: GoalLifecycleStatus (required): Codes that reflect the current state of a goal and whether the goal is still being targeted.


ele-1: All FHIR elements must have a @value or children
... subject Σ 1..1 Reference(ehealth-patient) {r} Who this goal is intended for
ele-1: All FHIR elements must have a @value or children
... expressedBy Σ 0..1 Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson) Who's responsible for creating Goal?
ele-1: All FHIR elements must have a @value or children
... addresses 0..* Reference(ehealth-condition | ehealth-observation | MedicationStatement | NutritionOrder | ehealth-servicerequest | RiskAssessment) {r} Issues addressed by this goal
ele-1: All FHIR elements must have a @value or children
... outcomeReference 0..* Reference(ehealth-observation) {r} Observation that resulted from goal
ele-1: All FHIR elements must have a @value or children

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
Goal.lifecycleStatusrequiredGoalLifecycleStatus
http://hl7.org/fhir/ValueSet/goal-status|4.0.1
from the FHIR Standard
Goal.descriptionrequiredGoalDescription (a valid code from Goal Description)
http://ehealth.sundhed.dk/vs/goal-description
from this IG

 

Other representations of profile: CSV, Excel, Schematron