Root - These are fields that come directly from the data source. All of these fields are available in Data Warehouse Connector.

Custom Calculations - These are calculations that were built in Tableau for the purpose of standard content usage. These could be fields for filtering, coloring thresholds, or extrapolating specific data from a field.

System Calculations - These are fields in the database that are used for data processing and monitoring. They are not intended for client reporting.

A historical view of Discharge Milestones recorded, the times they are marked as delayed or completed, and any notes associated with them.

Each row in this data set represents an individual discharge milestone for a patient record. This data source has a latency of 3 hours.

Root - These are fields that come directly from the data source. All of them are available in the Data Warehouse Connector.

System Calculations - These are fields in the database that are used for data processing and monitoring. They are not intended for client reporting.

IQ Behavioral Health is a Standard Lane data source that contains historical details about behavioral health assessments recorded in TransferCenter IQ. Each row in this data set represents a single assessment in a Transfer Center Case.

A transfer center case may have more than one assessment associated with it. This data source has a latency of 45-90 minutes.

The IQ Case Physician Communication Detail data source contains the detailed events occurring in physician communications in each transfer center case. Each of the events in the communications history will be a unique row in this data set, including the times contacted, the times when the call is returned, the times conferenced, and the times when any disposition is set on the communication record.

Previously, our existing "IQ_Case Physician Communication" data source contained one entry per physician communication card. This existing data source contained the latest updates on the communication disposition but did not have the historical timestamps for each update to the communication card.

The new data source includes each entry made into the physician communication history.

In the example communication card below, there would have only been one record in the "IQ_Case Physician Communication" data source. In the new data source, "IQ_CASE_Physician_Communication_Detail_teletracking," there is a row for each communication event.

The Location Action Status data source contains bed location and status level information from Capacity Management Suite. The granularity of this data source is at the Action Status Level for a given location – meaning each row represents a different action for a bed.

There are different types of action status that show occupancy, cleanliness, and availability.

Each action status change comes with an associated timestamp for when that action began and when it was completed.

Patient level information is also available for Occupied actions. There is a fast lane version of this data source named Current Location Action Status, and a standard lane version named Location Action Status that contains all historical bed location data.

For example, the image below shows the Actions on a two bed location for two days. Each action has a Status Start Timestamp (when the action began) and a Status End Timestamp (when the status was removed). In the cases where there are 2 rows for an action (Dirty and Pending), both of those actions were started and completed at the same time.

The following image provides a visual example of the actions for a given location:

In this example, Bed 1 was occupied from Midnight until 4 PM, then it was set to a status of Pending/Dirty for about an hour. Then, the action status was briefly changed to action statuses of In Progress and Complete before being Clean for about 5 hours.

In the Blocked Beds standard content, users can see the currently blocked beds by looking at any location that has an Action of “Blocked” and a Status End Timestamp of “Null”. This means that the action has been set to “Blocked”, but that action has not been removed.

This same logic can be used to create a list of currently occupied patients. Any patient that has an Action of “Occupied” and a Status End Timestamp of “Null” are currently occupying a bed in the health system.