Use of Lugol’s Solution in the Management of Complex Graves’ Disease-a Small Case Series
Bibliographic record
Abstract
Abstract Background: There are currently no clear guidelines for the peri-operative use of Lugol’s solution (LS) as an alternative to conventional anti-thyroid drug (ATD) therapy in patients with complex Graves’ thyrotoxicosis. Clinical Cases: Case 1 is a 44- year-old woman who presented with symptoms of hyperthyroidism and a moderately enlarged goiter due to Graves disease. She was treated initially with Methimazole 45 mg, once daily which was reduced to 30 mg once daily after a week. She subsequently presented to the emergency department with severe anxiety, sore throat, and a high fever. A blood panel showed evidence of profound agranulocytosis due to Methimazole. Methimazole was stopped and she was treated with a 10-day course of LS followed by a semi-elective total thyroidectomy. Case 2 is a 54-year-old old woman who presented with thyrotoxicosis due to Graves’ disease. She was started on Propylthiouracil (PTU) to which she developed hepatotoxicity and the decision was made to stop PTU. Methimazole was substituted to which she developed a severe desquamating rash hence it had to be stopped immediately. She was given a 10 day course of LS followed by semi-elective total thyroidectomy. Conclusion: In both cases, hyperthyroidism was successfully treated with Lugol’s solution and their surgeries were uneventful with full recovery. Although beneficial, Lugol’s Solution may result in adverse effects such as severe hypothyroidism, escape hyperthyroidism and death. These cases highlight the need for evidence based treatment guidelines for the use of Lugol’s solution in complex hyperthyroid cases.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.003 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.001 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.003 | 0.002 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".