|
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 |
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. |
|
|
4 |
CONTACT_DATE |
DATETIME |
No |
|
|
|
The date of this contact in calendar format. |
|
|
5 |
COMM_SENT_HOUSE_NO |
VARCHAR |
No |
|
|
|
Communication recipient house number |
|
|
6 |
COMM_SENT_DISTRCT_C_NAME |
VARCHAR |
No |
|
|
|
The category number for the district in the communication recipient's address. |
May contain organization-specific values: Yes |
|
|
7 |
COMM_SENT_COUNTY_C_NAME |
VARCHAR |
No |
|
|
|
The category number for the county in the communication recipient's address. |
May contain organization-specific values: Yes |
|
|
8 |
COMM_SENT_UID_ID |
VARCHAR |
No |
|
|
|
The unique ID of the user who sent the communication. |
|
|
9 |
COMM_SENT_UID_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
10 |
COMM_SENT_INST |
DATETIME (Local) |
No |
|
|
|
The instant when the communication was sent. |
|
|
11 |
COMM_SENT_INI |
VARCHAR |
No |
|
|
|
The record type of the communication's recipient, for example SER for provider, DEP for department, etc. |
|
|
12 |
COMM_SENT_SER_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. |
|
|
13 |
COMM_SENT_TO_NAME |
VARCHAR |
No |
|
|
|
Communication recipient name |
|
|
14 |
COMM_SENT_FAX |
VARCHAR |
No |
|
|
|
Communication recipient fax number |
|
|
15 |
COMM_SENT_PHONE |
VARCHAR |
No |
|
|
|
Communication recipient phone number |
|
|
16 |
COMM_SENT_ADDR |
VARCHAR |
No |
|
|
|
The street address of the communication recipient. |
|
|
17 |
COMM_SENT_CITY |
VARCHAR |
No |
|
|
|
Communication recipient city |
|
|
18 |
COMM_SENT_STATE |
VARCHAR |
No |
|
|
|
Communication recipient state. |
|
|
19 |
COMM_SENT_ZIP |
VARCHAR |
No |
|
|
|
Communication recipient zip code. |
|
|
20 |
COMM_SENT_COUNTRY |
VARCHAR |
No |
|
|
|
Communication recipient country |
|
|
21 |
COMM_SENT_METHOD_C_NAME |
VARCHAR |
No |
|
|
|
The category value for the method used to send the communication. |
May contain organization-specific values: Yes |
Category Entries: |
In Basket |
Fax |
Mail |
Phone Call |
MyChart |
Network Printer |
Courier Service |
Outside Provider Messaging |
Print Locally |
EDI |
Opt Out |
E-mail |
FHIR |
Save to File |
Electronic Authorization Message |
Suppress Result Routing |
Payer Platform Notification |
|
|
22 |
COMM_SENT_LTR_NUM |
VARCHAR |
No |
|
|
|
Letter number of the communication sent |
|
|
23 |
COMM_SENT_RPT_ID |
VARCHAR |
No |
|
|
|
The unique ID of the report sent with the communication. |
|
|
24 |
COMM_SENT_RPT_ID_REPORT_NAME |
VARCHAR |
No |
|
|
|
|
25 |
COMM_SENT_OTH_BLBID |
VARCHAR |
No |
|
|
|
Blob ID of the communication sent |
|
|
26 |
COMM_SENT_LTR_BLOB |
VARCHAR |
No |
|
|
|
Letter blob of the communication sent. Only applies to communications sent via fax. |
|
|
27 |
COMM_SENT_RPT_BLOB |
VARCHAR |
No |
|
|
|
Report blob of the communication sent. Only applies to communications sent via fax. |
|
|
28 |
COMM_SENT_STAT_C_NAME |
VARCHAR |
No |
|
|
|
Communication sent status category number for the communication. |
May contain organization-specific values: No |
Category Entries: |
Not Ready |
Ready To Send |
Sent |
New Job |
Support Staff |
Voided |
Sent & Acknowledged |
Preparing to Send |
|
|
29 |
COMM_SENT_JOB_ID |
VARCHAR |
No |
|
|
|
The unique ID of the communication job. |
|
|
30 |
COMM_SENT_BY_USR_ID |
VARCHAR |
No |
|
|
|
The unique ID of the user (EMP) who actually sent the communication from the communication management module. |
|
|
31 |
COMM_SENT_BY_USR_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
32 |
COMM_SENT_SER_ADDR |
VARCHAR |
No |
|
|
|
Stores the selected address ID if the recipient is a provider |
|
|
33 |
COMM_ROUTING_MESSG |
VARCHAR |
No |
|
|
|
The routing message included when the communication is routed to support staff. |
|
|
34 |
OR_LOG_ID |
VARCHAR |
No |
|
|
|
The unique ID of the surgical log (ORL) record associated with the communication note. |
|
|
35 |
COMM_SENT_HNO_ID |
VARCHAR |
No |
|
|
|
The unique ID of the note (HNO) record associated with the communication note. |
|
|
36 |
COMM_SENT_EMP_ID |
VARCHAR |
No |
|
|
|
The unique ID of the user (EMP) record for the communication recipient. |
|
|
37 |
COMM_SENT_EMP_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
38 |
COMM_IS_OVERDUE_YN |
VARCHAR |
No |
|
|
|
Indicates whether the communication has been waiting for either transcriptions, results, or both, and is now overdue. A Y indicates that it is overdue. N indicates that the communication is not overdue. |
May contain organization-specific values: No |
Category Entries: |
No |
Yes |
|
|
39 |
COMM_PREV_LETTER_YN |
VARCHAR |
No |
|
|
|
Indicates whether the communication is using a previously sent letter. A Y indicates that the communication is using a previously sent letter. N indicates that the communication is not using a previously sent letter. |
The category values for this column were already listed for column: COMM_IS_OVERDUE_YN |
|
|
40 |
COMM_WAIT_FOR_TX_C_NAME |
VARCHAR |
No |
|
|
|
Indicates whether the communication is waiting for transcriptions. Yes indicates that the communication is waiting for transcriptions, No indicates that the communication is not waiting for transcriptions, and Resulted indicates that the communication was waiting for a transcription that has since been completed. |
May contain organization-specific values: No |
Category Entries: |
Yes |
No |
Resulted |
|
|
41 |
COMM_WAIT_FOR_RES_C_NAME |
VARCHAR |
No |
|
|
|
Indicates whether the communication is waiting for results. Yes indicates that the communication is waiting for results, No indicates that the communication is not waiting for results, and Resulted indicates the communication was waiting for results that have since been resulted. |
May contain organization-specific values: No |
Category Entries: |
Yes |
No |
Resulted |
|
|
42 |
COMM_SENT_DIR_ADDR |
VARCHAR |
No |
|
|
|
This is the Direct address to which a communication is sent. |
|
|
43 |
COMM_CREATED_MTH_C_NAME |
VARCHAR |
No |
|
|
|
This item stores the communication's creation method. "Automatic on Close Encounter" means the communication was created from an automatic communication when the encounter was closed and has not been sent yet. "ED Discharge" is for automatic communications created upon discharge from the emergency department. "IP Discharge" is for automatic communications created upon discharge from an inpatient admission. "Order Transmittal" is for automatic communications created based on order transmittal rules when an order is signed. "Referral Transmittal" is for automatic communications created with referral workqueue functionality. Otherwise, communications created with the Communication Management navigator section or activity will have the "Standard" value. |
May contain organization-specific values: Yes |
Category Entries: |
Standard |
Automatic on Close Encounter |
Additional |
By interface for full letter dictations |
ED Discharge |
Continued Care and Services Coordination |
IP Discharge |
Order Transmittal |
Referral Transmittal |
Event Notification |
ED Event Change Filing Extension |
Flowsheets |
Payer Communication |
ED Notification |
Referral Notification |
SC Decision Letter |
Chart Abstraction |
Bulk Letters |
Waitlist Letters |
Referral Fax with Attachment |
Specialty Plan of Care |
ED Excuse Letter |
SOTE Patient Refusal Letter |
Referral Notification w/ Consent |
Medication Therapy Management |
Canto Regular Comms |
Canto Quick Comms |
Health Maintenance Reminders |
Form Filler Auto Print |
Outside Message |
HOV Completion |
Automatic Action Letter Notification |
HH Plan of Care Update Message |
Hospice Non-Covered Document |
Imaging Reminder Letter |
|
|
44 |
COMM_CE_SUB_MTHD_C_NAME |
VARCHAR |
No |
|
|
|
This is the sub routing method when the routing method "Outside provider messaging" is used in a communication. |
May contain organization-specific values: No |
Category Entries: |
None |
Outgoing Direct Address |
EpicCare Link Direct Address |
MedCom |
PCEHR |
Kanta |
Pika XML |
|
|
45 |
COMM_SENT_EMAIL |
VARCHAR |
No |
|
|
|
Communication recipient email |
|
|
46 |
COMM_PRIORITY_C_NAME |
VARCHAR |
No |
|
|
|
Communication priority |
May contain organization-specific values: Yes |
Category Entries: |
High |
Routine |
Low |
|
|
47 |
COMM_SOURCE_RFL_ID |
NUMERIC |
No |
|
|
|
Stores a referral ID associated with a transition of care communication. |
|
|
48 |
COMM_SENT_INSTANT_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
Communication sent instant in UTC format |
|
|
49 |
COMM_UPDATE_INST_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
The instant (in UTC) at which the associated communication was last updated. |
|
|
50 |
COMM_VOID_REASON_C_NAME |
VARCHAR |
No |
|
|
|
Selected reason for voiding this communication |
May contain organization-specific values: Yes |
Category Entries: |
Incorrect recipient; replacement needed |
Incorrect recipient; no replacement needed |
Wrong patient |
Wrong encounter |
Sent accidentally |
Excuse letter removed |
Excuse letter modified |
Negative Acknowledgment |
Missing Acknowledgment |
Voided by utility |
Invalid recipient; destination pool invalid |
Returned to sender |
|
|
51 |
COMM_VOID_USER_ID |
VARCHAR |
No |
|
|
|
User (EMP) ID of user who voided this communication |
|
|
52 |
COMM_VOID_USER_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
53 |
COMM_VOID_INSTANT_DTTM |
DATETIME (UTC) |
No |
|
|
|
The instant (in UTC) at which this communication was voided |
|
|
54 |
CONSENT_DOC_INFO_ID |
VARCHAR |
No |
|
|
|
The unique ID of the document (DCS) record which grants patient consent for sending the message. |
|
|
55 |
COMM_SENT_EAF_ID_LOC_NAME |
VARCHAR |
No |
|
|
|
The name of the revenue location. |
|
|
56 |
COMM_SENT_HIP_ID |
NUMERIC |
No |
|
|
|
The unique ID of the registry (HIP) record for the communication recipient. |
|
|
57 |
COMM_SENT_HIP_ID_REGISTRY_NAME |
VARCHAR |
No |
|
|
|
The name of the In Basket registry in the HIP master file. |
|
|
58 |
COMM_SENT_DEP_ID_EXTERNAL_NAME |
VARCHAR |
No |
|
|
|
The external name of the department record. This is often used in patient correspondence such as reminder letters. |
|
|
59 |
COMM_SENT_AGY_ID |
VARCHAR |
No |
|
|
|
The unique ID of the agency (AGY) record for the communication recipient. |
|
|
60 |
COMM_SENT_AGY_ID_AGENCY_NAME |
VARCHAR |
No |
|
|
|
|
61 |
COMM_SENT_DXO_ID |
NUMERIC |
No |
|
|
|
The unique ID of the data exchange organization (DXO) record for the communication recipient. |
|
|
62 |
COMM_SENT_DXO_ID_EXTERNAL_NAME |
VARCHAR |
No |
|
|
|
Organization's external name used as the display name on forms and user interfaces. |
|
|
63 |
COMM_RES_CMT |
VARCHAR |
No |
|
|
|
Indicates what was done to resolve the negative or missing acknowledgment |
|
|
64 |
COMM_VOID_COMMENT |
VARCHAR |
No |
|
|
|
Comment for communication retraction reason. |
|
|
65 |
COMM_PRINT_STATUS_C_NAME |
VARCHAR |
No |
|
|
|
Stores status of print job attached to communication |
May contain organization-specific values: No |
Category Entries: |
Completed |
Submitted |
Error |
Deleted |
Rerouted |
Rescheduled |
Start Processing on Generic Queue |
Transfer requested from Epic Print Service |
Transfer in progress to Epic Print Service |
Submitted to Epic Print Service |
Processing in Epic Print Service |
Failed - Aborted in Epic Print Service |
Failed - Timeout in Epic Print Service |
Failed in Epic Print Service |
Waiting for Pickup |
Waiting for Batch |
Failed - Fax Transmission Failure |
Processing on fax server |
Sent to Spooler |
Failed - Printer Failure |
Spooling Complete |
Sent to Third Party |
Pending Printout |
Failed - Pending Print Timeout |
Failed - Inactive User |
Failed - No ALP Clients |
Failed - Rendering Failed |
No Printable Content |
Rendering Started |
Rendering Completed |
Failed - Output Failed |
Output Started |
Output Completed |
Failed - Third Party Error |
Failed - Local Printing Failure |
Batch Collecting Jobs |
Batch Started Printing |
Batch Finished Spooling |
Batch Finished |
Pending Printout |
Retrieving Downtime Job Metadata |
Retrieving Downtime Job Data |
Processing Downtime Job |
Failed - WBS Report Import |
Waiting Downtime Job Pickup |
Downtime Job Contains No Data |
File Ready to Save |
Expired |
Failed - User Canceled |
Waiting for Pickup - Flood Controlled |
Submitted - Flood Controlled |
|
|