The CLINICAL OBJECT store the real information collected about the evolution of PATIENT in the context of a PROGRAM.

• ADMISSION OBJECT: Represents the participation of a CASE OBJECT (PATIENT) in a SUBSCRIPTION OBJECT. An ADMISSION contains the information that will be collected along the ADMISSION life cycle. This information is materialized as TASKS, EVENTS, FORMS and other clinical objects that belong to that ADMISSION.

• EVENT OBJECT: Represents a communication addressed to a user (either a CASE, ASSOCIATE or PROFESSIONAL). EVENTS are used to send messages to participants of the platform. For example, if a PROFESSIONAL wants to communicate something to the patient, an EVENT would be created with the desired message and sent to the patient through the desired communication channel (SMS, email, etc.).

• TASK OBJECT: Is a object generated from the combination of a WORKPLAN OBJECT and a TASK TEMPLATE OBJECT (see LIBRARY OBJECTS). A TASK contains a number of ACTIVITES that the professional or the patient should complete. There exist also 'system' TASKS that are executed automatically by the system. A TASK can be assigned to a specific person, or to a TEAM or ROLE.

• REPORT OBJECT: Is an object generated as a copy of a REPORT TEMPLATE OBJECT. It is used to create reports showing information collected during the lifetime of an ADMISSION.

• FORM OBJECT: Is an object generated as a copy of a FORM TEMPLATE OBJECT. In most situations is a questionnaire addressed to a user (professional or patient) with questions that must be answered to follow the workflow of the PROGRAM. In general terms is a container of a list of ITEM OBJECT (that can be questions, calculations, actions, etc.).

• ITEM OBJECT: Is an object generated as a copy of a ITEM TEMPLATE OBJECT. There are multiple types of ITEMS that go from questions, static texts, calculations, actions, etc.

HIERARCHY