Files > TRACK EDITS

parent

409.48

name

TRACK EDITS

number

409.481

Fields

#	Name	Location	Type	Details	Index	Description
.01	edit number	0;1	NUMERIC		B	This field contains a unique entry for each edit. The edits are stored in order beginning at 1. Under ordinary circumstances there will usually only be between 1 and 3 edits for any record although there is no specific maximum.
.02	date edited	0;2	DATE-TIME			This is the date that the user edited this encounter. A trigger on this field will also update the DATE LAST EDITED field in the main file.
.03	edited by	0;3	POINTER	200		This is the user who edited this encounter. A trigger on this field will also update the LAST EDITED BY field in the main file.
.04	type of entry	0;4	SET OF CODES	U:USER C:CLINICAL S:SUPERVISOR		This is the type of user who edited this encounter. "USER" any standard user of this package. "CLINICAL" a clinical reviewer with the appropriate security key. "SUPERVISOR" a supervisor with the appropriate security key.
.05	serv. connect (ok by user?)	0;5	BOOLEAN	0:NO 1:YES		This field will contain 1 ('YES') or 0 ('NO') based on the user determination of the encounter's service connected value. A trigger on this field will also update the SERV. CONNECT (OK BY USER?) field in the main file.
.06	review required?	0;6	BOOLEAN	0:NO 1:YES		This field will be set to 1 ('YES') if a regular user determines that this record requires further review by a clinical reviewer. A trigger will also set the STATUS field in the main file to 'REVIEW'.