Hospital Settings

Modified on Wed, Nov 8, 2023 at 5:32 PM

Welcome to the Hospital Settings page. Hospital Settings are only accessible to Admin-level users, and will always be set up by a Bluesight Implementation Specialist when they onboard you to our amazing product. However, as implied, the Hospital Settings carry great weight in the functionality of your ControlCheck product within your hospital and how your data is calculated and displayed. We want you to have all the necessary information to optimize your experience with ControlCheck and get you the data you need. 

In this file, we will review the options in Hospital Settings that are the most relevant to you and explore how each of these options will impact your data in ControlCheck.

Audit Page Settings

This section defines functionality for workflows involving the Audit Table

Email Event Summary Enabled

This setting enables the permission Email Event Summaries to display and be assigned in Security Roles.

The setting default is enabled.

Default Audit Table Date Range

This setting defines the default number of days that the audit table will display event summaries upon loading. This setting applies to both the Patient Care and Pharmacy Audit tables. 

This setting is defined by you, based on the needs of your hospital. 

Error Resolution Settings

Auto-resolve Documentation Errors

This setting allows event summaries to be automatically closed when there is a drug strength difference but the total amount of medication is accounted for. 

The setting default is enabled.

Example: The Dispense is for Lorazepam 1mg tablet (2mg of medication dispensed), and the Admin is for Lorazepam 2mg tablet(2mg of medication administered). The dispense amount was marked as two tablets at 1mg strength, but the dispense was resolved with one tablet at 2mg strength. Although the Lorazepam 1mg and Lorazepam 2mg are technically two different formulary items, this event summary was marked as closed because the total amount of medication dispensed was equal to the amount administered. 

Auto-resolve PF Documentation Errors

This setting allows event summaries to be automatically closed when there is a preservative-free (PF) medication difference, but the total amount of medication is still accounted for. 

The setting default is enabled. 

Auto-resolve Patient ID Errors

This setting allows event summaries to automatically close when there are more than one patient identifiers for a patient of the same type.

The setting default is enabled. 

Additional Settings

Investigation Portfolios Enabled

This setting enables the ControlCheck Investigations feature for your hospital. 

The default setting is enabled. 

Patches Enabled

This setting allows your hospital to audit patches if they part of your formulary.

The default setting is enabled. 

Event Grouping - Strict Event Type Rule 

This setting controls how far apart two events can be before ControlCheck decides to group them or not, based on event type. This can be set between 0 and 30 minutes. 

This setting is defined by you, based on the needs of your hospital. Our recommendation is 10 minutes. 

Example: The setting is 10 minutes. Let's say a user dispenses a 10mg oxycodone tablet at 12:05pm and then administers the 10mg, but doesn’t chart the admin. Later, the user goes back and back charts to say they gave the med at 12pm. ControlCheck will auto-resolve that case because the events correlate with each other, a dispense and admin, and were enacted within the set time limit.

Default Threshold Percent 

This setting can be adjusted for any given medication in a hospital’s formulary. This setting acts as a margin of error for the amount missing before ControlCheck will create a variance. 

The default setting is 0.05 for medications. 

Example: Let’s say a user draws up 50mcg dose of fentanyl in a syringe. They administer the dose but document 49.5 mcg. If the threshold percent for this med is 5% (0.05), then up to 5% of that dose can be missing before ControlCheck will create a variance.

Aggregation Delay 

When a file set is satisfied, this setting dictates the wait time before triggering the aggregation of that set. 

The default setting is 15 minutes. 

Example: Let’s say a hospital requires 1 EMR file and 1 ADC file every day. They also provide another EMR file for the weekdays as a supplemental file for their procedural transactions. The first EMR file was uploaded at 7:00am, the ADC file was uploaded at 7:00am, and the second EMR file was uploaded at 7:10am. With this setting, it delays the files at 7:00am from aggregating prematurely and allows other files to process within that 15-minute timeframe.

Automatically Archive Old Re-opened Event Summaries 

This setting determines what events will automatically archive when a new medication is enabled for auditing. 

The default setting is 90 days. 

Example: If the setting is 90 days, any event within that 90-day period will be shown on the audit table; anything outside of the 90 days will be automatically moved to an Open - Historical status.

Immediate Processing 

This setting requires an EMR and ADC file to be uploaded to ControlCheck prior to processing. If this setting is enabled, when a file is uploaded, it will immediately process, regardless of whether the matching file has been uploaded.

The setting default is disabled.

Adapter Class 

The default setting should be IncludeNursesHospitalAdapter

Patient Identifiers

The Patient Identifiers allowed in ControlCheck are MRN, FIN, Order, and Other. 

The default selection is MRN, FIN, and Order. We do not recommend selecting Other as a patient identifier because it indicates matching on patient name which can have downstream consequences for your data.

Duplicate Events

ControlCheck does not allow duplicate events (two identical lines in a file) to process. However, ControlCheck does have the ability to allow duplicates in either the EMR file, the ADC file, or both, depending on the site.

The default setting is disabled. 

Role - Care Area Mapping 

Every role in ControlCheck is routed by default to the Nursing or the OR module. 

Enable IRIS Dashboard
Admins can enable or disable all care areas in a hospital (OR, Nursing, Pharmacy) with the toggles under each Care Area section. 
  • Ancillary Care - OR 
  • Anesthesiologist - OR 
  • CRNA - OR 
  • Diagnostics Imaging Technician - OR 
  • Licensed Practice Nurse - Nursing 
  • Nurse Practitioner - Nursing 
  • Pharmacist - OR 
  • Pharmacy Technician - OR 
  • Physician - OR 
  • RN - Nursing 
  • Resident - OR 
  • Respiratory Therapist - Nursing 
  • Student - OR

Case Time Out 

This setting determines how far apart (in hours) two events can be for whether they are grouped together or not when there is missing documentation. 

This setting is defined by you, based on the needs of your hospital. We recommend setting the threshold higher for the OR care area because the workflow is longer. 

Recommended defaults:

  • OR - 12
  • Nursing - 4

Example: Let’s say the setting is 4 hours for Nursing. A user dispenses 10mg of Oxycodone at 12pm and never documents an admin, waste, or return. Then, 6 hours later, the user dispenses another 10mg, and again does not document a corresponding admin, waste, or return. The setting of 4 hours will split these events into two variances instead of one. If the setting was 8 hours, for example, then these two dispenses would have ended up on the same variance summary. 

Processing Cutoff (Hours) 

This setting controls how close to midnight ControlCheck will hold events in a pending state for processing, before waiting for the next day’s worth of data to come in. The goal of this setting is to prevent false variances from showing up for cases that have events before and after midnight. 

This setting is defined by you, based on the needs of your hospital. We recommend the following:

  • OR - 4
  • Nursing - 4

Example: A hospital has the setting for Nursing at 4 hours. A user dispenses 10mg of Oxycodone at 11pm and does not administer the medication. At the end of their shift at 7am the next day, they waste the dose. ControlCheck will hold the dispense event in pending until the next day’s events come in and can pair with the dispense and auto-close. In this example, 11pm happens 1 hour before midnight so it falls within the 4 hour setting for processing cutoff. 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article