Files > TEAM POSITION

name

TEAM POSITION

number

404.57

location

^SCTM(404.57,

description

This table contains the practitioner and administrative positions associated with a Team.

Fields

#	Name	Location	Type	Details	Index	Description
.01	position(+)	0;1	FREE TEXT		B	This is the Name of the Team Position.
.02	team(+)	0;2	POINTER	404.51	C	Entry in the team file.
.03	standard role name(+)	0;3	POINTER	403.46	AC	Standard role the provider performs as part of this team. These standard positions are defined by Central Office.
.04	possible primary practitioner?	0;4	BOOLEAN	1:YES 0:NO		Can this position be the primary care provider for a patient? (Even if the position's principle purpose is not primary care, it still maybe able act as a primary care provider for some patients. This field indicates if that is possible.) Note: This also enables the position to be a PC Attending Position.
.08	max number of patients	0;8	NUMERIC			Once the current number of assigned patients reaches this level, further assignment of this position should be avoided.
.09	associated clinic	0;9	POINTER	44		This field is no longer updated since the release of SD*5.3*297. during various appointing and information processes.
.1	*preceptor position	0;10	POINTER	404.57		This field contains the name of the Team Position that is responsible for supervising this current position. It is an optional field. However, when indicated, this field usually contains an attending position.
.11	beeper number	0;11	FREE TEXT			This is the pager or beeper number that is used by this team position.
.12	can act as preceptor?	0;12	BOOLEAN	1:YES 0:NO		By answering 'YES', this position may be used as a preceptor position for the team.
.13	user class	0;13	POINTER	8930	AUSR	This is an entry in the USR CLASS file to which anyone assigned to the position must belong.
1	position description	1;0	WORD-PROCESSING
2.01	death message	2;1	SET OF CODES	T:TEAM'S PATIENTS P:POSITION'S PATIENTS N:DO NOT SEND		This determines for which patients the position receives messages related to patient death.
2.02	inpatient message	2;2	SET OF CODES	T:TEAM'S PATIENTS P:POSITION'S PATIENTS N:DO NOT SEND		This determines for which patients the position receives messages related to inpatient activity.
2.03	team message	2;3	SET OF CODES	T:TEAM'S PATIENTS P:POSITION'S PATIENTS N:DO NOT SEND		This determines for which patients the position receives messages related to team activity such as assignment or re-assignment of a position or team to the patient.
2.04	consult message	2;4	SET OF CODES	T:TEAM'S PATIENTS P:POSITION'S PATIENTS N:DO NOT SEND		This determines for which patients the position receives messages related to activity in clinics to which the patient is not enrolled.
2.05	preceptor death message	2;5	BOOLEAN	1:YES 0:NO		A yes entry triggers a mailmessage on a death entry for the preceptor of this position.
2.06	preceptor inpatient message	2;6	BOOLEAN	1:YES 0:NO		A yes entry triggers a mailmessage on inpatient activity for the preceptor ofthis position.
2.07	preceptor team message	2;7	BOOLEAN	1:YES 0:NO		A yes entry triggers a mailmessage on team activity for the preceptor of this position.
2.08	preceptor consult message	2;8	BOOLEAN	1:YES 0:NO		A yes entry triggers a mailmessage on consult activity for the preceptor of this position.
2.09	automatic inactivation message	2;9	SET OF CODES	T:TEAM'S PATIENTS P:POSITION'S PATIENTS N:DO NOT SEND		Determines where patient inactivation messages are sent
2.1	preceptor inactivation message	2;10	BOOLEAN	1:YES 0:NO		Notify Preceptor if patient is automatically inactivated
5	associated clinics	5;0	MULTIPLE	404.575		Multiple Entry of Associated Clinics. This replaces single value used before patch SD*5.3*297
200	current # of pc patients		COMPUTED			This calculates the current number of Primary Care patients for this team position.
201	current # of patients		COMPUTED			This is the number of all patients (primary care & otherwise) associated with the team.
202	future # of pc patients		COMPUTED			The number of current AND future PC assignments to this team position.
203	future # of patients		COMPUTED			The number of current AND future assignments to this team position.
300	current status		COMPUTED			This indicates if the team position is active on the current date.
301	current effective date		COMPUTED			This is the most recent date (not in future) that the active status changed.
302	current activation date		COMPUTED			This is the activation date of the position based on today's date: For positions never active - this is the next date where the position is active For positions that are active now - this is the date it became active For positions that are currently inactive - this is the last activation date
303	current inactivation date		COMPUTED			If it is inactive, this is the day the position became inactive. If it is active it is the day the position will become inactive.
304	current practitioner		COMPUTED
305	current preceptor position		COMPUTED
306	current preceptor		COMPUTED
307	active precepts		COMPUTED
400	allow precepted change		COMPUTED			Determines if a patient assignment has been made after the date a position became precepted. A 'NO' return flags the GUI to always require an active preceptor assignment and disables the 'can act as preceptor' and 'can act as preceptor' controls.
401	allow preceptor change		COMPUTED			Determines if a preceptor assignment has been made after the date a position became preceptor. A 'NO' return flags the GUI to always require an active staff assignment and disables the 'can act as preceptor' and 'can act as preceptor' controls.
402	staff/pos inconsistent reason		COMPUTED			This is a computed field that checks for any inconsistency between the Position Role, PC assignment and the Person Class of the current active provider. The value is blank if there is not an inconsistency.