task_list_date ( session, date, type, id )

DEPRECATED: use new functions:

Is a function to list all tasks and events in a given date. The tasks and the events returned depends of the type:

"ADMI": to view all tasks and events of a patient in an admission
"CASE": to view all tasks and events from all admissions of a patient ( in the active team of the session)
“CALLS”: returns events with CALL type.
"USR": returns the AGENDA for this user.

Input

parameters:

session: a token to the session obtained from session_init ()

date: is the date to list the events and the tasks

type: ADMI|CASE|USR|SCH|DUE

“ADMI” : returns the tasks of the admission. The ID input parameter is the admission_id referenced by the URL

“CASE”: returns the tasks and the events of the case. The ID input parameter is the case_id referenced by the URL

“USR”: returns the tasks assigned to the user, assigned to the rol but not assigned to the user, and events created by or assigned to the user. Is called from USER(CALENDAR) graphic object. The ID input parameter is the id that is referenced by the URL

“CALLS”: returns events with CALL type.

“SCH”: returns tasks not assigned or not programmed. Is called by SCHEDULE graphic object. There is no ID input parameter

“DUE”: returns overdue tasks or open events. Will called by a graphic object. The ID input parameter is a id reference /to show the pending tasks and open events of a defined user, or none to see all due tasks or open events

id: the user, case or admission id depending on the type ( can be an external ID like SOURCE/ID/NNNN )

Output

parameters:

tasks:

id: is the task_id

locked: true o false, flag of accesibility of task

class: PRO_TASK/SYS_TASK/EVENT

code: TASK_CODE

type:

CASE/CALL/VIDEO/MSG/TELE/CARE/TEAM for protocol tasks.

CASE: Assigned to the CASE (patient)
CALL: Phone call
VIDEO: Video call
MSG: Message
TELE: Remote device
REPORT: Report
DOCUMENT: Document file
CARE: Task not in any of the categories above.

ENROLL/JOIN/REJECT/SUSPEND/RESUME/DISCHARGE for system tasks.

CARE/SOCIAL/ADMIN/TECH/ENROL_REQ/OPINION_REQ for events.

status: UNASSIGNED/NOT SENT/PENDING/DONE/CANCELLED/PAUSED for tasks. OPEN/CLOSED for events.

external: Open task due to be performed by someone else

if active role is not "Case Manager"
- assigned to a role different from the active role or
- assigned to same role than the active role and assigned to a TEAM different from the active TEAM and the active TEAM is not a member of the assigned TEAM with the assigned role and
if active role is "Case Manager":
- assigned to a role "Service" (Service assigned TASKs are not shown to any other role) or
- assigned to a role other than "Service" and assigned to a TEAM different from the active TEAM and the active TEAM is not a member of the assigned TEAM with the assigned role or with the "Case Manager" role

date: is the date of the task

hour: is the hour of the task

description: is the description of the task in the given language in the input parameter, or the language of the active session of the token given.

group_by: is the tag to group events and tasks if the function input parameter is USR. The information is the name of the patient plus the age or the telephone number or name of the issuer for events.

admission: is the admission related by the task

case: is the case of the admission

id: the case id

nick: case nick name

byear: case birthday year

bdate: case birthday date (AAAA-MM-DD)

age: case age at task’s date

gender: case gender

ndocs: is the number of docs of the admission

issuer: is the issuer of the event

name: can be POSTER/CASE/OTHER/UNKNOWN

description: is the issuer description in the gived session language

duration: is the duration of the event

ErrorMsg: any fault in the call, either in the validation of input parameters, errors in the connection to the database or any other error, this parameter returns the error message produced

Request

sample:

task_list_date (“LCAAAAAAAAA”, ‘2012-01-01’, ‘CASE’, ‘1234’, ‘ES’);

Response

sample:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>

<tasks>
  <next>
    <date>2015-06-04</date>
  </next>
  <prev>
    <date>2015-04-14</date>
  </prev>
   <task>
      <class>PRO_TASK</class>
      <id>55380</id>
      <code>ENROLL</code>
      <locked>false</locked>
	  <external>true</external>
      <type>CASE</type>
      <date>2015-01-28</date>
      <hour>00:00:00</hour>
      <description>ESTRATIFICACIÓN</description>
      <admission>
         <ref>21844</ref>
      </admission>
      <case>
         <ref>13752</ref>
         <data>
            <nickname>ALFREDO  M</nickname>
            <byear>1945</byear>
            <bdate>1945-12-11</bdate>
            <age>69</age>
            <gender>F</gender>
         </data>
      </case>
      <group_by>ALFREDO  M (69)</group_by>
      <status>UNASSIGNED</status>
	  <progress>55</progress>
   </task>
</tasks>

Notes:

a) Nowadays if an EVENT is assigned to nobody and is not associated to an ADMISSION, it will not appear in the agenda of anybody. It's a case still not resolved because we don't have the concept of a "reference" patient.

b) If a task or event haven't assigned a person, it will only appear in users with that role in the proprietary TEAM of a SUBSCRIPTION, but it will not appear in users with that role in a TEAM which is member of the SUBSCRIPTION. Another case still not resolved, that we can associate with a TASK or EVENT of a TEAM.

Additionally, system tasks such as ENROLL, JOIN... will not apear in any agenda (because are system tasks, although it's associated with "case manager" role for legacy reasons).

Browser not supported