The Demo site for our new HL7 Version 2+ (plus) Standard
visit the hl7 website

Draft Website - For Review Purposes Only

GOL - Goal Detail Segment

The goal detail segment contains the data necessary to add, update, correct, and delete the goals for an individual.

HL7 Attribute Table - GOL - Goal Detail Segment
Seq# DataElement Description Must Implement Flags Cardinality Length C.LEN Vocabulary DataType
GOL
1 00816 Action Code SHALL [1..1] [2..2] ID
2 00817 Action Date/Time SHALL [1..1] DTM
3 00818 Goal ID SHALL [1..1] CWE
4 00819 Goal Instance ID SHALL [1..1] EI
5 00820 Episode of Care ID [0..1] EI
6 00821 Goal List Priority = [0..1] 3 NM
7 00822 Goal Established Date/Time [0..1] DTM
8 00824 Expected Goal Achieve Date/Time [0..1] DTM
9 00825 Goal Classification [0..1] CWE
10 00826 Goal Management Discipline [0..1] CWE
11 00827 Current Goal Review Status [0..1] CWE
12 00828 Current Goal Review Date/Time [0..1] DTM
13 00829 Next Goal Review Date/Time [0..1] DTM
14 00830 Previous Goal Review Date/Time [0..1] DTM
15 00831 Goal Review Interval SHALL NOT W [0..0]
16 00832 Goal Evaluation [0..1] CWE
17 00833 Goal Evaluation Comment = [0..*] 300 ST
18 00834 Goal Life Cycle Status [0..1] CWE
19 00835 Goal Life Cycle Status Date/Time [0..1] DTM
20 00836 Goal Target Type [0..*] CWE
21 00837 Goal Target Name [0..*] XPN
22 02182 Mood Code MAY
True:
False:
C
[1..1]
[0..1]
CNE

GOL-1: Action Code (ID) 00816

(Definition from OH1.2 in Ch. 3)

Definition: This field contains a code defining the action to be taken for this segment. It allows this segment to be sent to delete or update, for example, previously sent information. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.

(Definition from OH2.2 in Ch. 3)

Definition: This field contains a code defining the action to be taken for this segment. It allows this segment to be sent to delete or update, for example, previously sent information. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.

(Definition from OH3.2 in Ch. 3)

Definition: This field contains a code defining the action to be taken for this segment. It allows this segment to be sent to delete or update, for example, previously sent information. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.

(Definition from OH4.2 in Ch. 3)

Definition: This field contains a code defining the action to be taken for this segment. It allows this segment to be sent to delete or update, for example, previously sent information. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.

(Definition from ORC.35 in Ch. 4)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.

The action code can only be used when either ORC-2 and/or ORC 3 is valued with a unique identifier in accordance with Chapter 2, Section 2.10.4.2.

(Definition from OBR.55 in Ch. 4)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.

The action code can only be used when either an OBR-2 and/or OBR-3 is valued with unique identifier in accordance with Chapter 2, Section 2.10.4.2.

(Definition from IPC.10 in Ch. 4)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.

The action code can only be used when the combination of IPC-1, IPC-2, IPC-3, and IPC-4 represents a unique identifier according to Chapter 2, Section 2.10.4.2.

(Definition from BPX.22 in Ch. 4)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.

The action code can only be used when an BPX is uniquely identified sufficiently within the specific implementation using BPX-17 or BPX-6 as agreed to by the trading partners and in accordance with Chapter 2, Section 2.10.4.2.

(Definition from BTX.21 in Ch. 4)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.

The action code can only be used when an BTX is uniquely identified sufficiently within the specific implementation using BTX-20 or BTX-3 as agreed to by the trading partners in accordance with Chapter 2, Section 2.10.4.2.

(Definition from DON.34 in Ch. 4)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.

The action code can only be used when an DON is uniquely identified sufficiently within the specific implementation using DON-1 in accordance with Chapter 2, Section 2.10.4.2.

(Definition from BUI.13 in Ch. 4)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.

The action code can only be used when an BUI is uniquely identified sufficiently within the specific implementation using BUI-2 in accordance with Chapter 2, Section 2.10.4.2

(Definition from RXV.22 in Ch. 4A)

Definition: The intended handling by the receiver of the infusion order is represented by this segment. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.

(Definition from CDO.2 in Ch. 4A)

Definition: The Action Code indicates whether the cumulative dosage segment is intended to be added, deleted, updated, or did not change. If the field is not valued in any CDO segments for the order, the segments are considered to have been sent in snapshot mode. If some but not all CDO segments for the order do not have the action code valued, the default value is Add. Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values.

(Definition from OBR.55 in Ch. 7)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.

The action code can only be used when an either OBR-2 and/or OBR-3 is valued with unique identifier in accordance with Chapter 2, Section 2.10.4.2.

(Definition from OBX.31 in Ch. 7)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.

The action code can only be used when an OBX-21 is valued in accordance with guidance in Chapter 2, Section 2.10.4.2.

(Definition from SPM.35 in Ch. 7)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.

The action code can only be used when an SPM-2 or SPM-31 is valued in accordance with the guidance in Chapter 2, Section 2.10.4.2.

(Definition from PRT.2 in Ch. 7)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0287 – Problem/goal action code for valid values.

(Definition from CSR.17 in Ch. 7)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.

The action code can only be used when CSR-1 and CSR-4, or CSR-2 and CSR-5 are valued as agreed to by the trading partners in accordance with the guidance in Chapter 2, Section 2.10.4.2.

(Definition from CTI.4 in Ch. 7)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.

The action code can only be used when CTI-1 is valued in accordance with the guidance in Chapter 2, Section 2.10.4.2.

(Definition from SHP.12 in Ch. 7)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.

The action code can only be used when SHP-1 is valued in accordance with the guidance in Chapter 2, Section 2.10.4.2.

(Definition from PAC.9 in Ch. 7)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.

The action code can only be used when PAC-2 is valued in accordance with the guidance in Chapter 2, Section 2.10.4.2.

(Definition from GOL.1 in Ch. 12)

Definition: The action code field gives the intent of the problem or goal. Refer to HL7 Table 0287 – Problem/Goal Action Code in Chapter 2C, Code Tables, for valid values.

(Definition from PRB.1 in Ch. 12)

Definition: This field contains the intent of the message. Refer to HL7 Table 0287 – Problem/Goal Action Code in Chapter 2C, Code Tables, for valid values.

(Definition from PTH.1 in Ch. 12)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0287 – Problem/Goal Action Code in Chapter 2C, Code Tables, for valid values.

(Definition from DEV.1 in Ch. 17)

Definition: This field reveals the intent of the message. Refer to HL7 Table 0287 – Problem/goal action code for valid values.

GOL-2: Action Date/Time (DTM) 00817

(Definition from GOL.2 in Ch. 12)

Definition: This field contains the date/time that the operation represented by the action code was performed.

(Definition from PRB.2 in Ch. 12)

Definition: This field contains the date/time that the operation represented by the action code was performed.

GOL-3: Goal ID (CWE) 00818

Definition: This field identifies the goal. This is the identifier from an institution's master list of goals.

GOL-4: Goal Instance ID (EI) 00819

Definition: This field contains the unique identifier assigned by an initiating system to this instance of the goal.

Note: It is required that the value in this field be unique over time. This instance ID identifies a specific instance for a specific patient and is unique across all patients. See entity ID data type description in Chapter 2.


GOL-5: Episode of Care ID (EI) 00820

(Definition from GOL.5 in Ch. 12)

Definition: This field uniquely identifies the episode of care to which this goal applies. See note under "Ongoing issues."

Note: Based on application use, this field is required to be unique over time.


(Definition from PRB.5 in Ch. 12)

Definition: This field uniquely identifies the episode of care to which this problem applies. (See note under "Ongoing issues.")

Note: It is required that this field be unique over time.


GOL-6: Goal List Priority (NM) 00821

Definition: This field prioritizes this goal on a list that is maintained for an individual.

GOL-7: Goal Established Date/Time (DTM) 00822

Definition: This field identifies the date/time when the stated goal was initially created.

GOL-8: Expected Goal Achieve Date/Time (DTM) 00824

Definition: This field contains the projected date/time for achieving the stated goal.

GOL-9: Goal Classification (CWE) 00825

Definition: This field indicates the kind of goal. This field can be used to categorize goals so that they may be managed and viewed independently within different applications (e.g., admission, final, post-operative, pre-operative, outpatient, discharge, etc.).

Note: This field can be used to differentiate separate goal lists that may be managed independently within applications.


GOL-10: Goal Management Discipline (CWE) 00826

Definition: This field indicates the category of caregiver with responsibility for managing this specific goal (e.g., care team, nursing, medicine, respiratory therapy, occupational therapy, dietary etc.). This is a repeating field to allow identification of all disciplines that may have the responsibility for this goal.

GOL-11: Current Goal Review Status (CWE) 00827

Definition: This field contains the current point in the continuum of a goal review cycle (e.g., due, initiated, reviewed, overdue, verified, etc.).

GOL-12: Current Goal Review Date/Time (DTM) 00828

Definition: This field contains the date/time of the current review of the goal.

GOL-13: Next Goal Review Date/Time (DTM) 00829

Definition: This field contains the date/time of the next scheduled goal review.

GOL-14: Previous Goal Review Date/Time (DTM) 00830

Definition: This field contains the date/time that the goal was reviewed prior to the current review.

GOL-15: Goal Review Interval

As of Version 2.5, this field was retained for backward compatibility only and withdrawn and removed as of v2.7. Refer to the TQ1 segment described in Chapter 4.

GOL-16: Goal Evaluation (CWE) 00832

Definition: This field provides an indicator of progress towards achievement of the goal (e.g., achieved, ahead of schedule, delayed, failed to achieve, etc.).

GOL-17: Goal Evaluation Comment (ST) 00833

Definition: This field contains the comments associated with the goal evaluation. Examples of comments that might be entered in this field include: a reason for delay in achieving goal, or a clinical footnote about progress made towards the goal, etc.

GOL-18: Goal Life Cycle Status (CWE) 00834

Definition: This field contains an indication of the state of the goal (e.g., Active, Canceled, Inactive, Suspended, etc.).

GOL-19: Goal Life Cycle Status Date/Time (DTM) 00835

Definition: This field contains the effective date/time of the current goal life cycle status.

GOL-20: Goal Target Type (CWE) 00836

Definition: This field contains the individual/group for whom the goal has been established (e.g., family group, family member, patient, etc.).

Note: This field is focused on a specific person/group that is directly patient-related.


GOL-21: Goal Target Name (XPN) 00837

Definition: This field contains the identification of the person(s) on whom the goal is focused. This is a repeating field which allows for the identification of a group of individuals.

GOL-22: Mood Code (CNE) 02182

(Definition from OBX.22 in Ch. 7)

Definition: This field identifies the actuality of the observation (e.g., intent, request, promise, event). Refer to HL7 Table 0725 – Mood Codes for valid values. This field may only be used with new trigger events and new messages from v 2.6 onward. When this field is not valued in a message that qualifies, then the Value is assumed to be 'EVN'.

Note: OBX-22 Mood Code was introduced in v 2.6 to support Patient Care messaging concepts and constructs. At this time, there are no documented use cases for this field in the context messages as described in this chapter. This statement does not preclude the use of OBX-22, but implementers should exercise caution in using this field outside of the Patient Care context until appropriate use cases are established. While a similar note exists for OBX-21 Observation Instance Identifier, particular care should be taken with OBX-22 as this could modify the intent of the segment/message and create backward compatibility problems.


(Definition from GOL.22 in Ch. 12)

Definition: This field indicates the Mood of the Goal. It allows expression of the context of the problem.

Note: As Mood Code changes the meaning of the segment it must only be used in new messages as of v2.6.


Refer to HL7 Table 0725 – Mood Codes in Chapter 2C, Code Tables, for allowed values.