2.7.31 Release Notes
Bug fixes
ADMISSION actions (discharge, pause, resume) should only be allowed to a user with role CASE MANAGER or SERVICE in the SUBSCRIPTION
In TRIAL or STRATIFIED PROGRAMS the action list of optional TASKS doesn't show all the available TASKS
ADMISSION actions (discharge, pause, resume) should only be allowed to a user with role CASE MANAGER or SERVICE in the SUBSCRIPTION
When a creating a new EVENT, the function should check if there was a similar EVENT open (same event type, poster, assigned to...) to avoid creating unnecessary repeated EVENTS, but the verification was failing when the creator of the EVENT was a patient (duplicated EVENTs were always created)
Do not allow to insert a TASK with the property RECURSIVE=”SINGLE” in a date where already exists another similar TASK (based in the same TASK TEMPLATE)
ADMISSION_REFERRAL_SET() must check that the professional is CASE MANAGER of the SUBSCRIPTION
event_insert (),EVENT_INSERT() : when a patient inserts a new EVENT, the function was not checking properly whether there existed another similar open EVENT with the same characteristics (type of EVENT, poster, assigned to). The consequence was that a new EVENT was always inserted instead of reusing the similar open EVENT to continue the conversation
event_set () : was changing the ISSUER_TYPE from "CASE" to "POSTER"
extraction_action_list () : was not returning the list of DATACODES of a TASK or FORM
extraction_tasks () : crashed when the parameter "suscription" was not null
library_program_set_profile () :
Do not allow to assign duplicate PROGRAM CODES
Do not allow invalid characters in the PROGRAM CODE.
library_program_task_set () : was not assigning the image to the TASK TEMPLATE
https://linkcare.atlassian.net/wiki/spaces/DES/pages/16974082 : When trying to insert a TASK with recursive frequency = “SINGLE”, do not allow the insertion if there exist a similar open TASK in the same date
task_insert_by_task_code () : When trying to insert a TASK with recursive frequency = “SINGLE”, do not allow the insertion if there exist a similar open TASK in the same date
task_set () When changing the date of a TASK with the property RECURSIVE=”SINGLE”, do not allow the change if in that date already exists another similar TASK (based in the same TASK TEMPLATE)
team_user_insert () : was allowing to create a new USER with a duplicate USERNAME
user_get_program_list () : the count of EVENTs was not taking into account the active ROLE
https://linkcare.atlassian.net/wiki/spaces/WS/pages/524402 : do not remove the "Staff" ROLE when the "Professional Role" property is set to empty
OBJECT CODE evaluation: When evaluating the value of the OBJECT CODES in a REPORT, the default property was not calculated correctly when the OBJECT CODE expression ended with a curly bracket
Incompatibility with previous versions
The parameters or the response or the following functions have changed in a way that make the incompatible with previous version of the API.
To maintain compatibility with previous version ensure to indicate the desired API version when initiating a session with https://linkcare.atlassian.net/wiki/spaces/WS/pages/524509
https://linkcare.atlassian.net/wiki/spaces/WS/pages/5898366 Changed XML response format
https://linkcare.atlassian.net/wiki/spaces/WS/pages/5898373 Changed XML response format
task_set () : Change in the XML node for specifying the assignments of the TASK
New functions
https://linkcare.atlassian.net/wiki/spaces/WS/pages/3350560785 : Function to update an ADMISSION from a PROGRAM version to a newer version.
https://linkcare.atlassian.net/wiki/spaces/WS/pages/3354132481 : Function to update all ADMISSIONS of a SUBSCRIPTION from a PROGRAM version to a newer version.
library_program_task_set () : When assigning a image to a TASK TEMPLATE, the image was not stored
Improvements
action_list_case () : performance improvements
https://linkcare.atlassian.net/wiki/spaces/WS/pages/794034181 : performance improvements
https://linkcare.atlassian.net/wiki/spaces/WS/pages/95723680 : When invoked by a patient, do not include TASKS with status “CANCELED”, “PAUSED” or “EXPIRED”
https://linkcare.atlassian.net/wiki/spaces/WS/pages/801177622 : Will not allow to open an EVENT if there exists another similar one already opened (involves the same POSTER and ASSIGNED_TO, and same type of EVENT)
https://linkcare.atlassian.net/wiki/spaces/WS/pages/525893650 : Added information about the default timezone
https://linkcare.atlassian.net/wiki/spaces/WS/pages/6750308 :
Permissions grouped in the node “permissions” of the response
In previous version, the “editable” permission was defined directly as a property of the ADMISSION instead of defining it into the node “permissions”.
Added the permission “delete” to indicate whether the active USER has privileges to delete the SUBSCRIPTION
Added new information to indicate how many outdated ADMISSIONS exist in the SUBSCRIPTION
https://linkcare.atlassian.net/wiki/spaces/WS/pages/12288038 :
Permissions grouped in the node “permissions” of the response
In previous version, the “editable” permission was defined directly as a property of the ADMISSION instead of defining it into the node “permissions”.
Added the permission “delete” to indicate whether the active USER has privileges to delete the SUBSCRIPTION
Added new information to indicate how many outdated ADMISSIONS exist in the SUBSCRIPTION
https://linkcare.atlassian.net/wiki/spaces/WS/pages/128057345 :
Permissions grouped in the node “permissions” of the response
In previous version, the “editable” permission was defined directly as a property of the ADMISSION instead of defining it into the node “permissions”.
Added the permission “delete” to indicate whether the active USER has privileges to delete the SUBSCRIPTION
Added new information to indicate how many outdated ADMISSIONS exist in the SUBSCRIPTION
https://linkcare.atlassian.net/wiki/spaces/WS/pages/12288029 :
Permissions grouped in the node “permissions” of the response
In previous version, the “editable” permission was defined directly as a property of the ADMISSION instead of defining it into the node “permissions”.
Added the permission “delete” to indicate whether the active USER has privileges to delete the SUBSCRIPTION
Added new information to indicate how many outdated ADMISSIONS exist in the SUBSCRIPTION
https://linkcare.atlassian.net/wiki/spaces/WS/pages/96024402 :
Do not include TASKS with status “CANCELED”, “PAUSED” or “EXPIRED”
New status filter: “PENDING” when the request includes this filter, then TASKs scheduled in the future will not be returned. Only open TASKS scheduled up to the current date will be returned
Deprecated functions
FORM FORMULAS
https://linkcare.atlassian.net/wiki/spaces/WS/pages/9306292 : Do not allow to insert a TASK with the frequency property = ”SINGLE” in a date where already exists another similar TASK (based in the same TASK TEMPLATE):
OBJECT CODES
OBJECT CODE "IDENTIFIER": in TEAM IDENTIFIERS support a scope to filter by a specific TEAM
Other
New ADMISSION stage: “MIGRATION”. This stage can be used to define TASKS that should be executed when an ADMISSION is updated from a PROGRAM version to a newer PROGRAM version.
Importing / Updating PROGRAMS: when importing a new PROGRAM with a PROGRAM CODE that already exists, avoid duplicating the PROGRAM CODE by appending a suffix to the imported PROGRAM CODE. The same thing applies when the update of an existing PROGRAM includes a modification of the PROGRAM CODE that already is assigned to a different PROGRAM