EXT_ELIG_STATUS
Description:
This table stores results of eligibility queries returned by RxHub. The related External Eligibility Query Line information is stored in the EXT_ELIG_STATUS_1 table.

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 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 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.
5 CONTACT_DATE DATETIME No
The date of this contact in calendar format.
6 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.
7 EXT_FORM_STATUS_C_NAME VARCHAR No
The external formulary query status category number for this eligibility query.
May contain organization-specific values: No
Category Entries:
Valid
Valid no Data
Not Found
Canceled
Deferred
E-Pending
Connectivity/Syntax Error
Copied Connect/Syntax Error
Copied E-Pending
8 EXT_FORM_SENT_TM DATETIME (Local) No
The date and time when the external formulary query was sent.
9 EXT_FORM_RECVD_TM DATETIME (Local) No
The date and time that the external formulary query was received.
10 EXT_FORM_ACUTE_YN VARCHAR No
Flag to indicate if the eligibility query was sent as an acute care query.
May contain organization-specific values: No
Category Entries:
Yes
No
11 ACUTE_CARE_MSG VARCHAR No
To store the message ID returned from ISA13 in the query so we can send it in the med history request