CMS 7.0.0.10

1

CMS Desktop

Vitals

The default vital view brings back vitals for the last 12 months. This is causing problems for customers who record vitals on a daily basis. the vitals will now bring back the last 12 recorded dates of data. So if a vital is recorded monthly this will be 12 months if daily this will be 12 days. If a vital is recorded multiple times on one day (e.g. Fluid) it will bring back all readings within the last 12 days

2

1

CMS Desktop

Reports

When printing the resident list, you were prompted for a parameter

when printing an assessment from the Assessment Wizard screen you were prompted for parameters

2

A & I

When viewing incidents on a smaller screen size, the scroll bar was missing, preventing you from viewing all incident details

3

Vitals

If the date of a new vital was changed this resulted in the record being duplicated

4

Shift Handover

When returning to shift handover screen after visiting another, the view would default to tasks

Tasks

When a new resident has been admitted the tasks are basing missed episodes from the task start date rather than the resident's admission date

5

Assessment Downloads

when downloading assessments from our web server this was resulting in duplication of the template models

6

CMS Tablet

Login

The tablet will now remember who last logged in

The locations will populate in a more timely fashion if the tablet has gone offline. This was quite slow and gave the impression to the user that the locations were not populating

7

Vitals

If a vital is made up of 2 parts for example Fluid In and Fluid Out, then if only the second category has a reading this was not being displayed.

The time logged was not being displayed

When viewing Fluids - the running totals were not being dispalyed

Comments were not displayed

8

Security Groups

There was an issue with security groups. The residents were not correctly filtered

9

Error Logging

Improved error logging

10

CMS Tablet Service

Crashing

There have been reported instances where the CMS service starts to over load the computer and then results in the service being closed. This issue has now been resolved.