Hartritmestoornissen-Voorkamerflutter / Hartziekten-Hartritmestoornissen / Patiënten-Hartziekten

Hartritmestoornissen - Voorkamerflutter

Een voorkamerflutter lijkt in vele opzichten op voorkamerfibrillatie maar het ontstaansmechanisme is anders. Flutter ontstaat meestal in de rechtervoorkamer en in plaats van vele chaotische prikkels is er hier sprake van honderden kleine elektrische circuits die de voorkamers prikkelen. Het hartritme is meestal regelmatig in tegenstelling tot bij voorkamerfibrillatie. De symptomen, oorzaken, diagnose en behandeling zijn gelijkaardig aan deze bij voorkamerfibrillatie.

terug naar Hartziekten-Hartritmestoornissen

This website uses cookies

We use cookies to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners who may combine it with other information that you’ve provided to them or that they’ve collected from your use of their services.

Deny Allow selection Allow all

Necessary

Preferences

Statistics

Marketing

Show details

Name	Provider	Purpose	Expiry	Type
rc::a	Google	This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website.	Persistent	HTML
rc::c	Google	This cookie is used to distinguish between humans and bots.	Session	HTML
1.gif	Cookiebot	Used to count the number of sessions to the website, necessary for optimizing CMP product delivery.	Session	Pixel
JSESSIONID	New Relic	Preserves users states across page requests.	Session	HTTP
__cf_bm	Vimeo	This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website.	1 day	HTTP
AWSALBAPP-0	Thinglink	This cookie is used in context with load balancing - This optimizes the response rate between the visitor and the site, by distributing the traffic load on multiple network links or servers.	7 days	HTTP
AWSALBAPP-1	Thinglink	This cookie is used in context with load balancing - This optimizes the response rate between the visitor and the site, by distributing the traffic load on multiple network links or servers.	7 days	HTTP
AWSALBAPP-2	Thinglink	This cookie is used in context with load balancing - This optimizes the response rate between the visitor and the site, by distributing the traffic load on multiple network links or servers.	7 days	HTTP
AWSALBAPP-3	Thinglink	This cookie is used in context with load balancing - This optimizes the response rate between the visitor and the site, by distributing the traffic load on multiple network links or servers.	7 days	HTTP
algoliasearch-client-js	hartcentrumieper.be	Necessary in order to optimize the website's search-bar function. The cookie ensures accurate and fast search results.	Persistent	HTML
CookieConsent	Cookiebot	Stores the user's cookie consent state for the current domain	1 year	HTTP
CraftCookieTest	hartcentrumieper.be/td>	Registers whether the user is logged in. This allows the website owner to make parts of the website inaccessible, based on the user's log-in status.	Session	HTTP
CSRF_TOKEN	hartcentrumieper.be	Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor.	Session	HTTP

Name	Provider	Purpose	Expiry	Type
ypsession	Yumpu	Stores a unique ID string for each chat-box session. This allows the website-support to see previous issues and reconnect with the previous supporter.	30 days	HTTP
yumpu_slc	Yumpu	The cookie determines the preferred language and country-setting of the visitor - This allows the website to show content most relevant to that region and language.	7 days	HTTP

Name	Provider	Purpose	Expiry	Type
collect	Google	Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels.	Session	Pixel
vuid	Vimeo	Collects data on the user's visits to the website, such as which pages have been read.	2 years	HTTP
td	Google	Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.	Session	Pixel
_ga	Google	Registers a unique ID that is used to generate statistical data on how the visitor uses the website.	2 years	HTTP
_ga_#	Google	Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit.	2 years	HTTP
_gat	Google	Used by Google Analytics to throttle request rate	1 day	HTTP
_gid	Google	Registers a unique ID that is used to generate statistical data on how the visitor uses the website.	1 day	HTTP
ypsitetrack	Yumpu	Used to implement blog or article content onto the website from other websites. This implementation also allows the origin-website to track on the website.	1 year	HTTP

Name	Provider	Purpose	Expiry	Type
AVP_UUID	Yumpu	Collects data on user behaviour and interaction in order to optimize the website and make advertisement on the website more relevant.	Persistent	HTML
AVPUID	Advert Serve	Used to identify the visitor across visits and devices. This allows the website to present the visitor with relevant advertisement - The service is provided by third party advertisement hubs, which facilitate real-time bidding for advertisers.	1 year	HTTP
maps/gen_204	Google	Used in context with the website's map integration. The cookie stores user interaction with the map in order to optimize its functionality.	Session	Pixel