cc360 healthcenter administrator user manual · 12.2 enable/ disable modules ... in the users...

Confidential

© 2015 CGI– All rights reserved 12 April 2017 Lautruhøj 10, 2750 Ballerup, Denmark

CC360 HealthCenter Administrator user manual

Release 3.9

CC360 HealthCenter Administrator user manual Release 3.9

Confidential

© 2015 CGI– All rights reserved 12 April 2017 Lautruhøj 10, 2750 Ballerup, Denmark

Product Identification

Product name Model/number

CGI CommunityCare360-HealthCenter (CC360-HC) Version 3.7

Manufacturer

Name of Company Address Representative

CGI Danmark A/S Lautruphoej 10

DK-2750 Ballerup

Denmark

Michael Zakarias

Conformity Assessment

Health Authority Registration Device classification and registra-

tion number Route to compliance

Health Canada Class I Medical Device

MDEL # 7049

Medical Devices Regulations SOR/98-282

FDA Class I Medical Device

Operator Number 10048035

21 Code of federal Regulations

Parts 800

Class I Medical device

No registration number is given for Class I devices.

Annex VII of the Medical Devices Directive 93/42/EEC.


Confidential 12 April 2017 © 2015 CGI– All rights reserved

cgi.com © 2015 CGI GROUP INC 3

Declaration of Conformity

Manufacturer CGI Danmark A/S

Lautruphoej 10 DK-2750 Ballerup

Denmark

Authorized representative Not applicable

Conformity assessment procedure Annex VII of the Medical Devices Directive 93/42/EEC with amendments.

Product CGI CommunityCare360-HealthCenter (CC360-HC) Version 3.7

Risk Class Class I

We, the legal manufacturer hereby declare that the abovementioned product complies with the European Medical Device Directive 93/42/EEC, its amendments and its relevant transposition into all national laws of the member states into which we place the devices.

Signed in Ballerup 20. May 2015

Name and authority Michael Zakarias, R&D Director

Signature

List of changes

Version no. Date Produced by Changes

0.1 09.12.2014 Anand Packiam

Initial Version

1.0 20.08.2015 Khushboo

Verma

Published for release 3.5.1

1.1 16.11.2015 Anand Britto Upgraded to new system settings 3.5.2

2.0 07.12.2015 Khushboo Verma

Published for Release 3.5.2

3.0 18.05.2016 Khushboo Verma

Published for Release 3.6

4.0 09.09.2016 Khushboo

Verma

Published for Release 3.7




Contents

1. Introduction ...........................................................................................................................6

2. Intended use .........................................................................................................................6

3. Product Specifications ...........................................................................................................6 3.1 Compatibility ..............................................................................................................6

4. Using CGI CommunityCare360 – HealthCenter Administrator Web ........................................6 4.1 Getting started ...........................................................................................................6 4.2 Product features ........................................................................................................7

5. User management .................................................................................................................8 5.1 User roles ..................................................................................................................8 5.2 Clinician users ......................................................................................................... 11 5.3 Citizen users ............................................................................................................ 14

6. Classification ....................................................................................................................... 18 6.1 Country classification ............................................................................................... 18 6.2 Region classification ................................................................................................ 21 6.3 Municipality classification ......................................................................................... 22 6.4 Diagnosis classification ............................................................................................ 23 6.5 Result codes classification ....................................................................................... 24 6.6 Organizational unit code classification...................................................................... 26 6.7 Citizen Organizational Unit....................................................................................... 27 6.8 Allergies .................................................................................................................. 29

7. Templates ........................................................................................................................... 30 7.1 Template Plans........................................................................................................ 30 7.2 Template Activities................................................................................................... 31 7.3 Template Questionnaires ......................................................................................... 33 7.4 Template Question .................................................................................................. 34 7.5 Template Answer Group .......................................................................................... 35 7.6 Template Answer ..................................................................................................... 37 7.7 Template Answer Alert............................................................................................. 38 7.8 Template Check List Items....................................................................................... 39 7.9 Template Continuity ................................................................................................. 41 7.10 Template Allowed Results ...................................................................................... 42

8. State algorithm .................................................................................................................... 43 8.1 Maintaining in SugarCRM ........................................................................................ 44 8.2 Validation rules ........................................................................................................ 44 8.3 Import using CC360 format ...................................................................................... 44 8.4 Calculation Logic ..................................................................................................... 44

9. System settings ................................................................................................................... 45 9.1 Maintaining in sugarCRM ......................................................................................... 46 9.2 Validation rules ........................................................................................................ 46 9.3 Configuration options ............................................................................................... 47 9.4 CC360 csv import format ......................................................................................... 51 9.5 Citizen important info ............................................................................................... 53 9.6 Maintaining in sugarCRM ......................................................................................... 53 9.7 Circle of Care .......................................................................................................... 54 9.8 Primary Care Physician/GP ..................................................................................... 55 9.9 Other Info / Notes .................................................................................................... 55

10. Logging ............................................................................................................................. 57 10.1 Access log reports ................................................................................................. 57 10.2 Transaction log reports .......................................................................................... 58 10.3 User activity reports ............................................................................................... 59

11. SMTP Settings (email Settings) ......................................................................................... 60 11.1 SMTP Settings ....................................................................................................... 60




12. Procedures ........................................................................................................................ 62 12.1 Change unit for existing measurement type............................................................ 62 12.2 Enable/ Disable modules ....................................................................................... 62 12.3 Setting Decimal points for measurement types ....................................................... 63

13. Troubleshooting ................................................................................................................. 63




1. Introduction

CGI CommunityCare60 HealthCenter Administration manual helps you to work with the CGI Communi-tyCare60 HealthCenter administration and configuration as an administrator or a clinician. The administra-tion web uses SugarCRM and incorporates features from SugarCRM that are described in this manual. SugarCRM is a web-based customer relation management, or CRM, tool that facilitates the management of multiple business roles. The SugarCRM application furthers the high standards set by the open source community around the world. Unlike most proprietary CRM offerings, all SugarCRM applications are na-tively built on the pure Open Source LAMP (also WAMP) platform: Linux or Windows, Apache or IIS, MySQL, PHP, and SugarCRM. It is highly recommended that no changes are made to Sugar CRM/ Admin module beyond the scope of this manual.

2. Intended use

CGI CommunityCare360 HealthCenter administrator is intended to administer and configure CGI Com-munityCare360 HealthCenter application. An administrator can implement access control on CC360 HC modules, create new modules or configure existing modules. The intended users for browser based administration application (CGI CommunityCare360 HealthCenter Administration Application) are the health professionals having an interest in configuration of the system and administrators for user management and other configurations. This document does not describe default features provided by SugarCRM that are not relevant for CGI CommunityCare360 HealthCenter. All yellow highlighted information needs localization. Please remove the highlights before distribution. This statement must be removed as well.

3. Product Specifications

This user manual describes CGI CommunityCare360 HealthCenter version 3.7.

3.1 Compatibility

3.1.1 Browser

CGI CommunityCare360 - HealthCenter Administrator Web portal is designed for use in the following browsers:

Browser name Version

Firefox 3+

Internet Explorer 9+

Chromium and Google Chrome

All

Safari 3.0+

4. Using CGI CommunityCare360 – HealthCenter Administrator Web

4.1 Getting started

4.1.1 How to find the administrator web portal

You can find the web portal for administrator at Insert link here




4.1.2 Login

The login credentials as administrator are provided to you by CGI. Both user name and password are case sensitive. The limit of incorrect login attempts is set to five by default. If you fail to login within five attempts, the account will be locked. CGI support desk helps you unlock the account. Clinicians can as well log in to CGI CommunityCare360 HealthCenter administrator web using their regular clinician creden-tials.

Administrator has administrative privileges in SugarCRM to perform tasks such as creating users. Clini-cian users can access and use SugarCRM modules but do not have administrative privileges. To login

1. To access the CGI CommunityCare360 HealthCenter, click on the following link < Link>. 2. Go to the CC360 Login screen. 3. In the Username field, enter the username. 4. In the Password field, enter the password. 5. To login, click Login.

Now you are logged in successfully and directed to the Template Treatment Plans tab screen. 4.1.3 Log out

The logout option is available at the top of the portal.

To Logout

1. Click Log out located at the top right corner of the CGI CommunityCare360 screen. Now, you are successfully logged out and the Login screen appears again.

4.1.4 Forgot password

In case the user forgets password, an email with new generated password is sent upon click of link Forgot password.

4.2 Product features

SugarCRM Dashboard is opened after logging in. The following features are important features of administrator web:




User management

Role management

Password management These features are described in detail in the following chapters.

5. User management Click on the Admin link from the top right corner to go to user management.

In the Users subtab screen, click the User Management link on left and the user page appears.

5.1 User roles

Field Name Field Type Description

Id Char(36)

Name Varchar(150) User Role Name

Description Text About the Role

User Roles enables you to group users according to the tasks that they need to perform and then define a set of privileges. User roles control what a user can do with a record once the system retrieves the record from the database. You can assign users to more than one role. When a user is assigned to multiple roles, the role with the more restrictive prevails. The Role page is available from the system links, in the top right corner of Sugar. To view available roles




1. Login to Sugar with your administrator login and password 2. Click on the Admin link located at the top right corner.

3. In the Users sub tab screen, click the Role Management link and the Roles page appears. 4. Click List Roles to view the complete list.

5.1.1 Maintaining Role in sugarCRM

1. Click Create Role to add new role in Sugarcrm. 2. Enter the appropriate values in the required fields. 3. To add a new role to the database, click Save.




5.1.2 Maintaining User and Change the privileges for the Role

In the Roles screen, you can manage and change privileges given to a user. Click the Role Name and Change the privileges based on the module (Access, Delete, View, Edit, Export, and Import.)

Click to change the privilages for Inidiviual Users Roles.

Add the Users as per the Role.

Select User to add to specific Role.

Click on Role to add Module Privileges




5.2 Clinician users

Clinician User Management allows you to create, edit, activate, and deactivate users in Sugar and Clini-cian login.


id char(36) Clinician Unique ID

user_ name varchar(60) Unique User Name

user_hash varchar(255) Clinician Password

first_name varchar(30) First Name

last_name varchar(30) Last Name

Email_address varchar(30) Email Address

description text About User

status varchar(100) Active, De-active

cls_organizational_units_id_c char(36) Organization ID

user_role_c varchar(100) User Role

user_logincount_c varchar(100) Login Count

Clinician_id_c text

Unique ID for clinician,

for example, National Provider Identifier, CPSO license

To create new user, go to User Management on Admin page, and click “Create New User”.

5.2.1 Maintaining User in sugarCRM

User Management allows you to create, edit, activate, and deactivate users in Sugar and Clinician login.

Create New User




5.2.2 Import Users through CSV file

Check create new records only and click Next.

Confirm import file and properties:

Enter the User Name

Enter the Last Name

Enter the Password

Click Import Users.

Click Browse to import the csv file.

Enter email address




Confirm Field Mappings

Map the module field with CSV file field.

Click next to import the data.

5.2.3 Teams and coordinators

The users can be assigned into teams, which can be created manually by the administrator. An organiza-tion can contain several teams, and teams can contain several users. To create and assign team:

Go to All tab

Select Teams

Click “Create Teams”

Fill out Name (and other fields if desired)

Click Save




The users can now be assigned to the team in User Management by selecting the team. Coordinator

A user can be assigned the role as Team Coordinator. This allows them to assign tasks and activities between teams in CC360. A team can have more than one coordinator. To make a user a Team Coordinator, select Yes in the Team Coordinator field in User Management.

5.3 Citizen users


id char(36) Citizen Unique ID

name varchar(255) Unique User Name

password varchar(255) Citizen Password

first_name varchar(255) First Name

last_name varchar(255) Last Name

national_unique_id varchar(255) National Unique ID

national_unique_id2_c varchar(255) National Unique ID 2

status varchar(100) Active, De-active

phone_number varchar(255) Phone Number

email_address varchar(255) Email Address

postal_address varchar(255) Postal Address

zip_code varchar(255) Zip Code

city varchar(255) City

guardian_name varchar(255) Guardian Name





guardian_phone varchar(255) Guardian Phone

guardian_address varchar(255) Guardian Address

cls_countries_id_c char(36) Country List

cls_municipalities_id_c char(36) Municipality List

cls_regions_id_c char(36) Regions List

cls_organizational_units_id_c char(36) Org Unit List

skype_id_c varchar(255) Skype ID

ctz_login_count_c ctz_login_count_c

test_c test_c

clinicianlist_c clinicianlist_c

citizenlist_c citizenlist_c

national_unique_id2_c national_unique_id2_c

dateofbirth_c dateofbirth_c

sendalarm_c sendalarm_c

gender_c gender_c

Citizen users are used to login to the Citizen Web portal. http://crm.ehealthbox.dk.logica.com/CitizenClient/citizenclient.html?locale=en Citizen User Management allows you to create, edit, and view users in SugarCRM

View Citizen List

http://crm.ehealthbox.dk.logica.com/CitizenClient/citizenclient.html?locale=en




5.3.1 Maintaining Citizen User in sugarCRM

To add a new citizen

1. Click on the Create Patient link.

2. Enter the appropriate data in the required fields. For example User Name (Unique User Name), Password, First Name, Last Name, National Unique ID, Status, and so on.

3. To create the Citizen User in database (DB), click Save.

A new citizen user has been added to the database successfully. 5.3.2 Citizen User Validation rules

User Name: The Username is a unique and mandatory field.

Password: The Password is a mandatory field.

First Name: The First name is a mandatory field

Last Name: The Last Name is a mandatory field

National Unique ID: The National Unique ID is a mandatory field, eg CPR number or Social Se-curity Number

Status: By default, the status is set as Active for all users. 5.3.3 Import Citizen Users through CSV file

You can import users through CSV files used during migration and bulk update.

Enter the User Name

Create Patient

Enter a Password




Select Create new records only option button and click Next.


Click Import Patients





Confirm Field Mappings:

Map the module field with CSV file field. Click next to import the data.

6. Classification

6.1 Country classification


id char(36) Unique Database ID

name varchar(255) Country Name

code varchar(255) Unique Country Code

valid_from date Valid From Date

valid_to date Valid To Date




Country Code, Country Name is used throughout the application. The list of country and code is imported through CSV files.

6.1.1 Maintaining Country in sugarCRM

6.1.2 Validation rules

Code: The code is a mandatory field.

Name: The name is a mandatory field. 6.1.3 Import Country using CC360 format

Three Step to import the Country Data :

1. Upload import file (countrycode.csv) 2. Confirm import file Properties. 3. Confirm Field Mapping

Country Code Country Name

Valid From Date

Valid To Date

Click Countries

Create Countries




Select to upload the file (csv)

View import Properties

Select Import




6.2 Region classification



name varchar(255) Region Name

code varchar(255) Unique Region Code



6.2.1 Maintaining Region in sugarCRM

Create Region

Region Code

Region Name

Valid From Date Valid To Date

View Region





Code: The Code is a mandatory field.

Name : The Name is a mandatory field. 6.2.3 Import using CC360 format

Follow the import method from CSV .

6.3 Municipality classification



name varchar(255) Municipality Name

code varchar(255) Unique Municipality Code



6.3.1 Maintaining in sugarCRM

Select Municipalities

Create Municipality

Municipality Code Municipality Name

Valid From Date Valid To Date






Name: The Name is a mandatory field. 6.3.3 Import using CC360 format

Follow the import method from CSV.

6.4 Diagnosis classification



name varchar(255) Diagnosis Name

code varchar(255) Unique Diagnosis Code

producer varchar(100) Producer

diagnosis_type_c varchar(100) Type



List Diagnosis




6.4.1 Maintaining Diagnosis in sugarCRM



Name: The Name is a mandatory field 6.4.3 Import using CC360 format


6.5 Result codes classification



name varchar(255) Result Code Name

code varchar(255) Unique Result Code

unit varchar(255) Unit Name



Create Diagnosis

Diagnosis Code

Diagnosis Name

Valid From Date

Valid To Date




6.5.1 Maintaining Result Code in sugarCRM



Name: The Name is a mandatory field.

Unit: The Unit is a mandatory field. 6.5.3 Import using CC360 format


List Result Codes

Create Result Code

Result Code Name Result Code

Valid To Date

Valid From Date

Select Result Codes




6.6 Organizational unit code classification


id char(36) Unique ID

name varchar(255) Org Unit Name

code varchar(255) Org Unit Code

ean_location_number varchar(255) EAN Number

postal_address varchar(255) Org Address


city varchar(255) Org City

phone_number varchar(255) Org Phone Number

ydernr varchar(255) Ydernr Code

sks_code varchar(255) SKS Code



Select Organizational Units




6.6.1 Maintaining Organization Unit in sugarCRM



Name: The Name is a mandatory field 6.6.3 Import using CC360 format


6.7 Citizen Organizational Unit


Patient_unique_id Text ID for patient for the organi-zation Unit (e.g. hospital)

date_entered datetime date_entered

date_modified datetime date_modified

modified_user_id char(36) modified_user_id

created_by char(36) created_by

deleted tinyint(1) deleted

ctzn_citizen_cou_citizen_organizational_unit char(36) Organizational Unit

Org Unit Code Org Unit Name

Valid From Date

Valid To Date






Patient Unique ID: a mandatory field. 6.7.3 Import using CC360 format





6.8 Allergies

The allergies are based on the ICD-10 classifications. To add an allergy to the list:

- Click “Create CC360_Allergy” To edit an existing allergy:

- Click the Edit button


Code: The Code is a mandatory field

Allergen: The Name is a mandatory field

Type: The Type is a mandatory field




7. Templates

7.1 Template Plans



name varchar(255) Org Unit Name

code varchar(255) Org Unit Code

ean_location_number varchar(255) EAN Number

postal_address varchar(255) Org Address


city varchar(255) Org City

phone_number varchar(255) Org Phone Number

ydernr varchar(255) Ydernr Code

sks_code varchar(255) SKS Code











7.2 Template Activities





The following new fields are added to the Template Activity: 1. Notify responsible 2. Instruction to Clinician To create a dependency for an activity:

- Click on the arrow in the “Depend on”-field - Select an activity to create a dependency



Name: The Name is a mandatory field 7.2.3 Activity type

Activity type Description Special effect

Appointment A physical meeting like a patient-doctor consultation

None

Measurement A measurement activity, like a heart rate reading

Possibility to add Measurement data directly from the Patients Overview / Calendar

Empowerment An empowerment activity like exercise Possibility for the patient to check if this empowerment activity has been com-pleted

Other Anything else None




7.2.4 Import using CC360 format


7.3 Template Questionnaires



name varchar(255) questionnaire name





description text description


assigned_user_id char(36) assigned_user_id

questionnaire_id int(255) questionnaire_id






Questionnaire ID: The Questionnaire is a mandatory field. Name: The Name is a mandatory field 7.3.3 Import using CC360 format


7.4 Template Question


id char(36) id

name varchar(255) Question name








question_id int(255) question_id






Question ID: The Question Id is a mandatory field.

Question Name: The Name is a mandatory field 7.4.3 Import using CC360 format


7.5 Template Answer Group


id char(36) id

name varchar(255) Answer Group












answrer_group_id int(255) answer_group_id



Answer Group ID: The Answer Group Id is a mandatory field.

Answer Group Name: The Answer Group Name is a mandatory field 7.5.3 Import using CC360 format





7.6 Template Answer


id char(36) id

name varchar(255) Answer name








answer_id int(255) answer_id

ta_template_answer_alert_id_c char(36) ta_template_answer_alert_id_c






Answer ID: The Answer Id is a mandatory field.

Answer Name: The Answer Name is a mandatory field 7.6.3 Import using CC360 format


7.7 Template Answer Alert


id char(36) id

name varchar(255) name








answer_alert_id int(255) answer_alert_id

answer_diagnosis varchar(100) answer_diagnosis

answer_alert_color varchar(100) answer_alert_color






Answer Alert ID: The Answer Alert Id is a mandatory field. Answer Alert Name: Answer Alert Name is a mandatory field 7.7.3 Import using CC360 format


7.8 Template Check List Items


id char(36) id









check_list_id int(255) check_list_id






Check List ID: The Checklist ID is a mandatory field.






7.9 Template Continuity


id char(36) Unique DB Id









rel_to_date_value int(255) rel_to_date_value

rel_to_date_unit varchar(100) rel_to_date_unit

rel_from_date_value int(255) rel_from_date_value

rel_from_date_unit varchar(100) rel_from_date_unit

frequency_value int(255) frequency_value

frequency_unit varchar(100) frequency_unit






Name: The Name is a mandatory field

Continuity ID : The Continuity ID is a mandatory field 7.9.3 Import using CC360 format


7.10 Template Allowed Results











allowed_result_id int(255) allowed_result_id

fixed_value_c float Sets a fixed reference value

set_measurement_c tinyint Sets first measurement as ref-erence value






Result Code: The Result Code is a mandatory field.



8. State algorithm











diagnosis_type varchar(100) diagnosis_type




8.1 Maintaining in SugarCRM

8.2 Validation rules


Name: The Name is a mandatory field.

8.3 Import using CC360 format


8.4 Calculation Logic

2.16.4.1 Information used by state color calculation logic Algorithm uses two sets of information to calculate state color

1. STATE_MATRIX ,EVALUATION_TIME_INTERVAL, VALIDATION_TIME_FOR_RED, VALIDA-

TION_TIME_FOR_YELLOW -all details fetched from sugarcrm

2. actual results records (created through Clinicianweb, citizenweb,Tablet)




2.16.4.2 Terms

1. VALIDATION_TIME

a. VALIDATION_TIME_FOR_RED - minutes that must pass before last actual result was received - if it exceeds this

number the state will go into RED

b. VALIDATION_TIME_FOR_YELLOW - minutes that must pass before last actual result was received - if it exceeds

this number the state will go into YELLOW

2. EVALUATION_TIME_INTERVAL - used if multiple actual result records are used in state calculation

3. VALIDATION_TIME_FOR_RED, VALIDATION_TIME_FOR_YELLOW , EVALUATION_TIME_INTERVAL values should be

set in minutes

2.16.4.3 Calculation Logic

1. State color calculation logic creates/updates state color records only if there exist any actual result for the citizen

2. State color calculation logic creates new state color record only if there exist no state color record meeting criteria

STATE_COLOR.RESULT_DATE=(ACTUAL_RESULT.MODIFIED_DATE of latest actual result)

3. State color calculation logic updates existing start color record if there exist a state color record meeting criteria

STATE_COLOR.RESULT_DATE=(ACTUAL_RESULT.MODIFIED_DATE of latest actual result)

4. State color calculation is triggered whenever one of these events happen

a. batch process started

b. reference value of allowed result through „clinicianweb->data&goals „is created or updated

c. actual results is created,or updated through i)clinicianweb,or ii)citizenweb,or iii)devices connected to android app/iOS

application,or iv)addResults SOAP service,v)corresponding REST resource

5. but delete operation of actual result would involve two actions

I. If there exist a state color record meeting criteria

STATE_COLOR.RESULT_DATE=(ACTUAL_RESULT.MODIFIED_DATE of latest actual result),delete this record

II. Invoke state color calculation

6. State indicator comment pop-up(displayed in citizenweb) picks up the latest record from STATE_COLOR based on CREAT-

ED_DATE,and not RESULT_DATE

7. State graph(clinicianweb->citizenOverview) would have RESULT_DATE values as x-axis

2.16.4.4 Examples

http://ws3.global.logica.com/sites/021078/CC360/eHBv3%20-%20SugarCRM/Design%20specification/

9. System settings



name varchar(255) Name

namespace varchar(255) Name Space

namespace_key varchar(255) Namespace Key

namespace_value varchar(255) Namespace Value

http://ws3.global.logica.com/sites/021078/CC360/Archive/eHBv3%20-%20Final/Design%20specification




9.1 Maintaining in sugarCRM

9.2 Validation rules

Namespace: The Name Space is a mandatory field.

Namespace Key: The Name space key is a mandatory field.

Namespace Value: The Name space Value is a mandatory field.




9.3 Configuration options

Namespace Namespace key Namespace value

about address Lautruphoej 10, DK-2750 Ballerup, Denmark

citizen.calendar.appointments appointment.rescheduling yes

about ce Class I Medical device,No registration number is given for Class I devices(Annex VII of the Medical Devices Directive 93/42/EEC)

global.environment.properties citizenlogin.password.minLength 6

global.environment.properties citizenlogin.password.onelower FALSE

global.environment.properties citizenlogin.password.onenumber FALSE

global.environment.properties citizenlogin.password.oneupper FALSE

global.environment.properties citizenlogin.username.minLength 6

about citizenManualLink /doc/CC360HC_Citizen_User_Manual.pdf

global.environment.properties citizenweb.tabs

resultgoals.visible=true;diary.visible=true; questionnaires.visible=true;instructions.visible=true; calendar.visible=true;medications.visible=true; socialnetwork.visible=true;contacts.visible=true

ehealthbox.webservice.securekey.properties clinician.password.ignore TRUE

about clinicianManualLink /doc/CC360HC_Clinician_User_Manual.pdf

global.environment.properties clinicianweb.tabs

treatmentplan.visible=true;calendar.visible=true; resultgoals.visible=true;medications.visible=true; questionnaires.visible=true;instructions.visible=true; notes.visible=true;links.visible=true

about company © CGI Danmark A/S

citizenweb.networkui.datalimit.dairynotes.properties datalimit.dairynotes 10

citizenweb.networkui.datalimit.events.properties datalimit.events 10




citizenweb.networkui.datalimit.medicine.properties datalimit.medicine 10

citizenweb.networkui.datalimit.results.properties datalimit.results 10

global.datagoals.datalimit.properties datalimit.results.count 20

global.timeline.default.startwindow.properties days.abeforday.present.time 30

global.questionnaire.default.endwindow.properties days.ahead.present.time 20

global.timeline.default.endwindow.properties days.aheaday.present.time 90

global.questionnaire.default.startwindow.properties days.before.present.time 10

citizenweb.networkui.datalimit.events.properties days.interval.ahead 20

citizenweb.networkui.datalimit.events.properties days.interval.behind 5

global.environment.properties debug TRUE

global.statecolor.notification.clinician distribution.email.send FALSE

global.environment.properties dropdown.editor.filepath /opt/sugarcrm-6.5.5/apps/sugarcrm/htdocs/custom /include/language/en_us.lang.php

ehealthbox.webservice.securekey.properties ehealthbox.webservice.securekey securekey

global.environment.properties email.notification.list [email protected]

global.environment.properties enable.email.notification TRUE

about fda Class I Medical Device ,Operator Number 10048035(21 Code of federal Regulations Parts 800)

finland.webservice.endpoint finland.webservice.endpoint.customer https://mob3.mobilog.info/mobilogapicc360/ws/

finland.webservice.endpoint finland.webservice.endpoint.site https://mob3.mobilog.info/mobilogapicc360/ws/

finland.webservice.endpoint finland.webservice.endpoint.workorder https://mob3.mobilog.info/mobilogapicc360/ws/

finland.webservice.endpoint finland.webservice.endpoint.workorderexport https://mob3.mobilog.info/mobilogapicc360/ws/

global.environment.properties global.clientname.text CGI DEV

global.environment.installation.properties global.personnumber.age.algorithm DK

citizenweb.incorrect.login.properties incorrect.login.attempts 5

clinicianweb.incorrect.login.properties incorrect.login.attempts 5

about license Class I Medical Device ,MDEL # 6334(Medical Devices Regulations SOR/98-282)




clinicianweb.automatic.logout.properties minutes.to.automatic.logout 15

citizenweb.automatic.logout.properties minutes.to.automatic.logout 15

about name CGI CommunityCare360-HealthCenter(CC360-HC)

citizen.info nationalUniqueIdentifier.number.1.mask FALSE

citizen.info nationalUniqueIdentifier.number.1.mask.firstchars 4

citizen.info nationalUniqueIdentifier.number.1.mask.lastchars 4




citizen.info nationalUniqueIdentifier.number.3.mask TRUE






citizen.info nationalUniqueIdentifier.number.ssn 1

citizen.info nationalUniqueIdentifier.number.use 1

global.environment.properties nationalUniqueIdentifier.ssn.mask TRUE

global.environment.properties nationalUniqueIdentifier.ssn.mask.firstdigits FALSE

global.environment.properties nationalUniqueIdentifier.ssn.mask.lastdigits FALSE

global.environment.properties nationalUniqueIdentifier.ssn.regex ^(?!000|666)[0-8][0-9]{2}-(?!00)[0-9]{2}-(?!0000)[0-9]{4}$

global.environment.properties newresponsible.emailbody You are now responsible for activity

global.environment.properties newresponsible.emailsubject HealthCenter new responsible

whiteboard.page.limit page.limit 10

clinician.web.find.citizen.page.limit page.limit 20

about phoneneo +45 44784000

about representative Michael Zakarias




citizenweb.timer.properties seconds.to.checksession 10

clinicianweb.timer.properties seconds.to.checksession 10

citizenweb.timer.properties seconds.to.refresh 5

clinicianweb.timer.properties seconds.to.refresh 5

whiteboard.timer.property seconds.to.refresh 10

global.webservice.securekey.properties security.phrase eHealthbox_Access_Granted_2_All_WebServices

global.skype.callcenter.user.properties skype.username cc360hc.test

global.environment.properties sugar.config.override.settings /opt/sugarcrm-6.5.5/apps/sugarcrm/htdocs/config_override.php

global.environment.properties sugar.home /opt/sugarcrm-6.5.5/apps/sugarcrm

about title About CC360 HC

about version CGI eHB v3.6 -rev 6501- Nov 06-2015

finland.webservice.endpoint wfc.citizenexport.enabled TRUE

global.ws.integration wfc.workorder.offset 60

finland.webservice.endpoint wfc.workorderexport.durationminutes 60

finland.webservice.endpoint wfc.workorderexport.enabled TRUE

finland.webservice.endpoint wfc.workorderexport.organizationid eHealthbox

finland.webservice.endpoint wfc.workorderexport.sendtomobile TRUE

finland.webservice.endpoint wfc.workorderexport.teamworktype NOT_TEAMWORK

finland.webservice.endpoint wfc.workorderexport.workorderpriority P3

finland.webservice.endpoint wfc.workorderexport.workordertype.default Health Center

global.environment.properties wfc.workorderalarm.durationminutes 60

global.environment.properties wfc.workorderalarm.enabled FALSE

finland.webservice.endpoint wfc.workorderalarm.organizationid eHealthbox

finland.webservice.endpoint wfc.workorderalarm.sendtomobile TRUE

finland.webservice.endpoint wfc.workorderalarm.teamworktype NOT_TEAMWORK

finland.webservice.endpoint wfc.workorderalarm.workordertype HEALTHCENTER




9.4 CC360 csv import format

A description of T161-00107-13_eHBv3_Temp_Health_Effort_import.xlsx

9.4.1 Import Citizen Users through CSV file

Import users through CSV files used during migration and bulk update.

Click Import Patients




Select create new records only option button and click Next.






Confirm Field Mappings:

Map the module field with CSV file field. Click next to import the data.

9.5 Citizen important info

9.6 Maintaining in sugarCRM





Type: The Type is a mandatory field.

Status : The Status is a mandatory field 9.6.2 Import using CC360 format


9.7 Circle of Care


Type: The Type is a mandatory field.

Name: The Name is a mandatory field




9.7.2 Import using CC360 format


9.8 Primary Care Physician/GP


Type: The Type is a mandatory field. 9.8.2 Import using CC360 format


9.9 Other Info / Notes





None. 9.9.2 Import using CC360 format





10. Logging

http://hc.communitycare360.com:8090/pentaho/

10.1 Access log reports

Access Log reports provide the complete login details of the Citizen and Clinician. 10.1.1 Maintaining in Pentaho BI

http://hc.communitycare360.com:8090/pentaho/ 10.1.2 Citizen Access Log

Citizen Access log provides login details for citizen user based on the date and Name Criteria.

10.1.3 Clinician Access Log

Clinician Access log provides login details for clinician user based on the date and Name Criteria.






10.2 Transaction log reports

Transaction Log reports provide the complete transaction details like add, edit, view, delete of the Citizen and Clinician. 10.2.1 Maintaining in Pentaho BI

http://hc.communitycare360.com:8090/pentaho/ 10.2.2 Citizen Transaction Log





10.2.3 Clinician Transaction Log

10.3 User activity reports

User activity Report provide the complete Active / Inactive user information and user Login information 10.3.1 Maintaining in Pentaho BI

http://hc.communitycare360.com:8090/pentaho/ 10.3.2 User Summary Report





10.3.3 User Activity Report

11. SMTP Settings (email Settings)

11.1 SMTP Settings




Click Admin -> Select Email Settings.

1. Update the SMTP Server and Port. 2. Update the From Name and From Address. 3. Save and Test email.




12. Procedures

12.1 Change unit for existing measurement type

1. Create a new measurement type. Never change an existing measurement type to have a different unit. 2. Name the second measurement type so that it can be recognized and separated from the existing one Like weight (kilo) 3. Check the values are in correspondence with the reference value. 4. Remember to change the state algorithm in case the measurement type should be part of State algo-rithm. For example, if Weight (kilo) needs to be part of the state algorithm. Review the algorithm as a whole in administration module.

12.2 Enable/ Disable modules




12.3 Setting Decimal points for measurement types

13. Troubleshooting

Problem Possible Cause Solution (Action required)

The admin SugarCRM URL http://195.110.17.183:8080/sugarcrm/ is not accessible, getting an error „Page cannot be displayed‟.

May be SugarCRM service is stopped in server.

Go to SSH and connect to Linux serv-er 1. Provide the IP address 2. User name / Password 3. Start the service

The admin SugarCRM URL:http://195.110.17.183:8080/sugarcrm/ is accessible but not able to login to the Admin panel.

May be the mysql server has

been stopped in the server

Or No disk space on the

server on the MySQL folder

Go to SSH and connect to Linux server

1. Provide the IP address 2. User name / Password 3. df command

4. Delete the temp files 5. Start the service 6. Service SugarCRM start

http://195.110.17.183:8080/sugarcrm/

http://195.110.17.183:8080/sugarcrm/

http://195.110.17.183:8080/sugarcrm/

http://195.110.17.183:8080/sugarcrm/




Problem Possible Cause Solution (Action required)

Not able access jboss server

(Citizen web, Clinician

Web)

http://195.110.17.183/

http://195.110.17.183/Citizen

Cli-

ent/citizenclient.html?locale=

en

http://195.110.17.183/Clinicia

nCli-

ent/clinicianclient.html

?locale=en

May be the jboss server is stopped in server


1. Provide the IP address

2. User name / Password

3. Delete the jboss temp files

4. Start the service

5. Start service jboss7

The Admin Application is

logout if not used for a few

minutes

URLhttp://195.110.17.183:80

80/sugarcrm/

The feature of the application is like that it will logout after 15 min because of security reason

Login again with valid credential.

Sometimes the admin Pen-

thao BI Server URL

http://195.110.17.183:8090/p

entaho/ is not accessible.

For example, Page can‟t be displayed.

May be the Pentaho server

is stopped in the server




3. Start the service

4. Service pentaho start

File Upload is not Working

on the SugarCRM import

functionality.

Sometimes file upload will

fail due to folder permission

or upload max size




3. Choose the folder and use the

following command

4. chmod –R 777 Folder name

http://195.110.17.183/

http://195.110.17.183/CitizenClient/citizenclient.html?locale=en




http://195.110.17.183/ClinicianClient/clinicianclient.html?locale=en




http://195.110.17.183:8080/sugarcrm/

http://195.110.17.183:8080/sugarcrm/

http://195.110.17.183:8090/pentaho/

http://195.110.17.183:8090/pentaho/

cc360 healthcenter administrator user manual · 12.2 enable/ disable modules ... in the users...

Documents