| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | parameter number(+) | 0;1 | NUMERIC | B | Number assigned to given site parameter entry. Entry number 1 is the only entry that should exist in this file. MPI/PD does not support multiple site parameter entries for a single station. | |
| .02 | cmor request change(+) | 0;2 | SET OF CODES | 0:MANUAL 1:AUTOMATIC | Based on this field setting, any Coordinating Master of Record (CMOR) change request received from another station can either be manually reviewed or automatically approved. | |
| .03 | new request mailgroup | 0;3 | POINTER | 3.8 | If the CMOR Request Change parameter is set to manual, new CMOR change requests received will notify the mailgroup entered in this field. This gives a means of prompting someone to review the new request. | |
| .04 | local/missing date last ran | 0;4 | DATE-TIME | This field contains the date and time that the Local/Missing ICN Resolution Background Job [MPIF LOC/MIS ICN RES] last ran to completion. | ||
| 11 | auto accept demographics | 1;1 | SET OF CODES | 1:AUTO ACCEPT 0:NOT AUTO ACCEPT | This field is the parameter that a site would set to determine if data coming from another site, that is not the owner of the data, could be automatically uploaded. If this field is not set, then the software will assume that all incoming data can not be automatically uploaded. | |
| 12 | mpi/pd seeding comp date/time | 1;2 | DATE-TIME | This field, 'MPI/PD SEEDING COMP DATE/TIME', is used to track the date/time our seeding process completed. This field is used to ensure that the seeding process is run once and only once at a facility. If a date is present, our seeding process terminates. | ||
| 13 | mpi/pd data compare comp date | 1;3 | DATE-TIME | This field, 'MPI/PD DATA COMPARE COMP DATE', is used to track the date/time our data comparison process completed. This field is used to ensure that the data comparison process is run once and only once at a facility. If a date is present, our data comparison process terminates. | ||
| 14 | mpi/pd date last treated | 1;4 | DATE-TIME | 'MPI/PD DATE LAST TREATED' is used to track the completion date/time of the Date Last Treated process. This field is used to ensure that this Date Last Treated process is run only once at a facility. | ||
| 16 | stop mpi/pd messaging(+) | 1;6 | SET OF CODES | 1:SEND MESSAGES 0:STOP MESSAGES 2:SUSPEND MESSAGES | This field will instruct the software to allow MPI/PD messaging, stop it or suspend it. | |
| 17 | primary care clinic stops | PC;0 | MULTIPLE | 991.817 | All primary care Clinic Stops (Decision Support System (DSS) Identifiers). Used in CMOR patient activity score calculations. | |
| 18 | cmor last patient processed | CMOR;1 | POINTER | 2 | This field keeps track of the last sequential patient processed through the CMOR patient activity score calculations process. | |
| 19 | cmor init started date/time | CMOR;2 | DATE-TIME | This field contain the date/time that the Start/Restart CMOR Score Calculation option [RG CMOR START] was first run. | ||
| 20 | cmor init stopped date/time | CMOR;3 | DATE-TIME | This field contain the date/time that the Stop CMOR Score Calculation option [RG CMOR STOP] was last stopped either manually or normally. | ||
| 21 | cmor init manual stop | CMOR;4 | BOOLEAN | Y:YES | This field is used to stop the background task started by the Start/Restart CMOR Score Calculation option [RG CMOR START]. This field is populated by the Stop CMOR Score Calculation option [RG CMOR STOP]. | |
| 22 | cmor daily start time | CMOR;5 | FREE TEXT | This field identifies the daily start time in 24 hour format for the CMOR activity score calculations. | ||
| 23 | cmor daily stop time | CMOR;6 | FREE TEXT | This field identifies the daily stop time in 24 hour format for the CMOR activity score calculations. | ||
| 24 | cmor init status | CMOR;7 | SET OF CODES | R:RUNNING SN:SUCCESSFULLY COMPLETED SM:STOPPED MANUALLY INT:INTERRUPTED ABNORMALLY | This field contains the current status of the CMOR Score Calculations process. | |
| 25 | cmor run type | CMOR;8 | SET OF CODES | I:INITIAL RUN R:RESET ALL RS:RESTART FROM LAST CALCULATED | This field contains the current type of CMOR Score Calculation run. This field is used by the Start/Restart CMOR Score Calculation option [RG CMOR START] to identify a starting point. | |
| 26 | cmor last task# | CMOR;9 | NUMERIC | This field contains the task number of the CMOR Score Calculation process. | ||
| 30 | cmor comp last patient | COMP;1 | POINTER | 2 | This patient was the last processed patient in the CMOR Comparison process. | |
| 31 | cmor comp started date/time | COMP;2 | DATE-TIME | This is the date/time the CMOR Comparison process started. | ||
| 32 | cmor comp stopped date/time | COMP;3 | DATE-TIME | When the CMOR Comparison stopped, (either naturally or manually) a time is logged in this field for record. | ||
| 33 | cmor comp status | COMP;4 | SET OF CODES | R:RUNNING MS:MANUALLY STOPPED C:COMPLETED | This is the status of the CMOR Comparison process in your system. | |
| 34 | cmor comp last task # | COMP;5 | NUMERIC | This is the task number that the CMOR Comparison ran on last. | ||
| 35 | cmor comp flag | COMP;6 | BOOLEAN | Y:YES N:NO | This flag is for the user to request the CMOR Comparison process to stop. | |
| 40 | exc purge start date/time | EXCPRG;1 | DATE-TIME | This field contains the date and time the MPI/PD Exception Purge was last started. | ||
| 41 | exc purge stop date/time | EXCPRG;2 | DATE-TIME | This field contains the date and time the MPI/PD Exception Purge last completed. | ||
| 42 | exc purge status | EXCPRG;3 | SET OF CODES | R:RUNNING C:COMPLETE | This field contains the current status of the MPI/PD Exception Purge process. | |
| 50 | admin point of contact | POC;1 | POINTER | 200 | The ADMIN POINT OF CONTACT field contains the name of the individual at the facility who is in a position to resolve patient issues for Master Patient Index/Patient Demographics. This field is populated using the Add/Edit Point of Contact [RG UPDATE POINT OF CONTACT] option. The information is sent to a remote mail group whose members maintain the point of contact list on the website. | |
| 51 | irm point of contact | POC;2 | POINTER | 200 | The IRM POINT OF CONTACT field contains the name of the individual at the facility who supports the VistA Master Patient Index/Patient Demographics application. This field is populated using the Add/Edit Point of Contact [RG UPDATE POINT OF CONTACT] option. The information is sent to a remote mail group whose members maintain the point of contact list on the website. | |
| 52 | hl7 point of contact | POC;3 | POINTER | 200 | The HL7 POINT OF CONTACT field contains the name of the individual at the facility who supports the VistA Health Level Seven (HL7) application. Master Patient Index/Patient Demographics uses HL7 for message transmission and frequently needs to contact the HL7 point of contact. This field is populated using the Add/Edit Point of Contact [RG UPDATE POINT OF CONTACT] option. The information is sent to a remote mail group whose members maintain the point of contact list on the website. | |
| 53 | alt admin point of contact | POC;4 | POINTER | 200 | The ALT ADMIN POINT OF CONTACT field contains the name of a second individual at the facility who is in a position to resolve patient issues for Master Patient Index/Patient Demographics. This field is populated using the Add/Edit Point of Contact [RG UPDATE POINT OF CONTACT] option. The information is sent to a remote mail group whose members maintain the point of contact list on the website. | |
| 54 | alt irm point of contact | POC;5 | POINTER | 200 | The ALT IRM POINT OF CONTACT field contains the name of a second individual at the facility who supports the VistA Master Patient Index/Patient Demographics application. This field is populated using the Add/Edit Point of Contact [RG UPDATE POINT OF CONTACT] option. The information is sent to a remote mail group whose members maintain the point of contact list on the website. | |
| 55 | alt hl7 point of contact | POC;6 | POINTER | 200 | The ALT HL7 POINT OF CONTACT field contains the name of a second individual at the facility who supports the VistA Health Level Seven (HL7) application. Master Patient Index/Patient Demographics uses HL7 for message transmission and frequently needs to contact the HL7 point of contact. This field is populated using the Add/Edit Point of Contact [RG UPDATE POINT OF CONTACT] option. The information is sent to a remote mail group whose members maintain the point of contact list on the website. | |
| 100 | rel init status | PRE;1 | SET OF CODES | R:RUNNING SN:STOPPED NORMALLY SM:STOPPED MANUALLY | This field contains the current status of the religion status process. | |
| 101 | rel init start | PRE;2 | DATE-TIME | This field contains the initial start date/time of the patient religion status process. | ||
| 102 | rel init stop | PRE;3 | DATE-TIME | This field contains the date/time that the patient religion status process stopped. | ||
| 103 | rel init last | PRE;4 | POINTER | 2 | This field contains the last patient processed by the religion status process. | |
| 104 | rel init user | PRE;5 | POINTER | 200 | This field contains the person who ran the initial religion status process. | |
| 105 | mar init status | PRE;6 | SET OF CODES | R:RUNNING SN:STOPPED NORMALLY SM:STOPPED MANUALLY | This field contains the status of the marital status initialization process. | |
| 106 | mar init start | PRE;7 | DATE-TIME | This field contains the starting date/time of the marital status initialization process. | ||
| 107 | mar init stop | PRE;8 | DATE-TIME | This field contains the date/time that the marital status initialization process stopped. | ||
| 108 | mar init last | PRE;9 | POINTER | 2 | This field contains the last PATIENT file (#2) entry that was processed by the marital status initialization process. | |
| 109 | mar init user | PRE;10 | POINTER | 200 | This field contains the user that ran the marital status initialization process. | |
| 110 | elig init status | PRE1;1 | SET OF CODES | R:RUNNING SN:STOPPED NORMALLY SM:STOPPED MANUALLY | This field contains the status of the patient eligibility initialization process. | |
| 111 | elig init start | PRE1;2 | DATE-TIME | This field contains the date/time that the patient eligibility initialization process was started. | ||
| 112 | elig init stop | PRE1;3 | DATE-TIME | This field contains the date/time that the patient eligibility initialization process was stopped. | ||
| 113 | elig init last | PRE1;4 | POINTER | 2 | This field contains the last PATIENT file (#2) entry processed by the patient eligibility initialization process. | |
| 114 | elig init user | PRE1;5 | POINTER | 200 | This field contains the user that ran the patient eligibility initialization process. | |
| 115 | pseudo init status | PRE1;6 | SET OF CODES | R:RUNNING SN:STOPPED NORMALLY SM:STOPPED MANUALLY | This field contains the status of the Pseudo-SSN initialization process. | |
| 116 | pseudo init start | PRE1;7 | DATE-TIME | This field contains the start date/time of the Pseudo-SSN initialization process. | ||
| 117 | pseudo init stop | PRE1;8 | DATE-TIME | This field contains the date/time that the Pseudo-SSN initialization process was stopped. | ||
| 118 | pseudo init last | PRE1;9 | POINTER | 2 | This field contains the last PATIENT file (#2) entry that was processed by the Pseudo-SSN initialization process. | |
| 119 | pseudo init user | PRE1;10 | POINTER | 200 | This field contains the user that ran the Pseudo-SSN initialization process. |
Not Referenced