Global: ^SCTM(404.57

This is the Name of the Team Position.

1)= S ^SCTM(404.57,"B",$E(X,1,30),DA)=""

2)= K ^SCTM(404.57,"B",$E(X,1,30),DA)

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).

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).

Entry in the team file.

Pointer  to TEAM File (#404.51)

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).

1)= S ^SCTM(404.57,"C",$E(X,1,30),DA)=""

2)= K ^SCTM(404.57,"C",$E(X,1,30),DA)

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).

These standard positions are defined by Central Office.

1)= S ^SCTM(404.57,"AC",$E(X,1,30),DA)=""

2)= K ^SCTM(404.57,"AC",$E(X,1,30),DA)

(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.

Short Descr:  Workload event creation

Description:  Workload Event Creation. Triggers entry in PCMM HL7 EVENT file for workload HL7 messaging.

Set Logic:  D POSBXREF^SCMCHLX(DA,404.57)

Set Cond:  S X=$G(X2(1))

Kill Logic:  D POSBXREF^SCMCHLX(DA,404.57)

Kill Cond:  S X=$G(X1(1))

X(1):  POSSIBLE PRIMARY PRACTITIONER?  (404.57,.04)  (Subscr 1)  (forwards)

Once the current number of assigned patients reaches this level, further assignment of this position should be avoided.

Short Descr:  Workload HL7 Trigger

Description:  Workload HL7 trigger. Triggers entry in PCMM HL7 EVENT file.

Set Logic:  D POSBXREF^SCMCHLX(DA,404.57)

Set Cond:  S X=0 I $P($G(^SCTM(404.57,DA,0)),U,4) S X=1

Kill Logic:  Q

X(1):  MAX NUMBER OF PATIENTS  (404.57,.08)  (Subscr 1)  (forwards)

during various appointing and information processes.

NO LONGER UPDATED WITH RELEASE OF SD*5.3*297

1)= S ^SCTM(404.57,"D",$E(X,1,30),DA)=""

2)= K ^SCTM(404.57,"D",$E(X,1,30),DA)

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.

It is an optional field. However, when indicated, this field usually contains an attending position.

This is the pager or beeper number that is used by this team position.

By answering 'YES', this position may be used as a preceptor position for the team.

This is an entry in the USR CLASS file to which anyone assigned to the position must belong.

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

This determines for which patients the position receives messages related to patient death.

This determines for which patients the position receives messages related to inpatient activity.

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.

This determines for which patients the position receives messages related to activity in clinics to which the patient is not enrolled.

A yes entry triggers a mailmessage on a death entry for the preceptor of this position.

A yes entry triggers a mailmessage on inpatient activity for the preceptor ofthis position.

A yes entry triggers a mailmessage on team activity for the preceptor of this position.

A yes entry triggers a mailmessage on consult activity for the preceptor of this position.

Determines where patient inactivation messages are sent

Notify Preceptor if patient is automatically inactivated

Multiple Entry of Associated Clinics. This replaces single value used before patch SD*5.3*297

This calculates the current number of Primary Care patients for this team position.

This is the number of all patients (primary care & otherwise) associated with the team.

The number of current AND future PC assignments to this team position.

The number of current AND future assignments to this team position.

This indicates if the team position is active on the current date.

This is the most recent date (not in future) that the active status changed.

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

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.

act as preceptor' controls.

as preceptor' controls.

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.