|
Name |
Type |
Discontinued? |
|
| 1 |
VIPOR_EXEC_ID |
NUMERIC |
No |
|
|
|
| The unique identifier (.1 item) for the Variant Interpretation Pipeline Orchestrator (VIPOr) record. |
|
|
| 2 |
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. |
|
|
| 3 |
LINE |
INTEGER |
No |
|
|
|
| The line number for the information associated with this contact. Multiple pieces of information can be associated with this contact. |
|
|
| 4 |
CONDITION_DX_ID_DX_NAME |
VARCHAR |
No |
|
|
|
| The name of the diagnosis. |
|
|
| 5 |
CONDITION_INCL_IN_REQUEST_YN |
VARCHAR |
No |
|
|
|
| Whether this clinical indication was included in the Variant Interpretation Pipeline Orchestrator (VIPOr) execution. A value of Yes indicates the clinical indication was sent to VIPOr as a pipeline argument. A value of No indicates the user chose to exclude this clinical indication from the run. All clinical indications presented to the user are stored in the group regardless of this value. |
| May contain organization-specific values: No |
| Category Entries: |
| No |
| Yes |
|
|
| 6 |
CONDITION_SOURCE_C_NAME |
NUMERIC |
No |
|
|
|
| The source of the clinical indication (i.e., where it was pulled from the chart). |
| May contain organization-specific values: No |
| Category Entries: |
| Manual |
| Order Diagnosis |
| Order Question |
| Test Build |
|
|