|
Name |
Type |
Discontinued? |
|
1 |
EPISODE_ID |
NUMERIC |
No |
|
|
|
The unique ID of the episode of care record. |
|
|
2 |
NAME |
VARCHAR |
No |
|
|
|
|
3 |
SUM_BLK_TYPE_ID_EPISODE_DEF_NAME |
VARCHAR |
No |
|
|
|
This column displays the name of the episode / block definition record. |
|
|
4 |
START_DATE |
DATETIME |
No |
|
|
|
The date the episode was initiated. |
|
|
5 |
END_DATE |
DATETIME |
No |
|
|
|
The date the episode was resolved in calendar format. This field is called "Resolved" on the clinical system screen. |
|
|
6 |
COMMENTS |
VARCHAR |
No |
|
|
|
Any free text comments about the episode. |
|
|
7 |
PREGRAVID_WEIGHT |
NUMERIC |
No |
|
|
|
This field contains the pre-pregnancy weight maintained before this episode. |
|
|
8 |
NUMBER_OF_BABIES |
INTEGER |
No |
|
|
|
Prior to delivery, this column is expected to contain the number of fetuses that the patient is carrying. This can be manually documented, such as in the Prenatal Vitals section, or the value can be automatically set by creating or removing fetal result tabs in the ultrasound activity. If your organization documents on the Delivery Summary then after the Delivery Summary is signed, this column is expected to contain the number of viable deliveries associated with the pregnancy. Specifically, this is the number of delivery records attached to the pregnancy. This expectation is based on Epic's recommendation that only viable deliveries should be documented on the Delivery Summary. Your organization may follow a different policy for when to create a delivery record. The behavior of this column containing the number of delivery records may be overridden at the profile level in system definitions, in which case it will continue to contain the number of fetuses that were being carried unless the number of deliveries is manually documented in its place. |
|
|
9 |
PRIMARY_LPL_ID |
NUMERIC |
No |
|
|
|
The primary problem linked to the episode. |
|
|
10 |
STATUS_C_NAME |
VARCHAR |
No |
|
|
|
The status category number for the episode. |
May contain organization-specific values: No |
Category Entries: |
Active |
Resolved |
Deleted |
|
|
11 |
L_UPDATE_USER_ID |
VARCHAR |
No |
|
|
|
The ID of the last user that updated the episode of care record. |
|
|
12 |
L_UPDATE_USER_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
13 |
PATERNITY_ACK_C_NAME |
VARCHAR |
No |
|
|
|
Whether a paternity acknowledgement has been signed by the biological father of the baby if the parents are not married. This column may not be applicable depending on the identity of the second parent and the two parents' relationship. |
May contain organization-specific values: Yes |
Category Entries: |
Yes |
No |
Unknown |
Unnecessary |
|
|
14 |
SMOKE_3_MO_BEF |
INTEGER |
No |
|
|
|
The number of cigarettes/packs smoked per day 3 months before the pregnancy by the mother. |
|
|
15 |
SMOKE_3_MO_BEF_C_NAME |
VARCHAR |
No |
|
|
|
The unit of measurement for the quantity of cigarettes being smoked 3 months before the pregnancy by the mother. |
May contain organization-specific values: Yes |
Category Entries: |
Packs |
Cigarettes |
|
|
16 |
SMOKE_1ST_3_MO |
INTEGER |
No |
|
|
|
The number of cigarettes/packs smoked per day in the first 3 months of the pregnancy by the mother. |
|
|
17 |
SMOKE_1ST_3_MO_C_NAME |
VARCHAR |
No |
|
|
|
The unit of measurement for the quantity of cigarettes being smoked the first three months of the pregnancy by the mother. |
The category values for this column were already listed for column: SMOKE_3_MO_BEF_C_NAME |
|
|
18 |
SMOKE_2ND_3_MO |
INTEGER |
No |
|
|
|
The number of cigarettes/packs smoked per day in the second 3 months of the pregnancy by the mother. |
|
|
19 |
SMOKE_2ND_3_MO_C_NAME |
VARCHAR |
No |
|
|
|
The unit of measurement for the quantity of cigarettes being smoked the second three months of the pregnancy by the mother. |
The category values for this column were already listed for column: SMOKE_3_MO_BEF_C_NAME |
|
|
20 |
SMOKE_3RD_TRI |
INTEGER |
No |
|
|
|
The number of cigarettes/packs smoked per day in the third trimester of the pregnancy by the mother. |
|
|
21 |
SMOKE_3RD_TRI_C_NAME |
VARCHAR |
No |
|
|
|
The unit of measurement for the quantity of cigarettes being smoked the third trimester of the pregnancy by the mother. |
The category values for this column were already listed for column: SMOKE_3_MO_BEF_C_NAME |
|
|
22 |
DRINK_3_MO_BEF |
INTEGER |
No |
|
|
|
The number of alcoholic drinks consumed per week 3 months before the pregnancy by the mother. |
|
|
23 |
DRINK_1ST_3_MO |
INTEGER |
No |
|
|
|
The number of alcoholic drinks consumed per week in the first three months of the pregnancy by the mother. |
|
|
24 |
DRINK_2ND_3_MO |
INTEGER |
No |
|
|
|
The number of alcoholic drinks consumed per week in the second three months of the pregnancy by the mother. |
|
|
25 |
DRINK_3RD_TRI |
INTEGER |
No |
|
|
|
The number of alcoholic drinks consumed per week in the third trimester of the pregnancy by the mother. |
|
|
26 |
IN_CITY_LIMITS_YN |
VARCHAR |
No |
|
|
|
Whether the address of the mother is inside the city limits. |
May contain organization-specific values: No |
Category Entries: |
No |
Yes |
|
|
27 |
WIC_FOODS_YN |
VARCHAR |
No |
|
|
|
Did the mother receive WIC foods during this pregnancy? |
The category values for this column were already listed for column: IN_CITY_LIMITS_YN |
|
|
28 |
TOTAL_PNC |
INTEGER |
No |
|
|
|
Override value to be used in situations where not all prenatal care was given at the same Epic provider and so not all prenatal care visits are in the system. |
|
|
29 |
MONTH_1ST_PNC |
INTEGER |
No |
|
|
|
Override value to be used in situations where not all prenatal care was given at the same Epic provider and so first date of prenatal care is not in the system and the month of the pregnancy when prenatal care began cannot be calculated. |
|
|
30 |
LIVE_BIRTHS_LIVING |
INTEGER |
No |
|
|
|
Override value to be used in situations where not all prenatal care was given at the same Epic provider, and consequently, other pregnancy information is not available. The number of children born alive which are still living not including children born at this birth. |
|
|
31 |
LIVE_BIRTHS_DEAD |
INTEGER |
No |
|
|
|
Override value to be used in situations where not all prenatal care was given at the same Epic provider, and consequently, other pregnancy information is not available. The number of other children born alive which are now deceased not including any born alive and deceased at this birth. |
|
|
32 |
MOTHER_MARRIED_YN |
VARCHAR |
No |
|
|
|
Whether the mother is married at birth, conception, or any time in between. |
The category values for this column were already listed for column: IN_CITY_LIMITS_YN |
|
|
33 |
OB_PREGRAVID_BMI |
NUMERIC |
No |
|
|
|
The patient's pre-pregnancy BMI for this pregnancy episode. |
|
|
34 |
FIRST_PNT_LOC_C_NAME |
VARCHAR |
No |
|
|
|
This item stores who the patient's first prenatal care was with. |
May contain organization-specific values: Yes |
|
|
35 |
SERV_AREA_ID_LOC_NAME |
VARCHAR |
No |
|
|
|
The name of the revenue location. |
|
|
36 |
OB_WRK_EDD_DT |
DATETIME |
No |
|
|
|
The estimated date of delivery for a pregnancy episode. |
|
|
37 |
EXPECTED_DEL_LOC_C_NAME |
VARCHAR |
No |
|
|
|
Location where the woman plans to deliver her baby. |
May contain organization-specific values: Yes |
|
|
38 |
DEL_LOC_CHANGE_C_NAME |
VARCHAR |
No |
|
|
|
Why the delivery location changed from the expected delivery location (EXPECTED_DEL_LOC_C) for a pregnancy episode. |
May contain organization-specific values: Yes |
|
|
39 |
OB_FEEDING_INTENTIONS_C_NAME |
VARCHAR |
No |
|
|
|
Mother's intended feeding method for the baby. |
May contain organization-specific values: Yes |
Category Entries: |
Breast Milk |
Formula |
Breast Milk and Formula |
|
|
40 |
INTENT_TREAT_C_NAME |
VARCHAR |
No |
|
|
|
The intended treatment for an implanted Mechanical Circulatory Device. |
May contain organization-specific values: Yes |
Category Entries: |
Medical Management |
Bridge to Recovery |
Rescue Therapy |
Bridge to Transplant - Currently Listed |
Possible Bridge to Transplant - Likely Eligible |
Possible Bridge to Transplant - Moderate Likelihood |
Possible Bridge to Transplant - Unlikely Eligible |
Destination Therapy - Modifiable |
Destination Therapy - Unmodifiable |
Unknown |
Other |
|
|
41 |
INTENT_TREAT_OTHR |
VARCHAR |
No |
|
|
|
The free text intended treatment for an implanted Mechanical Circulatory Device. |
|
|
42 |
MCS_DISCHARGE_DT |
DATETIME |
No |
|
|
|
Date a Mechanical Circulatory Device patient is discharged. |
|
|
43 |
MCS_EVAL_DT |
DATETIME |
No |
|
|
|
The start date of the Mechanical Circulatory Device evaluation. |
|
|
44 |
MCS_REV_DT |
DATETIME |
No |
|
|
|
The date when the Mechanical Circulatory Device case was reviewed by the evaluation committee. |
|
|
45 |
MCS_ADMISSION_DT |
DATETIME |
No |
|
|
|
Date of the admission for the Mechanical Circulatory Device procedure. |
|
|
46 |
MCS_SURG_DT |
DATETIME |
No |
|
|
|
The date of the Mechanical Circulatory Device surgery. |
|
|
47 |
MCS_IS_HISTORIC_YN |
VARCHAR |
No |
|
|
|
Flag indicating a historic Mechanical Circulatory Device episode. This is intended to flag if the Device was implanted at another center than the Center that is currently following the patient. |
May contain organization-specific values: No |
Category Entries: |
Yes |
No |
|
|
48 |
MCS_EVAL_END_DT |
DATETIME |
No |
|
|
|
The date on which the Mechanical Circulatory Device evaluation was completed. |
|
|
49 |
MCS_NEXT_REVIEW_DT |
DATETIME |
No |
|
|
|
The date on which both the Mechanical Circulatory Device episode and the patient chart should be reviewed. |
|
|
50 |
MCS_REFERRAL_DT |
DATETIME |
No |
|
|
|
The date the patient was referred for the Mechanical Circulatory Device. |
|
|
51 |
MCS_TXPORT_MTHD_C_NAME |
VARCHAR |
No |
|
|
|
The method of transportation to the implantation center. |
May contain organization-specific values: Yes |
Category Entries: |
Car |
Ambulance |
Airplane |
Helicopter |
|
|