Great post…thanks for sharing your thoughts. If I may opine on this as a radiologist with some technical understanding of LLMs/VLMs: I agree radiologists will not be automated away anytime soon. Your elastic demand point is mostly right (some modalities impart ionizing radiation so there is a good reason to not scan as frequently as you want), and I’d add a more fundamental one. The current transformer-based AI algorithms are extremely sample-inefficient compared to humans, especially when it comes to vision tasks (as opposed to text-based tasks). When I was a radiology resident, I read maybe 3000 CTs of the chest, abdomen and pelvis to reach expert/attending level. I can also make a rare-disease diagnosis after having seen 1 example study (or none; I can make a real-life diagnosis purely from reading and seeing an example case from a textbook). Currently, the best radiology VLM models, such as Nvidia’s NV-Reason-CT model, do not reliably call even some of the most common pathologies, despite having trained on >70,000 CTs that surely contain many examples of a common finding (macro-F1 of 0.614). I can think of several reasons for this: these models usually leverage weakly supervised learning such as CLIP, pairing radiology reports with the images, since wide-scale expert annotation is impractical for every study for every finding (Radiology’s Bitter Lesson, if you will; however, the signal that can scale is the noisy one). To scale, the model(s) will need to learn to associate image findings with words in the radiology reports. However, using radiology reports as ground truth can substantially limit learning. (1) As any radiologist will tell you, we don’t mention everything that we see. Otherwise, your radiology report would be like 30 pages long and not clinically useful. We mostly call the things that matter (for the most part). Sometimes, we don’t even call things that matter. Thus, some reports may mention “diverticulosis” when there is diverticulosis, while other reports don’t, even if there are findings of diverticulosis in the images. (2) Another limitation is that the actual real ground truth is never confirmed, which I suspect is a much bigger problem and harder to correct. When I was a radiology resident, I saved many cases in which my attendings and I made a certain call, and I was curious if those were correct. Right before I was about to graduate, I checked every case I had logged. Many calls were incorrect (and I trained at a major academic center in which subspecialized radiologists read their part of the body, so the attendings making those calls are above-average radiologists; real-world data is likely much worse). (1) and (2) make training very difficult when there is so much incorrectness, ambiguity and noise in the training data. The above observations are pretty self-evident when you look at other vision tasks, such as self-driving, for which there is (1) ample data with predominantly correct actions (labels), and (2) known ground truths (the task of driving is, for the most part, unambiguous. You see a red light, you stop. You want to make a left turn? You signal and yield to passing cars before turning. Those are universally agreed-upon “correct” actions). To use Tesla FSD as an example: even with the best compute, engineers and data, it took over a decade to reach limited, geofenced driverless service. And this is despite the fact that driving has a much shorter tail than radiology does. Further, self-driving usually has one correct action at a time. In radiology, that’s not true. There are so many different radiological appearances of one disease, as well as the same appearances of different diseases. And various diseases can involve the same anatomical location (for example, look up adrenal collision tumor). To “automate radiology” is also a huge simplification. The vast breadth of radiological studies is seldom mentioned. For a single modality of a body part, there are so many different variants. Say, for example, CT of the abdomen and pelvis: there are at least 10 different flavors of this. To name a few, there is the non-contrast CT, the portal venous phase CT (bread-and-butter workhorse), and then there are specialized versions such as the liver mass protocol, CT angiogram GI bleed protocol, pancreatic mass protocol CT, adrenal mass protocol CT, kidney mass protocol CT, and CT urogram, each of which contains 3-4 phases and is tailored to answer a specific question. All of this is just one modality for one section of the body. Now do ultrasound, X-rays, gamma studies, PET studies, and MRI. And then consider all the other body parts (brain, head and neck, chest, etc.). I’ve only touched upon the surface of all the nuances, but I think the current capability gap and your demand argument point the same way: radiologists will be busy for a long time.

Real life, baby

I tried this one time, from way lower, and didn’t quite make it to the water. Never again!

The FDA cleared a robot that performs joint ultrasounds and writes the report itself. @ROPCA3's Arthur scans fingers/hands/wrists for arthritis; its AI, Diana, reads them. 72% of US counties have zero rheumatologists. Translation: the scan and the first read move from a scarce specialist to a machine buff.ly/W68NJ2g #HealthTech #Rheumatology #AI

When I first learned about fusion, I heard what most people hear: tokamaks have received the most funding, but sustaining stable plasmas is extremely challenging; stellarators help with plasma instability, but they can be difficult to engineer and build. And when doing that early research, I, like many people, came away wondering if fusion might be too expensive and slow to be commercially viable, even when we solve the remaining engineering challenges. But the more I dug in, the more convinced I became that fusions potential is too immense to ignore. And when thinking about the end product: cheap, safe, abundant electricity on the grid, it helped challenge and reframe the problem and all the existing solutions. So Helion's co-founders and I treated fusion as a product rather than an experiment. We designed with plant and machine operation costs in mind which meant we designed around less infrastructure and less plasma stability requirements (one that doesn't even require ignition!). Helion does break conventions AND we also build and learn very quickly. We've done a lot of building and learning over the last seven thermonuclear prototypes that very few people in fusion get to do in their careers. Conventional thinkers don't like it, but we are doing what no one has ever done before. And when there is clean, abundant, safe fusion energy on the grid, it will be worth it.

AI will assist doctors. A lot. But one thing it will never replace is a doctor or nurses "Spidey sense" - the feeling that something is off despite the normal blood test results and vital signs It's an intuition you gain from years of experience AI will never have it

This is a view from Starship's forward flap looking down towards the bottom of the ship. Notice the spacing difference between the tiles on the far left (red arrow) and along the edges, catch pin, and windward side (yellow arrow). Remember, gaps = areas of significant heating and expansion. The tiles by the yellow arrow are surrounded by white because there has to be some material in the gaps to prevent plasma flowing into the gaps and under the tiles on reentry. This also means that as long as the heat shield design remains where the tiles are pinned to the expanding and contracting hull, you'll always need gaps and sealant, and Starship's heat shield will never be airplane-like fully and rapidly reusable. The tiles near the red arrow experience less expansion and contraction due to their leeward location out of the main plasma flow and thus can be placed tightly together. A proposed design that decouples the moving pins from the tiles, solving the gap problem, is "pinned" to my profile 🙂