Files > ORDER DEA ARCHIVE INFO

name
ORDER DEA ARCHIVE INFO
number
101.52
location
^ORPA(101.52,
description
The purpose of this file is to satisfy the Drug Enforcement Agency (DEA) requirement for an electronic prescribing system to maintain an archive of all controlled substance prescriptions that were electronically entered. The file will store all the information that is considered a part of the prescription. The file should always be audited. In addition, the file should NEVER be edited using FileMan. These are both DEA requirements. In order to satisfy the requirement that both the prescribing (CPRS) and filling systems (Outpatient Pharmacy) create an archive, but to reduce the need for additional storage space, both CPRS and Pharmacy will use the same file. CPRS will create the entries when an order is signed or when a backdoor order message is received from Pharmacy. Once Pharmacy verifies the data in the Pharmacy system is an exact match for what CPRS stored, they will subscribe to the entry in the archive file and will update the PRESCRIPTION NUMBER (#1) field. The file was defined in a different global name in order to handle the volume set from the rest of the CPRS system (i.e., the ORDER file). It is important to note that to fully meet the DEA requirements, the fields required by the DEA cannot be pointers. We must store the data completely. The fields that are pointers are for our internal use, rather than for the DEA purposes.
Fields
#NameLocationTypeDetailsIndexDescription
.01cprs order number(+)0;1POINTER100BThe CPRS order number that is associated with this archive entry.
1prescription number0;2POINTER52The prescription number associated with this archive entry. This field is populated once Outpatient Pharmacy has determined that the contents of the prescription received match what was entered by the provider.
2dig sig hash0;3FREE TEXTThis is the digital signature hash associated with this order. This 'hash' is calculated by a Microsoft API that is called by the Kernel code during the signature process in CPRS. It is stored here so that, at any time, a hash can be calculated and compared to this value to ensure the contents have not changed.
4issuance date1;1DATE-TIMEThis is the date this order was issued. In other words, what date was it entered into CPRS.
6drug name1;2FREE TEXTThis is the drug name associated with the CPRS orderable item for this order. It will only be present if the dispense drug is known at the time the archive entry is created. This information comes from the GENERIC NAME field (#.01) from the DRUG file (#50).
8qty prescribed1;5NUMERICThis is the quantity of pills/tablets/liquid specified by the provider for this order. This field correlates to the QTY field (#7) in the PRESCRIPTION file (#52).
9directions for use (sig)2;0MULTIPLE101.529This is a multiple field for storing the directions for use. In this particular storage location, directions are stored in the format that they are transmitted via the HL7 array and protocols to Pharmacy, rather than in human readable format.
10dea #3;1FREE TEXTThis is the DEA license number of the provider that signed the order. The DEA number is pulled from one of two places. If present and valid, it will be the DEA# field (#53.2) in the NEW PERSON file (#200) at the time the order is signed. If the provider doesn't have personal DEA credentials, this field will contain the facility DEA number, followed by a '-', followed by the provider's VA suffix. This number pulls from the FACILITY DEA NUMBER field (#52) in the INSTITUTION file (#4) and the VA# field (#53.3) in the NEW PERSON file (#200).
11detox #3;2FREE TEXTThis is the Detox/Maintenance license number associated with the provider that signed this order. This comes from the DETOX/MAINTENANCE ID NUMBER field (#53.11) from the NEW PERSON file (#200) at the time the order is signed. Not every medication requires a Detox/Maintenance license, so this field will frequently be blank.
12provider name3;3FREE TEXTThe name of the provider, from the NAME field (#.01) of the NEW PERSON file (#200), at the time the order is signed.
13provider address #14;1FREE TEXTThis is the VA facility name where this order was signed. This comes from the NAME field (.01) of the INSTITUTION file (#4).
14provider address #24;2FREE TEXTThis is the first line of the street address for the VA facility where this order was signed. This comes from the STREET ADDR. 1 field (1.01) of the INSTITUTION file (#4).
15provider address #34;3FREE TEXTThis is the second line of the street address of the VA facility where this order was signed. This comes from the STREET ADDR. 2 field (#1.02) in the INSTITUTION file (#4).
16provider city4;4FREE TEXTThis is the city associated with the VA facility where this order was signed. This comes from the CITY field (#1.03) in the INSTITUTION file (#4).
17provider state4;5FREE TEXTThis is the state associated with the VA facility where this order was signed. This is from the NAME field (.01) of the STATE file (#5).
17.5provider zip+44;6FREE TEXTThis is the ZIP or ZIP + 4 of the VA facility where this order was signed. This field comes from the ZIP field (#1.04) in the INSTITUTION file (#4).
18patient name5;1FREE TEXTThis is the patient name of the patient for whom the prescription was written and signed. This is correlated to the NAME field (#.01) of the PATIENT file (#2).
19patient5;2POINTER2This is the patient associated with this order.
20icn5;3FREE TEXTThis is the Integration Control Registration (ICN) number associated with the patient for which this order was written/signed. This is the value returned from GETICN^MPIF001. It may be a national ICN or a local ICN.
21patient address #16;1FREE TEXTThis is the address of the patient at the time the order was placed. It is the VAPA(1) return value from the call to ADD^VADPT. Assuming no temporary or foreign address, it would be the STREET ADDRESS [LINE 1] field (#.111) from the PATIENT file (#2).
22patient address #26;2FREE TEXTThis is address line 2 of the patient associated with this order. It is the VAPA(2) return value from the call to ADD^VADPT. Assuming no temporary or foreign address, it would be the STREET ADDRESS [LINE 2] field (#.112) from the PATIENT file (#2).
24patient address #36;3FREE TEXTThis is address line 3 for the patient associated with this order. It is the VAPA(3) return value from the call to ADD^VADPT. Assuming no temporary or foreign address, it would the STREET ADDRESS [LINE 3] field (#.113) from the PATIENT file (#2).
25patient city6;4FREE TEXTThis is the city associated with the address for the patient associated with this order. It is the VAPA(4) return value from the call to ADD^VADPT. Assuming no temporary or foreign address, it would the CITY field (#.114) from the PATIENT file (#2).
26patient state6;5FREE TEXTThis is the state for the address of the patient associated with this order. It is the VAPA(5) return value from the call to ADD^VADPT. Assuming no temporary or foreign address, it would the STATE field (#.115) from the PATIENT file (#2).
27patient zip+46;6FREE TEXTThis is the ZIP or ZIP+4 code for the city of the address for the patient associated with this order. It is the VAPA(6) return value from the call to ADD^VADPT. Assuming no temporary or foreign address, it would the ZIP CODE field (#.116) from the PATIENT file (#2).
28# of refills1;6NUMERICThis is the number of refills specified by the provider at the time the drug is ordered. There are some limitations on refills for controlled substances and there are times when Pharmacy may correct this after validating the hash. This is correlated to the # OF REFILLS (#9) of the PRESCRIPTION file (#52).
29dispense drug1;3POINTER50This is the dispense drug associated with this order. It is possible this field will be blank if there is no dispense drug known at the time the order was signed in CPRS.
30dea schedule1;4FREE TEXTThis is the Drug Enforcement Agency (DEA) drug schedule associated with the medication on this order. For example: 2 for a schedule two non-narcotic or 2n for the schedule two narcotic. This comes from the DEA, SPECIAL HDLG field (#3) in the DRUG file (#50).
31provider3;4POINTER200This is the provider who signed this order.
40source7;0MULTIPLE101.53
41stack8;1FREE TEXTStores the stack trace of the process that created this entry.

Not Referenced