| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | registry name(+) | 0;1 | FREE TEXT | YOU MUST NOT EDIT THIS FIELD IF IT IS PART OF A NATIONAL REGISTRY DEFINITION! You can either select an existing registry or add a new one. Registry names must be unique. Names of the National registries must start with "VA". You can only select records of those registries that you have appropriate security key(s) for. | ||
| .09 | national | 0;11 | BOOLEAN | 0:NO 1:YES | ONLY AUTHORIZED NATIONAL REGISTRY DEVELOPERS CAN EDIT THIS FIELD! The national registries must have this field set to "YES". This prevents local editing of other fields of national registry definitions. | |
| 1 | registry updated until | 0;2 | DATE-TIME | This field indicates the date of the last successful run of the regular registry update process. The search engine looks for new patients starting from this date. Usually, this field should not be manually edited; it is updated automatically. Before initial population of the registry, enter the date that the data search should start from. | ||
| 2 | data extracted until | 0;3 | DATE-TIME | This field indicates the date of the last successful run of the regular data extraction process. Do not edit this field. | ||
| 3 | selection rule | 1;0 | MULTIPLE | 798.13 | The SELECTION RULE field contains a list of the top-level selection rules that are used to screen the patients to be added to the registry. The records of the multiple are uniquely identified by the selection rule names. The "A" primary key and the uniqueness index "B" are used for this purpose. | |
| 4 | short description(+) | 0;4 | FREE TEXT | YOU MUST NOT EDIT THIS FIELD IF IT IS PART OF A NATIONAL REGISTRY DEFINITION! | ||
| 5 | description | 2;0 | WORD-PROCESSING | Any additional reference information related to the registry may be stored in this field. | ||
| 6.1 | before update | 4;E1,245 | FREE TEXT | YOU MUST NOT EDIT THIS FIELD IF IT IS PART OF A NATIONAL REGISTRY DEFINITION! Enter a full name ($$TAG^ROUTINE) of the external MUMPS function that will be called before adding a new record to the registry. This entry point can be used to prepare any additional data. | ||
| 6.2 | after update | 5;E1,245 | FREE TEXT | YOU MUST NOT EDIT THIS FIELD IF IT IS PART OF A NATIONAL REGISTRY DEFINITION! Enter a full name ($$TAG^ROUTINE) of the external MUMPS function that will be called after adding a new record to the registry. This entry point can be used to create record(s) in additional linked file(s) of the local registry. | ||
| 7 | extract period for new patient | 0;5 | NUMERIC | YOU MUST NOT EDIT THIS FIELD IF IT IS PART OF A NATIONAL REGISTRY DEFINITION! Enter the number of days that should be subtracted from the earliest date when the patient passed one of the selection rules. The result will be used as the start date of the data extraction for this new patient. If this field is empty, the default value of 3650 is used. | ||
| 8 | enable log | 0;6 | BOOLEAN | 0:NO 1:YES | Select "YES" to enable recording of different kinds of events (debug messages, errors, etc.) generated by registry processes. | |
| 8.1 | log event | 3;0 | MULTIPLE | 798.11 | The LOG EVENT multiple contain a list of event types that are enabled to record. If the list is empty and recording is enabled, all events except debug messages will be recorded. Otherwise, only recording of the events from the list and error messages will be enabled. | |
| 10 | message builder | 7;E1,245 | FREE TEXT | YOU MUST NOT EDIT THIS FIELD IF IT IS PART OF A NATIONAL REGISTRY DEFINITION! Enter a full name ($$TAG^ROUTINE) of the external MUMPS function that will be called to generate the registry-specific section of the HL7 message for each record of the registry. If this field has no value, the default entry point ($$REGDATA^ROREXT02) will be used. | ||
| 11 | registry status | 0;7 | SET OF CODES | 0:ACTIVE 1:INACTIVE | Select the "INACTIVE" code if you want to exclude the registry from the regular registry updates and data transmissions. | |
| 12 | extracted result | 8;0 | MULTIPLE | 798.112 | This multiple contains a list of Lab result codes. These results will be extracted and transmitted to AAC. | |
| 13 | protocol | 9;1 | POINTER | 101 | YOU MUST NOT EDIT THIS FIELD IF IT IS A PART OF NATIONAL REGISTRY DEFINITION! This field contains a pointer to the protocol in the PROTOCOL file that is used as the event driver for sending HL7 messages. | |
| 13.1 | maximum message size | 9;2 | NUMERIC | This field stores the maximum size (in megabytes) of a batch HL7 message that can be sent to Austin Automation Center (AAC). If this field is empty or contains 0, the size is not limited. You must coordinate your intentions with AAC support personnel if you are going to edit this field. | ||
| 13.2 | alert frequency | 9;3 | NUMERIC | Value of the ALERT FREQUENCY field determines how often e-mail notifications and VistA alerts are sent to the AAC and local staff in case of problems with the site's CCR software (data extraction problems, unsent HL7 messages, etc.). If this field is empty or 0, notifications are not sent. Otherwise, the nightly task increments the error counters and checks the remainders from division of the counters by the value of this field. When a reminder becomes 0, the software sends the corresponding e-mail notification to the AAC and generates the VistA alert to the local staff listed in the NOTIFICATION multiple (14). For example, if the nightly task runs every night and the ALERT FREQUENCY is 2, then alerts and notifications will be sent every other night. | ||
| 13.3 | national notification e-mail | 9;4 | FREE TEXT | YOU MUST NOT EDIT THIS FIELD IF IT IS A PART OF NATIONAL REGISTRY DEFINITION! The NATIONAL NOTIFICATION E-MAIL field holds an e-mail address where notifications about registry problems (mostly, data transmission problems) are sent to. If the field is empty, e-mail notifications will not be sent. | ||
| 14 | notification | 10;0 | MULTIPLE | 798.114 | This multiple contains a list of VistA users that should be notified about problems with the local registry. | |
| 15.1 | lag days | 11;1 | NUMERIC | Number of days that defines an overlap of the data searches during the registry updates and a data extraction delay during the regular data extractions. If this field is empty, the default value of 1 is used by the registry update and data extraction processes. See the package documentation or Technical Description of the field in the data dictionary for more information. | ||
| 18 | security key | 18;0 | MULTIPLE | 798.118 | This multiple stores a list of security keys associated with the registry. | |
| 19.1 | number of patients | 19;1 | NUMERIC | The NUMBER OF PATIENTS field contains total number of confirmed patients in the registry right after the last registry update. | ||
| 19.2 | number of pending patients | 19;2 | NUMERIC | The NUMBER OF PENDING PATIENTS field stores number of pending patients in the registry right after the last registry update. | ||
| 19.3 | hl7 attempt counter | 19;3 | NUMERIC | The HL7 ATTEMPT COUNTER field is incremented each time the nightly task (the Registry Update & Data Extraction [ROR TASK] option) encounters at least one unsent HL7 message. The nightly task assigns 1 to the field when new HL7 messages are generated (only if all previous messages have been successfully transmitted). Usually, you should not edit this field. | ||
| 21.01 | automatic backpull | 21;1 | POINTER | 799.6 | This field stores the pointer to the historical data extraction definition that was used during the previous run of the nightly task. | |
| 21.04 | local data resent | 21;3 | DATE-TIME | This field holds the date when all local registry data was resent to AAC after the installation (to fix the data incorrectly overwritten with the historical data). Usually, you should not modify this field. If you need to resend all local registry and demographic data to AAC, you should clear this field. The data will be resent automatically during the next nightly transmission. | ||
| 21.05 | hdt date/time | 21;4 | DATE-TIME | This field is initialized with the current date/time by the registry setup task upon successful completion of the initial registry population. | ||
| 22 | last batch control id | 22;0 | MULTIPLE | 798.122 | This multiple contains a list of identifiers of the HL7 batch messages generated during the previous run of the nightly task. | |
| 25 | enable protocols | 0;14 | BOOLEAN | 0:NO 1:YES | If this field is set to "YES", event protocols will be used by the package to speed up the registry processing. The protocols create references to patient events in the ROR PATIENT EVENTS file. Only those patients that have new references will be processed by the next registry update. If several registries are updated at the same time and at least one of them has this field set to "YES", all these registries will be processed using event references. | |
| 26 | exclude employees | 0;10 | BOOLEAN | 0:NO 1:YES | YOU MUST NOT EDIT THIS FIELD IF IT IS PART OF A NATIONAL REGISTRY DEFINITION! If this field is set to "YES", patients who are employees will not be processed by the registry update or data extraction functions. | |
| 27 | available reports | 27;E1,250 | FREE TEXT | YOU MUST NOT EDIT THIS FIELD IF IT IS A PART OF NATIONAL REGISTRY DEFINITION! The AVAILABLE REPORTS field stores a list of report codes (not the IENs!) separated by commas. These reports will be available for this registry in the GUI. | ||
| 28 | local test name | 28;0 | MULTIPLE | 798.128 | This multiple maps local lab tests to the predefined lab test groups that are used in the reports. | |
| 29 | local drug name | 29;0 | MULTIPLE | 798.129 | This multiple maps local medication names to the predefined medication groups that are used in the reports. | |
| 30 | report stats | 30;0 | MULTIPLE | 798.12 | Records of this multiple store the statistic data related to running reports. Usually, the stats are reset after successful data transmission to the AAC. | |
| 31 | auto-confirm | 6;1 | BOOLEAN | 0:NO 1:YES | C | This field is used during the registry update to set the status of new patients. If the registry is set to auto-confirm, the patient status is set to 'Confirmed'. If auto-confirm is no, the patient status is set to 'Pending'. |