|
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_ID |
VARCHAR |
No |
|
|
|
The unique ID of the patient record for this row. This column is frequently used to link to the PATIENT table. |
|
|
4 |
CONTACT_DATE |
DATETIME |
No |
|
|
|
The date of this contact in calendar format. |
|
|
5 |
CM_CT_OWNER_ID |
VARCHAR |
No |
|
|
|
The Community ID (CID) of the instance that owns this contact. This is only populated if you use IntraConnect. |
|
|
6 |
COORD_NOTE_ID |
VARCHAR |
No |
|
|
|
Contains the HNO (unified clinical notes master file) IDs of any coordination notes that have been created for the current patient encounter. Coordination notes exist to document any additional context surrounding current service coordination plans that cannot be documented in the plan itself. |
|
|
7 |
NOTE_IS_PINNED_YN |
VARCHAR |
No |
|
|
|
Matches with an HNO ID stored in I EPT 97118, and documents if that coordination note is "pinned." Pinned coordination notes will show up in the Services to Coordinate navigator section, and any users accessing that patient's chart will be able to see that note during service coordination. |
May contain organization-specific values: No |
Category Entries: |
No |
Yes |
|
|