FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W3059285843> ?p ?o ?g. }

• W3059285843 endingPage "373" @default.
• W3059285843 startingPage "372" @default.
• W3059285843 abstract "We appreciate the comments of Sempsrott et al1Sempsrott J.R. Hawkins S.C. Graham D.A. Davis C.A. Abo B.N. Schmidt A.C. In response to flush drowning as a cause of whitewater deaths: targeting prevention with uniform definitions.Wilderness Environ Med. 2020; 31: 371-372Abstract Full Text Full Text PDF Scopus (1) Google Scholar regarding the article “Flush Drowning as a Cause of Whitewater Deaths”2Farstad D.J. Luttrell J.M. Flush drowning as a cause of whitewater deaths.Wilderness Environ Med. 2020; 31: 11-15Abstract Full Text Full Text PDF PubMed Scopus (3) Google Scholar and find their observations terminologically insightful. We agree that adding qualifiers to the term drowning, such as “dry, secondary, or near” sometimes adds more confusion than clarity. Our use of “flush drowning” deviates from the current definition of “drowning” in several respects; for instance, flush drowning in our definition is always fatal, whereas most uses of the word “drowning” involve variable outcomes. Human death most often is influenced by preexisting comorbidities that may interact with various triggering or enhancing environmental precipitants, any of which may or may not be anticipated or recognized by a medical examiner. Diagnostic uncertainty exists in many deaths, and in the case of lethal drowning, pathologists recognize the inherent risk of missing important confounders, such as seizures, intoxicants, trauma, or hypothermia.3Armstrong E.J. Erskine K.L. Investigation of drowning deaths: a practical review.Acad Forensic Pathol. 2018; 8: 8-43Crossref PubMed Scopus (12) Google Scholar, 4Otavio Savassi Rocha L. Death certificate: admitting uncertainty.Autops Case Rep. 2018; 8e2018024Crossref PubMed Google Scholar, 5Smith Sehdev A.E. Hutchins G.M. Problems with proper completion and accuracy of the cause-of-death statement.Arch Intern Med. 2001; 161: 277-284Crossref PubMed Scopus (248) Google Scholar Although we agree with most of the statements of Sempsrott et al, we would like to make several other comments regarding the letter. First, our usage of the term “flush drowning” was driven primarily by its long-standing prior establishment and name recognition within the whitewater community, which is our target audience. As for the general suitability of the phrase in the medical literature, not only does use of “drowning” rightly raise questions, but the qualifier “flush” is even more problematic because it implies that flush drownings only occur in “flushing” flows, which is incorrect. In fact, it is our opinion that water temperature has a profound effect on flush drowning. Second, because drowning definitions variably refer to immersion or submersion in a liquid medium with respiratory impairment as required substrates, most lack further specificity as to the antecedents leading to respiratory compromise. In fatal drownings, many current definitions, taken literally, could suggest any “in water” death is a drowning, considering that all death involves respiratory impairment. Although this may or may not be the intention of the epidemiologists, such an application does little to differentiate the primary or sequential physiologic events leading to respiratory compromise. In regard to cold water immersion, we have suggested lethal arrhythmias may be an important cause of death. As such, if the head is never submersed and there is no head-above-water aspiration, the respiratory compromise could be a secondary effect of immersion-produced arrythmia. Other similar potentially lethal effects of cold-water immersion that do not necessarily require aspiration or head submersion may include hypothermia, hypertension-induced vascular catastrophe, and post-rescue collapse. Although such events may still be considered a drowning in the strictest sense, preventing adverse outcomes may require varied approaches. Lastly, the suggestion by Sempsrott et al that flush drownings be called “fatal drowning due to X,” where “X” presumably represents the antecedent cause of the drowning, may be attractive in certain applications, but such phrasing would be largely a semantic gesture as applied to flush drowning. Until we can differentiate which deaths in this cohort directly result from cold water immersion versus other causes, X will remain elusive. This confusion is further compounded because secondary submersion or aspiration events can follow any cause of death. These constructs have always presented problems for physicians signing death certificates.3Armstrong E.J. Erskine K.L. Investigation of drowning deaths: a practical review.Acad Forensic Pathol. 2018; 8: 8-43Crossref PubMed Scopus (12) Google Scholar,5Smith Sehdev A.E. Hutchins G.M. Problems with proper completion and accuracy of the cause-of-death statement.Arch Intern Med. 2001; 161: 277-284Crossref PubMed Scopus (248) Google Scholar For instance, does the fisherman who is standing in knee-deep water and is fatally struck by lightning represent a fatal drowning secondary to lightning strike? Does this hold true even if the victim’s head never becomes submersed and no aspiration occurs? Likewise, does the deceased jogger found face up in 10 cm (4 in) of water with an intoxicant in the bloodstream represent drowning or something else? With respect to flush drowning, because of the inability to reliably define X, we arrive back at “fatal drowning due to flush drowning,” or whatever phrase one decides to call this amorphous group. Although we agree new terminology is required, until we can reliably differentiate X, this effort may offer little enlightenment, although it may appease the semasiologists." @default.
• W3059285843 created "2020-08-24" @default.
• W3059285843 creator A5041710087 @default.
• W3059285843 date "2020-09-01" @default.
• W3059285843 modified "2023-09-25" @default.
• W3059285843 title "In Reply to Dr Sempsrott et al" @default.
• W3059285843 cites W1977884651 @default.
• W3059285843 cites W2807087178 @default.
• W3059285843 cites W2808002547 @default.
• W3059285843 cites W3005690273 @default.
• W3059285843 doi "https://doi.org/10.1016/j.wem.2020.06.002" @default.
• W3059285843 hasPubMedId "https://pubmed.ncbi.nlm.nih.gov/32830027" @default.
• W3059285843 hasPublicationYear "2020" @default.
• W3059285843 type Work @default.
• W3059285843 sameAs 3059285843 @default.
• W3059285843 citedByCount "0" @default.
• W3059285843 crossrefType "journal-article" @default.
• W3059285843 hasAuthorship W3059285843A5041710087 @default.
• W3059285843 hasBestOaLocation W30592858431 @default.
• W3059285843 hasConcept C11171543 @default.
• W3059285843 hasConcept C142724271 @default.
• W3059285843 hasConcept C15744967 @default.
• W3059285843 hasConcept C2777683767 @default.
• W3059285843 hasConcept C2779134260 @default.
• W3059285843 hasConcept C2781140086 @default.
• W3059285843 hasConcept C29374701 @default.
• W3059285843 hasConcept C71924100 @default.
• W3059285843 hasConceptScore W3059285843C11171543 @default.
• W3059285843 hasConceptScore W3059285843C142724271 @default.
• W3059285843 hasConceptScore W3059285843C15744967 @default.
• W3059285843 hasConceptScore W3059285843C2777683767 @default.
• W3059285843 hasConceptScore W3059285843C2779134260 @default.
• W3059285843 hasConceptScore W3059285843C2781140086 @default.
• W3059285843 hasConceptScore W3059285843C29374701 @default.
• W3059285843 hasConceptScore W3059285843C71924100 @default.
• W3059285843 hasIssue "3" @default.
• W3059285843 hasLocation W30592858431 @default.
• W3059285843 hasOpenAccess W3059285843 @default.
• W3059285843 hasPrimaryLocation W30592858431 @default.
• W3059285843 hasRelatedWork W17264326 @default.
• W3059285843 hasRelatedWork W1975012905 @default.
• W3059285843 hasRelatedWork W1993529151 @default.
• W3059285843 hasRelatedWork W2022762925 @default.
• W3059285843 hasRelatedWork W2052006516 @default.
• W3059285843 hasRelatedWork W2159292390 @default.
• W3059285843 hasRelatedWork W2290053626 @default.
• W3059285843 hasRelatedWork W2304549429 @default.
• W3059285843 hasRelatedWork W2409763986 @default.
• W3059285843 hasRelatedWork W4205717199 @default.
• W3059285843 hasVolume "31" @default.
• W3059285843 isParatext "false" @default.
• W3059285843 isRetracted "false" @default.
• W3059285843 magId "3059285843" @default.
• W3059285843 workType "article" @default.