Files > ROR REGISTRY RECORD

name

ROR REGISTRY RECORD

number

798

location

^RORDATA(798,

description

The ROR REGISTRY RECORD file contains records of local registries. Each record associates a patient with a registry and contains registry-specific and additional service information (when the patient was added to the registry, if they were confirmed, etc). Records of the file are uniquely identified by the patient and the registry (the "A" primary key and the uniqueness index "KEY" are used for that purpose). When the record of this file is deleted, the logic of the ADELETE cross-reference tries to delete the associated records from the ROR HIV RECORD (#799.4), ROR PATIENT (#798.4), and ROR PATIENT EVENTS (#798.3) files. A permanent screen (the ^DD(798,0,"SCR") node) restricts access to records of this file. Users can only access records of those registries that they have the security key(s) for. Users with the ROR VA IRM security key can access all records of the file. If you want the changes in the security keys allocation to have an effect immediately, you should rebuild the "ACL" cross-reference of the .01 field of the SECURITY KEY multiple of the ROR REGISTRY PARAMETERS file (#798.1). See the description of the cross-reference for more details.

Fields

#	Name	Location	Type	Details	Index	Description
.01	patient name(+)	0;1	POINTER	798.4	B	The PATIENT NAME field identifies a patient in the registry. You can select a patient either from the local registry or the ROR PATIENT file, or you can add a new patient from the PATIENT file. You can only select records of those registries that you have appropriate security key(s) for.
.02	registry(+)	0;2	POINTER	798.1	AC	The REGISTRY field identifies the registry that the record belongs to.
1	date entered	0;3	DATE-TIME			The DATE ENTERED field is automatically populated by the trigger associated with the REGISTRY field when the patient is added to the registry.
2	date confirmed	0;4	DATE-TIME			A trigger associated with the STATUS field automatically populates the DATE CONFIRMED field with the current date and time when the patient is confirmed in the registry.
2.1	confirmed by	0;10	POINTER	200		A trigger associated with the STATUS field automatically populates this field with a pointer to the record of the user who confirmed the patient.
3	status	0;5	SET OF CODES	0:Confirmed 4:Pending 5:Deleted		The STATUS field indicates current status of the registry record.
3.1	selection rule	1;0	MULTIPLE	798.01		The SELECTION RULE multiple contains a list of selection rules that the patient passed when added to the registry.
3.2	date selected		COMPUTED			Value of this field is calculated as the earliest date of selection rules from the SELECTION RULE multiple (3.1). If that multiple is empty, then the date part of the DATE ENTERED field (1) will be used.
3.3	location selected		COMPUTED			Computation algorithm of this field returns the LOCATION field (2) value of the earliest selection rules from the SELECTION RULE multiple (3.1).
4	update demographics	0;6	BOOLEAN	0:NO 1:YES		Usually, you should not edit this field. Set the value of this field to "YES" if you want patient demographic data to be sent to the AAC.
4.1	demographics updated	0;8	DATE-TIME			The DEMOGRAPHICS UPDATED field stores the date/time of the last change in the patient's demographic data that was detected by the Clinical Case Registries software.
5	update local registry data	0;7	BOOLEAN	0:NO 1:YES		Usually, you should not edit this field. Set the value of this field to "YES" if you have changed any local registry data of the patient and want this data to be sent to the AAC.
5.1	local data updated	0;9	DATE-TIME			The LOCAL DATA UPDATED field stores the date/time of the last change in the patient's local registry data.
6	date deleted	0;11	DATE-TIME			Trigger associated with the STATUS field (3) automatically populates this field with the current date and time when the patient is deleted from the registry.
6.1	deleted by	0;12	POINTER	200		Trigger associated with the STATUS field (3) automatically populates this field with a pointer to the record of the user who deleted the patient from the registry.
8	active		COMPUTED			This is a computed field that indicates if the patient's record in the registry is active and should be considered by the software.
9.1	data acknowledged until	2;1	DATE-TIME			The DATA ACKNOWLEDGED UNTIL field contains a date that the patient data has been extracted up to and successfully transmitted.
9.2	data extracted until	2;2	DATE-TIME			This field contains a date that registry data of the patient has been extracted up to. Actual transmission of this data is not confirmed.
10	message id	2;3	FREE TEXT		AM	The MESSAGE ID field contains the identifier of latest individual HL7 message created for this registry record. Value of this field should have the following format: BatchID-N, where BatchID is the identifier of the HL7 batch message (see the INTERNAL BATCH ID field of the LAST BATCH CONTROL ID multiple of the ROR REGISTRY PARAMETERS file), and N is the sequential number of the message in the batch.
11	don't send	2;4	BOOLEAN	0:NO 1:YES		Set this field to "YES" if you do not want any data to be sent to the national registry for this record.
12	pending patient comment	3;1	FREE TEXT			This is any user input concerning a patient who hasn't been confirmed into a registry.
20	local field	20;0	MULTIPLE	798.02		The LOCAL FIELD multiple contains a list of local field values for the registry patient along with the corresponding dates and comments.