Privacy, Workflow and Security

EMHware complies with the PHIPA guidelines ensuring that the privacy rights of the client can be maintained. Privacy is a very important part of EMHware system and different granularities of security is in place to ensure that privacy is met on every level of the system. Through the use of:

• Passwords restrictions are completely configurable to the agencies needs, (example: expiry, length, letters, capitals, numbers and symbols, caching passwords, resetting password and so much more)
• Program privacy can be configured to keep separate each and every program from one another
• Worker privacy can be configured to allow all workers, some workers, or only one worker access to a client record. Worker privacy can also be configured to deny all workers, some workers or only one worker access to a clients file as well, depending on the circumstances. Any worker who is denied access to a client record will not even be able to find the client in the database.

The ability to only allow workers the ability to see the clients that they service is also configurable.

EMHware functionality is enforced using comprehensive role-based security. Roles include permissions capable of controlling every section of the application including sub-components. Permissions can be used to limit/hide access to interfaces and control read/write security conditions in many sections of the application.

MOHLTC Workflow for CDS-MH, MIS, and OCAN

EMHware's usage model is designed to accommodate the workflow required to produce valid CDS-MH, MIS and OCAN reports as defined by the MOHLTC. Data workflow within EMHware is built to make capturing information as simply as possible while maintaining maximum data quality. Application-level workflow enforcement is essential to ensuring the system is used by the proper people in the correct way. EMHware includes built-in validation to ensure data quality is not compromised during regular application use.