CritView ^® Connect

Implementation

Designed for flexibility, CritView Connect integrates with its host system in the way that best suits the technology and work flow of the host organization. In one configuration possibility, CritView Connect can be launched from a link or an icon embedded in the host system user-interface and it can return review results via XML directly into the host database. Data transfer can be accomplished in a variety of formats including XML, URL parameters, and plain text.

Depending on the needs of your organization the host computer system and CritView Connect can be integrated as tightly or as loosely as needed. The closeness of integration is controlled by the way that review information is returned to the host.

• Seamless integration: CritView Connect sends review results to the host and stores them directly in the host database. Review information is combined with existing treatment information and can be accessed using third party reporting tools.
• Loose integration: CritView Connect sends review results to the host to be stored in a single database field. Results are sent in plain text or similar format. System users can use review information as a reference but reporting to expose review trends can only be done on the CritView Connect database, not the host database. Reporting requires third-party tools.

Database Storage

CritView Connect uses an Oracle database to store all information received from the host system and all information generated by the review process. The stored information provides benefits including the following:

• Users can save incomplete reviews and complete them later (for example, when additional information is needed).
• Administrators can change completed reviews if necessary.
• Reviews can be referred to physician adviser and performed as allowed by the physician advisor's schedule.
• Administrators can run reports based on criteria, reasons, delays and qualities using third-party tools.

The database stores only the following:

• The minimum information required to identify patients
• Review details

The database does not store information about patients or treatment such as length of stay, attending physicians, insurance, or location. All information that is stored is encrypted to secure patient privacy.