STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

4.6.6 Resource Goal - Detailed Descriptions

Detailed Descriptions for the elements in the Goal resource.

Goal
Definition

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.

Control1..1
Comments

Goal can be achieving a particular change or merely maintaining a current state or even slowing a decline.

Goal.identifier
Definition

This records identifiers associated with this care plan that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation).

NoteThis is a business identifer, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
Requirements

Need to allow connection to a wider workflow.

Goal.subject
Definition

Identifies the patient, group or organization for whom the goal is being established.

Control0..1
TypeReference(Patient | Group | Organization)
Requirements

Subject is optional to support annonymized reporting.

Summarytrue
Goal.start[x]
Definition

The date or event after which the goal should begin being pursued.

Control0..1
BindingGoalStartEvent: Codes describing events that can trigger the initiation of a goal (Example)
Typedate|CodeableConcept
[x] NoteSee Choice of Data Types for further information about how to use [x]
Requirements

Goals can be established prior to there being an intention to start pursuing them; e.g. Goals for post-surgical recovery established prior to surgery.

Summarytrue
Goal.target[x]
Definition

Indicates either the date or the duration after start by which the goal should be met.

Control0..1
Typedate|Duration
[x] NoteSee Choice of Data Types for further information about how to use [x]
Requirements

Identifies when the goal should be evaluated.

Summarytrue
Goal.category
Definition

Indicates a category the goal falls within.

Control0..*
BindingGoalCategory: Codes for grouping and sorting goals (Example)
TypeCodeableConcept
Requirements

Allows goals to be filtered and sorted.

Summarytrue
Goal.description
Definition

Human-readable description of a specific desired objective of care.

Control1..1
Typestring
Requirements

Without a description of what's trying to be achieved, element has no purpose.

Summarytrue
Goal.status
Definition

Indicates whether the goal has been reached and is still considered relevant.

Control1..1
BindingGoalStatus: Indicates whether the goal has been met and is still being targeted (Required)
Typecode
Is Modifiertrue
Requirements

Allows measuring outcome and whether goal needs to be further tracked.

Summarytrue
Goal.statusDate
Definition

Identifies when the current status. I.e. When initially created, when achieved, when cancelled, etc.

Control0..1
Typedate
Summarytrue
Comments

To see the date for past statuses, query history.

Goal.statusReason
Definition

Captures the reason for the current status.

Control0..1
BindingGoalStatusReason: Codes to identify the reason for a goal's current status (Example)
TypeCodeableConcept
Comments

This will typically be captured for statuses such as rejected, on-hold or cancelled, but could be present for others.

Goal.author
Definition

Indicates whose goal this is - patient goal, practitioner goal, etc.

Control0..1
TypeReference(Patient | Practitioner | RelatedPerson)
Summarytrue
Comments

This is the individual reponsible for establishing the goal, not necessarily who recorded it. (For that, use the Provenance resource.).

Goal.priority
Definition

Identifies the mutually agreed level of importance associated with reaching/sustaining the goal.

Control0..1
BindingGoalPriority: The level of importance associated with a goal (Preferred)
TypeCodeableConcept
Requirements

Used for sorting and presenting goals.

Summarytrue
Comments

Extensions are available to track priorities as established by each participant (i.e. Priority from the patient's perspective, different practitioners' perspectives, family member's perspectives)

The ordinal extension on Coding can be used to convey a numerically comparable ranking to priority. (Keep in mind that different coding systems may use a "low value=important".

Goal.addresses
Definition

The identified conditions and other health record elements that are intended to be addressed by the goal.

Control0..*
TypeReference(Condition | Observation | MedicationStatement | NutritionOrder | ProcedureRequest | RiskAssessment)
Requirements

Allows specific goals to explicitly linked to the concerns they're dealing with - makes the goal more understandable.

Goal.note
Definition

Any comments related to the goal.

Control0..*
TypeAnnotation
Requirements

There's a need to capture information about the goal that doesn't actually describe the goal.

Comments

May be used for progress notes, concerns or other related information that doesn't actually describe the goal itself.

Goal.outcome
Definition

Identifies the change (or lack of change) at the point where the goal was deepmed to be cancelled or achieved.

Control0..*
Requirements

Outcome tracking is a key aspect of care planning.

Comments

Note that this should not duplicate the goal status.

To DoDefine a proper value set for this.
Goal.outcome.result[x]
Definition

Details of what's changed (or not changed).

Control0..1
BindingGoalOutcome: The result of the goal; e.g. "25% increase in shoulder mobility", "Anxiety reduced to moderate levels". "15 kg weight loss sustained over 6 months"
TypeCodeableConcept|Reference(Observation)
[x] NoteSee Choice of Data Types for further information about how to use [x]