PAT_ENC_RSH
Description:
This table extracts information for patient encounters linked to patient research study records.

Primary Key
Column Name Ordinal Position
PAT_ENC_CSN_ID 1
LINE 2

Column Information
Name Type Discontinued?
1 PAT_ENC_CSN_ID NUMERIC No
The unique contact serial number for this contact. This number is unique across all patient encounters in your system. If you use IntraConnect, this is the Unique Contact Identifier (UCI).
2 LINE INTEGER No
The line number for the information associated with this contact. Multiple pieces of information can be associated with this contact.
3 CONTACT_DATE DATETIME No
The date of this contact in calendar format.
4 ENC_RESEARCH_ID VARCHAR No
This column stores the unique identifier for the research study linked to this patient encounter. This column is frequently used to link to the CLARITY_RSH table.
5 ENROLL_ID NUMERIC No
This column stores the unique identifiers for associated enrollment information records for the study/patient combination for the research studies linked to this patient encounter.
6 MANUAL_LINK_YN VARCHAR No
Indicates whether the non-inferred columns of this table are based on manual user linkage. Y indicates that a user manually linked the encounter to the patient timeline. N indicates the data was inferred based on the encounter date and the patient timeline's dates.
May contain organization-specific values: No
Category Entries:
No
Yes
7 PROTOCOL_ID NUMERIC No
This column stores the unique identifier for the protocol linked from the encounter within the patient's study timeline.
8 PROTOCOL_ID_PROTOCOL_NAME VARCHAR No
The SmartSet/Protocol record name. This is different from the display name, which is stored in CL_PRL_SS_OT.DISPLAY_NAME.
9 PROTOCOL_VER INTEGER No
If the encounter is linked to a protocol, this is the version number of that protocol.
10 PROTOCOL_CONT_DATE_REAL FLOAT No
If the encounter is linked to a protocol, this is the unique contact date of the protocol, in decimal format. The integer portion of the number indicates the date of contact. The digits after the decimal distinguish different contacts on the same date and are unique for each contact on that date. For example, .00 is the first/only contact, .01 is the second contact, etc.
11 UNIQ_DAY_NUM INTEGER No
The encounter is linked to this unique day number within the protocol of the patient's study timeline.
12 INF_PROTOCOL_ID NUMERIC No
When comparing the encounter date with the patient's study timeline, and regardless of any manually specified encounter-timeline relationship, this is the inferred protocol for the encounter. The value of this column may be different from the actual linked protocol if a user has linked the encounter to a different point in the timeline.
13 INF_PROTOCOL_ID_PROTOCOL_NAME VARCHAR No
The SmartSet/Protocol record name. This is different from the display name, which is stored in CL_PRL_SS_OT.DISPLAY_NAME.
14 INF_PROTOCOL_VER INTEGER No
When comparing the encounter date with the patient's study timeline, and regardless of any manually specified encounter-timeline relationship, INF_PROTOCOL_ID contains the inferred protocol ID for the encounter while this column contains the version number of the protocol.
15 INF_PROTOCOL_CONT_DATE_REAL FLOAT No
When comparing the encounter date with the patient's study timeline, and regardless of any manually specified encounter-timeline relationship, INF_PROTOCOL_ID contains the inferred protocol ID for the encounter while this column contains the unique contact date of the protocol, in decimal format. The integer portion of the number indicates the date of contact. The digits after the decimal distinguish different contacts on the same date and are unique for each contact on that date. For example, .00 is the first/only contact, .01 is the second contact, etc.
16 INF_UNIQ_DAY_NUM INTEGER No
When comparing the encounter date with the patient's study timeline, and regardless of any manually specified encounter-timeline relationship, this is the inferred unique day number for the encounter. The value of this column may be different from the actual linked day if a user has linked the encounter to a different point in the timeline.