The Help You Need
When You Need It

• The Holon app, which is installed on every workstation that will need the ability to show notifications.
• The Holon sensor, which enables the interaction of the Holon app with the EHR. The specific sensor type to deploy is determined by the Holon engineer and is matched to the specific EHR’s technology in place. In many scenarios, the sensor is either included in the application packaging, or is loaded as a Chrome extension where applicable. Some less common scenarios require a sensor called the Lightweight Sensor (LWS), which is installed as a service on a server.

When the practice utilizes an EHR that requires an LWS, it must be installed on a server within the practice. Machine specifications will be provided by the project manager or account executive. Holon will ask that IT download and install the LWS. Holon resources can then collaborate with onsite IT and complete the LWS configuration.

Holon sensors may require tuning or adaptation, as EHR implementation or practice infrastructure can vary greatly. The practice’s IT resource(s) should expect requests to:

• Create a Windows user ID for the Holon engineer and grant it local admin rights on the sensor server (if an LWS is needed). If policy restricts this, Holon can work with IT over screensharing technology.
• Provide access to a copy of the EHR’s client application for testing and validation. This should include an ability to log in, read-only is preferred (no chart edit rights). It is used in testing and (in rare cases) ongoing operations.
• Create a read-only account in the EHR’s database engine, given the LWS sensor is required. 

The Holon implementation team will remotely install/configure our sensors as described above and will support installing the Insights app on a few workstations as training for local resources to deploy to all desired workstations.

The Holon installation package offers an option to install for “all users” on a workstation or just the “current user”. An “all users” installation requires administrative rights. While the “current user” option does not require admin rights for Holon software, if the workstation does not have Microsoft VC++ redistributable already installed, the installer wizard can install it, and that activity does require admin rights.

This is supported, but in rare cases may be limited by functionality inherent in the EHR design itself. The sensing of context within the EHR depends on a clear identification of the clinical user and the workstation they are signed in from in the EHR so that notifications and gap notifications can be triggered for the correct Holon user. We recommend that the practice review common user workflow and work processes (sharing, concurrent use, etc.) with the project team prior to the technical installation phase.

• Training for local IT or office staff for product use and deployment is provided.
• If escalation is required or local administrative resources are not available, a support contact will be provided. Holon is often sponsored by a third-party or health system, and support contacts and escalation procedures are determined by the project team prior to start of the project.

There is no charge to the practice.

Macs are not supported.

The Holon app will install so that it will auto-start. In addition, it has a “Keep me signed in” setting to save user ID and password after first login. Once that is enabled, the workstation may be rebooted, be put into sleep mode, or be shut down, and once back up, the Holon app will auto-start and sign you in automatically.

Yes, all Holon software communication is encrypted to standards required by HIPAA.

Holon will communicate to sponsors when releases are available. The update may be downloadable from the website.

No. The Holon app does not persist any clinical data or PHI when not running. Data objects that may contain PHI or other clinical information are held in memory (and shown onscreen as needed) only while the application is running.

The sponsoring organization (e.g. the ACO, MSO, payer, etc.) enables the connections to the data sources (proprietary databases, population health management vendors, etc.) that provides all insights presented in the Holon app. Holon does not generate this information in any way.

Please contact your sponsoring organization.

Chart content, actions or clinical activities that pertain to closing a gap are captured by systems and processes outside of Holon app and then incorporated by the data analytics provider. As those processes occur, the analytics solution will correlate such activities to the related gap(s). Holon then will be able to show updates (or simply not show open gaps) as applicable.

Notifications will not occur if there are no insights to show. Otherwise, notification of content will occur each visit to the chart.

In addition, the navigation bar will indicate a red dot over the patient care icon.

If there is information to show, but not appropriate for the task at hand, the user may use the Mute Notifications feature to temporarily turn off notifications. The user may select the Mute duration by clicking on the Mute Notifications button in the navigation bar. The available durations are determined by your sponsor admin.

No. All notifications are managed on a per EHR user basis. Related in part to the FAQ entry on sharing workstations, if sharing of a workstation is part of the office workflow, it will be managed on a per machine basis.