Global: ^SCTM(404.57

FileMan FileNo	FileMan Filename	Package
404.57	TEAM POSITION	Scheduling

Package	Total	Routines
Scheduling	21	SCMCCV6 SCMCFPOS SCMCHLZ SCMCMH SCMCMHTC SCMCMU SCMCQK1 SCMCQK2 SCMCTSK1 SCMCTSKG SCRPO SCRPTPOS SD53P297 SD53P504 SD53P520 SDWLCU2 SDWLE6 SDWLPL SDWLQSC SDWLREB SDWLRP2
Virtual Patient Record	3	VPRDJ00 VPRDPT VPRPCMM

Package	Total	FileMan Files
Scheduling	9	HOSPITAL LOCATION(#44)[#44.40457(.01)] PATIENT TEAM POSITION ASSIGNMENT(#404.43)[.02] PCMM HL7 TRANSMISSION LOG(#404.471)[.07] PCMM HL7 EVENT(#404.48)[.07] POSITION ASSIGNMENT HISTORY(#404.52)[.01] PRECEPTOR ASSIGNMENT HISTORY(#404.53)[.01, .06] TEAM POSITION(#404.57)[.1] TEAM POSITION HISTORY(#404.59)[.01] SD WAIT LIST(#409.3)[6]

Package	Total	FileMan Files
Scheduling	4	HOSPITAL LOCATION(#44)[.09, #404.575(.01)] TEAM(#404.51)[.02] TEAM POSITION(#404.57)[.1] STANDARD POSITION(#403.46)[.03]
Authorization Subscription	1	USR CLASS(#8930)[.13]

Fields, Total: 37

Field #	Name	Loc	Type	Details
.01	POSITION	0;1	FREE TEXT	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `N SCZ K:$L(X)>30!($L(X)<3) X D:$D(X) IPTF^SCMCTPU(X,.SCZ,.X)` LAST EDITED: `MAR 06, 1996` HELP-PROMPT: `Answer must be 3-30 characters in length - No duplicate position names within a team.` DESCRIPTION: `This is the Name of the Team Position.` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER` CROSS-REFERENCE: `404.57^B` `1)= S ^SCTM(404.57,"B",$E(X,1,30),DA)=""` `2)= K ^SCTM(404.57,"B",$E(X,1,30),DA)` CROSS-REFERENCE: `404.57^APRIMARY^MUMPS` `1)= N SC2 S SC2=$P($G(^SCTM(404.57,DA,0)),U,2) I SC2 S ^SCTM(404.57,"APRIMARY",X,SC2,DA)=""` `2)= N SC2 S SC2=$P($G(^SCTM(404.57,DA,0)),U,2) I SC2 K ^SCTM(404.57,"APRIMARY",X,SC2,DA)` `This sorts by POSITION(#.01), then by TEAM(#.02). There is an associated cross reference for the TEAM Field (#.02).` CROSS-REFERENCE: `404.57^ATMPOS^MUMPS` `1)= N SC1 S SC1=$P($G(^SCTM(404.57,DA,0)),U,2) I SC1 S ^SCTM(404.57,"ATMPOS",SC1,X,DA)=""` `2)= N SC1 S SC1=$P($G(^SCTM(404.57,DA,0)),U,2) I SC1 K ^SCTM(404.57,"ATMPOS",SC1,X,DA)` `This sorts by TEAM(#.02), then by POSITION(#.01). There is an associated cross reference for the TEAM Field (#.02).`
.02	TEAM	0;2	POINTER TO TEAM FILE (#404.51)	**********************REQUIRED FIELD********************** TEAM(#404.51) INPUT TRANSFORM: `N SC D:$D(X)#2 IPTF^SCMCTPU(.SC,X,.X)` LAST EDITED: `SEP 05, 1995` HELP-PROMPT: `This is the entry in the team File` DESCRIPTION: `Entry in the team file.` TECHNICAL DESCR: `Pointer to TEAM File (#404.51)` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER` CROSS-REFERENCE: `404.57^APRIMARY1^MUMPS` `1)= N SC1 S SC1=$P($G(^SCTM(404.57,DA,0)),U,1) I SC1]"" S ^SCTM(404.57,"APRIMARY",SC1,X,DA)=""` `2)= N SC1 S SC1=$P($G(^SCTM(404.57,DA,0)),U,1) I SC1]"" K ^SCTM(404.57,"APRIMARY",SC1,X,DA)` `This sorts by POSITION(#.01), then by TEAM(#.02). There is an associated cross reference for the POSITION Field (#.01).` CROSS-REFERENCE: `404.57^C` `1)= S ^SCTM(404.57,"C",$E(X,1,30),DA)=""` `2)= K ^SCTM(404.57,"C",$E(X,1,30),DA)` CROSS-REFERENCE: `404.57^ATMPOS1^MUMPS` `1)= N SC2 S SC2=$P($G(^SCTM(404.57,DA,0)),U,1) I SC2]"" S ^SCTM(404.57,"ATMPOS",X,SC2,DA)=""` `2)= N SC2 S SC2=$P($G(^SCTM(404.57,DA,0)),U,1) I SC2]"" K ^SCTM(404.57,"ATMPOS",X,SC2,DA)` `This sorts by TEAM(#.02), then by POSITION(#.01). There is an associated cross reference for the POSITION Field (#.01).`
.03	STANDARD ROLE NAME	0;3	POINTER TO STANDARD POSITION FILE (#403.46)	**********************REQUIRED FIELD********************** STANDARD POSITION(#403.46) LAST EDITED: `JAN 26, 1996` HELP-PROMPT: `This is the associated standard position from the list provided by VACO.` DESCRIPTION: `Standard role the provider performs as part of this team.` `These standard positions are defined by Central Office.` CROSS-REFERENCE: `404.57^AC` `1)= S ^SCTM(404.57,"AC",$E(X,1,30),DA)=""` `2)= K ^SCTM(404.57,"AC",$E(X,1,30),DA)`
.04	POSSIBLE PRIMARY PRACTITIONER?	0;4	SET	'1' FOR YES; '0' FOR NO; LAST EDITED: `FEB 13, 2003` HELP-PROMPT: `'YES' indicates that this position may function as primary practitioner or attending.` DESCRIPTION: `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	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>99999)!(X<0)!(X?.E1"."1N.N) X` LAST EDITED: `FEB 13, 2003` HELP-PROMPT: `Type a Number between 0 and 99999, 0 Decimal Digits` DESCRIPTION: `Once the current number of assigned patients reaches this level, further assignment of this position should be avoided.`
.09	ASSOCIATED CLINIC	0;9	POINTER TO HOSPITAL LOCATION FILE (#44)	HOSPITAL LOCATION(#44) LAST EDITED: `JAN 29, 2008` HELP-PROMPT: `Field is no longer used` DESCRIPTION: `This field is no longer updated since the release of SD5.3297.` `during various appointing and information processes.` TECHNICAL DESCR: `NO LONGER UPDATED WITH RELEASE OF SD5.3297` SCREEN: `S DIC("S")="IF $P(^(0),""^"",3)=""C"""` EXPLANATION: `Allows only clinic locations.` CROSS-REFERENCE: `404.57^ASCTEAM^MUMPS` `1)= D SETSCTM^SCMCDD2(DA,X)` `2)= D KILLSCTM^SCMCDD2(DA,X)` `This edits the whole cross reference in the Hospital Location File (#44), 'TEAM'. This cross-reference allows users to use the team name to find clinics associated with the team's team positions. See the 'ASCTEAM'` `cross-reference of the TEAM (#404.51) File's NAME (#.01) Field.`
.1	*PRECEPTOR POSITION	0;10	POINTER TO TEAM POSITION FILE (#404.57)	TEAM POSITION(#404.57) INPUT TRANSFORM: `S DIC("S")="I $$OKPREC^SCAPMCU1($P(^SCTM(404.57,DA,0),U,2))" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X` LAST EDITED: `JUN 10, 1999` HELP-PROMPT: `Enter position that supervises this current position.` DESCRIPTION: `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.` SCREEN: `S DIC("S")="I $$OKPREC^SCAPMCU1($P(^SCTM(404.57,DA,0),U,2))"` EXPLANATION: `requires preceptor to be of team & possible preceptor`
.11	BEEPER NUMBER	0;11	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>20!($L(X)<3) X` LAST EDITED: `AUG 01, 1995` HELP-PROMPT: `Answer must be 3-20 characters in length.` DESCRIPTION: `This is the pager or beeper number that is used by this team position.`
.12	CAN ACT AS PRECEPTOR?	0;12	SET	'1' FOR YES; '0' FOR NO; LAST EDITED: `JUL 17, 1995` HELP-PROMPT: `This indicates if position can supervise other positions.` DESCRIPTION: `By answering 'YES', this position may be used as a preceptor position for the team.`
.13	USER CLASS	0;13	POINTER TO USR CLASS FILE (#8930)	USR CLASS(#8930) LAST EDITED: `MAY 17, 1996` HELP-PROMPT: `Class of users who will fill this position` DESCRIPTION: `This is an entry in the USR CLASS file to which anyone assigned to the position must belong.` CROSS-REFERENCE: `404.57^AUSR` `1)= S ^SCTM(404.57,"AUSR",$E(X,1,30),DA)=""` `2)= K ^SCTM(404.57,"AUSR",$E(X,1,30),DA)` `This provides a x-ref on the USER CLASS Field`
1	POSITION DESCRIPTION	1;0	WORD-PROCESSING #404.571	LAST EDITED: `FEB 22, 1995` HELP-PROMPT: `Detailed description of position where duties of the role are outlined.` DESCRIPTION: `This is the long description of the position.`
2.01	DEATH MESSAGE	2;1	SET	'T' FOR TEAM'S PATIENTS; 'P' FOR POSITION'S PATIENTS; 'N' FOR DO NOT SEND; LAST EDITED: `MAY 02, 1996` HELP-PROMPT: `This determines for which patients the position receives messages related to patient death.` DESCRIPTION: `This determines for which patients the position receives messages related to patient death.`
2.02	INPATIENT MESSAGE	2;2	SET	'T' FOR TEAM'S PATIENTS; 'P' FOR POSITION'S PATIENTS; 'N' FOR DO NOT SEND; LAST EDITED: `MAY 02, 1996` HELP-PROMPT: `This determines for which patients the position receives messages related to inpatient activity.` DESCRIPTION: `This determines for which patients the position receives messages related to inpatient activity.`
2.03	TEAM MESSAGE	2;3	SET	'T' FOR TEAM'S PATIENTS; 'P' FOR POSITION'S PATIENTS; 'N' FOR DO NOT SEND; LAST EDITED: `MAY 02, 1996` HELP-PROMPT: `This determines for which patients the position receives messages related to team activity.` DESCRIPTION: `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	'T' FOR TEAM'S PATIENTS; 'P' FOR POSITION'S PATIENTS; 'N' FOR DO NOT SEND; LAST EDITED: `MAY 02, 1996` HELP-PROMPT: `This determines for which patients the position receives messages related to activity in clinics to which the patient is not enrolled.` DESCRIPTION: `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	SET	'1' FOR YES; '0' FOR NO; LAST EDITED: `MAY 11, 1999` HELP-PROMPT: `Enter 'YES' if the preceptor should be notified on death entries.` DESCRIPTION: `A yes entry triggers a mailmessage on a death entry for the preceptor of this position.`
2.06	PRECEPTOR INPATIENT MESSAGE	2;6	SET	'1' FOR YES; '0' FOR NO; LAST EDITED: `MAY 11, 1999` HELP-PROMPT: `Enter 'YES' if the preceptor should be notified on inpatient activity.` DESCRIPTION: `A yes entry triggers a mailmessage on inpatient activity for the preceptor ofthis position.`
2.07	PRECEPTOR TEAM MESSAGE	2;7	SET	'1' FOR YES; '0' FOR NO; LAST EDITED: `MAY 11, 1999` HELP-PROMPT: `Enter 'YES' if the preceptor should be notified on team activity.` DESCRIPTION: `A yes entry triggers a mailmessage on team activity for the preceptor of this position.`
2.08	PRECEPTOR CONSULT MESSAGE	2;8	SET	'1' FOR YES; '0' FOR NO; LAST EDITED: `MAY 11, 1999` HELP-PROMPT: `Enter 'YES' if the preceptor should be notified on consult activity.` DESCRIPTION: `A yes entry triggers a mailmessage on consult activity for the preceptor of this position.`
2.09	AUTOMATIC INACTIVATION MESSAGE	2;9	SET	'T' FOR TEAM'S PATIENTS; 'P' FOR POSITION'S PATIENTS; 'N' FOR DO NOT SEND; LAST EDITED: `SEP 22, 2003` HELP-PROMPT: `This determines for which patients the position receives messages related to patient inactivation.` DESCRIPTION: `Determines where patient inactivation messages are sent`
2.1	PRECEPTOR INACTIVATION MESSAGE	2;10	SET	'1' FOR YES; '0' FOR NO; LAST EDITED: `SEP 22, 2003` HELP-PROMPT: `Enter 'YES' if the preceptor should be notified on automatic patient inactivation.` DESCRIPTION: `Notify Preceptor if patient is automatically inactivated`
5	ASSOCIATED CLINICS	5;0	POINTER Multiple #404.575	404.575 DESCRIPTION: `Multiple Entry of Associated Clinics. This replaces single value used before patch SD5.3297`
200	CURRENT # OF PC PATIENTS		COMPUTED	MUMPS CODE: `S X=$$PCPOSCNT^SCAPMCU1(D0,DT)` ALGORITHM: `S X=$$PCPOSCNT^SCAPMCU1(D0,DT)` LAST EDITED: `JUL 28, 1995` DESCRIPTION: `This calculates the current number of Primary Care patients for this team position.`
201	CURRENT # OF PATIENTS		COMPUTED	MUMPS CODE: `S X=$$PCPOSCNT^SCAPMCU1(D0,DT,0)` ALGORITHM: `S X=$$PCPOSCNT^SCAPMCU1(D0,DT,0)` LAST EDITED: `MAR 22, 2004` DESCRIPTION: `This is the number of all patients (primary care & otherwise) associated with the team.`
202	FUTURE # OF PC PATIENTS		COMPUTED	MUMPS CODE: `S X=$$PCPOSCNT^SCAPMCU1(D0,DT,1,1) S X=$J(X,0,0)` ALGORITHM: `S X=$$PCPOSCNT^SCAPMCU1(D0,DT,1,1) (ALWAYS 0 DECIMAL DIGITS)` DESCRIPTION: `The number of current AND future PC assignments to this team position.`
203	FUTURE # OF PATIENTS		COMPUTED	MUMPS CODE: `S X=$$PCPOSCNT^SCAPMCU1(D0,DT,0,1) S X=$J(X,0,0)` ALGORITHM: `S X=$$PCPOSCNT^SCAPMCU1(D0,DT,0,1) (ALWAYS 0 DECIMAL DIGITS)` DESCRIPTION: `The number of current AND future assignments to this team position.`
300	CURRENT STATUS		COMPUTED	MUMPS CODE: `S X=$S((+$$ACTTP^SCMCTPU(D0)=1):"Active",1:"Inactive")` ALGORITHM: `S X=$S((+$$ACTTP^SCMCTPU(D0)=1):"Active",1:"Inactive")` LAST EDITED: `JUL 14, 1995` DESCRIPTION: `This indicates if the team position is active on the current date.`
301	CURRENT EFFECTIVE DATE		COMPUTED	MUMPS CODE: `N Y S X="" S Y=$P($$ACTTP^SCMCTPU(D0),U,2) D DD^%DT S X=Y` ALGORITHM: `N Y S X="" S Y=$P($$ACTTP^SCMCTPU(D0),U,2) D DD^%DT S X=Y` LAST EDITED: `JUL 09, 2007` DESCRIPTION: `This is the most recent date (not in future) that the active status changed.`
302	CURRENT ACTIVATION DATE		COMPUTED	MUMPS CODE: `N Y S X="" S Y=$P($$DATES^SCAPMCU1(404.59,D0,DT),U,2) D DD^%DT S X=Y` ALGORITHM: `N Y S X="" S Y=$P($$DATES^SCAPMCU1(404.59,D0,DT),U,2) D DD^%DT S X=Y` LAST EDITED: `JUL 09, 2007` DESCRIPTION: `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	MUMPS CODE: `N Y S X="" S Y=$P($$DATES^SCAPMCU1(404.59,D0,DT),U,3) D DD^%DT S X=Y` ALGORITHM: `N Y S X="" S Y=$P($$DATES^SCAPMCU1(404.59,D0,DT),U,3) D DD^%DT S X=Y` LAST EDITED: `JUL 09, 2007` DESCRIPTION: `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	MUMPS CODE: `S X=$P($$GETPRTP^SCAPMCU2(D0,DT),U,2)` ALGORITHM: `S X=$P($$GETPRTP^SCAPMCU2(D0,DT),U,2)` LAST EDITED: `NOV 13, 2003`
305	CURRENT PRECEPTOR POSITION		COMPUTED	MUMPS CODE: `S X=$P($$OKPREC3^SCMCLK(D0,DT),U,2)` ALGORITHM: `S X=$P($$OKPREC3^SCMCLK(D0,DT),U,2)` LAST EDITED: `APR 12, 1999`
306	CURRENT PRECEPTOR		COMPUTED	MUMPS CODE: `S X=$P($$OKPREC2^SCMCLK(D0,DT),U,2)` ALGORITHM: `S X=$P($$OKPREC2^SCMCLK(D0,DT),U,2)`
307	ACTIVE PRECEPTS		COMPUTED	MUMPS CODE: `S X=$S(+$$OKPREC1^SCMCLK(D0,DT)=0:"YES",1:"")` ALGORITHM: `S X=$S(+$$OKPREC1^SCMCLK(D0,DT)=0:"YES",1:"")`
400	ALLOW PRECEPTED CHANGE		COMPUTED	MUMPS CODE: `S X=$S($$OKPREC4^SCMCLK(D0)=1:"YES",1:"NO")` ALGORITHM: `S X=$S($$OKPREC4^SCMCLK(D0)=1:"YES",1:"NO")` DESCRIPTION: `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	MUMPS CODE: `S X=$S($$OKPREC1^SCMCLK(D0,1)=1:"YES",1:"NO")` ALGORITHM: `S X=$S($$OKPREC1^SCMCLK(D0,1)=1:"YES",1:"NO")` DESCRIPTION: `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	MUMPS CODE: `D POSIN^SCMCTSK3(D0)` ALGORITHM: `D POSIN^SCMCTSK3(D0)` LAST EDITED: `MAR 23, 2004` DESCRIPTION: `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.`

ICR LINK	Subscribing Package(s)	Fields Referenced
ICR #2810	Clinical Reminders	ASSOCIATED CLINIC (.09). Access: Direct Global Read & w/Fileman
ICR #3285	Registration	BEEPER NUMBER (.11). Access: Read w/Fileman
ICR #6064	Mobile Scheduling Applications Suite	POSITION (.01). Access: Read w/Fileman

Customize PDF page

Package: Scheduling

Global: ^SCTM(404.57

Information

Description

Accessed By FileMan Db Calls, Total: 24

Pointed To By FileMan Files, Total: 9

Pointer To FileMan Files, Total: 5

Fields, Total: 37

Found Entries, Total: 3

ICR, Total: 3