Includes Tube Side Quick Switch to connect tube to either side of the patient
Kink-free prongs and flexible, low-noise tube
Humidoflo High Flow Nasal Cannula is compatible with any ventilator with a standard 22mm ISO connector, including Respironics V60
Humidoflo is a suitable alternative to Philips AC611
Humidoflo is comparable to F&P OptiFlow cannula (OPT942, OPT944, OPT946)
With the optional F&P Adapter, Humidoflo High Flow Nasal Cannula is compatible with Airvo II system, 850 High Flow system, and 950 High Flow system
With high flow nasal cannula (also known as HFNC) therapy, patients benefit from warmed, humidified oxygen at a flow rate greater than those seen with conventional oxygen delivery devices, and more than peak inspiratory airflow. High flow nasal cannula treatment is better tolerated due to the heated and humidified air. The Humidoflo High Flow Nasal Cannula delivery device is also smaller and more comfortable on the face than an NIV mask. Patients can continue eating, drinking and talking during treatment, leading to higher compliance. Delivery respiratory gases range from 2 – 60 L/min and oxygen concentrations range from 21 – 100%. The Humidoflo High Flow Nasal Cannula is intended for patients in homes and long-term care facilities and may help prevent intubation.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
SourceBuster is used by WooCommerce for order attribution based on user source.
Name
Description
Duration
sbjs_session
The number of page views in this session and the current page path
30 minutes
sbjs_udata
Information about the visitor’s user agent, such as IP, the browser, and the device type
session
sbjs_first
Traffic origin information for the visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current
Traffic origin information for the visitor’s current visit to your store
session
sbjs_first_add
Timestamp, referring URL, and entry page for your visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current_add
Timestamp, referring URL, and entry page for your visitor’s current visit to your store
session
sbjs_migrations
Technical data to help with migrations between different versions of the tracking feature