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

Draft Website - For Review Purposes Only

PRB - Problem Detail Segment

NOTE: This segment will be taken over by the Orders and Observations Work Group.

The problem detail segment contains the data necessary to add, update, correct, and delete the problems of a given individual.

HL7 Attribute Table - PRB - Problem Detail Segment
Seq# DataElement Description Must Implement Flags Cardinality Length C.LEN Vocabulary DataType
PRB
1 00816 Action Code SHALL [1..1] [2..2] ID
2 00817 Action Date/Time SHALL [1..1] DTM
3 00838 Problem ID SHALL [1..1] CWE
4 00839 Problem Instance ID SHALL [1..1] EI
5 00820 Episode of Care ID [0..1] EI
6 00841 Problem List Priority [0..1] NM
7 00842 Problem Established Date/Time [0..1] DTM
8 00843 Anticipated Problem Resolution Date/Time [0..1] DTM
9 00844 Actual Problem Resolution Date/Time [0..1] DTM
10 00845 Problem Classification [0..1] CWE
11 00846 Problem Management Discipline [0..*] CWE
12 00847 Problem Persistence [0..1] CWE
13 00848 Problem Confirmation Status [0..1] CWE
14 00849 Problem Life Cycle Status [0..1] CWE
15 00850 Problem Life Cycle Status Date/Time [0..1] DTM
16 00851 Problem Date of Onset [0..1] DTM
17 00852 Problem Onset Text = [0..1] 80 ST
18 00853 Problem Ranking [0..1] CWE
19 00854 Certainty of Problem [0..1] CWE
20 00855 Probability of Problem # [0..1] 4 NM
21 00856 Individual Awareness of Problem [0..1] CWE
22 00857 Problem Prognosis [0..1] CWE
23 00858 Individual Awareness of Prognosis [0..1] CWE
24 00859 Family/Significant Other Awareness of Problem/Prognosis = [0..1] 200 ST
25 00823 Security/Sensitivity [0..1] CWE
26 02234 Problem Severity [0..1] CWE
27 02235 Problem Perspective [0..1] CWE
28 02237 Mood Code MAY
True:
False:
C
[1..1]
[0..1]
CNE

The business and/or application must assume the responsibility for maintaining knowledge about data ownership, versioning, and/or audit trail control (for purposes of data integrity). It is also their responsibility to represent the appropriate version of that data.

PRB-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.

PRB-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.

PRB-3: Problem ID (CWE) 00838

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

PRB-4: Problem Instance ID (EI) 00839

Definition: This field contains the identifier assigned by an initiating system to an instance of a problem.

Note: It is required that this value remain 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.


PRB-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.


PRB-6: Problem List Priority (NM) 00841

Definition: This field prioritizes this problem on a list that is maintained for the individual.

PRB-7: Problem Established Date/Time (DTM) 00842

Definition: This field contains the date/time when the corresponding problem was initially identified by the caregiver.

PRB-8: Anticipated Problem Resolution Date/Time (DTM) 00843

Definition: This field contains the estimated date/time for resolving the stated problem.

PRB-9: Actual Problem Resolution Date/Time (DTM) 00844

Definition: This field contains the date/time that the problem was actually resolved.

PRB-10: Problem Classification (CWE) 00845

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

PRB-11: Problem Management Discipline (CWE) 00846

Definition: This field indicates the category of caregiver with responsibility for managing this specific problem (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 problem.

PRB-12: Problem Persistence (CWE) 00847

Definition: This field contains the perseverance of a problem (e.g., acute, chronic, etc.).

PRB-13: Problem Confirmation Status (CWE) 00848

Definition: This field contains the verification status of a problem (e.g., confirmed, differential, provisional, rule-out, etc.).

PRB-14: Problem Life Cycle Status (CWE) 00849

Definition: This field contains the current status of the problem at this particular date/time (e.g., active, active-improving, active-stable, active-worsening, inactive, resolved, etc.).

PRB-15: Problem Life Cycle Status Date/Time (DTM) 00850

Definition: This field indicates the effective date/time of the current problem life cycle status.

PRB-16: Problem Date of Onset (DTM) 00851

Definition: This field contains the date/time when the problem began.

PRB-17: Problem Onset Text (ST) 00852

Definition: This field allows for a textual representation of the time when the problem began.

PRB-18: Problem Ranking (CWE) 00853

Definition: This field contains a user-defined prioritization of a problem (e.g., numeric ranking, or the use of words such as "primary," "secondary," etc.).

PRB-19: Certainty of Problem (CWE) 00854

Definition: This field contains a qualitative representation of the certainty of a problem (e.g., HI - high, LO - low, ME - medium, etc.).

PRB-20: Probability of Problem (NM) 00855

Definition: This field contains a quantitative or numeric representation of the certainty that the problem exists for this patient. This field has a valid range of 0 to 1. For example, a healthcare provider may be 75% (.75) sure that the problem has been correctly identified.

Note: We have provided for two different representations of the certainty of the problem due to varying representations in applications.


PRB-21: Individual Awareness of Problem (CWE) 00856

Definition: This field contains the individual's comprehension of the problem (e.g., full, marginal, partial, etc.).

PRB-22: Problem Prognosis (CWE) 00857

Definition: This field contains the prognosis for the individual's problem (e.g., good, poor, etc.).

PRB-23: Individual Awareness of Prognosis (CWE) 00858

Definition: This field contains the individual's comprehension of the prognosis for the problem (e.g., full, marginal, partial, etc.).

PRB-24: Family/Significant Other Awareness of Problem/Prognosis (ST) 00859

Definition: This field indicates the individual's family or significant other's comprehension of the actual problem/prognosis.

PRB-25: Security/Sensitivity (CWE) 00823

Definition: This field contains information about the level of security and/or sensitivity surrounding the problem (e.g., highly sensitive, not sensitive, sensitive, etc.).

PRB-26: Problem Severity (CWE) 02234

Definition: This field indicates the severity of the Problem. Refer to User-defined Table 0836- Problem Severity in Chapter 2C, Code Tables, for suggested values.

PRB-27: Problem Perspective (CWE) 02235

Definition: This field indicates from whose perspective this problem was identified. Refer to User-defined Table 0838 - Problem Perspective in Chapter 2C, Code Tables, for suggested values.

PRB-28: Mood Code (CNE) 02237

Definition: This field indicates the Mood of the Problem. 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.