The problem detail segment contains the data necessary to add, update, correct, and delete the problems of a given individual.
Figure 12-3. PRB attributes
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM # |
ELEMENT NAME |
1 |
2 |
ID |
R |
0287 |
00816 |
Action Code |
|
2 |
26 |
TS |
R |
00817 |
Action Date/Time |
||
3 |
80 |
CE |
R |
00838 |
Problem ID |
||
4 |
60 |
EI |
R |
00839 |
Problem Instance ID |
||
5 |
60 |
EI |
O |
00840 |
Episode of Care ID |
||
6 |
60 |
NM |
O |
00841 |
Master Problem List Number |
||
7 |
26 |
TS |
O |
00842 |
Problem Established Date/Time |
||
8 |
26 |
TS |
O |
00843 |
Anticipated Problem Resolution Date/Time |
||
9 |
26 |
TS |
O |
00844 |
Actual Problem Resolution Date/Time |
||
10 |
80 |
CE |
O |
00845 |
Problem Classification |
||
11 |
80 |
CE |
O |
Y |
00846 |
Problem Management Discipline |
|
12 |
80 |
CE |
O |
00847 |
Problem Persistence |
||
13 |
80 |
CE |
O |
00848 |
Problem Confirmation Status |
||
14 |
80 |
CE |
O |
00849 |
Problem Life Cycle Status |
||
15 |
26 |
TS |
O |
00850 |
Problem Life Cycle Status Date/Time |
||
16 |
26 |
TS |
O |
00851 |
Problem Date of Onset |
||
17 |
80 |
ST |
O |
00852 |
Problem Onset Text |
||
18 |
80 |
CE |
O |
00853 |
Problem Ranking |
||
19 |
60 |
CE |
O |
00854 |
Certainty of Problem |
||
20 |
5 |
NM |
O |
|
00855 |
Probability of Problem (0-1) |
|
21 |
80 |
CE |
O |
00856 |
Individual Awareness of Problem |
||
22 |
80 |
CE |
O |
00857 |
Problem Prognosis |
||
23 |
80 |
CE |
O |
00858 |
Individual Awareness of Prognosis |
||
24 |
200 |
ST |
O |
00859 |
Family/Significant Other Awareness of Problem/Prognosis |
||
25 |
80 |
CE |
O |
00823 |
Security/Sensitivity |
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.
12.3.2.0 PRB field definitions
Definition: This field contains the intent of the message. Refer to HL7 table 0287 - Action code for valid values.
Definition: This field contains the date/time that the operation represented by the action code was performed.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field identifies the problem.
Components: <entity identifier (ST)> ^ <assigning authority (HD)>
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. |
Components: <entity identifier (ST)> ^ <assigning authority (HD)>
Definition: This field uniquely identifies the episode of care to which this problem applies. (See note under "Ongoing issues."
Note: It is expected that this field be unique over time. |
Definition: This field prioritizes this problem on a master list that is maintained for the individual.
Definition: This field contains the date/time when the corresponding problem was initially identified by the care giver.
Definition: This field contains the estimated date/time for resolving the stated problem.
Definition: This field contains the date/time that the problem was actually resolved.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
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.).
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
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 who may have the responsibility for this problem.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the perseverance of a problem (e.g., acute, chronic, etc.).
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the verification status of a problem (e.g., confirmed, differential, provisional, rule-out, etc.).
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
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.).
Definition: This field indicates the effective date/time of the current problem life cycle status.
Definition: This field contains the date/time when the problem began.
Definition: This field allows for a textual representation of the time when the problem began.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
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.).
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains a qualitative representation of the certainty of a problem (e.g., HI - high, LO - low, ME - medium, etc.).
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 health care 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. |
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the individuals comprehension of the problem (e.g., Full, Marginal, Partial, etc.).
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the prognosis for the individuals problem (e.g., good, poor, etc.).
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the individuals comprehension of the prognosis for the problem (e.g., full, marginal, partial, etc.).
Definition: This field indicates the individuals family or significant others comprehension of the actual problem/prognosis.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains information about the level of security and/or sensitivity surrounding the problem (e.g., highly sensitive, not sensitive, sensitive, etc.).