Key result
Historical review credits both Loesch and Goldblatt with discovering renal ischemia causes persistent hypertension.
Why the study?
Both John Loesch and Harry Goldblatt independently demonstrated that renal ischemia causes persistent hypertension, but Loesch's earlier work has been underrecognized.
May warrant equal credit in hypertension histories; challenges Goldblatt-centric accounts and leaves open further archival validation.
In 1934, Harry Goldblatt and colleagues published an article titled "The Production of Persistent Elevation of Systolic Blood Pressure by Means of Renal Ischemia" in the Journal of Experimental Medicine. One year earlier, John Loesch had published a similar study in a German-language journal, Zentralblatt für Innere Medizin. His article appeared on 18 and 25 February 1933, in 3 parts, under the title "A Contribution to Experimental Nephritis and to Arterial Hypertension." The central proposition of both papers was the same: Renal ischemia causes persistent hypertension. Goldblatt's article is one of the best known in the history of medicine, and the words "Goldblatt kidney" are still commonly used. Although Loesch succeeded in producing persistent hypertension by inducing ischemia and in correctly interpreting this and its ramifications earlier than Goldblatt, his article has been cited only a few times. In this article, the authors share what is known about the studies of Loesch and of Goldblatt. They believe that both Loesch and Goldblatt should receive equal credit for these important first observations.
No takes yet. Share an insight, caveat, or question.
Glodny et al. (2006) conducted a review in Renovascular hypertension. Renal ischemia was evaluated on Persistent hypertension. Renal ischemia was identified as a cause of persistent hypertension by both John Loesch in 1933 and Harry Goldblatt in 1934, discoveries for which both pioneers should receive equal credit.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: