|
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 |
PAT_ENC_DATE_REAL |
FLOAT |
No |
|
|
|
A unique, internal contact date in decimal format. The integer portion of the number indicates the date of the 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. |
|
|
3 |
CONTACT_DATE |
DATETIME |
No |
|
|
|
The date of this contact in calendar format. |
|
|
4 |
CM_CT_OWNER_ID |
VARCHAR |
No |
|
|
|
The Community ID (CID) of the instance that owns this contact. This is populated only if you use IntraConnect. |
|
|
5 |
CS_SURG_SURGEON_ID_PROV_NAME |
VARCHAR |
No |
|
|
|
The name of the service provider. This item may be hidden in a public view of the CLARITY_SER table. |
|
|
6 |
CS_SURG_PROC_ID |
VARCHAR |
No |
|
|
|
The unique ID of the primary procedure for the surgery, stored here so that it can be synched across deployments to be shown in the chart review. |
|
|
7 |
CS_SURG_PROC_ID_PROC_NAME |
VARCHAR |
No |
|
|
|
The name of the surgical procedure record. |
|
|
8 |
CS_SURG_LOCATION_ID_LOC_NAME |
VARCHAR |
No |
|
|
|
The name of the revenue location. |
|
|
9 |
CS_SURG_CASE_STAT_C_NAME |
VARCHAR |
No |
|
|
|
The case status category number for the associated surgery, stored here so that it can be synched across deployments to be shown in the chart review. |
May contain organization-specific values: Yes |
Category Entries: |
Scheduled |
Canceled |
Not Scheduled |
Missing Information |
Voided |
Pending |
Arrived |
Completed |
No Show |
Pending Unscheduled |
|
|
10 |
CS_SURG_LOG_STAT_C_NAME |
VARCHAR |
No |
|
|
|
The log status category number for the associated surgery, stored here so that it can be synched across deployments to be shown in the chart review. |
May contain organization-specific values: Yes |
Category Entries: |
Missing Information |
Posted |
Unposted |
Voided |
Completed |
Canceled |
|
|
11 |
CS_SURG_EAP_ID_PROC_NAME |
VARCHAR |
No |
|
|
|
The name of each procedure. |
|
|
12 |
CS_SURG_PROC_FRTXT |
VARCHAR |
No |
|
|
|
The procedure name as exactly ordered by the surgeon/provider, stored here so that it can be synced across deployments to be shown in the chart review. |
|
|
13 |
CS_SURG_PROC_LAT_C_NAME |
VARCHAR |
No |
|
|
|
The procedure laterality, stored here so that it can be synced across deployments to be shown in the chart review. |
May contain organization-specific values: Yes |
Category Entries: |
Left |
Right |
Bilateral |
N/A |
Default |
|
|
14 |
CS_SURG_SCHED_DTTM |
DATETIME (UTC) |
No |
|
|
|
The procedure scheduled time, stored here so that it can be synced across deployments to be shown in the chart review. |
|
|
15 |
CS_SURG_PROC_CMT |
VARCHAR |
No |
|
|
|
The procedure comments, stored here so that it can be synced across deployments to be shown in the chart review. |
|
|
16 |
CS_SURG_NOT_PERF_YN |
VARCHAR |
No |
|
|
|
The flag determining if the surgery was marked as procedure not performed, stored here so that it can be synced across deployments. |
May contain organization-specific values: No |
Category Entries: |
No |
Yes |
|
|
17 |
CS_SURG_CASE_CLASS_C_NAME |
VARCHAR |
No |
|
|
|
Stores the class of the case (either Inpatient or Outpatient), stored here so that the class of the case can be determined across deployments. |
May contain organization-specific values: No |
Category Entries: |
Inpatient |
Outpatient |
Cannot Be Determined |
|
|