PID|||624335A^^^WEST CLINIC~564325^^^SOUTH LAB|
Note that the PID segment returned does not include any person demographics as
the identifiers are not yet "attached" to any person record. Presumably the
querying system would eventually send back to the MPI an A28 Add person
information to create a person record for the identifiers or an A24 Link
patient information to link the identifiers to an existing person record.
This
trigger event is used when person/patient allergy information has changed. It
is used in conjunction with a new allergy segment, the IAM - patient allergy
information segment-unique identifier, which supports Action code/unique
identifier mode update for repeating segments as defined in 2.14.4 Modes for
updating via repeating segments.
ADT^A60^ADT_A60 |
ADT Message |
Chapter |
|---|---|---|
MSH |
Message Header |
2 |
EVN |
Event Type |
3 |
PID |
Patient Identification |
3 |
[ PV1 ] |
Patient Visit |
3 |
[ PV2 ] |
Patient Visit - Additional Info. |
3 |
[{ IAM }] |
Patient adverse reaction information |
3 |
ACK^A60^ACK |
General Acknowledgment |
Chapter |
|---|---|---|
MSH |
Message Header |
2 |
MSA |
Message Acknowledgment |
2 |
[ ERR ] |
Error |
2 |
An
A61 event is used as a result of a change in the consulting physician(s) for
the treatment of a patient.
When other important fields change, it is recommended that the A08 (update
patient information) event be used in addition. If the Patient Administration
system allows demographics to change at the same time (for example an address
change), two messages (an A61 followed by an A08) should be sent.
The new consulting doctor(s) of the patient should appear in the PV1-9 -
consulting doctor and may appear in a role segment per new consulting
physician.
If a consulting doctor stops being consulting doctor for this patient-visit,
the end date/time can be sent in the ROL-6 - Role end date/time.
For example, an A61 event can be used to notify the billing system that
doctors' fees for being a consulting doctor, should be billed to the new
doctor(s) starting from the timestamp in the message.
It is recommended that field EVN-6 - Event occurred contains the
date/time the event actually occurred to the patient.
The ROL - Role Segment is used in this message to communicate providers not
specified elsewhere. Person level providers with an ongoing relationship are
reported in the ROL segment following the PID/PD1 segments. Providers
corresponding to the PV1 data are reported in the ROL segment following the
PV1/PV2 segments. Providers related to a specific procedure are reported in
the ROL segment following the PR1 segment. Providers related to a specific
insurance are reported in the ROL segment following the IN1/IN2/IN3 segments.
To communicate the begin and end date of the provider, use the ROL-5 - Role
Begin Date/Time and the ROL-6 - Role End Date/Time in the ROL
segment, with the applicable ROL-3 - Role code. Refer to section 12.3.3
for the definition of the ROL segment.
ADT^A61^ADT_A61 |
ADT Message |
Chapter |
MSH |
Message Header |
2 |
EVN |
Event Type |
3 |
PID |
Patient Identification |
3 |
[ PD1 ] |
Additional Demographics |
3 |
PV1 |
Patient Visit |
3 |
[ {ROL} ] |
Role |
12 |
[ PV2 ] |
Patient Visit - Additional Info. |
3 |
ACK^ACK |
General Acknowledgment |
Chapter |
MSH |
Message Header |
2 |
MSA |
Message Acknowledgment |
2 |
[ ERR ] |
Error |
2 |
The
A62 event is sent when an A61 (change consulting doctor) event is cancelled,
either because of erroneous entry of the A61 event or because of a decision not
to change the consulting physician(s) after all. PV1-9 - consulting
doctor must show the patient's doctor prior to the change being
cancelled.
The fields included when this message is sent should be the fields pertinent to
communicate this event. When other important fields change, it is recommended
that the A08 (update patient information) event is used.
ADT^A62^ADT_A61 |
ADT Message |
Chapter |
MSH |
Message Header |
2 |
EVN |
Event Type |
3 |
PID |
Patient Identification |
3 |
[PD1] |
Additional Demographics |
3 |
PV1 |
Patient Visit |
3 |
[ {ROL} ] |
Role |
12 |
[ PV2 ] |
Patient Visit - Additional Info. |
3 |
ACK^ACK |
General Acknowledgment |
Chapter |
MSH |
Message Header |
2 |
MSA |
Message Acknowledgment |
2 |
[ ERR ] |
Error |
2 |
The
EVN segment is used to communicate necessary trigger event information to
receiving applications. Valid event types for all chapters are contained in
HL7 Table 0003 - Event type.
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
3 |
ID |
B |
0003 |
00099 |
Event Type Code |
|
2 |
26 |
TS |
R |
00100 |
Recorded Date/Time |
||
3 |
26 |
TS |
O |
00101 |
Date/Time Planned Event |
||
4 |
3 |
IS |
O |
0062 |
00102 |
Event Reason Code |
|
5 |
250 |
XCN |
O |
Y |
0188 |
00103 |
Operator ID |
6 |
26 |
TS |
O |
01278 |
Event Occurred |
||
7 |
180 |
HD |
O |
01534 |
Event Facility |
Definition: This field has been retained for backward compatibility only. We recommend using the second component (trigger event) of MSH-9 - Message Type to transmit event type code information. This field contains the events corresponding to the trigger events described in this section, e.g., admission, transfer, or registration. Refer to HL7 Table 0003 - Event type for valid values.
Definition: Most systems will default to the system date/time when the transaction was entered, but they should also permit an override.
Definition: This field contains the date/time that the event is planned. We recommend that PV2-8 - Expected Admit Date/Time, PV2-9 - Expected Discharge Date/Time or PV2-47 - Expected LOA Return date/time be used whenever possible.
Definition:
This field contains the reason for this event. Refer to User-defined Table
0062 - Eve
nt
reason for suggested values.
Value |
Description |
|---|---|
01 |
Patient request |
02 |
Physician/health practitioner order |
03 |
Census management |
Components:
<ID number (ST)> ^ <family name (ST)> <given name (ST)> ^
<second and further given names or initials thereof (ST)> ^ <suffix
(e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g.,
MD) (IS)> ^ <source table (IS)> ^ <assigning authority (HD)> ^
<name type code (ID)> ^ <identifier check digit (ST)> ^ <code
identifying the check digit scheme employed (ID)> ^ <identifier type code
(IS)> ^ <assigning facility (HD)> ^ <name representation code
(ID)> ^ <name context (CE)> ^ <name validity range (DR)>
Subcomponents of family name: <family name (ST)> & <own family
name prefix (ST)> & <own family name (ST)> & <family name
prefix from partner/spouse (ST)> & <family name from partner/spouse
(ST)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field identifies the individual responsible for triggering
the event. Refer to User-d
efined
Table 0188 - Ope
rator
ID for suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Definition: This field contains the date/time that the event actually occurred. For example, on a transfer (A02 transfer a patient), this field would contain the date/time the patient was actually transferred. On a cancellation event, this field should contain the date/time that the event being cancelled occurred.
Components:
<namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type
(ID)>
Definition: This field identifies the actual facility where the event occured
as differentiated from the sending facility (MSH-4). It would be the facility
at which the Operator (EVN-5) has entered the event.
Use Case: System A is where the patient is originally registered. This
registration message is sent to an MPI, System B. The MPI needs to broadcast
the event of this update and would become the sending facility. This new field
would allow for retention of knowledge of the originating facility where the
event occurred. The MPI could be the assigning authority for the ID number as
well which means that it is performing the function of assigning authority for
the facility originating the event.
The
PID segment is used by all applications as the primary means of communicating
patient identification information. This segment contains permanent patient
identifying and demographic information that, for the most part, is not likely
to change frequently.
It should be noted that from V2.4 onwards the demographics of animals can also
be sent in the PID segment (see PID-35 to PID-38).
The assigning authority, the fourth component of the patient identifiers, is a
HD data type that is uniquely associated with the assigning authority that
originally assigned the number. A given institution, or group of
intercommunicating institutions, should establish a list of assigning
authorities that may be potential assignors of patient identification (and
other important identification) numbers. The list will be one of the
institution's master dictionary lists. Since third parties (other than the
assignors of patient identification numbers) may send or receive HL7 messages
containing patient identification numbers, the assigning authority in the
patient identification numbers may not be the same as the sending and receiving
systems identified in the MSH. The assigning authority must be unique across
applications at a given site. This field is required in HL7 implementations
that have more than a single Patient Administration application assigning such
numbers. The assigning authority and identifier type codes are strongly
recommended for all CX data types.
With HL7 V2.3, the nomenclature for the fourth component of the patient
identifiers was changed from "assigning facility ID" to "assigning authority".
While the identifier may be unique to a given healthcare facility (for example,
a medical record assigned by facility A in Hospital XYZ), the identifier might
also be assigned at a system level (for example a corporate person index or
enterprise number spanning multiple facilities) or by a government entity, for
example a nationally assigned unique individual identifier. While a facility
is usually an assigning authority, not all assigning authorities are
facilities. Therefore, the fourth component is referred to as an assigning
authority, but retains backward compatibility using the construct of the HD
data type (see the note in section 2.8.18). Additionally, CX data types
support the use of assigning facility (HD) as the sixth component.
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
4 |
SI |
O |
00104 |
Set ID - PID |
||
2 |
20 |
CX |
B |
00105 |
Patient ID |
||
3 |
250 |
CX |
R |
Y |
00106 |
Patient Identifier List |
|
4 |
20 |
CX |
B |
Y |
00107 |
Alternate Patient ID - PID |
|
5 |
250 |
XPN |
R |
Y |
00108 |
Patient Name |
|
6 |
250 |
XPN |
O |
Y |
00109 |
Mother's Maiden Name |
|
7 |
26 |
TS |
O |
00110 |
Date/Time of Birth |
||
8 |
1 |
IS |
O |
0001 |
00111 |
Administrative Sex |
|
9 |
250 |
XPN |
B |
Y |
00112 |
Patient Alias |
|
10 |
250 |
CE |
O |
Y |
0005 |
00113 |
Race |
11 |
250 |
XAD |
O |
Y |
00114 |
Patient Address |
|
12 |
4 |
IS |
B |
0289 |
00115 |
County Code |
|
13 |
250 |
XTN |
O |
Y |
00116 |
Phone Number - Home |
|
14 |
250 |
XTN |
O |
Y |
00117 |
Phone Number - Business |
|
15 |
250 |
CE |
O |
0296 |
00118 |
Primary Language |
|
16 |
250 |
CE |
O |
0002 |
00119 |
Marital Status |
|
17 |
250 |
CE |
O |
0006 |
00120 |
Religion |
|
18 |
250 |
CX |
O |
00121 |
Patient Account Number |
||
19 |
16 |
ST |
B |
00122 |
SSN Number - Patient |
||
20 |
25 |
DLN |
O |
00123 |
Driver's License Number - Patient |
||
21 |
250 |
CX |
O |
Y |
00124 |
Mother's Identifier |
|
22 |
250 |
CE |
O |
Y |
0189 |
00125 |
Ethnic Group |
23 |
250 |
ST |
O |
00126 |
Birth Place |
||
24 |
1 |
ID |
O |
0136 |
00127 |
Multiple Birth Indicator |
|
25 |
2 |
NM |
O |
00128 |
Birth Order |
||
26 |
250 |
CE |
O |
Y |
0171 |
00129 |
Citizenship |
27 |
250 |
CE |
O |
0172 |
00130 |
Veterans Military Status |
|
28 |
250 |
CE |
B |
0212 |
00739 |
Nationality |
|
29 |
26 |
TS |
O |
00740 |
Patient Death Date and Time |
||
30 |
1 |
ID |
O |
0136 |
00741 |
Patient Death Indicator |
|
31 |
1 |
ID |
O |
0136 |
01535 |
Identity Unknown Indicator |
|
32 |
20 |
IS |
O |
Y |
0445 |
01536 |
Identity Reliability Code |
33 |
26 |
TS |
O |
01537 |
Last Update Date/Time |
||
34 |
40 |
HD |
O |
01538 |
Last Update Facility |
||
35 |
250 |
CE |
C |
0446 |
01539 |
Species Code |
|
36 |
250 |
CE |
C |
0447 |
01540 |
Breed Code |
|
37 |
80 |
ST |
O |
01541 |
Strain |
||
38 |
250 |
CE |
O |
2 |
0429 |
01542 |
Production Class Code |
Definition: This field contains the number that identifies this transaction. For the first occurrence of the segment, the sequence number shall be one, for the second occurrence, the sequence number shall be two, etc.
Components:
<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check
digit scheme employed (ID)> ^ < assigning authority (HD)> ^
<identifier type code (ID)> ^ < assigning facility (HD) ^
<effective date (DT)> ^ <expiration date (DT)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field has been retained for backward compatibility
only. The arbitrary term of "external ID" has been removed from the name of
this field. The repetition, assigning authority, healthcare facility, and
identifier type code attributes of PID-3 - patient identifier list allow
for distinctive identifier representation. This field remains for systems with
a negotiated understanding of "external." It is recommended to use PID-3 -
patient identifier list for all patient identifiers.
When used for backward compatibility, this field is valued when the patient is
from another institution, outside office, etc., and the identifier used by that
institution can be shown in this field. This may be a number that multiple
disparate corporations or facilities share. Refer to HL7 Table 0061 - Check
digit scheme.
Components:
<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check
digit scheme employed (ID)> ^ < assigning authority (HD)> ^
<identifier type code (ID)> ^ < assigning facility (HD) ^
<effective date (DT)> ^ <expiration date (DT)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the list of identifiers (one or more) used by
the healthcare facility to uniquely identify a patient (e.g., medical record
number, billing number, birth registry, national unique individual identifier,
etc.). In Canada, the Canadian Provincial Healthcare Number should be sent in
this field. Refer to HL7 Table 0061 - Check digit scheme for valid
values. The arbitrary term of "internal ID" has been removed from the name of
this field for clarity. Refer also to HL7 Table 0203 - Identifier type
and User-define
d
Table 0363 - Assigning authority for valid values.
Value |
Description |
|---|---|
AUSDVA |
Australia - Dept. of Veterans Affairs |
AUSHIC |
Australia - Health Insurance Commission |
CANAB |
Canada - Alberta |
CANBC |
Canada - British Columbia |
CANMB |
Canada - Manitoba |
CANNB |
Canada - New Brunswick |
CANNF |
Canada - Newfoundland |
CANNS |
Canada - Nova Scotia |
CANNT |
Canada - Northwest Territories |
CANNU |
Canada - Nanavut |
CANON |
Canada - Ontario |
CANPE |
Canada - Prince Edward Island |
CANQC |
Canada - Quebec |
CANSK |
Canada - Saskatchewan |
CANYT |
Canada - Yukon Territories |
NLVWS |
NL - Ministerie van Volksgezondheid, Welzijn en Sport |
USCDC |
US Center for Disease Control |
USHCFA |
US Healthcare Finance Authority |
USSSA |
US Social Security Administration |
Components:
<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check
digit scheme employed (ID)> ^ < assigning authority (HD)> ^
<identifier type code (ID)> ^ < assigning facility (HD) ^
<effective date (DT)> ^ <expiration date (DT)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field has been retained for backward compatibility
only. It is recommended to use PID-3 - patient identifier list for
all patient identifiers. When used for backward compatibility, this field
contains the alternate, temporary, or pending optional patient identifier to be
used if needed - or additional numbers that may be required to identify a
patient. This field may be used to convey multiple patient IDs when more than
one exist for a patient. Possible contents might include a visit number, a
visit date, or a Social Security Number.
Components:
In Version 2.3, replaces the PN data type. <family name (FN)> ^
<given name (ST)> ^ <second and further given names or initials
thereof (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g.,
DR) (ST)> ^ <degree (e.g., MD) (IS)> ^ <name type code (ID)
> ^ <name representation code (ID)> ^ <name context (CE)> ^
<name validity range (DR)> ^ <name assembly order (ID)>
Subcomponents of family name: <family name (ST)> & <own family
name prefix (ST)> & <own family name (ST)> & <family name
prefix from partner/spouse (ST)> & <family name from partner/spouse
(ST)>
Definition: This field contains the names of the patient, the primary or legal
name of the patient is reported first. Therefore, the name type code in this
field should be "L - Legal". Refer to HL7 Table 0200 - Name type for
valid values. Repetition of this field is allowed for representing the same
name in different character sets. Note that "last name prefix" is synonymous
to "own family name prefix" of previous versions of HL7, as is "second and
further given names or initials thereof" to "middle initial or name". Multiple
given names and/or initials are separated by spaces.
Value |
Description |
|---|---|
A |
Alias Name |
B |
Name at Birth |
C |
Adopted Name |
D |
Display Name |
I |
Licensing Name |
L |
Legal Name |
M |
Maiden Name |
N |
Nickname /"Call me" Name/Street Name |
P |
Name of Partner/Spouse (retained for backward compatibility only) |
R |
Registered Name (animals only) |
S |
Coded Pseudo-Name to ensure anonymity |
T |
Indigenous/Tribal/Community Name |
U |
Unspecified |
For animals, if a Name Type of "R" is used, use "Name Context" to identify the authority with which the animal's name is registered.
Components:
In Version 2.3, replaces the PN data type. <family name (FN)> ^
<given name (ST)> ^ <second and further given names or initials
thereof (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g.,
DR) (ST)> ^ <degree (e.g., MD) (IS)> ^ <name type code (ID)
> ^ <name representation code (ID)> ^ <name context (CE)> ^
<name validity range (DR)> ^ <name assembly order (ID)>
Subcomponents of family name: <family name (ST)> & <own family
name prefix (ST)> & <own family name (ST)> & <family name
prefix from partner/spouse (ST)> & <family name from partner/spouse
(ST)>
Definition: This field contains the family name under which the mother was
born (i.e., before marriage). It is used to distinguish between patients with
the same last name.
Definition: This field contains the patient's date and time of birth.
Definition:
This field contains the patient's sex. Refer to User-defined
Table
0001 -
Administrative sex for suggested values.
Value |
Description |
|---|---|
F |
Female |
M |
Male |
O |
Other |
U |
Unknown |
A |
Ambiguous |
N |
Not applicable |
Components:
In Version 2.3, replaces the PN data type. <family name (FN)> ^
<given name (ST)> ^ <second and further given names or initials
thereof (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g.,
DR) (ST)> ^ <degree (e.g., MD) (IS)> ^ <name type code (ID)
> ^ <name representation code (ID)> ^ <name context (CE)> ^
<name validity range (DR)> ^ <name assembly order (ID)>
Subcomponents of family name: <family name (ST)> & <own family
name prefix (ST)> & <own family name (ST)> & <family name
prefix from partner/spouse (ST)> & <family name from partner/spouse
(ST)>
Definition: This field has been retained for backward compatibility
only. It is recommended to use PID-5 - patient name for all patient
names. This field contained the name(s) by which the patient has been known at
some time. Refer to HL7 Table 0200
-
Name type for valid values.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field refers to the patient's race. Refer to User-defi
ned
Table 0005 -
Race
for suggested values. The second triplet of the CE data type for race
(alternate identifier, alternate text, and name of alternate coding system) is
reserved for governmentally assigned codes.
Value |
Description |
|---|---|
1002-5 |
American Indian or Alaska Native |
2028-9 |
Asian |
2054-5 |
Black or African American |
2076-8 |
Native Hawaiian or Other Pacific Islander |
2106-3 |
White |
2131-1 |
Other Race |
Note: The above values contain a pre-calculated Mod 10 check digit separated by a dash.
Components:
In Version 2.3 and later, replaces the AD data type. <street address
(ST)> ^ <other designation (ST)> ^ <city (ST)> ^ <state or
province (ST)> ^ <zip or postal code (ST)> ^ <country (ID)> ^
< address type (ID)> ^ <other geographic designation (ST)>
^ <county/parish code (IS)> ^ <census tract (IS)> ^
<address representation code (ID)> ^ <address validity range
(DR)>
Subcomponents of street address: <street address (ST)> &
<street name (ST)> & <dwelling number (ST)>
Definition: This field contains the mailing address of the patient. Address
type codes are defined by HL7 Table 0190 - Address type. Multiple
addresses for the same person may be sent in the following sequence: The
primary mailing address must be sent first in the sequence (for backward
compatibility); if the mailing address is not sent, then a repeat delimiter
must be sent in the first sequence.
Definition: This field has been retained for backward compatibility. This field contains the patient's county code. The county can now be supported in the county/parish code component of the XAD data type (PID-11 - Patient Address). Refer to User-defined Table 0289 - County/parish for suggested values
Components:
[NNN] [(999)]999-9999 [X99999] [B99999] [C any text] ^ <telecommunication
use code (ID)> ^ <telecommunication equipment type (ID)> ^ <e-mail
address (ST)> ^ <country code (NM)> ^ <area/city code (NM)> ^
<phone number (NM)> ^ <extension (NM)> ^ <any text
(ST)>
Definition: This field contains the patient's personal phone numbers. All
personal phone numbers for the patient are sent in the following sequence. The
first sequence is considered the primary number (for backward compatibility).
If the primary number is not sent, then a repeat delimiter is sent in the first
sequence. Refer to HL7 Table 0201 - Telecommunication use code and
HL7 Table 0202 - Telecommunication equipment type for valid values.
Components:
[NNN] [(999)]999-9999 [X99999] [B99999] [C any text] ^ <telecommunication
use code (ID)> ^ <telecommunication equipment type (ID)> ^ <e-mail
address (ST)> ^ <country code (NM)> ^ <area/city code (NM)> ^
<phone number (NM)> ^ <extension (NM)> ^ <any text
(ST)>
Definition: This field contains the patient's business telephone numbers. All
business numbers for the patient are sent in the following sequence. The first
sequence is considered the patient's primary business phone number (for
backward compatibility). If the primary business phone number is not sent,
then a repeat delimiter must be sent in the first sequence. Refer to HL7
Table 0201 - Telecommunication use code and HL7 Table 0202 -
Telecommunication equipment type for valid values.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the patient's primary language. HL7
recommends using ISO table 639 as the suggested values in User-defined Table
0296 - Primary Language.
Value |
Description |
|---|---|
No suggested values defined |
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the patient's marital (civil) status. Refer
to User-defined Table 0002 - Marital status for suggested values.
Value |
Description |
|---|---|
A |
Separated |
D |
Divorced |
M |
Married |
S |
Single |
W |
Widowed |
C |
Common law |
G |
Living together |
P |
Domestic partner |
R |
Registered domestic partner |
E |
Legally Separated |
N |
Annulled |
I |
Interlocutory |
B |
Unmarried |
U |
Unknown |
O |
Other |
T |
Unreported |
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the patient's religion, for example, Baptist,
Catholic, Methodist, etc. Refer to User-defined Table 0006 - Religion
for suggested values.
Value |
Description |
|---|---|
AGN |
Agnostic |
ATH |
Atheist |
BAH |
Baha'i |
BUD |
Buddhist |
BMA |
Buddhist: Mahayana |
BTH |
Buddhist: Theravada |
BTA |
Buddhist: Tantrayana |
BOT |
Buddhist: Other |
CFR |
Chinese Folk Religionist |
CHR |
Christian |
ABC |
Christian: American Baptist Church |
AMT |
Christian: African Methodist Episcopal |
AME |
Christian: African Methodist Episcopal Zion |
ANG |
Christian: Anglican |
AOG |
Christian: Assembly of God |
BAP |
Christian: Baptist |
CAT |
Christian: Roman Catholic |
CRR |
Christian: Christian Reformed |
CHS |
Christian: Christian Science |
CMA |
Christian: Christian Missionary Alliance |
COC |
Christian: Church of Christ |
COG |
Christian: Church of God |
COI |
Christian: Church of God in Christ |
COM |
Christian: Community |
COL |
Christian: Congregational |
EOT |
Christian: Eastern Orthodox |
EVC |
Christian: Evangelical Church |
EPI |
Christian: Episcopalian |
FWB |
Christian: Free Will Baptist |
FRQ |
Christian: Friends |
GRE |
Christian: Greek Orthodox |
JWN |
Christian: Jehovah's Witness |
LUT |
Christian: Lutheran |
LMS |
Christian: Lutheran Missouri Synod |
MEN |
Christian: Mennonite |
MET |
Christian: Methodist |
MOM |
Christian: Latter-day Saints |
NAZ |
Christian: Church of the Nazarene |
ORT |
Christian: Orthodox |
COT |
Christian: Other |
PRC |
Christian: Other Protestant |
PEN |
Christian: Pentecostal |
COP |
Christian: Other Pentecostal |
PRE |
Christian: Presbyterian |
PRO |
Christian: Protestant |
QUA |
Christian: Friends |
REC |
Christian: Reformed Church |
REO |
Christian: Reorganized Church of Jesus Christ-LDS |
SAA |
Christian: Salvation Army |
SEV |
Christian: Seventh Day Adventist |
SOU |
Christian: Southern Baptist |
UCC |
Christian: United Church of Christ |
UMD |
Christian: United Methodist |
UNI |
Christian: Unitarian |
UNU |
Christian: Unitarian Universalist |
WES |
Christian: Wesleyan |
WMC |
Christian: Wesleyan Methodist |
CNF |
Confucian |
ERL |
Ethnic Religionist |
HIN |
Hindu |
HVA |
Hindu: Vaishnavites |
HSH |
Hindu: Shaivites |
HOT |
Hindu: Other |
JAI |
Jain |
JEW |
Jewish |
JCO |
Jewish: Conservative |
JOR |
Jewish: Orthodox |
JOT |
Jewish: Other |
JRC |
Jewish: Reconstructionist |
JRF |
Jewish: Reform |
JRN |
Jewish: Renewal |
MOS |
Muslim |
MSU |
Muslim: Sunni |
MSH |
Muslim: Shiite |
MOT |
Muslim: Other |
NAM |
Native American |
NRL |
New Religionist |
NOE |
Nonreligious |
OTH |
Other |
SHN |
Shintoist |
SIK |
Sikh |
SPI |
Spiritist |
VAR |
Unknown |
Components:
<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check
digit scheme employed (ID)> ^ < assigning authority (HD)> ^
<identifier type code (ID)> ^ < assigning facility (HD) ^
<effective date (DT)> ^ <expiration date (DT)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the patient account number assigned by
accounting to which all charges, payments, etc., are recorded. It is used to
identify the patient's account. Refer to HL7 Table 0061 - Check digit
scheme for valid values.
Definition: This field has been retained for backward compatibility only. It is recommended to use PID-3 - Patient Identifier List for all patient identifiers. However, in order to maintain backward compatibility, this field should also be populated. When used for backward compatibility, this field contains the patient's social security number. This number may also be a RR retirement number.
Components:
<license number (ST)> ^ <issuing state, province, country (IS)> ^
<expiration date (DT)>
Definition: This field contains the patient's driver's license number. Some
sites may use this number as a unique identifier of the patient. The default
of the second component is the state in which the patient's license is
registered.
Components:
<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check
digit scheme employed (ID)> ^ < assigning authority (HD)> ^
<identifier type code (ID)> ^ < assigning facility (HD) ^
<effective date (DT)> ^ <expiration date (DT)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field is used, for example, as a link field for newborns.
Typically a patient ID or account number may be used. This field can contain
multiple identifiers for the same mother. Refer to HL7 Table 0061 - Check
digit scheme for valid values.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field further defines the patient's ancestry. Refer to
User-defined Table 0189 - Ethnic group for suggested values. The second
triplet of the CE data type for ethnic group (alternate identifier, alternate
text, and name of alternate coding system) is reserved for governmentally
assigned codes. In the US, a current use is to report ethnicity in line with US
federal standards for Hispanic origin.
Value |
Description |
|---|---|
H |
Hispanic or Latino |
N |
Not Hispanic or Latino |
U |
Unknown |
Definition: This field indicates the location of the patient's birth, for example "St. Francis Community Hospital of Lower South Side". The actual address is reported in PID-11 with an identifier of "N".
Definition: This field indicates whether the patient was part of a multiple birth. Refer to HL7 Table 0136 - Yes/No Indicator for valid values.
Definition: When a patient was part of a multiple birth, a value (number) indicating the patient's birth order is entered in this field.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the patient's country of citizenship. HL7
recommends using ISO table 3166 as the suggested values in User-defined
Table 0171 - Citizenship.
In the Netherlands, this field is used for "Nationaliteit".
Value |
Description |
|---|---|
No suggested values defined |
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the military status assigned to a veteran.
Refer to User-defined Table 0172 - Veterans military status for
suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: From V2.4 onward, this field has been retained for backward
compatibility only. It is recommended to refer to PID-10 - Race,
PID-22 - Ethnic group and PID-26 - Citizenship. This field
contains a code that identifies the nation or national grouping to which the
person belongs. This information may be different from a person's citizenship
in countries in which multiple nationalities are recognized (for example,
Spain: Basque, Catalan, etc.).
Definition: This field contains the date and time at which the patient death occurred.
Definition:
This field indicates whether the patient is deceased. Refer to HL7 Table
0136 - Yes/no indicator for valid values.
Y the patient is deceased
N the patient is not deceased
Definition:
This field indicates whether or not the patient's/person's identity is known.
Refer to HL7 Table 0136 - Yes/no indicator for suggested values.
Y the patient's/person's identity is unknown
N the patient's/person's identity is known
Definition:
This field contains a coded value used to communicate information regarding
the reliability of patient/person identifying data transmitted via a
transaction. Values could indicate that certain fields on a PID segment for a
given patient/person are known to be false (e.g., use of default or
system-generated values for Date of Birth or Social Security Number. Refer to
User-defined Table 0445 - Identity reliability code for suggested
values.
Value |
Description |
|---|---|
US |
Unknown/Default Social Security Number |
UD |
Unknown/Default Date of Birth |
UA |
Unknown/Default Address |
AL |
Patient/Person Name is an Alias |
Definition: This field contains the last update date and time for the patient's/person's identifying and demographic data, as defined in the PID segment. Receiving systems will use this field to determine how to apply the transaction to their systems. If the receiving system (such as an enterprise master patient index) already has a record for the person with a later last update date/time, then the EMPI could decide not to apply the patient's/person's demographic and identifying data from this transaction.
Definition:
This field identifies the facility of the last update to a patient's/person's
identifying and demographic data, as defined in the PID segment. Receiving
systems or users will use this field to determine how to apply the transaction
to their systems. If the receiving system (such as a hospital's patient
management system) already has a record for the patient/person, then it may
decide to only update its data if the source is a "trusted" source. A hospital
might consider other hospitals trusted sources, but not "trust" updates from
non-acute care facilities. For example:
...|Metro Hospital|...
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: The species of living organism. This may include the common or
scientific name, based on the coding system(s) used. SNOMED is the recommended
coding system. If this field is not valued, a human is assumed. Refer to
User-defined Table 0446 - Spec
ies
Code for suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Conditionality
Rule: This field must be valued if PID-36 - Breed Code or PID-38 -
Production Class Code is valued.
For example:
...|L-80700^Canine, NOS^SNM3|...
...|L-80100^Bovine^SNM3|...
...|L-80A00^Feline^SNM3|...
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: The specific breed of animal. This field, unlike Species and
Strain is specific to animals and cannot be generally used for all living
organisms. SNOMED is the recommended coding system. Refer to User-defined
Table 0447 - Breed Code for suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Conditionality
Rule: This field must be valued if PID-37 - Strain is valued.
For example, (showing primary and alternative coding systems, using locally
defined "American Kennel Club" nomenclature):
...|L-80733^ Staffordshire bull terrier^SNM3^^American Staffordshire
Terrier^99AKC|...
...|L-80900^Weimaraner^SNM3|...
...|L-80439^Peruvian Paso Horse^SNM3|...
Definition:
This field contains the specific strain of animal. It can also be expanded to
include strain of any living organism and is not restricted to animals.
Example:
...|DeKalb|...
...|Balb/c|...
...|DXL|...
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the code and/or text indicating the primary use
for which the living subject was bred or grown. Refer to User-defined Table
0429 - Production Class Code for suggested values. For example:
...|DA^Dairy^L|...
...|MT^Meat^L|...
...|RA^Racing^L|...
Value |
Description |
|---|---|
BR |
Breeding/genetic stock |
DA |
Dairy |
DR |
Draft |
DU |
Dual Purpose |
LY |
Layer, Includes Multiplier flocks |
MT |
Meat |
OT |
Other |
PL |
Pleasure |
RA |
Racing |
SH |
Show |
NA |
Not Applicable |
U |
Unknown |
The
PV1 segment is used by Registration/Patient Administration applications to
communicate information on an account or visit-specific basis. The default is
to send account level data. To use this segment for visit level data PV1-51
- visit indicator must be valued to "V". The value of PV-51 affects the
level of data being sent on the PV1, PV2, and any other segments that are part
of the associated PV1 hierarchy (e.g. ROL, DG1, or OBX).
The facility ID, the optional fourth component of each patient location field,
is a HD data type that is uniquely associated with the healthcare facility
containing the location. A given institution, or group of intercommunicating
institutions, should establish a list of facilities that may be potential
assignors of patient locations. The list will be one of the institution's
master dictionary lists. Since third parties other than the assignors of
patient locations may send or receive HL7 messages containing patient
locations, the facility ID in the patient location may not be the same as that
implied by the sending and receiving systems identified in the MSH. The
facility ID must be unique across facilities at a given site. This field is
required for HL7 implementations that have more than a single healthcare
facility with bed locations, since the same <point of care> ^
<room> ^ <bed> combination may exist at more than one facility.
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
4 |
SI |
O |
00131 |
Set ID - PV1 |
||
2 |
1 |
IS |
R |
0004 |
00132 |
Patient Class |
|
3 |
80 |
PL |
O |
00133 |
Assigned Patient Location |
||
4 |
2 |
IS |
O |
0007 |
00134 |
Admission Type |
|
5 |
250 |
CX |
O |
00135 |
Preadmit Number |
||
6 |
80 |
PL |
O |
00136 |
Prior Patient Location |
||
7 |
250 |
XCN |
O |
Y |
0010 |
00137 |
Attending Doctor |
8 |
250 |
XCN |
O |
Y |
0010 |
00138 |
Referring Doctor |
9 |
250 |
XCN |
B |
Y |
0010 |
00139 |
Consulting Doctor |
10 |
3 |
IS |
O |
0069 |
00140 |
Hospital Service |
|
11 |
80 |
PL |
O |
00141 |
Temporary Location |
||
12 |
2 |
IS |
O |
0087 |
00142 |
Preadmit Test Indicator |
|
13 |
2 |
IS |
O |
0092 |
00143 |
Re-admission Indicator |
|
14 |
6 |
IS |
O |
0023 |
00144 |
Admit Source |
|
15 |
2 |
IS |
O |
Y |
0009 |
00145 |
Ambulatory Status |
16 |
2 |
IS |
O |
0099 |
00146 |
VIP Indicator |
|
17 |
250 |
XCN |
O |
Y |
0010 |
00147 |
Admitting Doctor |
18 |
2 |
IS |
O |
0018 |
00148 |
Patient Type |
|
19 |
250 |
CX |
O |
00149 |
Visit Number |
||
20 |
50 |
FC |
O |
Y |
0064 |
00150 |
Financial Class |
21 |
2 |
IS |
O |
0032 |
00151 |
Charge Price Indicator |
|
22 |
2 |
IS |
O |
0045 |
00152 |
Courtesy Code |
|
23 |
2 |
IS |
O |
0046 |
00153 |
Credit Rating |
|
24 |
2 |
IS |
O |
Y |
0044 |
00154 |
Contract Code |
25 |
8 |
DT |
O |
Y |
00155 |
Contract Effective Date |
|
26 |
12 |
NM |
O |
Y |
00156 |
Contract Amount |
|
27 |
3 |
NM |
O |
Y |
00157 |
Contract Period |
|
28 |
2 |
IS |
O |
0073 |
00158 |
Interest Code |
|
29 |
1 |
IS |
O |
0110 |
00159 |
Transfer to Bad Debt Code |
|
30 |
8 |
DT |
O |
00160 |
Transfer to Bad Debt Date |
||
31 |
10 |
IS |
O |
0021 |
00161 |
Bad Debt Agency Code |
|
32 |
12 |
NM |
O |
00162 |
Bad Debt Transfer Amount |
||
33 |
12 |
NM |
O |
00163 |
Bad Debt Recovery Amount |
||
34 |
1 |
IS |
O |
0111 |
00164 |
Delete Account Indicator |
|
35 |
8 |
DT |
O |
00165 |
Delete Account Date |
||
36 |
3 |
IS |
O |
0112 |
00166 |
Discharge Disposition |
|
37 |
25 |
CM |
O |
0113 |
00167 |
Discharged to Location |
|
38 |
250 |
CE |
O |
0114 |
00168 |
Diet Type |
|
39 |
2 |
IS |
O |
0115 |
00169 |
Servicing Facility |
|
40 |
1 |
IS |
B |
0116 |
00170 |
Bed Status |
|
41 |
2 |
IS |
O |
0117 |
00171 |
Account Status |
|
42 |
80 |
PL |
O |
00172 |
Pending Location |
||
43 |
80 |
PL |
O |
00173 |
Prior Temporary Location |
||
44 |
26 |
TS |
O |
00174 |
Admit Date/Time |
||
45 |
26 |
TS |
O |
Y |
00175 |
Discharge Date/Time |
|
46 |
12 |
NM |
O |
00176 |
Current Patient Balance |
||
47 |
12 |
NM |
O |
00177 |
Total Charges |
||
48 |
12 |
NM |
O |
00178 |
Total Adjustments |
||
49 |
12 |
NM |
O |
00179 |
Total Payments |
||
50 |
250 |
CX |
O |
0203 |
00180 |
Alternate Visit ID |
|
51 |
1 |
IS |
O |
0326 |
01226 |
Visit Indicator |
|
52 |
250 |
XCN |
B |
Y |
0010 |
01274 |
Other Healthcare Provider |
Definition: This field contains the number that identifies this transaction. For the first occurrence of the segment, the sequence number shall be one, for the second occurrence, the sequence number shall be two, etc.
Definition:
This field is used by systems to categorize patients by site. It does not
have a consistent industry-wide definition. It is subject to site-specific
variations. Refer to User-
defined
Table 0004 - Patient class for suggested values.
Value |
Description |
|---|---|
E |
Emergency |
I |
Inpatient |
O |
Outpatient |
P |
Preadmit |
R |
Recurring patient |
B |
Obstetrics |
C |
Commercial Account |
N |
Not Applicable |
U |
Unknown |
"Commercial
Account" is used by reference labs for specimen processing when the service is
billed back to a third party. A registration is processed for the specimen to
facilitate the subsequent billing. The identity of the patient may be known or
unknown. In either case, for billing and statistical purposes, the patient
class is considered a commercial account due to the third party billing
responsibility.
"Not Applicable" is used only in cases where the PV1 segment itself is not
applicable but is retained in the message definitions for backwards
compatibility (for example when a managed care system sends A28, A29, or A31
messages to indicate the enrolment of a patient in the system and there is no
scheduled "visit" or "encounter" and hence the entire PV1 segment is not
applicable).
Components:
<point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^
<facility (HD)> ^ <location status (IS)> ^ <person location
type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location
description (ST)
Subcomponents of facility: <namespace ID (IS)> & <universal ID
(ST)> & <universal ID type (ID)>
Definition: This field contains the patient's initial assigned location or the
location to which the patient is being moved. The first component may be the
nursing station for inpatient locations, or clinic or department, for locations
other than inpatient. For canceling a transaction or discharging a patient,
the current location (after the cancellation event or before the discharge
event) should be in this field. If a value exists in the fifth component
(location status), it supersedes the value in PV1-40 - Bed Status.
Definition:
This field indicates the circumstances under which the patient was or will be
admitted. Refer to User-defined Table 0007 - Admission type for
suggested values. In the US, it is recommended to report the UB92 FL 19 "Type
of Admission" in this field.
Value |
Description |
Comments |
|---|---|---|
A |
Accident |
|
E |
Emergency |
US UB92 code "1" |
L |
Labor and Delivery |
|
R |
Routine |
|
N |
Newborn (Birth in healthcare facility) |
US UB92 code "4" |
U |
Urgent |
US UB92 code "2" |
C |
Elective |
US UB92 code "3" |
Components:
<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check
digit scheme employed (ID)> ^ < assigning authority (HD)> ^
<identifier type code (ID)> ^ < assigning facility (HD) ^
<effective date (DT)> ^ <expiration date (DT)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field uniquely identifies the patient's pre-admit account.
Some systems will continue to use the pre-admit number as the billing number
after the patient has been admitted. For backward compatibility, a ST data
type can be sent; however HL7 recommends use of the CX data type, like the
account number, for new implementations. The assigning authority and
identifier type code are strongly recommended for all CX data types.
Components:
<point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^
<facility (HD)> ^ <location status (IS)> ^ <person location
type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location
description (ST)
Subcomponents of facility: <namespace ID (IS)> & <universal ID
(ST)> & <universal ID type (ID)>
Definition: This field contains the prior patient location if the patient is
being transferred. The old location is null if the patient is new. If a value
exists in the fifth component (location status), it supersedes the value in
PV1-40 - bed status.
Components:
<ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^
<second and further given names or initials thereof (ST)> ^ <suffix
(e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g.,
MD) (IS)> ^ <source table (IS)> ^ <assigning authority (HD)> ^
<name type code (ID)> ^ <identifier check digit (ST)> ^ <code
identifying the check digit scheme employed (ID)> ^ <identifier type code
(IS)> ^ <assigning facility (HD)> ^ <name representation code
(ID)> ^ <name context (CE)> ^ <name validity range (DR)>
Subcomponents of family name: <family name (ST)> & <own family
name prefix (ST)> & <own family name (ST)> & <family name
prefix from partner/spouse (ST)> & <family name from partner/spouse
(ST)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the attending physician information. Multiple
names and identifiers for the same physician may be sent. The field sequences
are not used to indicate multiple attending doctors. The legal name must be
sent in the first sequence. If the legal name is not sent, then a repeat
delimiter must be sent in the first sequence. Depending on local agreements,
either ID or the name may be absent in this field. Refer to User-defined
Table 0010 - Physician ID for suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Components:
<ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^
<second and further given names or initials thereof (ST)> ^ <suffix
(e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g.,
MD) (IS)> ^ <source table (IS)> ^ <assigning authority (HD)> ^
<name type code (ID)> ^ <identifier check digit (ST)> ^ <code
identifying the check digit scheme employed (ID)> ^ <identifier type code
(IS)> ^ <assigning facility (HD)> ^ <name representation code
(ID)> ^ <name context (CE)> ^ <name validity range (DR)>
Subcomponents of family name: <family name (ST)> & <own family
name prefix (ST)> & <own family name (ST)> & <family name
prefix from partner/spouse (ST)> & <family name from partner/spouse
(ST)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the referring physician information. Multiple
names and identifiers for the same physician may be sent. The field sequences
are not used to indicate multiple referring doctors. The legal name must be
sent in the first sequence. If the legal name is not sent, then a repeat
delimiter must be sent in the first sequence. Depending on local agreements,
either the ID or the name may be absent from this field. Refer to
User-defined Table 0010 - Physician ID for suggested values.
Components:
<ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^
<second and further given names or initials thereof (ST)> ^ <suffix
(e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g.,
MD) (IS)> ^ <source table (IS)> ^ <assigning authority (HD)> ^
<name type code (ID)> ^ <identifier check digit (ST)> ^ <code
identifying the check digit scheme employed (ID)> ^ <identifier type code
(IS)> ^ <assigning facility (HD)> ^ <name representation code
(ID)> ^ <name context (CE)> ^ <name validity range (DR)>
Subcomponents of family name: <family name (ST)> & <own family
name prefix (ST)> & <own family name (ST)> & <family name
prefix from partner/spouse (ST)> & <family name from partner/spouse
(ST)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field has been retained for backward compatibility only.
It is recommended to use the ROL - Role segment for consulting physicians
instead. This field contains the consulting physician information. The field
sequences are used to indicate multiple consulting doctors. Depending on local
agreements, either the ID or the name may be absent from this field. Refer to
User-defined Table 0010 - Physician ID for suggested values.
Definition:
This field contains the treatment or type of surgery that the patient is
scheduled to receive. It is a required field with trigger events A01
(admit/visit notification), A02 (transfer a patient), A14 (pending admit), A15
(pending transfer). Refer to User-defined Table 0069 - Hospital service
for suggested values.
Values |
Description |
|---|---|
MED |
Medical Service |
SUR |
Surgical Service |
URO |
Urology Service |
PUL |
Pulmonary Service |
CAR |
Cardiac Service |
Components:
<point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^
<facility (HD)> ^ <location status (IS)> ^ <person location
type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location
description (ST)>
Subcomponents of facility: <namespace ID (IS)> & <universal
ID (ST)> & <universal ID type (ID)>
Definition: This field contains a location other than the assigned location
required for a temporary period of time (e.g., OR, operating theatre, etc.).
If a value exists in the fifth component (location status), it supersedes the
value in PV1-40 - bed status.
Definition:
This field indicates whether the patient must have pre-admission testing done
in order to be admitted. Refer to User-defined Table 0087 - Pre-admit test
indicator for suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Definition:
This field indicates that a patient is being re-admitted to the healthcare
facility and gives the circumstances. We suggest using "R" for
readmission or else null. Refer to User-defined Table 0092 - Re-admission
indicator for suggested values.
Value |
Description |
|---|---|
R |
Re-admission |
Definition:
This field indicates where the patient was admitted. Refer to
User-defined Table 0023 - Admit source for suggested values. In
the US, this field is used on UB92 FL20 "Source of Admission". The UB codes
listed as examples are not an exhaustive or current list; refer to a UB
specification for additional information.
Note: The official title of UB is "National Uniform Billing Data Element
Specifications." Most of the codes added came from the UB-92 specification,
but some came from the UB-82.
Value |
Description |
|---|---|
1 |
Physician referral |
2 |
Clinic referral |
3 |
HMO referral |
4 |
Transfer from a hospital |
5 |
Transfer from a skilled nursing facility |
6 |
Transfer from another health care facility |
7 |
Emergency room |
8 |
Court/law enforcement |
9 |
Information not available |
Definition:
This field indicates any permanent or transient handicapped conditions. Refer
to User-defined Table 0009 - Ambulatory status for suggested
entries.
Value |
Description |
|---|---|
A0 |
No functional limitations |
A1 |
Ambulates with assistive device |
A2 |
Wheelchair/stretcher bound |
A3 |
Comatose; non-responsive |
A4 |
Disoriented |
A5 |
Vision impaired |
A6 |
Hearing impaired |
A7 |
Speech impaired |
A8 |
Non-English speaking |
A9 |
Functional level unknown |
B1 |
Oxygen therapy |
B2 |
Special equipment (tubes, IVs, catheters) |
B3 |
Amputee |
B4 |
Mastectomy |
B5 |
Paraplegic |
B6 |
Pregnant |
Definition:
This field identifies the type of VIP. Refer to User-defined Table 0099 -
VIP indicator for suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Components:
<ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^
<second and further given names or initials thereof (ST)> ^ <suffix
(e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g.,
MD) (IS)> ^ <source table (IS)> ^ <assigning authority (HD)> ^
<name type code (ID)> ^ <identifier check digit (ST)> ^ <code
identifying the check digit scheme employed (ID)> ^ <identifier type code
(IS)> ^ <assigning facility (HD)> ^ <name representation code
(ID)> ^ <name context (CE)> ^ <name validity range (DR)>
Subcomponents of family name: <family name (ST)> & <own family
name prefix (ST)> & <own family name (ST)> & <family name
prefix from partner/spouse (ST)> & <family name from partner/spouse
(ST)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the admitting physician information. Multiple
names and identifiers for the same physician may be sent. The field sequences
are not used to indicate multiple admitting doctors. The legal name must be
sent in the first sequence. If the legal name is not sent, then a repeat
delimiter must be sent in the first sequence. By local agreement, the name or
ID may be absent in this field. Refer to User-defined Table 0010 -
Physician ID for suggested values.
Definition:
This field contains site-specific values that identify the patient type. Refer
to User-defined Table 0018 - Patient type for suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Components:
<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check
digit scheme employed (ID)> ^ < assigning authority (HD)> ^
<identifier type code (ID)> ^ < assigning facility (HD) ^
<effective date (DT)> ^ <expiration date (DT)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: For backward compatibility, a NM data type may be sent, but
HL7 recommends that new implementations use the CX data type. This
field contains the unique number assigned to each patient visit. The assigning
authority and identifier type code are strongly recommended for all CX data
types.
Components:
<financial class (IS)> ^ <effective date (TS)>
Definition: This field contains the financial class(es) assigned to the
patient for the purpose of identifying sources of reimbursement. Refer to
User-defined Table 0064 - Financial class for suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Definition:
This field contains the code used to determine which price schedule is to be
used for room and bed charges. Refer to User-defined Table 0032 -
Charge/price indicator for suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Definition:
This field indicates whether the patient will be extended certain special
courtesies. Refer to User-defined Table 0045 - Courtesy code for
suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Definition:
This field contains the user-defined code to determine past credit experience.
Refer to User-defined Table 0046 - Credit rating for suggested
values.
Value |
Description |
|---|---|
No suggested values defined |
Definition:
This field identifies the type of contract entered into by the healthcare
facility and the guarantor for the purpose of settling outstanding account
balances. Refer to User-defined Table 0044 - Contract code for
suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Definition: This field contains the date that the contract is to start or started.
Definition: This field contains the amount to be paid by the guarantor each period according to the contract.
Definition: This field specifies the duration of the contract for user-defined periods.
Definition:
This field indicates the amount of interest that will be charged the guarantor
on any outstanding amounts. Refer to User-defined Table 0073 - Interest
rate code for suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Definition:
This field indicates that the account was transferred to bad debts and gives
the reason. Refer to User-defined Table 0110 - Transfer to bad debt
code for suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Definition: This field contains the date that the account was transferred to a bad debt status.
Definition:
This field can be used as a ST type for backward compatibility. This
field uniquely identifies the bad debt agency to which the account was
transferred. This code is site defined. One possible implementation would be
to edit against a table such as User-defined Table 0021 - Bad debt agency
code; however, this is not required.
Value |
Description |
|---|---|
No suggested values defined |
Definition: This field contains the amount that was transferred to a bad debt status.
Definition: This field contains the amount recovered from the guarantor on the account.
Definition:
This field indicates that the account was deleted from the file and gives the
reason. Refer to User-defined Table 0111 - Delete account code for
suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Definition: This field contains the date that the account was deleted from the file.
Definition:
This field contains the disposition of the patient at time of discharge (i.e.,
discharged to home, expired, etc.). Refer to User-defined Table 0112 -
Discharge disposition for suggested values. In the US, this field is
used on UB92 FL22. The UB codes listed as examples are not an exhaustive or
current list; refer to a UB specification for additional information.
Value |
Description |
|---|---|
01 |
Discharged to home or self care (routine discharge) |
02 |
Discharged/transferred to another short term general hospital for inpatient care |
03 |
Discharged/transferred to skilled nursing facility (SNF) |
04 |
Discharged/transferred to an intermediate care facility (ICF) |
05 |
Discharged/transferred to another type of institution for inpatient care or referred for outpatient services to another institution |
06 |
Discharged/transferred to home under care of organized home health service organization |
07 |
Left against medical advice or discontinued care |
08 |
Discharged/transferred to home under care of Home IV provider |
09 |
Admitted as an inpatient to this hospital |
10 ...19 |
Discharge to be defined at state level, if necessary |
20 |
Expired (i.e. dead) |
21 ... 29 |
Expired to be defined at state level, if necessary |
30 |
Still patient or expected to return for outpatient services (i.e. still a patient) |
31 ... 39 |
Still patient to be defined at state level, if necessary (i.e. still a patient) |
40 |
Expired (i.e. died) at home |
41 |
Expired (i.e. died) in a medical facility; e.g., hospital, SNF, ICF, or free standing hospice |
42 |
Expired (i.e. died) - place unknown |
Components:
<discharge location (IS)> ^ <effective date (TS)>
Definition: This field indicates the healthcare facility to which the patient
was discharged. Refer to User-defined Table 0113 - Discharged to
location for suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field indicates a special diet type for a patient. Refer to
User-defined Table 0114 - Diet type for suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Definition:
This field is used in a multiple facility environment to indicate the
healthcare facility with which this visit is associated. Refer to
User-defined Table 0115 - Servicing facility for suggested values.
Value |
Description |
|---|---|
No suggested values defined |
An optional sixth component, the facility ID, may be valued in each individual location field in PV1, instead of placing it here.
Definition:
This field has been retained for backward compatibility only. The
information is now held in the fifth component of the PL datatype in PV1-3.
This field contains the status of the bed. Refer to User-defined Table
0116 - Bed status for suggested values.
Value |
Description |
|---|---|
C |
Closed |
H |
Housekeeping |
O |
Occupied |
U |
Unoccupied |
K |
Contaminated |
I |
Isolated |
Definition:
This field contains the account status. Refer to User-defined Table 0117 -
Account status for suggested values.
Value |
Description |
|---|---|
No suggested values defined |
Components:
<point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^
<facility (HD)> ^ <location status (IS)> ^ <person location
type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location
description (ST)>
Subcomponents of facility: <namespace ID (IS)> & <universal ID
(ST)> & <universal ID type (ID)>
Definition: This field indicates the point of care, room, bed, healthcare
facility ID, and bed status to which the patient may be moved. The first
component may be the nursing station for inpatient locations, or the clinic,
department, or home for locations other than inpatient. If a value exists in
the fifth component (location status), it supersedes the value in PV1-40 -
bed status.
Components:
<point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^
<facility (HD)> ^ <location status (IS)> ^ <person location
type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location
description (ST)>
Subcomponents of facility: <namespace ID (IS)> & <universal ID
(ST)> & <universal ID type (ID)>
Definition: This field is used to reflect the patient's temporary location
(such as the operating room/theatre or x-ray) prior to a transfer from a
temporary location to an actual location, or from a temporary location to
another temporary location. The first component may be the nursing station for
inpatient locations, or the clinic, department, or home for locations other
than inpatient.
Definition: This field contains the admit date/time. It is to be used if the event date/time is different than the admit date and time, i.e., a retroactive update. This field is also used to reflect the date/time of an outpatient/emergency patient registration.
Definition: This field contains the discharge date/time. It is to be used if the event date/time is different than the discharge date and time, that is, a retroactive update. This field is also used to reflect the date/time of an outpatient/emergency patient discharge.
Definition: This field contains the visit balance due.
Definition: This field contains the total visit charges.
Definition: This field contains the total adjustments for visit.
Definition: This field contains the total payments for visit.
Components:
<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check
digit scheme employed (ID)> ^ < assigning authority (HD)> ^
<identifier type code (ID)> ^ < assigning facility (HD) ^
<effective date (DT)> ^ <expiration date (DT)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the alternative, temporary, or pending
optional visit ID number to be used if needed. Refer to HL7 Table 0061 -
Check digit scheme for valid values. Refer to HL7 Table 0203 -
Identifier type for valid values. The assigning authority and
identifier type code are strongly recommended for all CX data types.
Definition:
This field specifies the level on which data are being sent. It is the
indicator used to send data at two levels, visit and account. HL7 recommends
sending an `A' or no value when the data in the message are at the account
level, or `V' to indicate that the data sent in the message are at the visit
level. Refer to User-defined Table 0326 - Visit indicator for suggested
values.
The value of this element affects the context of data sent in PV1, PV2 and any
associated hierarchical segments (e.g. DB1, AL1, DG1, etc.).
Value |
Description |
|---|---|
A |
Account level (default) |
V |
Visit level |
Components:
<ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^
<second and further given names or initials thereof (ST)> ^ <suffix
(e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g.,
MD) (IS)> ^ <source table (IS)> ^ <assigning authority (HD)> ^
<name type code (ID)> ^ <identifier check digit (ST)> ^ <code
identifying the check digit scheme employed (ID)> ^ <identifier type code
(IS)> ^ <assigning facility (HD)> ^ <name representation code
(ID)> ^ <name context (CE) ^ <name validity range (DR)>
Subcomponents of family name: <family name (ST)> & <own family
name prefix (ST)> & <own family name (ST)> & <family name
prefix from partner/spouse (ST)> & <family name from partner/spouse
(ST)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field has been retained for backward compatibility
only. Use the ROL-Role Segment to communicate providers not specified
elsewhere. Refer to section 12.3.3 for the definition of the ROL segment.
This field contains the other healthcare providers (e.g. nurse care
practitioner, midwife, physician assistant). Multiple healthcare providers can
be sent. Depending on local agreements, either the ID or the name may be
absent from this field. Use values in User-defined Table 0010 - Physician
ID for first component.
The
PV2 segment is a continuation of information contained on the PV1 segment.
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
80 |
PL |
C |
00181 |
Prior Pending Location |
||
2 |
250 |
CE |
O |
0129 |
00182 |
Accommodation Code |
|
3 |
250 |
CE |
O |
00183 |
Admit Reason |
||
4 |
250 |
CE |
O |
00184 |
Transfer Reason |
||
5 |
25 |
ST |
O |
Y |
00185 |
Patient Valuables |
|
6 |
25 |
ST |
O |
00186 |
Patient Valuables Location |
||
7 |
2 |
IS |
O |
Y |
0130 |
00187 |
Visit User Code |
8 |
26 |
TS |
O |
00188 |
Expected Admit Date/Time |
||
9 |
26 |
TS |
O |
00189 |
Expected Discharge Date/Time |
||
10 |
3 |
NM |
O |
00711 |
Estimated Length of Inpatient Stay |
||
11 |
3 |
NM |
O |
00712 |
Actual Length of Inpatient Stay |
||
12 |
50 |
ST |
O |
00713 |
Visit Description |
||
13 |
250 |
XCN |
O |
Y |
00714 |
Referral Source Code |
|
14 |
8 |
DT |
O |
00715 |
Previous Service Date |
||
15 |
1 |
ID |
O |
0136 |
00716 |
Employment Illness Related Indicator |
|
16 |
1 |
IS |
O |
0213 |
00717 |
Purge Status Code |
|
17 |
8 |
DT |
O |
00718 |
Purge Status Date |
||
18 |
2 |
IS |
O |
0214 |
00719 |
Special Program Code |
|
19 |
1 |
ID |
O |
0136 |
00720 |
Retention Indicator |
|
20 |
1 |
NM |
O |
00721 |
Expected Number of Insurance Plans |
||
21 |
1 |
IS |
O |
0215 |
00722 |
Visit Publicity Code |
|
22 |
1 |
ID |
O |
0136 |
00723 |
Visit Protection Indicator |
|
23 |
250 |
XON |
O |
Y |
00724 |
Clinic Organization Name |
|
24 |
2 |
IS |
O |
0216 |
00725 |
Patient Status Code |
|
25 |
1 |
IS |
O |
0217 |
00726 |
Visit Priority Code |
|
26 |
8 |
DT |
O |
00727 |
Previous Treatment Date |
||
27 |
2 |
IS |
O |
0112 |
00728 |
Expected Discharge Disposition |
|
28 |
8 |
DT |
O |
00729 |
Signature on File Date |
||
29 |
8 |
DT |
O |
00730 |
First Similar Illness Date |
||
30 |
250 |
CE |
O |
0218 |
00731 |
Patient Charge Adjustment Code |
|
31 |
2 |
IS |
O |
0219 |
00732 |
Recurring Service Code |
|
32 |
1 |
ID |
O |
0136 |
00733 |
Billing Media Code |
|
33 |
26 |
TS |
O |
00734 |
Expected Surgery Date and Time |
||
34 |
1 |
ID |
O |
0136 |
00735 |
Military Partnership Code |
|
35 |
1 |
ID |
O |
0136 |
00736 |
Military Non-Availability Code |
|
36 |
1 |
ID |
O |
0136 |
00737 |
Newborn Baby Indicator |
|
37 |
1 |
ID |
O |
0136 |
00738 |
Baby Detained Indicator |
|
38 |
250 |
CE |
O |
0430 |
01543 |
Mode of Arrival Code |
|
39 |
250 |
CE |
O |
Y |
0431 |
01544 |
Recreational Drug Use Code |
40 |
250 |
CE |
O |
0432 |
01545 |
Admission Level of Care Code |
|
41 |
250 |
CE |
O |
Y |
0433 |
01546 |
Precaution Code |
42 |
250 |
CE |
O |
0434 |
01547 |
Patient Condition Code |
|
43 |
2 |
IS |
O |
0315 |
00759 |
Living Will Code |
|
44 |
2 |
IS |
O |
0316 |
00760 |
Organ Donor Code |
|
45 |
250 |
CE |
O |
Y |
0435 |
01548 |
Advance Directive Code |
46 |
8 |
DT |
O |
01549 |
Patient Status Effective Date |
||
47 |
26 |
TS |
C |
01550 |
Expected LOA Return Date/Time |
Components:
<point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^
<facility (HD)> ^ <location status (IS)> ^ <person location
type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location
description (ST)>
Subcomponents of facility: <namespace ID (IS)> & <universal ID
(ST)> & <universal ID type (ID)>
Definition: This field is required for cancel pending transfer (A26) messages.
In all other events it is optional.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field indicates the specific patient accommodations for this
visit. Refer to User-defined Table 0129 - Accommodation code for
suggested values.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the short description of the reason for
patient admission.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the short description of the reason for a
patient location change.
Definition: This field contains the short description of patient valuables checked in during admission.
Definition: This field indicates the location of the patient's valuables.
Definition:
This field further categorizes a patient's visit with respect to an individual
institution's needs, and is expected to be site-specific. Refer to
User-defined Table 0130 - Visit user code for suggested values.
Value |
Description |
|---|---|
TE |
Teaching |
HO |
Home |
MO |
Mobile Unit |
PH |
Phone |
Definition: This field contains the date and time that the patient is expected to be admitted. This field is also used to reflect the date/time of an outpatient/emergency patient registration.
Definition: This field contains the date and time that the patient is expected to be discharged. This is a non-event related date used by ancillaries to determine more accurately the projected workloads. This field is also used to reflect the anticipated discharge date/time of an outpatient/emergency patient, or an inpatient.
Definition: This field specifies the estimated days of inpatient stays.
Definition: This field contains the actual days of inpatient stays. The actual length of the inpatient stay may not be calculated from the admission and discharge dates because of possible leaves of absence.
Definition: This field contains a brief user-defined description of the visit.
Components:
<ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^
<second and further given names or initials thereof (ST)> ^ <suffix
(e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g.,
MD) (IS)> ^ <source table (IS)> ^ <assigning authority (HD)> ^
<name type code (ID)> ^ <identifier check digit (ST)> ^ <code
identifying the check digit scheme employed (ID)> ^ <identifier type code
(IS)> ^ <assigning facility (HD)> ^ <name representation code
(ID)> ^ <name context (CE) ^ <name validity range (DR)>
Subcomponents of family name: <family name (ST)> & <own family
name prefix (ST)> & <own family name (ST)> & <family name
prefix from partner/spouse (ST)> & <family name from partner/spouse
(ST)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the name and the identification numbers of the
person or organization that made the referral. This person/organization is not
the same as the referring doctor. For example, Joe Smith referred me to the
Clinic (or to Dr. Jones at the Clinic).
Definition: This field contains the date of previous service for the same recurring condition. This may be a required field for billing certain illnesses (e.g., accident related) to a third party.
Definition: This field specifies whether a patient's illness was job-related. Refer to HL7 Table 0136 - Yes/no indicator for valid values.
Definition:
This field contains the purge status code for the account. It is used by the
application program to determine purge processing. Refer to User-defined
Table 0213 - Purge status code for suggested values.
Value |
Description |
|---|---|
P |
Marked for purge. User is no longer able to update the visit. |
D |
The visit is marked for deletion and the user cannot enter new data against it. |
I |
The visit is marked inactive and the user cannot enter new data against it. |
Definition: This field contains the date on which the data will be purged from the system.
Definition:
This field designates the specific health insurance program for a visit
required for healthcare reimbursement. Examples include Child Health
Assistance, Elective Surgery Program, Family Planning, etc. Refer to
User-defined Table 0214 - Special program codes for suggested
values.
Value |
Description |
|---|---|
No suggested values |
Definition: This field allows the user to control the financial and demographic purge processes at the visit. It is used to preserve demographic and financial data on specific, high priority visits. Refer to HL7 Table 0136 - Yes/no indicator for valid values.
Definition: This field contains the number of insurance plans that may provide coverage for this visit.
Definition: This field contains a user-defined code indicating what level of publicity is allowed (e.g., No Publicity, Family Only) for a specific visit. Refer to User-defined Table 0215 - Publicity code for suggested values. Refer to PD1-11 - publicity code for the patient level publicity code.
Definition: This field identifies the person's protection that determines, in turn, whether access to information about this person should be kept from users who do not have adequate authority for a specific visit. Refer to HL7 Table 0136 - Yes/no indicator for valid values. Refer to PD1-12 - protection indicator for the patient level protection indicator.
Components:
<organization name (ST)> ^ <organization name type code (ID)> ^
<ID number (ID)> ^ <check digit (NM)> ^ < check digit scheme
(ID)> ^ <assigning authority (HD)> ^ <identifier type code (ID)>
^ <assigning facility (HD)> ^ <name representation code
(ID)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the organization name or sub-unit and
identifier that is associated with the (visit) episode of care. For example,
the Allergy or Oncology Clinic within the healthcare facility might be named.
Definition:
This field indicates the status of the episode of care: for instance, Active
Inpatient, Discharged Inpatient. Refer to User-defined Table 0216 -
Patient status for suggested values.
Value |
Description |
|---|---|
No suggested values |
Definition:
This field contains the priority of the visit. Refer to User-defined
Table 0217 - Visit priority code for suggested values.
Value |
Description |
|---|---|
1 |
Emergency |
2 |
Urgent |
3 |
Elective |
Definition: This field contains the date that the patient last had treatment for any condition prior to this visit. In the case of a prior hospital visit, it is likely to be the previous discharge date.
Definition: This field describes what the patient's disposition is expected to be at the end of the visit. Refer to User-defined Table 0112 - Discharge disposition for suggested values.
Definition: This field contains the date on which a signature was obtained for insurance billing purposes.
Definition: This field is used to determine if the patient has a pre-existing condition.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains a user-defined code that indicates which
adjustments should be made to this patient's charges. Refer to User-defined
Table 0218 - Charge adjustment for suggested values. This field is the
same as GT1-26 - guarantor charge adjustment code.
Definition:
This field indicates whether the treatment is continuous. Refer to
User-defined Table 0219 - Recurring service for suggested
values.
Value |
Description |
|---|---|
No selected values |
Definition: This field indicates if the account is to be rejected from tape billing. Refer to HL7 Table 0136 - Yes/no indicator for valid values.
Definition: This field contains the date and time on which the surgery is expected to occur.
Definition: This field indicates that a military healthcare facility has contracted with a non-military healthcare facility for the use of its services. Refer to HL7 Table 0136 - Yes/no indicator for valid values.
Definition: This field indicates whether a patient has permission to use a non-military healthcare facility for treatment. Refer to HL7 Table 0136 - Yes/no indicator for valid values.
Definition: This field indicates whether the patient is a baby. Refer to HL7 Table 0136 - Yes/no indicator for valid values.
Definition: This field indicates if the baby is detained after the mother's discharge. Refer to HL7 Table 0136 - Yes/no indicator for valid values.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: Identifies how the patient was brought to the healthcare facility.
Refer to User-defined Table 0430 - Mode of arrival code for suggested
values.
Value |
Description |
|---|---|
A |
Ambulance |
C |
Car |
F |
On foot |
H |
Helicopter |
P |
Public Transport |
O |
Other |
U |
Unknown |
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field indicates what recreational drugs the patient uses. It
is used for the purpose of room assignment. Refer to User-defined Table
0431 - Recreational drug use code for suggested values.
Value |
Description |
|---|---|
A |
Alcohol |
K |
Kava |
M |
Marijuana |
T |
Tobacco - smoked |
C |
Tobacco - chewed |
O |
Other |
U |
Unknown |
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field indicates the acuity level assigned to the patient at
the time of admission. Refer to User-defined Table 0432 - Admission level
of care code for suggested values.
Value |
Description |
|---|---|
AC |
Acute |
CH |
Chronic |
CO |
Comatose |
CR |
Critical |
IM |
Improved |
MO |
Moribund |
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field indicates non-clinical precautions that need to be
taken with the patient. Refer to User-defined Table 0433 - Precaution
code for suggested values.
Value |
Description |
|---|---|
A |
Aggressive |
B |
Blind |
C |
Confused |
D |
Deaf |
I |
On IV |
N |
"No-code" (i.e. Do not resuscitate) |
P |
Paraplegic |
O |
Other |
U |
Unknown |
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field indicates the patient's current medical condition for
the purpose of communicating to non-medical outside parties, e.g. family,
employer, religious minister, media, etc,. Refer to User-defined Table
0434 - Patient condition code for suggested values.
Value |
Description |
|---|---|
A |
Satisfactory |
C |
Critical |
P |
Poor |
S |
Stable |
O |
Other |
U |
Unknown |
Definition:
This field indicates whether or not the patient has a living will and, if so,
whether a copy of the living will is on file at the healthcare facility. If
the patient does not have a living will, the value of this field indicates
whether the patient was provided information on living wills. Refer to
User-defined
Table 0315 - Living will code for suggested values. See also PD1-7 -
Living will code.
Value |
Description |
|---|---|
Y |
Yes, patient has a living will |
F |
Yes, patient has a living will but it is not on file |
N |
No, patient does not have a living will and no information was provided |
I |
No, patient does not have a living will but information was provided |
U |
Unknown |
Definition:
This field indicate whether the patient wants to donate his/her organs and
whether an organ donor card or similar documentation is on file with the
healthcare organization. Refer to
User-defined
Table 0316 - Organ donor code for suggested values. See also PD1-8 -
Organ donor.
Value |
Description |
|---|---|
Y |
Yes, patient is a documented donor and documentation is on file |
F |
Yes, patient is a documented donor, but documentation is not on file |
N |
No, patient has not agreed to be a donor |
I |
No, patient is not a documented donor, but information was provided |
R |
Patient leaves organ donation decision to relatives |
P |
Patient leaves organ donation decision to a specific person |
U |
Unknown |
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field indicates the patient's instructions to the healthcare
facility. Refer to User-defined Table 0435 - Advance directive
code for suggested values. See also PD1-15 - Advance directive
code.
Value |
Description |
|---|---|
DNR |
Do not resuscitate |
Definition: This field indicates the effective date for PV2-24 - Patient Status.
Definition: This field is conditionally required for A21 - Patient goes on LOA. It may be populated in A22 - Patient returns from LOA as well as in the A53 - Cancel LOA for a patient and the A54 - Cancel patient returns from LOA triggers. This field contains the date/time that the patient is expected to return from LOA.
The
NK1 segment contains information about the patient's other related parties.
Any associated parties may be identified. Utilizing NK1-1 - set ID,
multiple NK1 segments can be sent to patient accounts.
If a person or organization fulfills multiple contact roles, for example, a
person is an emergency contact and a next of kin, it is recommended to send a
NK1 segment for each contact role (field 7).
SEQ |
LEN |
DT |
OPT |
R P/# |
TBL# |
ITEM# |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
4 |
SI |
R |
00190 |
Set ID - NK1 |
||
2 |
250 |
XPN |
O |
Y |
00191 |
Name |
|
3 |
250 |
CE |
O |
0063 |
00192 |
Relationship |
|
4 |
250 |
XAD |
O |
Y |
00193 |
Address |
|
5 |
250 |
XTN |
O |
Y |
00194 |
Phone Number |
|
6 |
250 |
XTN |
O |
Y |
00195 |
Business Phone Number |
|
7 |
250 |
CE |
O |
0131 |
00196 |
Contact Role |
|
8 |
8 |
DT |
O |
00197 |
Start Date |
||
9 |
8 |
DT |
O |
00198 |
End Date |
||
10 |
60 |
ST |
O |
00199 |
Next of Kin / Associated Parties Job Title |
||
11 |
20 |
JCC |
O |
0327/0328 |
00200 |
Next of Kin / Associated Parties Job Code/Class |
|
12 |
250 |
CX |
O |
00201 |
Next of Kin / Associated Parties Employee Number |
||
13 |
250 |
XON |
O |
Y |
00202 |
Organization Name - NK1 |
|
14 |
250 |
CE |
O |
0002 |
00119 |
Marital Status |
|
15 |
1 |
IS |
O |
0001 |
00111 |
Administrative Sex |
|
16 |
26 |
TS |
O |
00110 |
Date/Time of Birth |
||
17 |
2 |
IS |
O |
Y |
0223 |
00755 |
Living Dependency |
18 |
2 |
IS |
O |
Y |
0009 |
00145 |
Ambulatory Status |
19 |
250 |
CE |
O |
Y |
0171 |
00129 |
Citizenship |
20 |
250 |
CE |
O |
0296 |
00118 |
Primary Language |
|
21 |
2 |
IS |
O |
0220 |
00742 |
Living Arrangement |
|
22 |
250 |
CE |
O |
0215 |
00743 |
Publicity Code |
|
23 |
1 |
ID |
O |
0136 |
00744 |
Protection Indicator |
|
24 |
2 |
IS |
O |
0231 |
00745 |
Student Indicator |
|
25 |
250 |
CE |
O |
0006 |
00120 |
Religion |
|
26 |
250 |
XPN |
O |
Y |
00109 |
Mother's Maiden Name |
|
27 |
250 |
CE |
O |
0212 |
00739 |
Nationality |
|
28 |
250 |
CE |
O |
Y |
0189 |
00125 |
Ethnic Group |
29 |
250 |
CE |
O |
Y |
0222 |
00747 |
Contact Reason |
30 |
250 |
XPN |
O |
Y |
00748 |
Contact Person's Name |
|
31 |
250 |
XTN |
O |
Y |
00749 |
Contact Person's Telephone Number |
|
32 |
250 |
XAD |
O |
Y |
00750 |
Contact Person's Address |
|
33 |
250 |
CX |
O |
Y |
00751 |
Next of Kin/Associated Party's Identifiers |
|
34 |
2 |
IS |
O |
0311 |
00752 |
Job Status |
|
35 |
250 |
CE |
O |
Y |
0005 |
00113 |
Race |
36 |
2 |
IS |
O |
0295 |
00753 |
Handicap |
|
37 |
16 |
ST |
O |
00754 |
Contact Person Social Security Number |
Definition: This field contains the number that identifies this transaction. For the first occurrence of the segment, the sequence number shall be one, for the second occurrence, the sequence number shall be two, etc.
Components:
In Version 2.3, replaces the PN data type. <family name (FN)> ^
<given name (ST)> ^ <second and further given names or initials
thereof (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g.,
DR) (ST)> ^ <degree (e.g., MD) (IS)> ^ <name type code (ID)
> ^ <name representation code (ID)> ^ <name context (CE)> ^
<name validity range (DR)> ^ <name assembly order (ID)>
Subcomponents of family name: <family name (ST)> & <own family
name prefix (ST)> & <own family name (ST)> & <family name
prefix from partner/spouse (ST)> & <family name from partner/spouse
(ST)>
Definition: This field contains the name of the next of kin or associated
party. Multiple names for the same person are allowed, but the legal name must
be sent in the first sequence. If the legal name is not sent, then the repeat
delimiter must be sent in the first sequence. Refer to HL7 Table 0200 -
Name type for valid values.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the actual personal relationship that the next
of kin/associated party has to the patient. Refer to User-defined Table
0063 - Relationship for suggested values.
Value |
Description |
|---|---|
SEL |
Self |
SPO |
Spouse |
DOM |
Life partner |
CHD |
Child |
GCH |
Grandchild |
NCH |
Natural child |
SCH |
Stepchild |
FCH |
Foster child |
DEP |
Handicapped dependent |
WRD |
Ward of court |
PAR |
Parent |
MTH |
Mother |
FTH |
Father |
CGV |
Care giver |
GRD |
Guardian |
GRP |
Grandparent |
EXF |
Extended family |
SIB |
Sibling |
BRO |
Brother |
SIS |
Sister |
FND |
Friend |
OAD |
Other adult |
EME |
Employee |
EMR |
Employer |
ASC |
Associate |
EMC |
Emergency contact |
OWN |
Owner |
TRA |
Trainer |
MGR |
Manager |
NON |
None |
UNK |
Unknown |
OTH |
Other |
Components:
In Version 2.3 and later, replaces the AD data type. <street address
(ST)> ^ <other designation (ST)> ^ <city (ST)> ^ <state or
province (ST)> ^ <zip or postal code (ST)> ^ <country (ID)> ^
< address type (ID)> ^ <other geographic designation (ST)>
^ <county/parish code (IS)> ^ <census tract (IS)> ^
<address representation code (ID)> ^ <address validity range
(DR)>
Subcomponents of street address: <street address (ST)> &
<street name (ST)> & <dwelling number (ST)>
Definition: This field contains the address of the next of kin/associated
party. Multiple addresses are allowed for the same person. The mailing
address must be sent in the first sequence. If the mailing address is not
sent, then the repeat delimiter must be sent in the first sequence.
Components:
[NNN] [(999)]999-9999 [X99999] [B99999] [C any text] ^ <telecommunication
use code (ID)> ^ <telecommunication equipment type (ID)> ^ <email
address (ST)> ^ <country code (NM)> ^ <area/city code (NM)> ^
<phone number (NM)> ^ <extension (NM)> ^ <any text
(ST)>
Definition: This field contains the telephone number of the next of
kin/associated party. Multiple phone numbers are allowed for the same person.
The primary telephone number must be sent in the first sequence. If the
primary telephone number is not sent, then the repeat delimiter must be sent in
the first sequence. Refer to HL7 Table 0201 - Telecommunication use
code and HL7 Table 0202 - Telecommunication equipment type for valid
values.
Components:
[NNN] [(999)]999-9999 [X99999] [B99999] [C any text] ^ <telecommunication
use code (ID)> ^ <telecommunication equipment type (ID)> ^ <email
address (ST)> ^ <country code (NM)> ^ <area/city code (NM)> ^
<phone number (NM)> ^ <extension (NM)> ^ <any text
(ST)>
Definition: This field contains the business telephone number of the next of
kin/associated party. Multiple phone numbers are allowed for the same person.
The primary business telephone number must be sent in the first sequence. If
the primary business telephone number is not sent, then the repeat delimiter
must be sent in the first sequence. Refer to HL7 Table 0201 -
Telecommunication use code and HL7 Table 0202 - Telecommunication
equipment type for valid values.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field indicates the specific relationship role (next of kin,
employer, emergency contact, etc.). Refer to User-defined Table 0131 -
Contact role for suggested values. This field specifies the role that
the next of kin/associated parties plays with regard to the patient. Examples
might include an employer, emergency contact, next of kin, insurance company,
state agency, federal agency, etc.
Value |
Description |
|---|---|
No suggested values |
Definition: This field contains the start date of the contact role.
Definition: This field contains the end date of the contact role.
Definition: This field contains the title of the next of kin/associated parties at their place of employment. However, if the contact role is the patient's employer, this field contains the title of the patient at their place of employment.
Components:
<job code (IS)> ^ <employee classification (IS)>
Definition: This field contains the employer's job code and the employee
classification used for the next of kin/associated parties at their place of
employment. However, if the contact role is the patient's employer, this field
contains the job code/class of the patient at their place of employment. Refer
to User-defined Table 0327 - Job code and User-defined Table 0328 -
Employee classification for suggested values.
Note: The JCC data element appears in other segments as ITEM# 00786
(GT1-50, IN2-47, STF-19). It is assigned a different ITEM# in the NK1 segment
because the element name and usage is variable. For example the job code/class
can be for the patient's employer, or for an associated party's employment
information.
Components:
<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check
digit scheme employed (ID)> ^ < assigning authority (HD)> ^
<identifier type code (ID)> ^ < assigning facility (HD) ^
<effective date (DT)> ^ <expiration date (DT)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: For backward compatibility, the ST data type can be sent;
however HL7 recommends that the CX data type be used for new implementations.
This field contains the number that the employer assigns to the employee that
is acting as next of kin/associated parties. However, if the contact role is
the patient's employer, this field contains the employee number of the patient
at their place of employment. The assigning authority and identifier type code
are strongly recommended for all CX data types.
Components:
<organization name (ST)> ^ <organization name type code (ID)> ^
<ID number (ID)> ^ <check digit (NM)> ^ < check digit scheme
(ID)> ^ <assigning authority (HD)> ^ <identifier type code (ID)>
^ <assigning facility (HD)> ^ <name representation code
(ID)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the name of the organization that serves as a
next of kin/associated party or as the next of kin of the patient. This field
may also be used to communicate the name of the organization at which the
associated party works. Multiple names for the same organization may be sent.
If multiple names are sent, the legal name must be sent in the first sequence.
If the legal name is not sent, then a repeat delimiter must be sent in the
first sequence.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the next of kin/associated party's marital
status. Refer to
User-defined
Table 0002 - Marital status for suggested values.
Definition: This field contains the next of kin/associated party's sex. Refer to User-defined Table 0001 - Administrative sex for suggested values.
Definition: This field contains the next of kin/associated party's birth date and time.
Definition: This field identifies specific living conditions (e.g., spouse dependent on patient, walk-up) that are relevant to an evaluation of the patient's healthcare needs. This information can be used for discharge planning. Examples might include Spouse Dependent, Medical Supervision Required, Small Children Dependent. This field repeats because, for example, "spouse dependent" and "medical supervision required" can apply at the same time. Refer to User-defined Table 0223 - Living dependency for suggested values.
Definition: This field identifies the transient rate of mobility for the next of kin/associated party. Refer to User-defined Table 0009 - Ambulatory status for suggested values.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the code to identify the next of
kin/associated party's citizenship. HL7 recommends using ISO 3166 as the
suggested values in User-defined Table 0171 - Citizenship.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field identifies the next of kin/associated party's primary
speaking language. HL7 recommends using ISO 639 as the suggested values in
User-defined Table 0296 - Language.
Definition: This field identifies the situation that the associated party lives in at his/her residential address. Refer to User-defined Table 0220 - Living arrangement for suggested values. Examples of living arrangements might include Alone, Family, Institution, etc.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field indicates what level of publicity is allowed (e.g., No
Publicity, Family Only) for the next of kin/associated party. Refer to
User-defined Table 0215 - Publicity code for suggested values.
Definition: This field identifies that next of kin/associated party's protection that determines, in turn, whether access to information about this person should be kept from users who do not have adequate authority. Refer to HL7 Table 0136 - Yes/no indicator for valid values.
Definition: This field identifies whether the next of kin/associated party is currently a student or not, and whether the next of kin/associated party is a full- or a part-time student. This field does not indicate the degree (high school, college) of the student or the field of study. Refer to User-defined Table 0231 - Student status for suggested values.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field indicates the type of religion practiced by the next of
kin/associated party. Refer to User-defined Table 0006 - Religion
for suggested values.
Components:
In Version 2.3, replaces the PN data type. <family name (FN)> ^
<given name (ST)> ^ <second and further given names or initials
thereof (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g.,
DR) (ST)> ^ <degree (e.g., MD) (IS)> ^ <name type code (ID)
> ^ <name representation code (ID)> ^ <name context (CE)> ^
<name validity range (DR)> ^ <name assembly order (ID)>
Subcomponents of family name: <family name (ST)> & <own family
name prefix (ST)> & <own family name (ST)> & <family name
prefix from partner/spouse (ST)> & <family name from partner/spouse
(ST)>
Definition: This field indicates the maiden name of the next of kin/associated
party's mother.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field identifies the nation or national group to which the
next of kin/associated party belongs. This information may be different than
the person's citizenship in countries in which multiple nationalities are
recognized (e.g., Spain: Basque, Catalan, etc.). Refer to User-defined Table
0212 - Nationality for suggested values.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the next of kin/associated party's ethnic
group. Refer to User-defined Table 0189 - Ethnic group for
suggested values. The second triplet of the CE data type for ethnic group
(alternate identifier, alternate text, and name of alternate coding system) is
reserved for governmentally assigned codes. In the US, a current use is to
report ethnicity in line with US federal standards for Hispanic origin.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field identifies how the contact should be used (e.g.,
contact employer if patient is unable to work). Refer to User-defined Table
0222 - Contact reason for suggested values.
Components:
In Version 2.3, replaces the PN data type. <family name (FN)> ^
<given name (ST)> ^ <second and further given names or initials
thereof (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g.,
DR) (ST)> ^ <degree (e.g., MD) (IS)> ^ <name type code (ID)
> ^ <name representation code (ID)> ^ <name context (CE)> ^
<name validity range (DR)> ^ <name assembly order (ID)>
Subcomponents of family name: <family name (ST)> & <own family
name prefix (ST)> & <own family name (ST)> & <family name
prefix from partner/spouse (ST)> & <family name from partner/spouse
(ST)>
Definition: This field contains the names of the people to contact, depending
on the value of the relationship defined in NK1-3 - relationship. This
field is typically needed when the NK1 is an organization. The legal name
should be sent first in the sequence. Refer to HL7 Table 0200 - Name
type for valid values.
Components:
[NNN] [(999)]999-9999 [X99999] [B99999] [C any text] ^
<telecommunication use code (ID)> ^ <telecommunication equipment type
(ID)> ^ <email address (ST)> ^ <country code (NM)> ^
<area/city code (NM)> ^ <phone number (NM)> ^ <extension
(NM)> ^ <any text (ST)>
Definition: This field contains the telephone numbers of the contact person
depending on the value of the relationship defined in NK1-3 -
relationship. This field is typically needed when the NK1 is an
organization. The primary telephone number must be sent in the first sequence.
If the primary telephone number is not sent, then a repeat delimiter must be
sent in the first sequence. Refer to HL7 Table 0201 -Telecommunication use
code and HL7 Table 0202 - Telecommunication equipment type for valid
values.
Components:
In Version 2.3 and later, replaces the AD data type. <street address
(ST)> ^ <other designation (ST)> ^ <city (ST)> ^ <state or
province (ST)> ^ <zip or postal code (ST)> ^ <country (ID)> ^
< address type (ID)> ^ <other geographic designation (ST)>
^ <county/parish code (IS)> ^ <census tract (IS)> ^
<address representation code (ID)> ^ <address validity range
(DR)>
Subcomponents of street address: <street address (ST)> &
<street name (ST)> & <dwelling number (ST)>
Definition: This field contains the addresses of the contact person depending
on the value of the relationship defined in NK1-3 - relationship. This
field is typically used when the NK1 is an organization. When multiple
addresses are sent, the mailing address must be sent first in the sequence.
Components:
<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check
digit scheme employed (ID)> ^ < assigning authority (HD)> ^
<identifier type code (ID)> ^ < assigning facility (HD) ^
<effective date (DT)> ^ <expiration date (DT)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the identifiers for the next of kin/associated
party, for example, Social Security Number, driver's license, etc. The
assigning authority and identifier type code are strongly recommended for all
CX data types.
Definition:
This field identifies the next of kin/associated party's job status. Refer to
User-defined Table 0311 - Job status for suggested values.
Values |
Description |
|---|---|
P |
Permanent |
T |
Temporary |
O |
Other |
U |
Unknown |
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field identifies the race of the next of kin/associated
party. Refer to User-defined Table 0005 - Race for suggested values.
The second triplet of the CE data type for race (alternate identifier,
alternate text, and name of alternate coding system) is reserved for
governmentally assigned codes.
Definition: This field contains the code that describes an associated party's disability. Refer to User-defined Table 0295 - Handicap for suggested values.
Definition: In the US, this field contains the contact person's social security number. This number may also be a RR retirement number. For the Social Security number of the associated party, see NK1-33 - next of kin/associated party's identifiers.
The
AL1 segment contains patient allergy information of various types. Most of
this information will be derived from user-defined tables. Each AL1 segment
describes a single patient allergy.
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
250 |
CE |
R |
00203 |
Set ID - AL1 |
||
2 |
250 |
CE |
O |
0127 |
00204 |
Allergen Type Code |
|
3 |
250 |
CE |
R |
00205 |
Allergen Code/Mnemonic/Description |
||
4 |
250 |
CE |
O |
0128 |
00206 |
Allergy Severity Code |
|
5 |
15 |
ST |
O |
Y |
00207 |
Allergy Reaction Code |
|
6 |
8 |
DT |
B |
00208 |
Identification Date |
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the number that identifies this transaction.
For the first occurrence of the segment, the sequence number shall be one, for
the second occurrence, the sequence number shall be two, etc.
Definition:
This field indicates a general allergy category (drug, food, pollen, etc.).
Refer to User-defined Table 0127 - Allergen type for suggested
values.
Value |
Description |
|---|---|
DA |
Drug allergy |
FA |
Food allergy |
MA |
Miscellaneous allergy |
MC |
Miscellaneous contraindication |
EA |
Environmental Allergy |
AA |
Animal Allergy |
PA |
Plant Allergy |
LA |
Pollen Allergy |
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field uniquely identifies a particular allergen. This
element may conform to some external, standard coding system (that must be
identified), or it may conform to local, largely textual or mnemonic
descriptions.
Definition:
This field indicates the general severity of the allergy. Refer to
User-defined T
able
0128 - Allergy severity for suggested values.
Value |
Description |
|---|---|
SV |
Severe |
MO |
Moderate |
MI |
Mild |
U |
Unknown |
Definition: This field identifies the specific allergic reaction that was documented. This element may conform to some external, standard coding system, or it may conform to a local, largely textual or mnemonic descriptions (e.g., convulsions, sneeze, rash, etc.).
Definition: this field contains the date that the allergy was identified.
The
IAM segment contains person/patient adverse reaction information of various
types. Most of this information will be derived from user-defined tables.
Each IAM segment describes a single person/patient adverse reaction. This
segment is used in lieu of the AL1 - Patient allergy information
segment to support action code/unique identifier mode update definition
of repeating segments as defined in <IP_ADDRESS>. The AL1 segment is used to
support Snapshot mode update definition as defined in <IP_ADDRESS>.
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
4 |
SI |
R |
01612 |
Set ID - IAM |
||
2 |
250 |
CE |
O |
0127 |
00204 |
Allergen Type Code |
|
3 |
250 |
CE |
R |
00205 |
Allergen Code/Mnemonic/Description |
||
4 |
250 |
CE |
O |
0128 |
00206 |
Allergy Severity Code |
|
5 |
15 |
ST |
O |
Y |
00207 |
Allergy Reaction Code |
|
6 |
250 |
CNE |
R |
0323 |
01551 |
Allergy Action Code |
|
7 |
80 |
EI |
R |
01552 |
Allergy Unique Identifier |
||
8 |
60 |
ST |
O |
01553 |
Action Reason |
||
9 |
250 |
CE |
O |
0436 |
01554 |
Sensitivity to Causative Agent Code |
|
10 |
250 |
CE |
O |
01555 |
Allergen Group Code/Mnemonic/Description |
||
11 |
8 |
DT |
O |
01556 |
Onset Date |
||
12 |
60 |
ST |
O |
01557 |
Onset Date Text |
||
13 |
8 |
TS |
O |
01558 |
Reported Date/Time |
||
14 |
250 |
XPN |
O |
01559 |
Reported By |
||
15 |
250 |
CE |
O |
0063 |
01560 |
Relationship to Patient Code |
|
16 |
250 |
CE |
O |
0437 |
01561 |
Alert Device Code |
|
17 |
250 |
CE |
O |
0438 |
01562 |
Allergy Clinical Status Code |
|
18 |
250 |
XCN |
O |
01563 |
Statused by Person |
||
19 |
250 |
XON |
O |
01564 |
Statused by Organization |
||
20 |
8 |
TS |
O |
01565 |
Statused at Date/Time |
Definition: This field contains the number that identifies this transaction. For the first occurrence of the segment, the sequence number shall be one, for the second occurrence, the sequence number shall be two, etc.
Definition: This field indicates a general allergy category (drug, food, pollen, etc.). Refer to User-defined Table 0127 - Allerg en type for suggested values.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field uniquely identifies a particular allergen. This
element may conform to some external, standard coding system (that must be
identified), or it may conform to local, largely textual or mnemonic
descriptions.
If a system maintains allergen codes as it's unique identifier for a particular
allergy, and two systems have agreed to process the IAM using update mode, then
this field can be used as the unique identifier instead of IAM-8 - Allergy
Unique Identifier. This does not preclude using allergen codes for unique
identifiers for snapshot processing.
Definition: This field indicates the general severity of the allergy. Refer to User-define d Table 0128 - Allergy severity code for suggested values.
Definition: This field identifies the specific allergic reaction that was documented. This element may conform to some external, standard coding system, or it may conform to a local, largely textual or mnemonic descriptions (e.g., convulsions, sneeze, rash, etc.).
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)> ^ <coding system version ID
(ST)> ^ alternate coding system version ID (ST)> ^ <original text
(ST)>
Definition: This field contains a code defining the status of the record. It
allows allergy messages to be sent to delete or update previously sent allergy
messages. Refer to HL7 Table 0323 - Action code for suggested
values.
Value |
Description |
|---|---|
A |
Add/Insert |
D |
Delete |
U |
Update |
Components:
<entity identifier (ST)> ^ <assigning authority (HD)>
Subcomponents of assigning authority: <application identifier 1
(IS)> & <universal identifier (UI)>
Definition: This field contains a value that uniquely identifies a single
allergy for a person. It is unique across all segments and messages for a
person. If a system maintains allergen codes as a unique identifier for a
particular allergy, then this field should not be used.
This field is conditionally required. The surrogate field to use is IAM-3 -
Allergen Code/Mnemonic/Description, if that field can uniquely identify the
allergy on the receiving system.
Definition: This field contains the reason for the action indicated in the IAM-7 - Allergy action code field.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the reason why the patient should not be
exposed to a substance. Refer to User-defined Table 0436 - Sensitivity
to causative Agent code for suggested values.
Value |
Description |
AD |
Adverse Reaction (Not otherwise classified) |
AL |
Allergy |
CT |
Contraindication |
IN |
Intolerance |
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the code, mnemonic, or description used to
uniquely identify an allergen group when both a detailed allergy (IAM-3) and
group level (IAM-11) need to be communicated. In cases where systems want to
communicate both a specific drug allergy and the group of drugs to which the
specific drug belongs (i.e., Bactrim and Sulfa drugs; Ceclor and
Penicillins/Cephalosporins) then the specific drug allergy is sent in IAM-3 and
the group level is sent in IAM-11. However, if only a group level is being
communicated, then it can be sent in IAM-3 as the primary identifier of the
allergy.
Definition: This field contains the actual date of the first reaction.
Definition: This field contains a text description of the time period of the first reaction when an exact date is not known. (e.g., adolescence, childhood, spring 1990).
Definition: This field contains the date/time the allergy was reported to a caregiver.
Components:
In Version 2.3, replaces the PN data type. <family name (FN)> ^
<given name (ST)> ^ <second and further given names or initials
thereof (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g.,
DR) (ST)> ^ <degree (e.g., MD) (IS)> ^ <name type code (ID)
> ^ <name representation code (ID)> ^ <name context (CE)> ^
<name validity range (DR)> ^ <name assembly order (ID)>
Subcomponents of family name: <family name (ST)> & <own family
name prefix (ST)> & <own family name (ST)> & <family name
prefix from partner/spouse (ST)> & <family name from partner/spouse
(ST)>
Definition: This field contains the name of the person reporting the allergy to
a caregiver at the time reported in IAM-14 - reported date/time.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the personal relationship that the person
reporting the allergy has to the patient. It uses the same table as that used
by NK1-3. Refer to User-defined Table 0063 - Relationship for
suggested values. Examples include: brother, sister, mother, father, friend,
spouse, etc.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field describes any type of allergy alert device the patient
may be carrying or wearing. Refer to User-defined Table 0437 - Alert
device for suggested values.
Value |
Description |
|---|---|
B |
Bracelet |
N |
Necklace |
W |
Wallet Card |
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field indicates the verification status for the allergy.
Refer to User-defined Table 0438 - Allergy clinical status for
suggested values.
Value |
Description |
|---|---|
U |
Unconfirmed |
P |
Pending |
S |
Suspect |
C |
Confirmed or verified |
I |
Confirmed but inactive |
E |
Erroneous |
D |
Doubt raised |
Components:
<ID number (ST)> ^ <family name (ST) > & < last_name_prefix
(ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^
<suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^
<degree (e.g., MD) (IS)> ^ <source table (IS)> ^ <assigning
authority (HD)> ^ <name type code(ID)> ^ <identifier check digit
(ST)> ^ <code identifying the check digit scheme employed (ID )> ^
<identifier type code (IS)> ^ <assigning facility (HD)> ^ < name
representation code(ID)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field identifies the provider who assigned the clinical
status to the allergy. (e.g. ...|Smith^John^J^III^DR^MD|...).
Components:
<organization name (ST)> ^ <organization name type code (IS)> ^
<ID number (NM)> ^ <check digit (NM)> ^ <code identifying the
check digit scheme employed (ID)> ^ <assigning authority (HD)> ^
<identifier type code (IS)> ^ <assigning facility ID (HD)> ^
<name representation code(ID)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the name of the organization providing the
update to the allergy (e.g. General Hospital).
Definition: The date and time that this allergy was last statused by the IAM-19 - Statused by person in the IAM-20 - Statused by organization.
The
NPU segment allows the updating of census (bed status) data without sending
patient-specific data. An example might include changing the status of a bed
from "housekeeping" to "unoccupied."
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
80 |
PL |
R |
00209 |
Bed Location |
||
2 |
1 |
IS |
O |
0116 |
00170 |
Bed Status |
Components:
<point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^
<facility (HD)> ^ <location status (IS)> ^ <person location
type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location
description (ST)>
Subcomponents of facility: <namespace ID (IS)> & <universal ID
(ST)> & <universal ID type (ID)>
Definition: This field contains the bed location that is a valid bed location.
Definition: This field contains the bed status. Refer to User-defined Table 0116 - Bed status for suggested values.
The
MRG segment provides receiving applications with information necessary to
initiate the merging of patient data as well as groups of records. It is
intended that this segment be used throughout the Standard to allow the merging
of registration, accounting, and clinical records within specific
applications.
The assigning authority, the fourth component of the patient identifiers, is an
HD data type that is uniquely associated with the assigning authority that
originally assigned the number. A given institution, or group of
intercommunicating institutions, should establish a list of assigning
authorities that may be potential assignors of patient identification (and
other important identification) numbers. The list will be one of the
institution's master dictionary lists. Since third parties (other than the
assignors of patient identification numbers) may send or receive HL7 messages
containing patient identification numbers, the assigning authority in the
patient identification numbers may not be the same as those of the sending and
receiving systems identified in the MSH. The assigning authority must be
unique across applications at a given site. This field is required in HL7
implementations that have more than a single Patient Administration application
assigning such numbers.
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
250 |
CX |
R |
Y |
00211 |
Prior Patient Identifier List |
|
2 |
250 |
CX |
B |
Y |
00212 |
Prior Alternate Patient ID |
|
3 |
250 |
CX |
O |
00213 |
Prior Patient Account Number |
||
4 |
250 |
CX |
B |
00214 |
Prior Patient ID |
||
5 |
250 |
CX |
O |
01279 |
Prior Visit Number |
||
6 |
250 |
CX |
O |
01280 |
Prior Alternate Visit ID |
||
7 |
250 |
XPN |
O |
Y |
01281 |
Prior Patient Name |
Components:
<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check
digit scheme employed (ID)> ^ < assigning authority (HD)> ^
<identifier type code (ID)> ^ < assigning facility (HD) ^
<effective date (DT)> ^ <expiration date (DT)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the prior patient identifier list. This field
contains a list of potential "old" numbers to match. Only one old number can
be merged with one new number in a transaction. Refer to HL7 Table 0061 -
Check digit scheme for valid values. The assigning authority and
identifier type code are strongly recommended for all CX data types.
Components:
<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check
digit scheme employed (ID)> ^ < assigning authority (HD)> ^
<identifier type code (ID)> ^ < assigning facility (HD) ^
<effective date (DT)> ^ <expiration date (DT)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field has been retained for backward compatibility
only. Use MRG-1 - Prior patient identifier list for all patient
identifiers. This field contains the prior alternate patient identifier.
Refer to HL7 Table 0061 - Check digit scheme for valid values. The
assigning authority and identifier type code are strongly recommended for all
CX data types.
Components:
<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check
digit scheme employed (ID)> ^ < assigning authority (HD)> ^
<identifier type code (ID)> ^ < assigning facility (HD) ^
<effective date (DT)> ^ <expiration date (DT)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the prior patient account number. Refer to
HL7 Table 0061 - Check digit scheme for valid values. The assigning
authority and identifier type code are strongly recommended for all CX data
types.
Components:
<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check
digit scheme employed (ID)> ^ < assigning authority (HD)> ^
<identifier type code (ID)> ^ < assigning facility (HD) ^
<effective date (DT)> ^ <expiration date (DT)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field has been retained for backward compatibility only.
Use MRG-1 - prior patient identifier list for all patient
identifiers. This field contains the prior patient identifier. Refer to
HL7 Table 0061 - Check digit scheme for valid values. The assigning
authority and identifier type code are strongly recommended for all CX data
types.
Components:
<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check
digit scheme employed (ID)> ^ < assigning authority (HD)> ^
<identifier type code (ID)> ^ < assigning facility (HD) ^
<effective date (DT)> ^ <expiration date (DT)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the prior visit number. Refer to HL7 Table
0061 - Check digit scheme for valid values. The assigning authority and
identifier type code are strongly recommended for all CX data types.
Components:
<ID (ST)> ^ <check digit (ST)> ^ <code identifying the check
digit scheme employed (ID)> ^ < assigning authority (HD)> ^
<identifier type code (ID)> ^ < assigning facility (HD) ^
<effective date (DT)> ^ <expiration date (DT)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the prior alternate visit number. Refer to
HL7 Table 0061 - Check digit scheme for valid values. The assigning
authority and identifier type code are strongly recommended for all CX data
types.
Components:
In Version 2.3, replaces the PN data type. <family name (FN)> ^
<given name (ST)> ^ <second and further given names or initials
thereof (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g.,
DR) (ST)> ^ <degree (e.g., MD) (IS)> ^ <name type code (ID)
> ^ <name representation code (ID)> ^ <name context (CE)> ^
<name validity range (DR)> ^ <name assembly order (ID)>
Subcomponents of family name: <family name (ST)> & <own family
name prefix (ST)> & <own family name (ST)> & <family name
prefix from partner/spouse (ST)> & <family name from partner/spouse
(ST)>
Definition: This field contains the prior name of the patient. This field is
not used to change a patient name. Refer to HL7 Table 0200 - Name type
for valid values.
The
patient additional demographic segment contains demographic information that is
likely to change about the patient.
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
2 |
IS |
O |
Y |
0223 |
00755 |
Living Dependency |
2 |
2 |
IS |
O |
0220 |
00742 |
Living Arrangement |
|
3 |
250 |
XON |
O |
Y |
00756 |
Patient Primary Facility |
|
4 |
250 |
XCN |
B |
Y |
00757 |
Patient Primary Care Provider Name & ID No. |
|
5 |
2 |
IS |
O |
0231 |
00745 |
Student Indicator |
|
6 |
2 |
IS |
O |
0295 |
00753 |
Handicap |
|
7 |
2 |
IS |
O |
0315 |
00759 |
Living Will Code |
|
8 |
2 |
IS |
O |
0316 |
00760 |
Organ Donor Code |
|
9 |
1 |
ID |
O |
0136 |
00761 |
Separate Bill |
|
10 |
250 |
CX |
O |
Y |
00762 |
Duplicate Patient |
|
11 |
250 |
CE |
O |
0215 |
00743 |
Publicity Code |
|
12 |
1 |
ID |
O |
0136 |
00744 |
Protection Indicator |
|
13 |
8 |
DT |
O |
01566 |
Protection Indicator Effective Date |
||
14 |
250 |
XON |
O |
Y |
01567 |
Place of Worship |
|
15 |
250 |
CE |
O |
Y |
0435 |
01548 |
Advance Directive Code |
16 |
1 |
IS |
O |
0441 |
01569 |
Immunization Registry Status |
|
17 |
8 |
DT |
O |
01570 |
Immunization Registry Status Effective Date |
||
18 |
8 |
DT |
O |
01571 |
Publicity Code Effective Date |
||
19 |
5 |
IS |
O |
0140 |
01572 |
Military Branch |
|
20 |
2 |
IS |
O |
0141 |
00486 |
Military Rank/Grade |
|
21 |
3 |
IS |
O |
0142 |
00487 |
Military Status |
Definition:
This field identifies specific living conditions (e.g., spouse dependent on
patient, walk-up) that are relevant to an evaluation of the patient's
healthcare needs. This information can be used for discharge planning. This
field repeats because, for example, "spouse dependent" and "medical supervision
required" can apply at the same time. Refer to User-defined Table 0223 -
Living dependency for suggested values.
Value |
Description |
|---|---|
S |
Spouse Dependent |
M |
Medical Supervision Required |
C |
Small Children Dependent |
O |
Other |
U |
Unknown |
Definition: This field identifies the situation in which the patient lives at his residential address. Examples might include Alone, Family, Relatives, Institution, etc. Refer to User-defined Table 0220 - Living arrangement for suggested values.
Components:
<organization name (ST)> ^ <organization name type code (ID)> ^
<ID number (ID)> ^ <check digit (NM)> ^ < check digit scheme
(ID)> ^ <assigning authority (HD)> ^ <identifier type code (ID)>
^ <assigning facility (HD)> ^ <name representation code
(ID)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> &