| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | trxn date/time(+) | 0;1 | DATE-TIME | B | This is the date/time (time is optional) of the transaction. | |
| .02 | device id(+) | 0;2 | FREE TEXT | This field identifies the unique device ID (eg, IP address or serial number) of the kiosk at which the patient performed the review of his/her allergies and medical history. | ||
| .03 | kiosk group(+) | 0;3 | FREE TEXT | This is the name of the kiosk group to which the kiosk belongs. | ||
| .04 | encounter clinic | 0;4 | POINTER | 44 | This is the clinic associated with the patient's appointment. | |
| .05 | appt date/time | 0;5 | DATE-TIME | This is the patient's appointment date/time (time is optional), taken from the APPOINTMENT DATE/TIME (#.001) field of the APPOINTMENT (#1900) multiple field of the PATIENT (#2) file. | ||
| .06 | provider | 0;6 | POINTER | 200 | This is the provider who conducts MRAR using the staff-facing module. | |
| .12 | mrar session id(+) | 0;11 | NUMERIC | The unique identifier of the AR or MR session initiated by the patient. | ||
| .13 | interface module | 0;12 | SET OF CODES | P:Patient-Facing Interface module S:Staff-Facing Interface module M:MHV O:Other | This field identifies the type of module which was used to initiate MRAR. | |
| 1 | ar initiated dt | 1;1 | DATE-TIME | This is the date/time (time is optional) stamp that a patient initiated Allergy Review. | ||
| 2 | ar completed dt | 1;2 | DATE-TIME | This is the date/time (time is optional) stamp the Allergy Review module was completed on a device. | ||
| 5 | ar incomplete dt | 1;5 | DATE-TIME | This is the date/time (time is optional) of AR module is incomplete in the patient-facing module. The AR INCOMPLETE REASON TYPE (#6) field lists reasons why the AR module might be incomplete. | ||
| 6 | ar incomplete reason type | 1;6 | SET OF CODES | 1:AR can't start, patient is too early,too late,or not early enough 2:Patient walked away or time limit expired 3:Patient selected to exit AR 4:Patient selected to bypass AR 5:Service Failure | This field contains the reason why AR module couldn't be completed. The AR Incomplete Reason type is one of the following: 1. The AR module could not be started because patient arrived TOO EARLY, TOO LATE, or NOT EARLY ENOUGH at the device. 2. Either the patient walked away in the middle of Allergy Review or the TIME LIMIT AR COMPLETE time expired. 3. The patient selected to exit the Allergy Review. 4. The patient selected to bypass the Allergy Review. 5. Service failure of VetLink at the site. TOO LATE, TOO EARLY, and NOT EARLY ENOUGH are defined in TIME LIMIT TOO LATE ARRIVAL (#7), TIME LIMIT TOO EARLY ARRIVAL (#8), and TIME LIMIT NOT EARLY ENOUGH (#9) fields of the PARAM INSTANCE (#853.01) subfile of VPS CONFIG HISTORY (#853). TIME LIMIT AR COMPLETE (#16) field is also defined in that subfile. | |
| 7 | ar session outcome | 1;7 | SET OF CODES | A:ABBREVIATED F:FULL | This field indicates that the AR session was full or abbreviated. It's a full session if the patient did review and returned in permitted period to re-review. It's abbreviated if the patient was just accepting the opportunity to review information and make any changes. | |
| 8 | add allergy initiated dt | 2;3 | DATE-TIME | This is the date/time (time is optional) that the patient initiated the additional allergy entry section of Allergy Review. | ||
| 9 | add allergy completed dt | 2;4 | DATE-TIME | This is the date/time (time is optional) that the patient completed the additional allergy section of AR in a session. | ||
| 10 | aller change completed dt | 1;8 | DATE-TIME | This is date/time (time is optional) stamp of the Allergy Review module was completed during a PDO invocable period. | ||
| 11 | aller change initiated dt | 1;9 | DATE-TIME | This is date/time (time is optional) stamp of the Allergy Review module was first activated during a PDO Invocable period. | ||
| 12 | ar free text used | 1;12 | SET OF CODES | 1:AR free text feature is used | This field indicates whether or not AR free text feature is being used. | |
| 13 | ar free text completed dt | 1;13 | DATE-TIME | This is the date/time (time is optional) that the patient-facing Allergy Review free text entry section was completed. | ||
| 14 | vet view add allergy comp dt | 1;14 | DATE-TIME | This is the date/time (time is optional) of the additional allergy interface in the staff-facing's Veteran view tab during a PDO invocable period was completed. | ||
| 15 | vet view add aller init dt | 1;15 | DATE-TIME | This is the date/time (time is optional) of the additional allergy interface was first activated in the staff-facing's Veteran view tab during a PDO invocable period. | ||
| 16 | vet view change aller comp dt | 1;16 | DATE-TIME | This is the date/time (time is optional) of the review-and-change allergy interface in the staff-facing's Veteran view tab was completed during a PDO invocable period. | ||
| 17 | vet view change aller init dt | 1;17 | DATE-TIME | This is the date/time (time is optional) of the review-and-change allergy interface was first activated in the staff-facing's Veteran view tab during a PDO invocable period. | ||
| 18 | mr change reason initiated dt | 5;14 | DATE-TIME | This field contains the date/time (time is optional) the patient first enters "How are you taking this medication?" during MR review. | ||
| 19 | oth allergy unk patient | 2;1 | SET OF CODES | 1:PATIENT DOES NOT KNOW OTHER ALLERGIES | Allergy Review structured response from patient at kiosk (e.g., check box selected): "I don't know what my other allergies are". | |
| 20 | no known drug allergies | 2;2 | SET OF CODES | 1:NO KNOWN DRUG ALLERGIES | Allergy Review structured response from patient at kiosk (e.g., Confirmation dialog): "Do you have any allergies or reactions?". | |
| 21 | mrar conducted with | MRARWITH;0 | MULTIPLE | 853.5121 | This multiple contains individuals (patient, Spouse, Other Family member, Caregiver, Friend, Outside Medication List, or Other) whom the provider conducted the MRAR with. | |
| 22 | mr multiple sessions | 5;3 | SET OF CODES | 1:MR COMPLETED OVER SEVERAL SESSIONS | This field indicates that the MR was completed over several sessions by the patient within the time limit. | |
| 23 | mr free text used | 5;15 | SET OF CODES | 1:MR FREE TEXT FEATURE USED | This field indicates that the MR Free Text feature is used in Medication Review. | |
| 24 | vet view chg dod med comp dt | 6;1 | DATE-TIME | This is the date/time (time is optional) of the review/change medication entry screen for DOD medication was last exited in the Veteran view tab of the staff-facing module during the PDO invocable period. | ||
| 25 | vet view chg dod med init dt | 6;2 | DATE-TIME | This is the date/time (time is optional) of when the review-change DOD medication entry screen is first opened in the Veteran view tab of the staff-facing module during the PDO invocable period. | ||
| 26 | vet view chg nonva med comp dt | 6;3 | DATE-TIME | This is the date/time (time is optional) of the review/change medication entry screen for NON-VA medication was last exited in the Veteran view tab of the staff-facing module during the PDO invocable period. | ||
| 27 | vet view chg nonva med init dt | 6;4 | DATE-TIME | This is the date/time (time is optional) of when the review-change NON-VA medication entry screen is first opened in the Veteran view tab of the staff-facing module during the PDO invocable period. | ||
| 28 | vet view chg local med comp dt | 6;5 | DATE-TIME | This field is the date/time (time is optional) of when the review-change for a local-VA medication was last existed in the Veteran view tab of the staff-facing module during the PDO invocable period. | ||
| 29 | vet view chg local med init dt | 6;6 | DATE-TIME | This is the date/time (time is optional) when the review-change local-VA medication entry screen is first opened in the Veteran view tab of the staff-facing module during the PDO invocable period. | ||
| 30 | allergies | ALLERGY;0 | MULTIPLE | 853.52 | Each transaction sent by Vetlink may contain multiple allergies. | |
| 31 | vet view chg remot med comp dt | 6;7 | DATE-TIME | |||
| 32 | vet view chg remot med init dt | 6;8 | DATE-TIME | This field is the date/time of when the review-change medication entry screen is first opened, a selection from "How are you taking this medication" made regarding a medication from the patient's remote VistA and the "Next" button selected in the Veteran view tab of the staff-facing module during the PDO invocable period. | ||
| 33 | web id | 7;1 | FREE TEXT | This field contains the unique identifier of the Web connection to the MRAR. | ||
| 40 | additional allergies | ALLERGYADD;0 | MULTIPLE | 853.53 | Each transaction sent by Vetlink may contain multiple additional allergies. | |
| 50 | medications | MEDS;0 | MULTIPLE | 853.54 | Each transaction sent by Vetlink may contain multiple medications. | |
| 60 | additional medications | MEDSADD;0 | MULTIPLE | 853.55 | Each transaction sent by Vetlink may contain multiple additional medications. | |
| 70 | pdo first invoked dt | 4;1 | DATE-TIME | This is the date/time (time is optional) that the PDO was first invoked in the PDO invocation period. | ||
| 72 | pdo invocation error | 4;3 | SET OF CODES | E:PDO INVOCATION PERIOD EXPIRED | When set to "E", this field indicates that a provider attempted to invoke the PDO but could not because the PDO invocation period expired. | |
| 73 | pdo next invoked dt | 4;4 | DATE-TIME | This field contains the subsequent date/time (time is optional) that the PDO was invoked after the first invoked in the PDO invocation period. The first invoked date/time is stored in PDO FIRST INVOKED (field #70). | ||
| 74 | staff module completed dt | 4;5 | DATE-TIME | This is the date/time (time is optional) that the staff module was completed. The staff module is considered completed after the provider performed the most recent of either of these events to occur within PDO invocable period: when the staff module is signed or TIU Note is signed. Note: This means it is possible for the staff-facing module to be completed multiple times within a PDO invocable period, where each completion is by a different provider. | ||
| 76 | staff module signed dt | 4;7 | DATE-TIME | This is the date/time (time is optional) that Staff Module was signed. | ||
| 77 | mr initiated dt | 5;1 | DATE-TIME | This is the date/time (time is optional) that the patient initiated Medication Review. | ||
| 78 | mr completed dt | 5;2 | DATE-TIME | This is the date/time (time is optional) that the patient-facing Medication Review module was completed. | ||
| 80 | mr change med initiated dt | 5;4 | DATE-TIME | This is the date/time (time is optional) of when the patient started entering the review/change medication interface. If the patient fails to start the interface, this field will be empty. NOTE: The user has only a limited amount of time to complete the process, as governed by the TIME LIMIT MR COMPLETE (#17) field of the PARAM INSTANCE (#853.01) subfile of the VPS CONFIG HISTORY (#853) file. | ||
| 81 | mr change med completed dt | 5;5 | DATE-TIME | This is the date/time (time is optional) of when the patient completed the review/change of the last medication interface. If patient fails to complete the interface, this field will be empty. NOTE: The user has only a limited amount of time to complete the process, as governed by the TIME LIMIT MR COMPLETE (#17) field of the PARAM INSTANCE (#853.01) subfile of the VPS CONFIG HISTORY (#853) file. | ||
| 82 | mr change reason completed dt | 5;6 | DATE-TIME | This is the date/time (time is optional) of when the patient completed either the "How are you taking this medication?" or the associated "Comment" interface. If the patient fails to complete the interface, this field will be empty. NOTE: The user has only a limited amount of time to complete the process, as governed by the TIME LIMIT MR COMPLETE (#17) field of the PARAM INSTANCE (#853.01) subfile of the VPS CONFIG HISTORY (#853) file. | ||
| 83 | mr incomplete reason type | 5;7 | SET OF CODES | 1:MR can't start, patient is too early,too late,or not early enough 2:Patient walked away or time limit expired 3:Patient selected to exit MR 4:Patient selected to bypass MR 5:Service Failure | This field contains the reason why MR module couldn't be completed. The MR Incomplete Reason type is one of the following: 1. The MR module could not be started because patient arrived TOO EARLY, TOO LATE, or NOT EARLY ENOUGH at the device. 2. Either the patient walked away in the middle of Medication Review or the TIME LIMIT MR COMPLETE time expired. 3. The patient selected to exit the Medication Review. 4. The patient selected to bypass the Medication Review. 5. Service failure of VetLink at the site. TOO LATE, TOO EARLY, and NOT EARLY ENOUGH are defined in TIME LIMIT TOO LATE ARRIVAL (#7), TIME LIMIT TOO EARLY ARRIVAL (#8), and TIME LIMIT NOT EARLY ENOUGH (#9) fields of the PARAM INSTANCE (#853.01) subfile of VPS CONFIG HISTORY (#853). TIME LIMIT MR COMPLETE (#17) field is also defined in that subfile. | |
| 84 | mr free text section done dt | 5;8 | DATE-TIME | This is the date/time (time is optional) of when the patient-facing Medication Review free text entry section was completed. | ||
| 85 | mr session outcome | 5;9 | SET OF CODES | F:FULL A:ABBREVIATED | This field indicates that the MR session was full or abbreviated. It's a full session if the patient did review and returned in permitted period to re-review. It's abbreviated if the patient was just accepting the opportunity to review information and make any changes. | |
| 86 | mr add med initiated dt | 5;10 | DATE-TIME | This is the date/time (time is optional) of when the patient started entering the additional medication interface. If the patient fails to start the interface, this field will be empty. NOTE: The user has only a limited amount of time to complete the process, as governed by the TIME LIMIT MR COMPLETE (#17) field of the PARAM INSTANCE (#853.01) subfile of the VPS CONFIG HISTORY (#853) file. | ||
| 87 | mr add med completed dt | 5;11 | DATE-TIME | This is the date/time (time is optional) of when the patient completed the entry of the last additional medication interface. If the patient fails to complete the interface, this field will be empty. NOTE: The user has only a limited amount of time to complete the process, as governed by the TIME LIMIT MR COMPLETE (#17) field of the PARAM INSTANCE (#853.01) subfile of the VPS CONFIG HISTORY (#853) file. | ||
| 88 | vet view add med initiated dt | 5;12 | DATE-TIME | This is the date/time (time is optional) of when the additional medication entry screen is first opened in the Veteran view tab of the staff-facing module during the PDO invocable period. | ||
| 89 | vet view add med completed dt | 5;13 | DATE-TIME | This is the date/time (time is optional) of when the staff exited the additional medication entry screen in the Veteran view tab of the staff-facing module during the PDO invocable period, in which the session's staff module was completed. | ||
| 92 | vet view chg all med init dt | 5;16 | DATE-TIME | This is the date/time (time is optional) of when the review-change medication entry screen is first opened, a selection from "How are you taking this medication?" is made regarding any medication, and the "Next" button is selected in the Veteran view tab of the staff-facing module during the PDO invocable period. | ||
| 93 | vet view chg all med comp dt | 5;17 | DATE-TIME | This is the date/time (time is optional) of when the review-change medication entry screen is last exited after a selection for any medication made from "How are you taking this medication?, and the "Next" button is selected in the Veteran view tab of the staff-facing module during the PDO invocable period, in which the session's staff module was completed. | ||
| 95 | mr incomplete dt | 5;19 | DATE-TIME | This is the date/time (time is optional) of MR module is incomplete in the patient-facing module. MR INCOMPLETE REASON TYPE (#83) field lists the reason why the MR module might be incomplete. | ||
| 105 | tiu note | 4;8 | POINTER | 8925 | This is the TIU note created by the provider after reviewing the allergy and medication for the patient. |
Error: Invalid Global File Type: 853.51