|
Name |
Type |
Discontinued? |
|
1 |
COMM_TRACE_ID |
NUMERIC |
No |
|
|
|
The unique identifier (.1 item) for the outreach record record. |
|
|
2 |
CONTACT_SERIAL_NUM |
NUMERIC |
No |
|
|
|
The contact serial number (CSN) of the contact. |
|
|
3 |
CONTACT_DATE_REAL |
FLOAT |
No |
|
|
|
A unique contact date 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. |
|
|
4 |
TEMPLATE_SETTING_ID |
NUMERIC |
No |
|
|
|
Contains the base template that was sent for this trace. |
|
|
5 |
TEMPLATE_SETTING_ID_SETTING_NAME |
VARCHAR |
No |
|
|
|
|
6 |
ROOT_TEMPLATE_SETTING_ID |
NUMERIC |
No |
|
|
|
Contains the root base template sent to start the conversation this trace is a part of. |
|
|
7 |
ROOT_TEMPLATE_SETTING_ID_SETTING_NAME |
VARCHAR |
No |
|
|
|
|
8 |
COMM_DIRECTION_C_NAME |
VARCHAR |
No |
|
|
|
The direction of this trace. |
May contain organization-specific values: No |
Category Entries: |
Outgoing |
Incoming |
|
|
9 |
SENDER_SETTING_ID |
NUMERIC |
No |
|
|
|
The sender record used to send this trace. |
|
|
10 |
SENDER_SETTING_ID_SETTING_NAME |
VARCHAR |
No |
|
|
|
|
11 |
SEGMENT_COUNT |
INTEGER |
No |
|
|
|
The number of individual messages that the underlying gateway actually sent for this one message. |
|
|
12 |
COMM_STATUS_C_NAME |
VARCHAR |
No |
|
|
|
The status of this trace. |
May contain organization-specific values: No |
Category Entries: |
Created |
Queued |
Sidetracked |
Session Active |
To Interconnect |
To Cloud |
Pending |
Sent |
Delivered |
Canceled |
Expired |
Failed |
Unknown |
Auto-Invite Tank |
Auto-Invite Queue |
Multiple Statuses |
ECS Not In Use |
|
|
13 |
LEGACY_CONTENT_YN |
VARCHAR |
No |
|
|
|
If the content of this trace came from legacy content that was passed into the cache API, this flag should be set to indicate that this content DID NOT come from ECS build. |
May contain organization-specific values: No |
Category Entries: |
No |
Yes |
|
|
14 |
LANGUAGE_ID |
NUMERIC |
No |
|
|
|
Contains the language that was requested for this trace. |
|
|
15 |
LANGUAGE_ID_LANGUAGE_NAME |
VARCHAR |
No |
|
|
|
The language name. If the language is written and uses more than one script to represent it, the name will contain the script in parentheses after the language name. |
|
|
16 |
RECV_PAT_ID |
VARCHAR |
No |
|
|
|
If the recipient for the trace has an EPT, this should point to it. |
|
|
17 |
RECV_ACCOUNT_ID |
NUMERIC |
No |
|
|
|
If the recipient for the trace has an EAR, this should point to it. |
|
|
18 |
RECV_PAT_RELATION_ID |
NUMERIC |
No |
|
|
|
If the recipient for the trace has a RLA, this should point to it. |
|
|
19 |
RECV_MYPT_ID |
VARCHAR |
No |
|
|
|
If the recipient for the trace has a WPR, this should point to it. |
|
|
20 |
ABOUT_PAT_ID |
VARCHAR |
No |
|
|
|
If this trace was about a specific patient, then this item should point to that patient. Note that the patient need not necessarily be a recipient. |
|
|
21 |
ABOUT_ACCOUNT_ID |
NUMERIC |
No |
|
|
|
If this trace was about a specific guarantor, then this item should point to that guarantor. Note that the guarantor need not necessarily be a recipient. |
|
|
22 |
COMM_CREATE_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
UTC that this trace was created in the database. |
|
|
23 |
SEND_REQ_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
UTC that this trace was requested be sent. |
|
|
24 |
TO_CLOUD_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
UTC that this trace was actually sent. |
|
|
25 |
SEND_EXP_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
UTC time after which this message should NOT be sent. |
|
|
26 |
DELIVERY_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
The UTC instant that that the message was delivered (or as close as we can detect it). |
|
|
27 |
CLOUD_RECV_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
The UTC instant that cloud reports having received this message. |
|
|
28 |
DB_RECV_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
The UTC instant that cache received this message. |
|
|
29 |
COMM_EXT_NUMBER |
VARCHAR |
No |
|
|
|
The external number associated with this trace. Data should be stored in E.164 format. The external number is the "to" number when sending from Epic, and the "from" number when receiving a mobile-originated message. |
|
|
30 |
COMM_INT_NUMBER |
VARCHAR |
No |
|
|
|
The internal number associated with this trace. Data should be stored in E.164 format. The internal number is the "from" number when sending from Epic, and the "to" number when receiving a mobile-originated message. |
|
|
31 |
CONTENT_UTF_TEXT |
VARCHAR |
No |
|
|
|
The content for the trace. This string should be UTF-8 encoded. The cloud foundation API limits characters to 1500. While not a perfect comparison using server logic, this item also uses 1500. A pure W1252 message is capped at 1500. With UTF8 characers taking various numbers of bytes, a UTF8 message may a lower limit, but that would be based on the characters used. |
|
|
32 |
CLOUD_MSG_IDENT |
VARCHAR |
No |
|
|
|
The message ID for this trace that was assigned from the cloud/gateway. |
|
|
33 |
FACILITY_ID_LOC_NAME |
VARCHAR |
No |
|
|
|
The name of the revenue location. |
|
|
34 |
SERV_AREA_ID_LOC_NAME |
VARCHAR |
No |
|
|
|
The name of the revenue location. |
|
|
35 |
LOC_ID_LOC_NAME |
VARCHAR |
No |
|
|
|
The name of the revenue location. |
|
|
36 |
DEPARTMENT_ID_EXTERNAL_NAME |
VARCHAR |
No |
|
|
|
The external name of the department record. This is often used in patient correspondence such as reminder letters. |
|
|
37 |
BUS_SEG_POS_ID_LOC_NAME |
VARCHAR |
No |
|
|
|
The name of the revenue location. |
|
|
38 |
PRIORITY |
INTEGER |
No |
|
|
|
The priority for this trace. A value from 1-99 (inclusive) where 1 is high and 99 is low. Code should not set arbitrary values, code should use one of the predefined priority buckets using constants, eg: $$ecsConstPriorityMedium(). |
|
|
39 |
PRE_COMM_WIN_SEND_REQ_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
UTC instant that this trace was requested to be sent before applying communication window restrictions. |
|
|
40 |
TO_VENDOR_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
UTC instant the status of this trace was updated to PENDING, indicating the message has been passed from cloud to the vendor. |
|
|
41 |
TO_NETWORK_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
UTC instant the status of this trace was updated to Sent, indicating the message has been passed on to the network. |
|
|
42 |
FAILURE_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
UTC instant the status of this trace was updated to Failed, indicating the message delivery has failed. |
|
|
43 |
SORT_INST_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
UTC instant that represents when the message was sent or received. |
|
|
44 |
RECV_USER_ID |
VARCHAR |
No |
|
|
|
If the recipient for the trace has an EMP, this should point to it. |
|
|
45 |
RECV_USER_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
46 |
ROOT_WORKFLOW_SETTING_ID |
NUMERIC |
No |
|
|
|
Contains the root base workflow associated with the template sent to start the conversation this trace is a part of. |
|
|
47 |
ROOT_WORKFLOW_SETTING_ID_SETTING_NAME |
VARCHAR |
No |
|
|
|
|
48 |
INT_EMAIL |
VARCHAR |
No |
|
|
|
The email address used to send a specific email trace: the "from" email address when sending email from Epic. |
|
|
49 |
COMPUTED_LANGUAGE_ID |
NUMERIC |
No |
|
|
|
Contains the language that was computed for this trace. |
|
|
50 |
COMPUTED_LANGUAGE_ID_LANGUAGE_NAME |
VARCHAR |
No |
|
|
|
The language name. If the language is written and uses more than one script to represent it, the name will contain the script in parentheses after the language name. |
|
|
51 |
USED_LANGUAGE_ID |
NUMERIC |
No |
|
|
|
Contains the language that was actually used for this trace. |
|
|
52 |
USED_LANGUAGE_ID_LANGUAGE_NAME |
VARCHAR |
No |
|
|
|
The language name. If the language is written and uses more than one script to represent it, the name will contain the script in parentheses after the language name. |
|
|
53 |
COMM_CHANNEL_C_NAME |
VARCHAR |
No |
|
|
|
Communication channel used to send this trace. |
May contain organization-specific values: No |
Category Entries: |
SMS |
Email |
Voice |
MMS |
Web |
Push Notification |
|
|
54 |
VOICE_EVENT_TYPE_C_NAME |
VARCHAR |
No |
|
|
|
Type of event for a voice call. |
May contain organization-specific values: No |
Category Entries: |
Started |
Input |
Outbound Content |
Invalid Response |
No Response |
|
|
55 |
SESS_SUMMARY_STAT_C_NAME |
VARCHAR |
No |
|
|
|
Summary of the end state of a session. This item will only be populated on the first trace of a session. |
May contain organization-specific values: No |
Category Entries: |
Completed |
In Progress |
Incomplete |
Delayed |
Failed |
Rejected |
Timeout |
Canceled |
Voicemail |
Line Busy |
Unanswered |
Unknown |
|
|
56 |
VOICE_CONVERSATION_UID |
VARCHAR |
No |
|
|
|
Unique ID specifically for the entire conversation. This is different from the call leg ID. |
|
|
57 |
VOICE_KEYPAD_INPUT |
VARCHAR |
No |
|
|
|
DTMF (keypad) input from the voice call. |
|
|