The CTD segment may identify any contact personnel associated with a patient referral message and its related transactions. The CTD segment will be paired with a PRD segment. The PRD segment contains data specifically focused on provider information in a referral. While it is important in an inter-enterprise transaction to transmit specific information regarding the providers involved (referring and referred-to), it may also be important to identify the contact personnel associated with the given provider. For example, a provider receiving a referral may need to know the office manager or the billing person at the institution of the provider who sent the referral. This segment allows for multiple contact personnel to be associated with a single provider.
Figure 11-5. CTD attributes
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
1 |
200 |
CE |
R |
Y |
0131 |
01155 |
Role |
2 |
106 |
XPN |
O |
Y |
01165 |
Contact Name |
|
3 |
60 |
XAD |
O |
01166 |
Contact Address |
||
4 |
60 |
PL |
O |
01167 |
Contact Location |
||
5 |
100 |
XTN |
O |
Y |
01168 |
Contact Communication Information |
|
6 |
200 |
CE |
O |
0185 |
01170 |
Preferred Method of Contact |
|
7 |
100 |
CM |
O |
Y |
01171 |
Contact Identifiers |
11.5.4.0 CTD field definitions
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the contact role that defines the relationship of the person described in this segment to the patient being referred. When a referral is inter-enterprise in nature, there are some important relationships that must be identified. For example, it may be necessary to identify the contact representative at the clinic that sent the referral. Refer to user-defined table 0131 - Contact role for suggested values.
Components: <family name (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) (ST)> ^ <name type code (ID) >
Definition: This field contains the name of the contact person identified in this segment. Generally, this field will describe a person or provider associated with the referral. If this contact name is a physician, you may refer to the CTD-7-contact identifiers (Section 11.5.4.7) for the physician identifier.
Components: <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)>
Definition: This field contains the mailing address of the contact person identified in this segment. One of the key components for completing the "circle of care" and provider/institution bonding is the issuance of follow-up correspondence to the referring provider.
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 location of the contact, which is required when a contact that may be external to a given enterprise must be referenced. For example, if this contact represents the office manager of the referred-to physician, then the contact location should identify the clinic of the physician or provider to whom this referral has been sent. The identification of the contacts location is specified by an application and facility identifier carried in the facility field. The application identifier and the facility identifier would be used in the same manner as their corresponding fields in the MSH segment (MSH-3-sending application, MSH-5-receiving application, MSH-4-sending facility, MSH-6-receiving facility). That is, the facility field will contain an application identifier and facility identifier which describes the location of this contact. However, it should be noted that they may describe a different location because the contact location being referenced in this field may not be the location from which the message originated, which is being described by the MSH.
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 information, such as the phone number or electronic mail address, used to communicate with the contact person or organization.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the preferred method to use when communicating with the contact person. Refer to user-defined table 0185 - Preferred method of contact for suggested values.
Components: <ID number (ST)> ^ <type of ID number (IS)> ^ <other qualifying info (ST)>
Definition: This repeating field contains the contacts unique identifiers such as UPIN, Medicare and Medicaid numbers. Refer to Chapter 8 (Section 8.6.3.6, "Practitioner ID numbers") for suggested values.