Pericardial friction rub

A pericardial friction rub, also pericardial rub, is an audible medical sign used in the diagnosis of pericarditis.[1] Upon auscultation, this sign is an extra heart sound of to-and-fro character, typically with three components, ONE systolic and TWO diastolic. It resembles the sound of squeaky leather and often is described as grating, scratching, or rasping. The sound seems very close to the ear and may seem louder than or may even mask the other heart sounds. The sound usually is best heard between the apex and sternum but may be widespread.

Cause

The pericardium is a double-walled sac around the heart. The inner and outer (visceral and parietal, respectively) layers are normally lubricated by a small amount of pericardial fluid, but the inflammation of pericardium causes the walls to rub against each other with audible friction. In children, rheumatic fever is often the cause of pericardial friction rub. Pericardial friction rubs can also be heard in pericarditis that is associated with uremia or post-myocardial infarction.

Differential diagnosis

Pericardial friction rub is one of several, similar sounds. A differential diagnosis may be possible, or not, depending upon the number of components that are audible. Pericardial friction rub may have one, two, or three audible components, whereas the similar pleural friction rub ordinarily has two audible components. One- and two-component rubs are ambiguous. A three-component rub distinguishes a pericardial rub and indicates the presence of pericarditis. Also, a pleural rub can only be heard during inspiration , whereas, the pericardial rub can be heard even after cessation of breathing. Pleural rub creates pain mostly on the lateral part of the chest wall, whereas pain due to pericardial rub is always central in location. The intensity of pleural rub is increased on pressing the diaphragm of the stethoscope over the affected area, whereas there is no such change in case of a pericardial rub.

gollark: VPNs prevent ISPs from seeing all this except possibly to some extent #3, but the VPN provider can still see it, and obviously whatever service you connect to has any information sent to it.
gollark: Anyway, with HTTPS being a thing basically everywhere and DNS over HTTPS existing, ISPs can only see:- unencrypted traffic from programs/services which don't use HTTPS or TLS- the *domains* you visit (*not* pages, and definitely not their contents, just domains) - DNS over HTTPS doesn't prevent this because as far as I know it's still in plaintext in HTTPS requestts- metadata about your connection/packets/whatever- also the IPs you visit, but the domains are arguably more useful anyway
gollark: On my (GNU/)Linux computing devices, which is all of my non-portable ones, I run dnscrypt-proxy, which acts as a local DNS server which runs my queries through DNS over HTTPS/DNS over TLS/DNSCrypt servers.
gollark: In other news, the first rule of tautology club is the first rule of tautology club.
gollark: Yes, Google is definitionally Google.

References
  1. Tingle LE, Molina D, Calvert CW (November 2007). "Acute pericarditis". Am Fam Physician. 76 (10): 1509–14. PMID 18052017.

See also
  • Precordial exam
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.