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: R4 R3

1.30.1.11.390 Code System http://hl7.org/fhir/goal-relationship-type

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/goal-relationship-type
Name:GoalRelationshipType
Definition:Types of relationships between two goals
Committee:Patient Care Work Group
OID:2.16.840.1.113883.4.642.1.390 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

1.30.1.11.390.1 Content

1.30.1.11.390.2 GoalRelationshipType

Types of relationships between two goals

This code system http://hl7.org/fhir/goal-relationship-type defines the following codes:

CodeDisplayDefinition
predecessor PredecessorIndicates that the target goal is one which must be met before striving for the current goal
successor SuccessorIndicates that the target goal is a desired objective once the current goal is met
replacement ReplacementIndicates that this goal has been replaced by the target goal
component ComponentIndicates that the target goal is considered to be a "piece" of attaining this goal.
other OtherIndicates that the relationship is not covered by one of the pre-defined codes. (An extension may convey more information about the meaning of the relationship.)

 

See the full registry of value sets defined as part of FHIR.

Explanation of the columns that may appear on this page:

LevelA few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance)
DisplayThe display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code