# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.001 | number | 11 | This allows users to select entries by the internal number. | |||
.01 | name(+) | 0;1 | POINTER | 2 | B | This is the name of a patient that has some type of pharmacy order. |
.02 | cap | 0;2 | SET OF CODES | 1:NON-SAFETY 0:SAFETY | This field is used to indicate if safety caps are to be issued to patient. | |
.03 | 0;3 | SET OF CODES | 0:REGULAR MAIL 1:CERTIFIED MAIL 2:DO NOT MAIL 3:LOCAL - REGULAR MAIL 4:LOCAL - CERTIFIED MAIL | This field is used to: A) Determine whether this patient's Rx's are to be sent to the CMOP, or retained for local distribution. If 2-4 are selected, none of this patient's Rx's will be transmitted to the CMOP. B) Select what the mail priority is. The CMOP choices are limited to (0) REGULAR and (1) CERTIFIED. Local mail may be designated (3) LOCAL - REGULAR or (4) LOCAL - CERTIFIED. The 'DO NOT MAIL' code (2) may be used to ensure that the patient's Rx's are not mailed. | ||
.04 | dialysis patient | 0;4 | BOOLEAN | 0:NO 1:YES | ADIA | This field is used to indicate if the patient is in dialysis. |
.05 | mail status expiration date | 0;5 | DATE-TIME | This field places a time limit on the 'Do Not Mail', 'Local - Regular Mail' and 'Local - Certified Mail' conditions in the 'MAIL' field. If a date is placed in this field and the software detects that the date the Rx is processed is greater than the date in the field (past the expired date) a default value of 'Regular Mail' will be assumed for the 'MAIL' field. NOTE: The actual value of the 'MAIL' field will not be changed by the software, but can only be modified by a user editing the 'MAIL' field. | ||
.07 | first service date | 0;7 | DATE-TIME | This is the login date of the first order for pharmacy services. | ||
.08 | actual/historical flag | 0;8 | SET OF CODES | A:ACTUAL H:HISTORICAL | The purpose of this field is to indicate whether the FIRST SERVICE DATE field was populated with actual or historical data. Actual indicates the field was populated when the first pharmacy service was filed. Historical indicates the field was populated by the conversion routine. | |
1 | narrative | 1;1 | FREE TEXT | This is notable information about the patient that pertains to pharmacy. | ||
3 | patient status | PS;1 | POINTER | 53 | This field is used to indicate a default patient status. | |
40 | community nursing home | 40;1 | BOOLEAN | 1:YES | This field is used to indicate if the patient resides within a community nursing home. | |
40.1 | nursing home contract | 40;2 | BOOLEAN | 1:YES | This field is used to indicate if the patient has a nursing home contract. | |
40.2 | last date of contract | 40;3 | DATE-TIME | This field is used to indicate the last date of the nursing home contract. | ||
41 | respite patient start date | 40;4 | DATE-TIME | This field is used to indicate the start date of respite care. | ||
41.1 | respite patient end date | 40;5 | DATE-TIME | This field is used to indicate the end date of respite care. | ||
50 | active scripts | COMPUTED | This field is used to indicate active prescriptions. | |||
52 | prescription profile | P;0 | MULTIPLE | 55.03 | This sub-file is used to indicate prescription history for this patient. | |
52.1 | rx update | 0;6 | SET OF CODES | 0:Nothing updated 1:Data movement complete 2:Backfill complete | This field is used to indicate if the patient's medications have been updated in the CPRS orders file. If the field is 0, nothing has been updated, 1 indicates the initial data movement is complete, and 2 indicates the Backfill to CPRS is complete. | |
52.2 | non-va meds | NVA;0 | MULTIPLE | 55.05 | This is the Non-VA Meds order multiple. It will be used to store the Non-VA Med orders entered through the CPRS application. | |
53 | clozapine registration number | SAND;1 | FREE TEXT | ASAND1 | This is the patient's authorization number assigned by national data base. | |
54 | clozapine status | SAND;2 | SET OF CODES | P:PRE-TREATMENT A:ACTIVE TREATMENT H:TREATMENT ON HOLD D:DISCONTINUED | This is the patient's clozapine treatment status. | |
55 | date of last clozapine rx | SAND;3 | DATE-TIME | This is the date of the patient's last clozapine prescription. | ||
56 | demographics sent | SAND;4 | BOOLEAN | 1:YES 0:NO | This indicates whether patient demographic data has been sent to the national database. | |
57 | responsible provider | SAND;5 | POINTER | 200 | This is the physician responsible for the patient's clozaril treatment. | |
58 | registration date | SAND;6 | DATE-TIME | This field is used to enter the date of registration. | ||
62 | unit dose | 5;0 | MULTIPLE | 55.06 | This represents the 'top' of the UNIT DOSE SUB-FILE, where all of a patient's active (and expired & dc'd) UNIT DOSE orders are kept. Although orders are initially entered into ^PS(53.1), the order is transferred into this sub-file (^PSGOT) upon verification. | |
62.01 | ud default stop date/time | 5.1;1 | DATE-TIME | This is date used as a default value for the STOP DATE/TIME of Unit Dose orders during the order entry and renewal processes, if the corresponding site parameter is turned on. The order entry and renewal processes will sometimes change this date. | ||
62.02 | ud provider | 5.1;2 | POINTER | 200 | This is the latest provider for this patient, used as a default value in order entry. | |
62.03 | ud last admission date | 5.1;3 | DATE-TIME | This is the last admission date for this patient. | ||
62.04 | ud last transfer date | 5.1;4 | DATE-TIME | This is the last transfer date for this patient. | ||
62.05 | ud last discharge date | 5.1;5 | DATE-TIME | This is the last discharge date for this patient. | ||
62.06 | ud exp up-date | 5.1;6 | DATE-TIME | This is a date used to update expired orders. (Internal) | ||
62.07 | ud hold flag | 5.1;7 | SET OF CODES | 0:ORDERS NOT ON HOLD 1:ORDERS ON HOLD 2:ORDERS AUTOMATICALLY PLACED ON HOLD | This is an internal flag set when all of the patient's orders have been placed on hold. If '2', all of a patient's Unit Dose AND IV orders were placed on hold automatically by the package. | |
62.08 | ud discharge flag | 5.1;8 | SET OF CODES | 1:PATIENT HAS BEEN DISCHARGED | This is an internal flag set when a patient is first found to have been discharged. It is set so that Inpatient Meds does not try to cancel the patient's orders every time the patient is accessed while discharged. | |
62.1 | comments | 5.2;0 | WORD-PROCESSING | This is used for temporary storage of data by the Unit Dose package. The data is deleted before and after each use! | ||
62.11 | hold reason | 5.1;10 | FREE TEXT | This is an explanation of why this patient's orders are being placed on hold. This explanation will show on the patient's Unit Dose profile. | ||
62.16 | *last ud order converted to v4 | 5.1;16 | FREE TEXT | This is the last Unit Dose order converted for use with version 4 of the Inpatient Medications package. THIS SHOULD NOT BE EDITED. Editing could result in corrupted data and possibly medication administration errors. | ||
62.2 | inpatient narrative | 5.3;1 | FREE TEXT | This field stores the Inpatient pharmacy narrative for the patient. | ||
63 | *ud stop date | 5.1;1 | DATE-TIME | This field is used by the UNIT DOSE PHARMACY package. It is NOT to be entered into anywhere else! | ||
99 | *no. of iv orders | COMPUTED | ||||
100 | iv | IV;0 | MULTIPLE | 55.01 | This subfile contains IV order information for any given patient. A separate IV order file does not exist. This isn't the same design as outpatient pharmacy -- which does contain a separate file for prescriptions. | |
101 | archive date | ARC;0 | MULTIPLE | 55.13 | This sub file is used to indicate archived prescriptions. | |
102 | *last admission number | IVD;1 | FREE TEXT | This field is updated by the IV PACKAGE every time action is taken on this particular patient. This piece will have two pieces of information on it. The first piece ('-' is the delimiter) is the current admissions number, and the second piece is the discharge date for this admissions number. This field is used for determining whether or not to DC IV ORDERS due to ADMISSIONS or DISCHARGE. | ||
102.1 | *last service | IVD;2 | SET OF CODES | M:MEDICINE S:SURGERY P:PSYCHIATRY NH:NHCU NE:NEUROLOGY I:INTERMIDIATE MED R:REHAB MEDICINE SCI:SPINAL CORD INJURY D:DOMICILLARY B:BLIND REHAB | This piece is updated by the IV PACKAGE every time this particular patient has any 'IV ACTION'. This piece represents the service of the last ward that this patient was in. It is a set of codes that was taken from the ADT package. This field is used to determine whether or not to DC IV ORDERS due to SERVICE transfer. | |
102.2 | *last interward transfer | IVD;3 | NUMERIC | This field is updated by the IV PACKAGE every time this particular patient has any 'IV ACTION'. This field represents the last INTERWARD TRANSFER NUMBER for the LAST ADMISSION NUMBER. This field is used to determine whether or not to DC IV ORDERS due to WARD TRANSFER. ORDERS due to SERVICE transfer. | ||
103 | *last iv order converted (4.0) | 5.1;9 | NUMERIC | This is the last IV order for a patient that had it's data converted to the New Person file (200). | ||
104 | conversion completed? | 5.1;11 | SET OF CODES | 1:VERSION 5 2:POE 3:IV VERIFIED | This field contains a 1 if the conversion to the patient's orders for version 5.0 has completed. It contains a 2 if the conversion to the patient's orders for Pharmacy Ordering Enhancement (POE) has completed. It contains a 3 if the patient's IV orders existed prior to BCMA V.2.0 has updated the Verifying Pharmacist field. | |
105 | bcma id | IVBCMA;0 | MULTIPLE | 55.0105 | This is the unique barcode ID in the format DFN_"V"_ID# ex: 740V1. | |
106 | other language preference | LAN;1 | BOOLEAN | 1:YES | This field is used to identify patients who have another language preference for printing medication instructions on bottle labels. | |
106.1 | pmi language preference | LAN;2 | SET OF CODES | 1:ENGLISH 2:SPANISH | This field will be used to determine the default language preference for printing the PMI sheets at the CMOPs. | |
108 | scriptalk enrollment activity | SCTALK;0 | MULTIPLE | 55.0108 | This multiple contains the history log information for ScripTalk enrollment activities for a patient. |