From a developer point of view, a library object can be understood as the formal definition of a Class, and a https://linkcare.atlassian.net/wiki/spaces/WS/pages/524496 is merely an instance of one of the library objects.

• https://linkcare.atlassian.net/wiki/spaces/WS/pages/4260259 : Is the topmost object in the hierarchy and defines the general properties of a care plan. For example consider a “Kidney Rehabilitation” program that contains the definition of all the tasks that a professional or a patient should do from the enrollment until the discharge of the patient. The https://linkcare.atlassian.net/wiki/spaces/WS/pages/4260259 is used to configure the general properties of the care plan (name of the program, description, configuration settings, etc...)

• https://linkcare.atlassian.net/wiki/spaces/WS/pages/994082921 : Once a https://linkcare.atlassian.net/wiki/spaces/WS/pages/4260259 has been created and configured, it is possible to generate different versions. For example consider a case where a PROGRAM has been fully defined, put in production, and some patients have already been enrolled and are executing the TASKs defined. Based on the experience with the patients we may find it desirable to add new TASKs, or improve existing ones. This is done creating new versions of an existing PROGRAM.

• https://linkcare.atlassian.net/wiki/spaces/WS/pages/20545605 : A PROGRAM may have different lines of actuation depending on some variables. For example, in a “Kidney Rehabilitation” program we would want to assign different tasks to the patient depending on the type of hemodialysis prescribed. When a patient is enrolled in a PROGRAM, it can be assigned to a specific PROTOCOL.

• https://linkcare.atlassian.net/wiki/spaces/WS/pages/4260264 : Defines which activities should be executed, who is the target (professional or patient), scheduling (at a specific day and/or time). Each https://linkcare.atlassian.net/wiki/spaces/WS/pages/4260264 contains a single https://linkcare.atlassian.net/wiki/spaces/WS/pages/27263072 and allows to configure the properties to define how/when/by who the TASK should be executed

• https://linkcare.atlassian.net/wiki/spaces/WS/pages/27263072 : Is basically a container of a list activities that a patient or professional should perform. The possible activities supported currently are

  • https://linkcare.atlassian.net/wiki/spaces/WS/pages/4260257 : Can be considered as a questionnaire with a list of https://linkcare.atlassian.net/wiki/spaces/WS/pages/579829764. Each https://linkcare.atlassian.net/wiki/spaces/WS/pages/579829764 can be a question that the professional or the patient should answer, an action that the platform will execute, an informative message, etc

  • https://linkcare.atlassian.net/wiki/spaces/WS/pages/37486691 : Definition of template to generate a document (PDF) showing information collected during the execution of the PROGRAM. For example, in a https://linkcare.atlassian.net/wiki/spaces/WS/pages/37486691 you define a header section, a footer section and a body section containing the texts and other data that you want to show

OBJECT HIERARCHY

Relation with CLINICAL OBJECTS

As mentioned before, a PROGRAM is only a template that is later materialized in a clinical object.

The following table shows the correspondence between library objects and clinical object.