The basic organization objects are the following:

• CONTACT OBJECT : Holds personal information about a person (name, email, phone, address, etc). The personal information is not necessarily stored in Linkcare DB because it is also possible to integrate with external systems, like a HIS.

• ACCOUNT OBJECT : Represents a user that can initiate a session in the system. An ACCOUNT OBJECT  is related to a CONTACT OBJECT because the system allows to login using credentials associated to personal information, like an email address or phone.

• PROFESSIONAL OBJECT : Represents a professional (doctor, nurse, caregiver...). Professionals can be members of TEAM OBJECTs and can have one or more roles that define the permissions granted.

• CASE OBJECT (PATIENT) : Represents a patient, someone who is under the attention of a PROFESSIONAL and is enrolled in one or more PROGRAM OBJECT

• ASSOCIATE OBJECT : Represents a person that has some relationship with a  CASE OBJECT (PATIENT) and can act on behalf of that patient. For example, if the case is an elderly person that cannot execute the tasks assigned to him, he could designate an associate (a son, daughter, friend...) to act in his name. Normally an ASSOCIATE has the ability to initiate a session in the system and view/execute the tasks assigned to the person he is caring for.

• TEAM OBJECT: Represents a group of professionals. A TEAM allows to create logical groups of professionals that have similar specialties, for example a TEAM of pneumologists of a hospital.

PROFESSIONALS, TEAMS and ROLES

As mentioned before, a PROFESSIONAL can be part of a TEAM. This relation is managed internally by a MEMBERSHIP object, which relates one PROFESSIONAL with one TEAM, or one TEAM with another TEAM. Additionally it is possible to assign certain privileges (ROLES) to each MEMBERSHIP.

• A PROFESSIONAL can belong to one or more TEAMS. Each MEMBERSHIP has his own ROLEs assigned, so it is possible for a PROFESSIONAL to belong to a TEAM with certain ROLES, and to another TEAM with a completely set of ROLES

• A TEAM can also be member of one or more TEAMS. This relation is also managed by MEMBERSHIPs.

• Each MEMBERSHIP can have one or more ROLES assigned

• The ROLES that can be assigned to a PROFESSIONAL can be grouped in:

  • Medical roles: assigned to PROFESSIONALS that will manage patients (e.g. CASE MANAGER, STAFF, SUPERVISOR...)

  • Administrative roles: Used to define which can browse/edit the organization objects. For example, a TEAM EDITOR can create and edit the properties of a TEAM.

A PROFESSIONAL that is not member of any TEAM can initiate session in the system, but will have nothing to do.

ACTIVE TEAM

When a PROFESSIONAL initiates a session in the system, he/she may be member of multiple TEAMs, but only one is the considered the "ACTIVE TEAM". The active TEAM is selected using the API function session_set_team () and has some implications when requesting information to the API. For example, the function subscription_list () will only return the list of SUBSCRIPTION OBJECTs in which the active TEAM is member.