ComeoCare | Configuring ComeoCare
15296
page-template-default,page,page-id-15296,page-parent,page-child,parent-pageid-15288,do-etfw,ajax_fade,page_not_loaded,,qode-child-theme-ver-1.0.0,qode-theme-ver-2.4,wpb-js-composer js-comp-ver-4.1.2,vc_responsive

Configuring ComeoCare

Users and roles

ComeoCare can run in different authentication modes: stand-alone, linked to an Active Directory or hybrid. Once the user is identified, the rights are then granted based on the group and role definitions in ComeoCare.

Within ComeoCare, groups can be created to ease the user right management. Permissions are always given to a group, never to an individual user.

Learn more

Installation and Support

ComeoCare can be delivered as an installable package or a complete virtual machine. If the hospital chooses to install ComeoCare as a VM, this VM contains both the web server and database. Of course, ComeoCare can also be installed on separate servers: a web server and a database server.

In most cases, ComeoCare is installed in a test environment and a production environment.

When installed, ComeoCare asks for a license key, which gives unlimited access for an unlimited number of computers and users. The license is however limited in time and number of treatment days. A valid license also gives the users acces to the help desk during office hours.

Learn more

Configuration

ComeoCare only comes in one version, but this version is fully configurable to fit each hospital’s specific needs.

The medical options include specific restrictions, validation required or not, warnings… All reporting and printing is also configurable.

Learn more

Integrating ComeoCare

Although ComeoCare can completely run as a stand-alone package, its true strength only comes alive when it is integrated with the other packages in the hospital: the user repository, the patient ADT data, the product definitions, the pharmacy stock management tool, the nursing care package, lab result data… 

ComeoCare contains a complete integration architecture, for both synchronous and asynchronous integration, and for both incoming and outgoing data. This pluggable architecture supports both standard data – HL7 messages – as custom formatted data.

Learn more