#OTD 1901, Queen Victoria's funeral took place. Here's a little medical history THREAD (1/9) about one of Britain's longest reigning monarchs. 👇
"Queen Victorian on her death bed" by Emil Fuchs.
More from Health
1/15
Why can cefepime cause neurological toxicity?
And why is renal failure the main risk factor for this complication?
The answer requires us to learn about cefepime's structure and why it unexpectedly binds to a certain CNS receptor.
#MedTwitter #Tweetorial
2/
Let's establish a few facts about cefepime:
🔺4th generation cephalosporin antibiotic
🔺Excretion = exclusively in the urine (mostly as unchanged drug)
🔺Readily crosses the blood-brain barrier (so it easily accesses the brain)
https://t.co/rjYG1BfGPR
3/
The first report of cefepime neurotoxicity was in 1999.
A patient w/ renal failure received high doses of cefepime and then developed encephalopathy, tremors, myoclonic jerks, and tonic-clonic seizures.
✅All symptoms resolved after hemodialysis.
https://t.co/u7JLVitQpp
4/
Cefepime neurotoxicity is surprisingly common, occurring in up to 15% of treated critically ill patients (w/ symptoms varying from encephalopathy to seizures).
💡The main risk factors = renal failure and lack of dose adjustment for renal function.
https://t.co/nxbnzSq8AR
5/
What about cefepime induces neurotoxicity?
One clue is that it's not the only antibiotic that causes neurotoxicity, particularly seizures.
This actually is a class effect w/ other beta-lactam antibiotics (including penicillins and carbapenems).
https://t.co/Lf4BhON9IY
Why can cefepime cause neurological toxicity?
And why is renal failure the main risk factor for this complication?
The answer requires us to learn about cefepime's structure and why it unexpectedly binds to a certain CNS receptor.
#MedTwitter #Tweetorial
2/
Let's establish a few facts about cefepime:
🔺4th generation cephalosporin antibiotic
🔺Excretion = exclusively in the urine (mostly as unchanged drug)
🔺Readily crosses the blood-brain barrier (so it easily accesses the brain)
https://t.co/rjYG1BfGPR
3/
The first report of cefepime neurotoxicity was in 1999.
A patient w/ renal failure received high doses of cefepime and then developed encephalopathy, tremors, myoclonic jerks, and tonic-clonic seizures.
✅All symptoms resolved after hemodialysis.
https://t.co/u7JLVitQpp
4/
Cefepime neurotoxicity is surprisingly common, occurring in up to 15% of treated critically ill patients (w/ symptoms varying from encephalopathy to seizures).
💡The main risk factors = renal failure and lack of dose adjustment for renal function.
https://t.co/nxbnzSq8AR
5/
What about cefepime induces neurotoxicity?
One clue is that it's not the only antibiotic that causes neurotoxicity, particularly seizures.
This actually is a class effect w/ other beta-lactam antibiotics (including penicillins and carbapenems).
https://t.co/Lf4BhON9IY
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.