A TEAM is a basic organizational object that represents a group of PROFESSIONAL OBJECT or other TEAM objects that share some common attribute (e.g. they belong to the same hospital unit)

BASIC CONCEPTS

TEAM OWNERSHIP

A TEAM belongs to one of the following groups depending on how it is created:

• Root level TEAMS: Are the TEAMS created by the superadministrator of the platform, and are not owned by any other TEAM

• Owned TEAMS: When a PROFESSIONAL user initiates a session in the platform, it is always working as a member of certain TEAM, which is the session’s active TEAM. If that PROFESSIONAL has administrative privileges to create other TEAMS, then the new TEAMS will be considered to be owned by the session’s active TEAM. Therefore, the new TEAMS are “Owned TEAMS”.
  A owned TEAM can be administered by the members of the "owner" team with administrative roles.

Example:

Let’s suppose that a Linkcare instance is deployed in a Hospital called “BARCELONA HOSPITAL”. Then the superuser can create a root level TEAM called “BARCELONA HOSPITAL” and add a PROFESSIONAL member with administrative roles to create and manage other TEAMS.

When the administrative user of the hospital initiates a session in the platform, he will be working as a member of the “BARCELONA HOSPITAL” TEAM. if now, for example he creates a new TEAM called “CARDIOLOGY” to group the professionals of the cardiology unit, then the new “CARDIOLOGY” TEAM will be owned by the “BARCELONA HOSPITAL” TEAM (because it was the session’s active TEAM when the administrator user created it).

From now on, any user member of “BARCELONA HOSPITAL“ with privileges to manage TEAMS will have the capability of managing the “CARDIOLOGY” TEAM.

TEAM MEMBERSHIPS

Once created, a team can insert members under two different approaches: The classical administration approach, and the networked approach.

PROFESSIONAL MEMBERS

A PROFESSIONAL member is a professional (doctor, nurse, etc..) that has been invited to be part of a TEAM and has been assigned with ROLES that give him the ability to perform certain actions.

A TEAM administrator can create and administer professional members in the TEAM and assign ROLES individually to each member.

TEAM MEMBERS

In an attempt to reduce administration costs and allow mutual interaction, it is also possible to add a TEAM as member of another TEAM and assign ROLES to it. Under this approach, all the PROFESSIONALs in the new TEAM member will also be granted with the ROLES assigned to the TEAM.

Note that a PROFESSIONAL that belongs to a TEAM member will inherit the ROLES assigned to that TEAM only if he has also that ROLE in the TEAM.

Example

Let’s suppose that the TEAM “CARDIOLOGY” is added as member of the TEAM “BARCELONA HOSPITAL” with role “Case Manager”.

Let’s also suppose that the TEAM “CARDIOLOGY” contains 2 PROFESSIONALS:

• “Professional A” with role “Case Manager”

• “Professional B” with role “Supervisor”

In this situation, “Professional A” can act as a “Case Manager” of the “BARCELONA HOSPITAL”, because he is a “Case Manager” of the “CARDIOLOGY” TEAM, and the “CARDIOLOGY” TEAM has the role “Case Manager” as a member of “BARCELONA HOSPITAL”

Nevertheless, the “Professional B” cannot act as a “Case Manager” of “BARCELONA HOSPITAL” even though he belongs to the “CARDIOLOGY” TEAM (which has role “Case Manager” in “BARCELONA HOSPITAL”), because he is not a “Case Manager” in the “CARDIOLOGY” TEAM.

INVITATIONS

When a PROFESSIONAL or a TEAM are added as members of another TEAM, they cannot in fact be added directly (for compliance with data privacy legislation) and instead, they are “invited” to join the TEAM.

By creating an invitation, a TEAM administrator may use some basic contact information (i.e. mail address or phone number) to send an invitation request. The recipient of the invitation may accept the invitation by clicked on the invitation link, and proceed to set his or her profile settings.

Pending invitation can be monitored in the team administrator dashboard. Once accepted or declined, the action is reported to the team administrator for follow up. Pending invitations can be re-send timely until a final response is received.

REQUESTS

In the opposite direction, individual teams or users may prefer to first register in Linkcare and then request to be part of a team by issuing a membership request. Membership requests are reported to the requested team administrators who can accept or decline the membership request. If the request is accepted, the team administrator may then set the accepted member roles. Membership requests can be re-send or cancelled by the request issuer.

PRIVATE TEAMS (PRACTICE TEAMS)

A TEAM is considered a “Private Team” when it is assigned to a specific professional USER (do not mistake “assigned” with “member of”). This is used normally by doctors that have their own office where they attend the patients.

In all other aspects, a PRIVATE TEAM behaves exactly the same than any other regular TEAM. It is possible to add members, assign ROLES, etc.

A USER can have only one PRIVATE TEAM.

A PRIVATE TEAM is created automatically by means of the following API functions:

• team_user_insert () : When a USER is added to an existing TEAM, it is possible to indicate that the USER should also have his own private TEAM. See the description of the function to get more details about the memberships and roles that are established between the TEAMS involved and the USER

• user_set () : when the property team_private is set to true, a PRIVATE TEAM is created for that USER.

TEAM OBJECT PROPERTIES

TEAM PROFILE

TEAM CATEGORY CODES

See: TEAM.CATEGORY CODES

WEB SERVICES

The following web services allow to access and modify TEAMS:

BROWSING TEAMS:

EDITING TEAMS:

MANAGING TEAMS' EVENTS:

MANAGING TEAMS' MEMBERS: