Elliot K. Fishman

Elliot K. Fishman is an American diagnostic radiologist, currently the director of diagnostic imaging and body CT and professor of radiology and radiological science at Johns Hopkins University School of Medicine.[1]

Fishman specializes in 3D imaging and renderinge. To date, he has published over 1,300 peer-reviewed publications and has co-authored 10 textbooks.[2] H

Career

Fishman received his medical degree in 1977 from the University of Maryland School of Medicine. He then did his residency at Sinai Hospital and subsequently completed a fellowship in CT at Johns Hopkins Hospital. In 1981, he joined the Johns Hopkins University faculty as an Assistant Professor and was promoted to Professor of Radiology and Oncology ten years later, in 1991. Currently, he also serves as the Director of Diagnostic Imaging and Body Computed Tomography, and is a member of the Johns Hopkins Kimmel Cancer Center. He is also co-principal investigator of the Felix Project for Early Detection of Pancreatic Cancer and co-chair of Image Wisely's executive committee.[3][4]

Fishman has won the Diagnostic Imaging’s 2016 Radiology Lifetime Achievement Award[5]; the 2016 Aunt Minnie Best Radiology Mobile App[6]; and the RSNA Honored Educator Award for 2012, 2014, 2016, and 2018[7]. He received an endowed professorship from the Johns Hopkins University School of Medicine in 2018.[8]

In the 1980s, Fishman worked in 3D imaging with Pixar Animation Studios.[9]

He also owns and runs a website called CTisus, subtitled "Everything you need to know about Computed Tomography (CT) & CT Scanning."[10]

gollark: I wonder how long it'll be before someone makes Unicode Turing-complete.
gollark: https://www.reddit.com/r/rust/comments/5penft/parallelizing_enjarify_in_go_and_rust/dcsgk7n/I think this just wonderfully encapsulates Go.
gollark: Oh, it also has that weird conditional compile thing depending on `_linux.go` suffixes or `_test.go` ones I think?
gollark: Okay, sure, you can ignore that for Go itself, if we had Go-with-an-alternate-compiler-but-identical-language-bits it would be irrelevant.
gollark: I can't easily come up with a *ton* of examples of this, but stuff like generics being special-cased in for three types (because guess what, you *do* actually need them), certain basic operations returning either one or two values depending on how you interact with them, quirks of nil/closed channel operations, the standard library secretly having a `recover` mechanism and using it like exceptions a bit, multiple return values which are not first-class at all and which are used as a horrible, horrible way to do error handling, and all of go assembly, are just inconsistent and odd.

References

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