SCROLL NEWS / DISCOVERY
Search headlines
Find the stories shaping the conversation.
Results for " ambient " 46 found 🔀 AI-powered Shuffle
Burning through Türkiye's GDP: The high cost of fossil fuel PM2.5 pollution on public health – Centre for Research on Energy and Clean Air
Türkiye’s reliance on fossil fuels is generating massive air pollution health costs both within the country and throughout the region. This report finds that fossil fuels account for more than half (52%) of Türkiye’s population exposure to PM2.5 air pollution. The cumulative health impacts are estimated to cost the Turkish economy approximately USD 55 billion each year, equivalent to 4.1% of national GDP in 2024. The pollution is also responsible for roughly 26,500 deaths per year in the country, including deaths from cardiovascular and respiratory diseases, lung cancer, stroke, and diabetes.The impacts begin at the very start of life, with fossil-fuel-derived PM2.5 pollution contributing to an estimated 8,000 preterm births, 8,200 low-birthweight infants, 5,100 new cases of childhood asthma, and 6,500 emergency-room visits for asthma each year in Türkiye.Beyond the estimated deaths each year in Türkiye, air pollution from the country’s fossil fuel emissions also contributes to deaths and economic losses in neighbouring countries. In 2024, these emissions were estimated to cause: 32,000 deaths and USD 2.1 billion in economic burden in Egypt; 1,700 deaths and USD 0.2 billion in economic burden in Syria; 800 deaths and USD 0.8 billion in economic burden in Iraq; 500 deaths and USD 4.5 billion in economic burden in Israel; and 400 deaths and USD 1.5 billion in economic burden in Greece.Türkiye currently has no national ambient air-quality standard for PM2.5, despite the substantial health burden associated with exposure to the pollutant. Figure — The percentage of annual PM2.5 emissions in Türkiye’s fossil fuel emissions, using the EMEP emission inventory and EMEP MSC-W chemical transport model Key findings Türkiye’s fossil fuel emissions (from domestic sources as well as international aviation and shipping) account for 52% of population exposure to PM₂.₅ nationwide. PM2.5 pollution attributable to Türkiye’s fossil fuel use is responsible for approximately 26,500 deaths in the country every year, including deaths from cardiovascular and respiratory diseases, lung cancer, stroke, and diabetes. Children are among the most affected, with fossil fuel-derived PM2.5 pollution contributing to an estimated 8,000 preterm births, 8,200 low-birth-weight infants, 5,100 new cases of childhood asthma and 6,500 emergency room visits for asthma each year. The cumulative health impacts of fossil fuel-derived PM2.5 pollution are estimated to cost the Turkish economy approximately USD 55 billion each year, equivalent to 4.1% of national GDP in 2024. Transboundary pollution attributable to Türkiye’s land-based fossil fuel emissions also leads to thousands of deaths in five neighbouring countries, with estimated economic burden per year (as of 2024) reaching USD 2.1 billion in Egypt (3,200 deaths), USD 0.2 billion in Syria (1,700 deaths), USD 0.8 billion in Iraq (800 deaths), USD 4.5 billion in Israel (500 deaths), and USD 1.5 billion in Greece (400 deaths). Türkiye currently has no national ambient air quality standard for PM2.5, despite the substantial health burden associated with exposure to the pollutant. Reducing fossil fuel use and emissions across Türkiye’s energy, transport and industrial systems would deliver substantial air quality and public health benefits by reducing exposure to PM2.5 and preventing associated illness and deaths. Figure — Annual deaths attributable to Türkiye’s land-based fossil fuel emissions in the five most affected countries, based on 2024 emissions
Amazon devices chief Panos Panay sees a future where AI devices replace the need to use apps
Speaking at TechCrunch Disrupt, Amazon devices chief Panos Panay described a future where ambient AI devices work in the background, anticipating users' needs instead of waiting for commands.
Q&A: Brian Eno on relaunching Opal Records, 'Music for Airports,' AI and Palestine
Brian Eno, the multi-hyphenate artist, producer, sound designer and political activist best known for his pioneering work in ambient and electronic music, relaunches his transformative label Opal Records on Friday | KNSS Radio
Q&A: Brian Eno on relaunching Opal Records, 'Music for Airports,' AI and Palestine
Brian Eno, the multi-hyphenate artist, producer, sound designer and political activist best known for his pioneering work in ambient and electronic music, relaunches his transformative label Opal Records on Friday | KCBS All News 106.9FM and 740AM
Former Plaud exec raises $26M for AI app that listens to you in the background
Ambi is releasing apps for iPhone, Mac, and Apple Watch that enables ambient capture
Teladoc unveils remote monitoring, ambient AI features
The company’s virtual care platform has integrated artificial intelligence scribing and camera-based vitals monitoring as it works to recover from significant financial setbacks.
An evening of acoustic folk and bluegrass
Aitkin County Friends of the Arts will present an evening of acoustic folk, bluegrass and ambient music featuring LaPlant Road, Kelley Smith and Everybird from 6-9 p.m. on Saturday, Oct.
September Monthly Review: Health MCP Guy?
For all the time I spend talking about APIs and data exchange, this newsletter has had embarrassingly little interoperability of its own. It’s old-school SaaS, baby - UI or bust. Not all of that is my fault! Substack, for all its popularity, is (as mentioned before) really frustrating as my system of record. The primary user it optimizes towards is the reader, whose attention feeds the app, the Notes feed, and the recommendation network that Substack is actually selling. Health API Guy is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber. Subscribe They’re falling into the same trap that Medium once sprinted into, albeit at a much more glacial speed. Younger generations may not remember (or never knew) it, but Medium once lured publications like The Ringer and Signal v. Noise onto its platform, only to lose them as it rebuilt itself around a paywall and an algorithmic feed. Substack’s original pitch circa 2020 was the antidote (you own your list), but every new feed feature chips away at it. I get it: writers are generic supply in the eyes of the Substack product team. Generic supply follows demand, so the consistent pressure on the PMs is to generate demand, which leads to every product cycle going toward discovery (Notes, recommendations, the app, live video). The end result lackluster author tools (laggy and broken analytics are truly crippling) all despite the premium price point. The archive is where it crosses from authorial gripes to actual reader impact, though. Across Substack and LinkedIn, I’ve published 1,218 posts and nearly 900,000 words since 2018. Substack’s native search can see only the 464 posts that live on Substack, and even there it’s woefully inadequate at surfacing relevant content (even for the guy who wrote it)! Readers have the same problem, writ large. Ask the Archive Fixing search (for both my readers and my own use) turned out to be extremely non-trivial, unfortunately: There’s no public API for readers to access content RSS exists for new content notification, but it only carries the 20 most recent posts and cuts paid ones off at the preview The only Substack MCP is an admin tool for analytics The export exists for authors, but it’s painfully awkward and slow. So I built something to work around that: the Health API Guy MCP. It’s a private MCP server holding the full text of everything I’ve written across Substack and LinkedIn. Add it to Claude or ChatGPT as a connector and you can ask things like: It pairs keyword search (for acronyms and case names, of which we have many) with semantic search. Every post is also labeled by topic, form, and court case, so you can pull a lawsuit’s (or multiple cases’) entire docket across Substack and LinkedIn in one query: Hail, Healthapiguyhydra This is also a bit of me eating my own cooking. I’ve spent the year arguing that headless healthcare is arriving and that developers want primitives over abstractions. Last week in Hail, Benihydra, I watched Salesforce plug its platform into Claude and bet that the records underneath outlive whatever interface sits on top: Salesforce must believe that the Hydra’s immortal head is the records, permissions, and business logic (in that they will survive whatever happens to the interface). It felt a bit hypocritical to keep my own archive behind a Substack search bar. The archive is the body. Substack is one head, and now whatever tool you might use is another. Will the EHRs follow my lead? Probably not imminently, but one can hope! Why Founding Members Only The MCP is available to Founding Member subscribers. A few reasons: It costs money and time to run. Hosting, the database, Clerk usage and AI compute for search and labeling are significant operational costs (that increase with usage). Substack gives me no way to automate access. There’s no API to check whether someone is a paid subscriber, so every user is manual operations for now. It’s a beta. We’ll need to improve things and parts will break. I’d rather they break for a small group of dedicated readers who will tell me about it. The Founding tier deserved a real benefit. Until now it was mostly a generous tip. Now it comes with something. If you’re already a Founding Member, reply to this email with the address you’d like provisioned. If you’re not and want in, upgrade here. Larger teams (such as companies) can get access too: group subscriptions at the Founding tier come with the group discount. The admin for the subscription can reply with the list of addresses to provision. Get 20% off a group subscription Pricing Founding membership is now a flat $200 a year, replacing the old suggested $150 that readers could adjust. Existing Founding Members will have access grandfathered in at their previous rate. Month in Review Articles Published Make Networks Dumb Again (Sep 11): AI is making old analog networks cheaper to use and flooding them with machine traffic in the process. A plea for agent-native rails with the intelligence at the endpoints, and for Washington to drag them to ubiquity. Interoperability, Unbuttoned (Sep 29): Interoperability is a series of workflows in a trenchcoat, and this post finally takes the trenchcoat off. A color-coded map shows which provider workflows went digital, which are fragmented, and which still run on fax. Video Content Antitrust’s System of Record Problem (Sep 3): The FTC’s investigation into Epic prompted a ninety-minute webinar, now posted with chapters and a smoothed transcript. We get into why market definition, missing B2B share data, and the SSNIP test leave antitrust poorly suited to systems of record, plus why information blocking may be doing more than any pending lawsuit. The Information Exchange: Cerner Milking Edition (Sep 18): This was so fucking fun. Ryan Tucker, Ryan Brickner, Brad Thorson, and I try an Around the Horn format, complete with points, penalties, and a mute button. We debate whether Oracle Health is dead, who would actually buy Cerner (IBM enters the chat), p(Doom), and why the front desk still hands you a clipboard. Regulatory Ask Not What Your Network Can Do (Sep 23): CDC’s RFI on public health data intermediaries lists use cases already served, unevenly, by eCR, lab reporting, IZ Gateway, and syndromic surveillance. The real opportunity sits in one question about AI: a network that can handle the next emergency without another interface project. Court cases Particle v. Epic: The Naughty Schoolteacher (Sep 4): After a summer-long vigil, the answer on Epic’s early summary judgment bid is two paragraphs and a remedial assignment. Particle advances to the next grade, and market definition gets another year of discovery. The Epic Discovery Files (Sep 8): Texas’s motions to compel arrive with a 251-page appendix of requests, objections, and meet-and-confer letters with Cravath. Inside: Epic using generative AI for document review, denied interoperability requests in scope, and Noerr-Pennington raised against lobbying discovery. Epic v. Health Gorilla: “Working as Designed” (Sep 9): Epic wants nothing to do with the data breach MDL, and explaining why puts fresh discovery on the public docket. The spiciest allegation: Health Gorilla told GuardDog to scrub its law firm business from its website instead of cutting off access. Veeva v. Epic: Legal Bypass Surgery (Sep 15): Veeva asks the Wisconsin Supreme Court to skip the Court of Appeals, while law professors and three policy groups line up as amici. Meanwhile, Epic’s lawyers apologize for another round of citation errors, including a quote that never existed. Texas v. Epic: Behind the Black Bars (Sep 17): The court portal served up Epic’s unredacted filings, revealing a $5 million document review budget and the AI workflow behind it. Also inside: the 200-plus company names Texas wants searched, and one very expensive Zoom invitation. OpenEvidence v. Doximity: Consequences Will Follow (Sep 25): OpenEvidence tells the court it will not comply with a discovery order, and its own lawyers at Quinn Emanuel say they won’t defend the choice. Add years of Slack reported unrecoverable, and Rule 37 sanctions come into view. Health Tech Keeps Choosing Violence (Sep 28): Doximity moves to end OpenEvidence’s case, Epic asks Texas to show its work, and a sleepy Audacious Inquiry patent fight sprouts antitrust and information blocking counterclaims. The main event is a long-sealed Cognizant v. Infosys ruling that hints where system of record antitrust claims can survive. EHRs One Verb for Oracle Health (Sep 14): Oracle’s earnings call quantifies every data center to the decimal point, while Oracle Health gets a single verb: “accelerate.” Panning the few healthcare mentions turns up an agentic care management system, a research-to-care ledger play, and the question of whether healthcare gets Larry’s patience. Epic’s Forretress Under Siege (Sep 30): Judy Faulkner tells a panel Epic paused hundreds of projects to harden its software and calls it a “shame,” while a spokesperson insists the roadmap hasn’t changed. Project Glasswing, a Pokémon-branded QAN sprint, and a trove of Jodel grievances reconcile the two Epics and preview the Jevons paradox coming for all software. Industry Analysis Scanning for a Network (Sep 1): Scan.com raises $220M to build the imaging network labs never got, speedrunning Zocdoc’s consumer-to-B2B pivot. Its wedge to network density may be the most American one available: personal injury litigation. The Front Desk Wants the Damn Whole Building (Sep 16): Hello Patient buys Converse Health, pushing its AI front desk into referrals, chart work, and prior auth. The copilot categories keep blurring, and your distribution partner is still your final boss. Cross-industry Comparisons A Different Patchwork Quilt (Sep 10): Healthcare loves to envy open banking, but the US version has no mandate, a toll booth at Chase, and data quality problems of its own. The grass isn’t greener; it’s another American patchwork quilt, and perhaps a worse one. Hail, Benihydra (Sep 21): Salesforce brings its platform into Claude, Slack, and its own agent, inviting the interfaces that might replace it. Cut off one head and more grow back, so long as the records underneath stay put. Living on A Trade Secret Prayer (Sep 22): Six credit unions are suing Fiserv, the Epic of core banking, by claiming their own member records as trade secrets. Banking has no Cures Act, so its lawyers reach for legal alchemy that healthcare has already tried. Other News None this month External Media Nabla Accelerate NYC: I kicked off fall conference season at Nabla’s Accelerate event in New York, where Delphine Groll opened by asking the room to picture the company it wants to become and the one it doesn’t. I liked her framework of bureaucracy, fear, and ego as the blockers. I also love vendor conferences/events in general - different vibe than industry biggies. Healthcare 101 with Nikhil Krishnan: I briefly guest lectured Out-Of-Pocket’s Healthcare 101 class. Appreciated Nikhil’s takeaways cover whether AI doctors can query HIEs, why healthcare’s data-liberation rules beat most industries’, and the hi-res graphic is in the comments. HCN: Epic Probed by the FTC: I joined the HCN guys to talk through the FTC’s investigation into Epic. Cedric’s new hairdo was an unexpected plot twist. The episode also covers MFN drug pricing, healthcare M&A and Eli Lilly’s acquisition streak. Fall Conferences: At eHealth Exchange’s Annual Meeting in Austin on Oct 27, I’ll moderate a panel on the tensions between AI, HIEs, and timely patient access with Jean Ross (Primary Record), Therasa Bell (Kno2), Byron Crowe (Doctronic), and Michael Marchant (Freenome). Here’s the rest of my schedule if you want to meet up: CommonWell (Redwood Shores, CA): Oct 13-14 Will be participating in a fun Jeopardy event Open@Epic (Madison, WI): Oct 20-23 Will be enjoying Verona, Willy Street, and other local adventures eHealth Exchange and Sequoia Project (Austin, TX): Oct 27-29 Yeehaw HLTH (Vegas): Nov 15-18 Groundhog Day, Venetian Edition RSNA (Chicago): Nov 30-Dec 2 See me at “Governing AI in Breast Imaging: What Health Systems Are Actually Doing” Digital Health Counsel 2026 AI Summit (Seattle): December 2-3 Will likely be speaking to a bunch of lawyers about information blocking Posts I Liked ChatGPT’s Epic integration: game changer or nothing burger?: Joshua Liu, MD offers five thoughts on OpenAI’s Epic launch, starting from the point that it rides the same open APIs available to anyone. He argues read-only access leaves ordering to Art and the ambient startups, and asks why HCA is piloting it alongside Commure. He’s sorta a must-follow at this point - consistently excellent, thought-provoking takes. Epic, Lilly, and the Discovery pass: Seth Chaney reads Epic’s first major Discovery deal (with Eli Lilly), as well as its revised developer terms on commercial displays, as the pipe finally opening between EHRs and pharma. Life sciences and health continue to collide. Scott Rossignol on EHR payer platforms and ePA fees: Scott argues the top ambulatory EHR vendors are turning the prior auth mandate into a per-member-per-year toll on payers, for an API whose operating cost has nothing to do with covered lives. His fix is two lines of regulatory text: put the CRD/DTR/PAS certification criteria in the Base EHR definition, and bring payer-facing ePA connectivity under § 170.404’s cost-based fee rules. It’s a good solution. Health API Guy is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber. Subscribe
Community & Health Impacts and Risks of Gas
Learn about benefits of electrification, community & health impacts and risks, and financial costs
Community & Health Benefits of Electrification
Learn about benefits of electrification, community & health impacts and risks, and financial costs
Apple Planning to Bring iPhone Duo Display Tech to Pro in 2029
Apple's 2029 "Pro" iPhones could adopt thinner and more power-efficient OLED screens, according to UBI Research. The technology, known as Color Filter on Encapsulation (CoE), removes the conventional polarizer from the OLED panel and places a color filter directly on top of its encapsulation layer. A polarizer helps suppress reflections from ambient light, but it also absorbs a significant portion of the light produced by the display.
Science Vs on the 49ers Substation: Anatomy of a Hatchet Job
In August, Pablo Torre Finds Out and Science Vs released an episode about my theory that electromagnetic fields from the electrical substation beside the 49ers facility may be contributing to the team’s run of soft-tissue injuries. As the originator of the theory, I was also a subject of the episode. I sat was interviewed by Wendy Zukerman and Rose Rimler of Sciene Vs. I sent them research, connected them with scientists, and spent hours digging through the City of Santa Clara’s and Silicon Valley Power’s records to help clarify critical details. Both Wendy and Rose came off as affable and professional, showing curiosity during the interviews, with Wendy going out of her way to question the “conspiracy theory” framing itself. Then they titled the episode We Solve the 49ers Viral Conspiracy Theory. I was familiar enough with their catalog that I never expected them to agree with my theory, but I did expect them to give it a fair hearing and to deliver their findings honestly. On both counts they came up short. They were not directly dishonest in anything they said, but rather in what they left out, in how what remained was cut, and in the picture painted by those two things in combination. They asked me to recorded the interview on my phone for better audio quality, and I held on to my copy for reference later. That turned out to be a fortuitous decision. Here is the raw audio of my first interview, unedited*. Only my side was recorded, so their questions aren’t on it, but you can generally infer them from the answers, and every claim I make below about what I said can be checked against my statements in this clip. (Note: Wendy had connection trouble at the beginning of the interview and was cutting in and out, which accounts for the false starts.) 0:00 -1:19:13 Audio playback is not supported on your browser. Please upgrade. Science Vs is a fun show. It is pitched at roughly a high-school understanding of science, for an audience that is skeptical, Snopes-oriented, and worried about misinformation. Take a claim circulating online, interview a supporter of the claim, interview consensus scientists, and then tell people which side of the line it lands on. I have listened to their episodes on raw milk, seed oils, 5G and other contested issues in the wellness space. I have problems with all of them, but each at least made an honest attempt to represent the actual range of scientific opinion by talking to credentialed scientists with differing perspectives. Dissenting researchers were heard from, answered, and often given a chance to respond. This episode did not do that. This article is not a relitigation of the science. I have written extensively about that already. This post is for the record. It is simply an accounting of what was wrong with their episode. Contents Is there a power plant next to the 49ers practice facility? — the clearest single example of getting something objectively wrong For the record — a high-level overview of all of the problems with their investigation Draw your own conclusions — why they had to make this episode at all What they left out about childhood leukemia — the exposure threshold, and playing games with statistics to minimize sick children What they left out about the mechanism — the body of literature they refused to cover, and evidence for the mechanism used against it The scientists Science Vs interviewed and did not air — four credential scientists who support myhe theory, recorded and cut, or not even called How they misrepresented me and my case — an answer severed from its question, and three telling edits How you would actually study the injuries — it doesn’t actually matter which team is the most injured, overall The theory: magnetic fields, oxidative stress, and collagen Since the episode never states my theory, here it is below. Those who are familiar with my work can skip this section. Electrical equipment produces magnetic fields, and those fields induce faint electrical currents in anything that passes through them, including people. My argument goes further than induced current. Mitochondria — the structures that generate a cell’s energy — run on continuous flows of electrons and protons, and those flows carry faint electromagnetic fields of their own. Maxwell’s principle of superposition shows that when two fields share the same space, they add together. An external field does not need to be strong to alter an internal field, it only needs to be present. The electron transport chain inside the mitochondria leaks a small fraction of its electrons by design, and those become reactive oxygen species — free radicals, which healthy cells use as signals. External magnetic fields cause the rate of leakage to change, increasing free radicals. When free radicals accumulate faster than the cell’s antioxidant systems can clear them, the result is oxidative stress. Oxidative stress is a recognized driver of chronic illness, including cardiovascular disease, neurodegeneration, diabetes and cancer, and it is in every medical school curriculum. One of its ordinary effects in connective tissue is that it switches on matrix metalloproteinases — MMPs, the enzymes that break collagen apart — while suppressing new collagen synthesis. Tendons are made of collagen. An athlete loading his soft tissue heavily six days a week is already creating oxidative stress in the tendons, so the addition of magnetic field exposure compounds the damage and inhibits repair, making him more susceptible to injury when enormous force lands on a tendon in a fraction of a second. That is the theory. We know that EMF causes oxidative stress, and we know that oxidative stress degrades collagen. The only thing missing is a study showing that direct connection. I have never claimed certainty that the substation is contributing to the elevated injury rate. I do believe it is likely, and I believe it warrants caution, and that a revenue machine like a major NFL team can easily afford to remove the exposure out of precaution. Is there a power plant next to the 49ers practice facility? Here is the clearest single instance of the problem with this episode. It requires no knowledge of electromagnetic fields at all. This story first came to me through Jon Feliciano, a former 49er, in an interview on Willard & Dibs on 95.7 The Game. Asked about why the 49ers are always injured, he said players used to joke that it was the power plant behind the practice fields. Wendy Zukerman corrects him on air. “It’s important to say that it’s not a power plant near the 49ers site.” Torre then asks her to explain the difference between a substation and a power plant. Her answer: a power plant generates electricity and transmits it to a substation, which converts the voltage into something your house can use and sends it on to your home or your business. There are two problems with that. The first is that there is a power plant on that site. The Gianera Generating Station is a natural-gas-fired peaker plant owned by Silicon Valley Power, and it has been there since 1986. I have published aerial photographs of the location from 1987 in which the gas plant is the only thing standing, before the practice facility was even there. I even mentioned the gas plant in my first interview. (Feliciano has since gone on record about this issue, and it is clear he had the substation in mind rather than the gas plant.) The second is that her definition describes a distribution substation, and the facility beside the 49ers is not that. It is the Northern Receiving Station, which takes in bulk power from outside the city’s grid and delivers it to distribution substations. Silicon Valley Power’s own map distinguishes receiving stations from substations, and Rose Rimler even reads the label out loud in the episode when she walks through that map on air. A few minutes before the map segment, Zukerman tells Torre: “like I said, we fact check everything.” Well, maybe not everything. I made a mistake On the morning of July 6th, at 10:20, I sent Rose and Wendy two studies. During the interview I had been asked which human studies show oxidative stress from electromagnetic fields, and I had not been able to name one on the spot. Rose emailed asking for the studies, I quickly searched for a couple, and I wrote that I thought these were the most relevant from that search. Unfortunately, I was busy and did not read either one closely at first. I picked them because they were topically relevant — one on substation workers, one on power plant workers. Neither were great studies, and their problems go past the ones raised in the episode. That was careless on my part. There is context that did not make the episode, though. Before that email I had been on a Zoom call with Rose talking about EMF and oxidative stress, and I pointed her to Dr. Henry Lai at the University of Washington, who has spent years aggregating the literature on this question. His tallies show that roughly 90% of studies since the late 1990s find oxidative effects from electromagnetic field exposure — hundreds of studies, systematically counted. Rose told me she was already aware of his work. So when she asked for studies, I understood her to have the aggregate view already and that she would report anything within that context. Not reading those two carefully was still a mistake, but the larger mistake was assuming the episode would be based on a thorough review of the actual body of literature, rather than on whatever I happened to send that morning. The second email At 1:49 that same afternoon — three hours and twenty-nine minutes after the first — I sent them a second email that I had been preparing for a while. It was a structured document in six numbered sections, written in response to a request they had made two weeks earlier, laying out my entire argument with citations attached to every link in the chain. The episode aired on August 13th, five weeks later, and not a single item from the second email is in it. Here is how it opens: The full email is included at the bottom of this post in Appendix B. Nearly 1,500 words in total. It contains two named mechanisms with the physics behind them. Occupational studies in humans. The literature on oxidative stress and collagen. A section addressing the strongest counter-evidence against my own theory, which I raised myself. And a closing section stating plainly what the theory cannot yet show. My entire argument, in writing, with detailed citations for every claim, provided to them five weeks before broadcast, and none of it made it into the episode. That is the single largest omission, but it is not an isolated one. The whole episode is riddled with similar problems, and the conclusion they came to is not merely a difference of opinion about the scientific evidence. Through omission and through strategic editing, Science Vs misinformed its audience — about what the evidence shows, about what I argued, and about who they spoke to. That is a notable outcome for a show whose stated purpose is correcting misinformation. For the record I am not going to tell you that Science Vs set out to discredit me, or that they had come to their conclusion before they reported the story, or that they used misleading editing to make me look like a man retreating from his own theory. I cannot know what was in anyone’s head, and I am not going to pretend otherwise, either. What I can tell you is what is on the record. They asked me for evidence and aired the weakest thing I sent. They interviewed three scientists who supported my theory and aired none of them. They discussed childhood leukemia without ever saying the exposure level at which it appears. And they took an answer I gave weeks before Ken Karipidis, the one EMF scientist who was put on air, was interviewed, and placed it directly after his critique, where it comes off as a major concession. A friend of mine who has worked as a journalist for thirty years read that last one and called it sleazy. I agree with her. Those are just the four issues that are impossible to defend as pure editorial decision, but they are not the only issues. The most glaring issues stem from what they left out: The exposure level at which the childhood leukemia association actually appears — three to four milligauss, a number the episode never states despite it being much lower than what I measured. The mechanism itself: The episode gets as far as “oxidative stress could weaken collagen,” which leaves it sounding like speculation, rather than a known pathway. The second email, and all the studies in it. Dr. Paul Héroux at McGill, whose work my proposed mechanism rests on, whose contact details I supplied, and who was never called. Dr. Beatrice Golomb at UC San Diego, who runs a research group on oxidative stress and mitochondrial function and has specific expdertice in collagen, interviewed and not aired. Dr. David Carpenter at Albany, the most prominent academic voice on the harm from magnetic field exposure, interviewed and not aired. Dr. Joel Moskowitz at Berkeley, interviewed and not even credited. The specific, testable condition I put in writing that would make me abandon the theory. My own unprompted statement of the theory’s evidentiary gap. My caveats about my own measurements. My ranking of EMF as one factor among several rather than the only one. The new equipment installed at those facilities between 2010 and 2014, and the sharp rise in system load from 2013 onward. But that is not all. What they kept, they selectively edited to serve a narrative that was not served by the raw transcripts of the interviews. A description of thousands of commercial routers in a workplace, reduced to the Wi-Fi in your house. My own acknowledgment, multiple times, that "I'm not a scientist" clipped in an episode that spends considerable energy pointing out that I am not a scientist. And a qualification I volunteered about my own measurements, cut from my answer and delivered later by their EMF expert as a correction. Together their edit produce a portrait of a wellness guy with Wi-Fi phobia and two bad studies, backing away from his theory the moment a “real” scientist looked at it. A practice facility where nothing changed because no new substation was built. Injuries written off as random because the 49ers were not quite the single most injured team in the league over the period in question. That portrait is false even though almost no individual statement made in the episode is. Draw your own conclusions At the top of the episode, Pablo Torre says his show had been flooded with requests to investigate the substation — that it was the thing they were asked to look into over and over again. Neither show went hunting for this story. It arrived from their own audience, in volume, and it could not be waved off. A thread I posted on X reached twenty-two million people. A guy with a gaussmeter and a brand-new Substack obligated a Pultizer prize winning program to spend an hour on a question about player health, that is considered fringe enough that most media operations won’t touch it. Pablo Torre Finds Out could not ignore it. So Science Vs came in and ran a “debunking” operation instead of an investigation. Everything below is what had to be left on the cutting room floor to deliver the “debunking”. They could not ignore it. So they tried debunked it instead. The demand was strong enough to force an episode, and since the episodes release the 49ers have sustained more injuries, including season ending ones, and interest has only grown. Demand from fans and playets is strong enough to force a better investigation from someone else. An omission is not a lie until you find out what was omitted. What follows is the detailed record so you can see the full picture. Draw your own conclusions. I have drawn mine. I am going to keep publishing. A note about Pablo Torre Finds Out After the episode aired I posted publicly, calling out Pablo Torre Finds Out for concerns I had about the integrity of their investigation, and about an interview directly with Pablo Torre which had been offered but never happened. I have since spoken with a producer at PTFO. The offer had rested on a misunderstanding about where things stood between us, and it fell away as the Science Vs part of the production widened past the science. He apologized for the miscommunication and I accepted. The producer also confirmed to me that they did essentially hand off the entire investigation to Science Vs for narrative purposes — so Pablo would be genuinely curious or potentially surprised by their findings — while still taking responsibility for what went out under their name. I appreciated the candor and the accountability, and I am comfortable with where we left things. So this post is not about PTFO. My disagreement is with Science Vs. What they left out about childhood leukemia Childhood leukemia appears at three milligauss. They gave no number at all. 1. They built an EMF ruler, then discussed childhood cancer without it. The sequence on air went like this: First I measured almost 9 mG, then I measured up to 50 milligauss. Torre reacts with concern — “that sounds high.” Cut to Karipidis: the public limit is 2,000 milligauss. Torre reacts again — “What happens at 2,000?” Karipidis explains that nothing happens at 2,000, that safety factors are built in. Then: at more than 50,000 milligauss you get flickers of light in the retina, and higher still, nerve stimulation. The listener now has a ruler (their ruler) to measure these numbers with. Fifty is nothing by their ruler. Then the episode turns to childhood leukemia and states, accurately, that there is a real association — but tellingly, they never give the exposure level at which that association appears. Childhood leukemia appears at three milligauss. They conveniently left that out. The pooled analyses that produced the World Health Organization’s carcinogen classification found roughly a doubling of childhood leukemia risk above three to four milligauss. That is the number that belongs in that segment, and it is more than ten times below the reading that had just been dismissed as trivial. I gave them that number myself, on tape, in the interview. Describing my own threshold, I said my comfort level for long-term chronic exposure is three to four milligauss, but preferably one. 2. Six children in thirteen million. The episode reports that these fields might explain one to four percent of childhood leukemias, then reframes it as a German estimate of perhaps six cases among thirteen million children. Torre, to his credit, is uncomfortable. What never gets explained is why that number is small. Almost no children lives above three milligauss in Europe. Fewer than two children in a hundred, in the Italian data. So even if the risk to those children doubles, the number of additional cases across an entire country stays small — not because the hazard is small, but because hardly anyone is exposed to it. Count the whole population and the few who are exposed disappear. And the reason hardly anyone is exposed is that siting rules keep housing away from transmission lines. In Europe, at least. The Dutch government has a standing precautionary policy against building new homes in any zone where the annual average magnetic field exceeds 4 milligauss — the same number the episode never mentioned. Denmark and Norway treat 4 milligauss as the level that triggers a look at mitigation. That is five hundred times below the ICNIRP figure quoted on air. The United States has no federal equivalent. That is evidence of infrastructure siting policy working. It is not evidence that there is no hazard. It is evidence that we already act as though there is one. If you listen to the raw audio you will hear that my proposed solution is EMF exposure is to build better infrastructure. What they left out about the mechanism 3. They accused me of cherry-picking, and then cherry-picked themselves. On air, Zukerman tells Torre that people who worry about electromagnetic fields dismiss the studies showing null results and collect the ones showing harm, and that this is why you have to be careful not to cherry-pick. They had two papers I had rattled off in a hurry, and a second email containing a carefully chosen set. They ran the two weakest, graded them on air, and presented the result as the state of the evidence for not only my theory, but the whole question of oxidative stress from magnetic fields. That is cherry-picking from my emails. The bigger picture is what they did with the literature as a whole. Zukerman acknowledges it exists, dismisses it, and disposes of it in a single stroke. You can go online right now, she tells Torre, and find scores of studies showing these fields increase oxidative stress. The issue, she says, is that they are not studies in people. Many of them are in people. The occupational studies in my second email are in people. That email had been in her inbox for five weeks. She waved off the literature on a factual claim that the documents in her possession contradict. (I have written separately about the evidentiary standard at work here). The effect was that they essentially baited me: ask the subject to supply the evidence, take the weakest thing he sends, and let that stand as a proxy for the whole argument. Wendy has been doing this show for ten years and clearly knows how to extract what she needs for her desired narrative. 4. They presented the collagen-improvement research as a gotcha, but I had already addressed it. The episode treats the existence of studies showing that EMF can improve collagen as a surprise that undercuts me, but I had pre-emptively addressed that five weeks earlier in the email they ignored. Those studies use measured, high-intensity pulsed dosing. The mechanism by which they work is oxidative signalling. The cell reads a controlled rise in reactive oxygen species as a warning, upregulates its antioxidant defenses, mounts a repair response, and the therapy stops before the system is overwhelmed. The key point is that it induces an oxidative response, which means those studies are actually evidence for my proposed mechanism, not against it. A field that produces a therapeutic effect cannot be biologically inert (which is the implication when they say “Nothing happens at 2,000 milligauss). Chronic ambient exposure is the same pathway with no off switch, and it is most consequential during the evening and while sleeping, when the body is in repair mode and the exposure does not stop. Section 5 of my email is titled What about the study showing improved collagen synthesis. I raised the counter-evidence myself, explained why I did not think it refuted the theory, and wrote that I was disappointed the question had not come up in the interview. That is worth holding against the cherry-picking charge in the item above: the studies they presented as inconvenient for me were studies I had gone out of my way to put in front of them. 5. Section 1 of my email stated a critical argument that was never put to the expert directly responsible for it. My email says the exposure limits exist to prevent acute effects and do not address chronic exposure at all, and that my dispute is with the entire framework. Zukerman gestures at this once. After Karipidis gives the 2,000 milligauss figure, she tells Torre that I would object because those levels do not capture “more subtle effects.” That is not my argument, and “subtle” is doing a lot of work here. My argument is that the limits are built to prevent acute effects — nerves firing, muscles twitching, etc — and were not designed to address chronic exposure at all. In fact, ICNIRP’s own documents state as much themselves. Mine is a structural objection to what the standard measures, reduced as a concern about subtlety, it becomes a matter of degree, rather than a categorical difference. They interviewed Ken Karipidis, vice chair of ICNIRP — the body that writes those limits. He was asked what the limit is, but he was never asked how it applies to chronic exposure. The scientists Science Vs interviewed and did not air 6. They interviewed four officials of the standards body. The episode credits roughly a dozen researchers. Four of them are associated with ICNIRP. Ken Karipidis is the vice chair. Rodney Croft chaired ICNIRP from 2020 to 2024 and led the development of its current guidelines. Dan Baaken is ICNIRP’s scientific secretary. Frank de Vocht sits on the Main Commission. One of them speaks in the episode. Their institution’s position is more than adequately represented — the 2,000 milligauss figure, the safety factors, the assurance that nothing happens below the line. 7. The four who were left out. Dr. Beatrice Golomb is Professor of Medicine at UC San Diego — a physics undergraduate degree, a PhD in biology, an MD. She directs a research group whose stated focus is the relationship between oxidative stress, mitochondrial function and health. That is the mechanism the episode spent its first half dismissing. Her published work includes the fluoroquinolone case series behind the FDA’s black box warning on an antibiotic class that ruptures tendons, where the accepted mechanism is oxidative stress and mitochondrial toxicity — the back half of my chain, already on a drug label. She is in the credits. She is not in the episode. She has told me she finds my theory biologically plausible, and that she has a recording of her interview. Dr. David Carpenter directed the Institute for Health and the Environment at the University at Albany for decades and is the most prominent academic voice arguing these fields cause harm. Childhood leukemia is the reason these fields carry a WHO classification at all, and Carpenter is the person you call if you want that case made by someone who has spent a career on it. He is in the credits. He is not in the episode. He has told me that when he was interviewed they could not have been less interested in what he had to say. Dr. Joel Moskowitz directs the Center for Family and Community Health at UC Berkeley’s School of Public Health. He told me directly that they interviewed him and that he thought it went well. He does not appear in the episode, and unlike Golomb and Carpenter, he does not even appear in the credits. Dr. Paul Héroux at McGill is the researcher whose work provides the foundation for the oxidative stress mechanism my theory rests on. I gave Rose his email address and phone number. He was never interviewed. They never even called him. 8. “He’s not a scientist.” The episode leans hard on the fact that I am not a credentialed scientist. Zukerman says it. Torre repeats it. “At all.” Having built a segment on that, they then left out the physicist-biologist-physician, the professor of public health, the director of a university environmental health institute, and the McGill researcher whose work the primary mechanism comes from. They spent the episode telling their audience I am not a scientist, and then kept four actual scientists who support the theory off because their argument does not survive otherwise. How they misrepresented me and my case 9. They played my words as a response to an interview I had never heard. Near the end of the hour, Zukerman says she went to me and told me the evidence was lacking. Then she plays me saying I am not wedded to it being an EMF, that I have staked my reputation on it needing more study, and that I am not certain of anything. That segment was placed immediately after Karipidis had finished taking the cherry-picked papers apart. It plays as a man folding under expert scrutiny. Commenters have used it against me since, but it is incorrect. Here is the sequence as it happened. I was interviewed. Karipidis was interviewed weeks later. I was never told what he said, or even who he was. I was never asked to respond to it. I did not know his name until the episode aired. That is not a simple editing decision. That is a quote from one interview, moved to follow a critique from a different interview it was not a response to, so that it would land as a concession. A friend of mine who has spent thirty years as a journalist read that sequence and called it sleazy. She is right. The full passage is reproduced in Appendix A, and it is worth reading. What airs is the preamble. Four paragraphs later I say “to directly answer your question” — and that answer, about what would change my mind if the team relocated, is not in the episode. Neither is the sentence two paragraphs on, where I say the EMF might turn out to be ten percent of the problem. I will say the underlying point again, though, because I meant it and I still do. I am not wedded to my theory that magnetic fields from the substation are contributing to the 49ers injuries. I could be wrong. What I am wedded to is the process of scientific inquiry, and the fact that we should be cautious around these exposures and we need more independently funded studies. 10. Three telling edits. They cut “I’m not a scientist” mid-sentence. What I said: “...and I am not certain of anything. I’m not a scientist. To me, I find the mechanisms compelling. I will go back to the fact that I got into this not because of the 49ers, but because of clients I was working with who suffer from EDS...” What aired: “...and that I am not certain of anything. I’m not.” The clip ends on the first two words of the sentence in which I say I am not a scientist, in an episode that spends considerable energy establishing that I am not a scientist. The full sequence is in Appendix A. They cut my own description of my work. Asked what I do, I said I run a wellness business, that I am focused on writing software to help people navigate environmental stressors, that environmental health is my focus, and that I also do independent journalism and research. What aired is the wellness business and the environmental health, with the software and the journalism removed from my own answer. The software engineering does come up later — narrated by them, as a hacker who grew up to write firmware — but my current work, in my own words, arrives as “wellness guy.” Thousands of commercial routers became home Wi-Fi. What I described: working at a wireless networking company surrounded by thousands of Wi-Fi routers, and a stress-induced health collapse afterward that working in that environment contributed to. What aired: Wi-Fi, the kind you have at home — reinforced by a clip of Christian McCaffrey talking about turning his router off at night. Three cuts, and every one of them makes me seem less credible. That is not a coincidence. 11. I gave them my own caveats and the test that would disprove me. In the first email I wrote that a well-designed chronic, ambient-level exposure study in tendon showing no collagen degradation, run over many months, would undercut my confidence in the theory. That is a specific, testable condition, stated in advance and in writing. There was a second interview, weeks later, which was not used in the episode, but in that I asked again for the falsification criterion to be included. What the episode presents instead is a man saying “we need more study,” which reads as a hedge, an open-ended request for the benefit of the doubt. It is the opposite of a hedge. Section 6 of my second email says, unprompted, that as far as I am aware there is not a single study showing EMF-driven oxidative stress degrading collagen in a human in vivo or in human tendon in a lab. I wrote that because it is true and because it is the first thing anyone should check. Under their standard it becomes the hinge of the entire first half, framed as something they had to surface without my cooperation. I had handed it to them five weeks earlier. And in the interview I said that my 25 to 50 milligauss readings were taken at knee level, and that these fields attenuate quickly, so by the time it reaches your head it is not that high anymore. That did not air either. The qualification arrives later, from Karipidis, as a correction. How you would actually study the injuries 12. They measured the wrong thing. The episode spends its final act on whether the 49ers are the most injured team in the NFL, finds no clean ranking, and lands on “injuries are random”. That is the wrong test. You would define the exposure — measured field levels at the facility — and the outcome narrowly: soft-tissue injuries, not a single MSK injury count that a broken finger and a ruptured Achilles both land in. Then you would compare the 49ers to themselves before and after the exposure changed, and compare that change against every other team over the same window. That controls for league-wide shifts in rules, turf and training load. It is a difference-in-differences design, and it is standard. I sent them that argument on July 28th, in writing, along with the fact that in eleven of the past twelve seasons the 49ers had finished top ten in Adjusted Games Lost. And by the episode’s own reporting, the 49ers are second in games lost to injury over the past decade, with FTN’s Aaron Schatz confirming that once you adjust for starters they come out second worst in the league — after having been one of the healthiest teams for years before that. A finding like that is where an investigation starts, not where it stops. 13. I did a lot of substation research for the episode that was never aired. I had reported that the substation next to the facility was expanded in 2014. That was wrong, and Rose Rimler and I sorted it out together. They gave me credit on air, which I appreciated, but framed it as a concession on my part to something they had found. In fact I had been investigating it myself, was uncertain before they asked, but was waiting for clarification from Silicon Valley Power. The uncertainty centered around a substation named “Esparanca” that was proposed right behind the facilities as part of the stadium construction, but now appears to never have been built. I spent days in Silicon Valley Power’s records, and did eventually reach Silicon Valley Power for confirmation and indentified the mistake myself. I also gave them highly detailed documents on what we do know about those facilities: new equipment installed between 2010 and 2014, and load growth across the system with an inflection around 2013–2014, with the Northern Receiving Station carrying the highest capacity in the system and sitting closest to the data center corridor. None of that is in the episode. I have a separate piece about it coming out soon. *I cut 2 seconds from the raw audio to remove personal information that had no connection to anything in the episode. Appendix A: the passage the clip was taken from This is the sequence from my first interview, in full. The episode uses one fragment of it. It’s tricky because my understanding is that there’s something like a 15-year half-life on collagen remodeling issues. They’re going to get a new crop of players. What I really need, though, is for the injuries to be broken down so we can see the soft tissue injuries. Right now, they’re categorized as MSK injuries, but let’s say we can actually identify them more specifically. Is that right? He was able to do that? Oh, cool. I wasn’t able to find that information. Interesting — I didn’t know that data existed. I tried so hard to get it, and I didn’t know it was available. Maybe you could connect me with that person. That would be amazing. I’m not wedded to it being an EMF, honestly. I’m not. I would say that, to a certain extent, I’ve staked my reputation on the fact that it needs more study. It’s important to look into it, and I am not certain of anything. I’m not a scientist. To me, I find the mechanisms compelling. I will go back to the fact that I got into this not because of the 49ers, but because of clients I was working with who suffer from EDS, Ehlers-Danlos Syndrome, a tendon hypermobility issue. This condition is documented to be partially caused by oxidative stress. I’ve worked with them to mitigate their EMF exposure and have seen people improve. I think it’s a bigger story. In a way, the 49ers represent an occupational cluster with specific exposure risks. If someone would conduct a study on this, I believe we could learn a lot. Perhaps we would discover that it’s like, okay, maybe it’s 10% of the problem. I don’t know the exact number, but I think either way, conducting the study would provide valuable insights. To directly answer your question, it’s challenging for me because it’s part of a bigger story. If the 49ers move and stop having injuries, I might conclude that it was related to the substation. However, if they move and still experience injuries, I would want to analyze the nature of those injuries. Are they primarily soft tissue injuries? I don’t think it’s necessarily a case closed, but the story might lose traction at that point regardless. Three things are worth noting. The aired fragment stops immediately before the sentence in which I say I am not a scientist — the cut described in item 10. It also stops four paragraphs before the words “to directly answer your question.” What the episode plays is the throat-clearing. The actual answer, about what would change my mind, never airs. And two paragraphs in, I say the EMF might turn out to be ten percent of the problem. That is the ranking the episode says I never gave. Appendix B: the full email, July 6th, 1:39 PM Hi Rose, You asked me to send you some studies a couple of weeks ago. I apologize for the delay. I have been incredibly busy. I also wanted to give you a chance to dig in yourself, and get your own perspective before I influenced you too much with mine. That said, I do want to make sure that the actual argument is abundantly clear, so here it is! One note before I begin, there are really two separate questions here: Does the substation cause the soft-tissue injuries? That was my specific claim, and what the podcast is about. Is the theory biologically sound? Can 50/60 Hz fields at these levels do anything biological below the safety limits? Question two is why people have been calling me a conspiracy theorist. The regulatory and advisory bodies (ICNIRP, etc) maintain that anything below their exposure limits is biologically inert, and that position is broadly accepted within the mainstream, but the actual science paints a different picture. To defend my theory I’ve had to defend a much larger claim: that the advisory bodies have the biology wrong. I can’t honestly answer question 1 without first addressing that. Here’s is a simplified outline of my theory, with links to studies: 1. Advisory body thresholds for biological effects The ELF magnetic-field limits (ICNIRP’s ~2,000 mG public / 10,000 mG occupational) exist to prevent acute effects from exposure. If a magnetic field is strong enough, it makes nerves fire and muscles contract. Muscles twitch. You can see faint flashes of light in your vision. People can even feel tingling or even a shock. That happens due to Faraday’s law, which states that a time-varying magnetic field induces an electric field inside the body via the creation of Eddy currents.The standards assume that those currents do nothing below the twitch threshold. They do not consider chronic effects at all. My argument is that they are biologically active and do have chronic effects. 2. There are multipe ELF-EMF mechanisms for inducing oxidative stress. This is basic biophysics. Below are the two primary mechanisms. Simplest first. Dr. Paul Héroux of McGill has the most intuitive explanation, which rests on Maxwell’s principle of superposition: because Maxwell’s equations are linear, two sets of electromagnetic waves sharing the same space simply add together. In the interview I pictured a pebble dropped into a pond, sending out clean ripples. Then a boat motors past at distance, sending larger waves, and where they meet the ripples, the two add together and the original pattern gets distorted. In our cells, the mitochondria run on continuous currents of electrons and protons that carry their own faint electromagnetic fields. An external field from a substation, by the principle of superposition, adds to those internal currents and shifts the pattern. The electron transport chain in the mitochondria leaks a fraction of its electrons by design as reactive oxygen species (ROS), which act as signalling molecules in a healthy cell. Distorting that field increases that electron leakage, creating oxidative stress. A tiny electromagnetic interference results in a large downstream effect. https://www.sciencedirect.com/science/article/pii/S2405844025006474 The more complex pathway is Dimitris Panagopoulos’s Ion Forced-Oscillation / Voltage-Gated Ion Channel (IFO-VGIC) mechanism. Weak, polarized, low-frequency fields force the ions (calcium, potassium, sodium) next to an ion channel’s voltage sensor to oscillate; because that force scales with the inverse cube of the distance involved, fields far below the stimulation threshold can still force the channel open, disrupting the cell’s ion balance and driving ROS overproduction (Nitric oxide and superoxide interact and produce peroxynitrite, a highly unstable cytotoxin that breaks down into free radicals). https://www.researchgate.net/publication/366088934 https://www.spandidos-publications.com/ijo/59/5/92 https://www.mdpi.com/1422-0067/22/18/10041 https://www.frontiersin.org/journals/public-health/articles/10.3389/fpubh.2025.1585441/full https://pmc.ncbi.nlm.nih.gov/articles/PMC3772193/ 3. Evidence of oxidative stress, in vivo, in humans from ELF-EMF There are many studies, and the strongest are occupational, which applies to the 49ers situation. 115 power-plant workers vs. 145 office controls. Serum malondialdehyde (MDA, the standard lipid-peroxidation marker), superoxide dismutase, and catalase were all significantly higher in the exposed group, and the markers rose with increasing field exposure. https://journals.sagepub.com/doi/abs/10.3233/WOR-203244 A follow-up where they reversed the oxidative stress in power plant workers. A double-blind randomized controlled trial: 91 power-plant workers given vitamin E, vitamin C, both, or placebo for 90 days. The antioxidant groups showed reduced lipid peroxidation and raised antioxidant capacity versus controls. https://pubmed.ncbi.nlm.nih.gov/32191586/ A spot-welder study: 46 welders occupationally exposed at 50 Hz, showed significantly altered red-blood-cell antioxidant enzyme activity and concluded ELF-MF “might act as an oxidative stressor… even at the recommended levels of exposure.” https://pubmed.ncbi.nlm.nih.gov/18504600/ A substation-specific study found oxidative stress and DNA damage https://pubmed.ncbi.nlm.nih.gov/24460415/ 4. Oxidative stress degrades collagen This half isn’t controversial at all. Oxidative stress activates the matrix metalloproteinases (MMPs) that break collagen down and suppresses its synthesis. Here are three example studies: Siwik et al. 2001: Oxidative stress raises MMPs and lowers collagen synthesis in cardiac fibroblasts. https://pubmed.ncbi.nlm.nih.gov/11121376/ Fisher et al. 2009: Collagen fragmentation drives oxidative stress and elevates MMP-1 in aged human skin. https://pmc.ncbi.nlm.nih.gov/articles/PMC2631323/ Varani et al. 2006: Decreased collagen production in oxidatively aged skin. https://pubmed.ncbi.nlm.nih.gov/16723701/ 5. What about the study showing improved collagen synthesis I’m glad you asked this question, and I’m bummed we didn’t get to it in the interview because it is a great question, and very important to understand. Superficially it may appear to be a refutation of my theory, but I would argue that it actually supports the underlying argument. That study used a short, high-intensity pulsed dose: therapeutic-PEMF, the same type of field used clinically to stimulate bone and tissue healing. The reason this works is because it triggers the very same biological pathways that can lead to oxidative stress. The exposure still stimulates ROS production, but done at a controlled dosage, for a limited duration it has a different effect. The cell reads the ROS as a warning signal and it upregulates its antioxidant defenses, and mounts a repair/proliferation response. The therapy is then stopped before the cell gets overwhelmed. That is essentially a hormetic response: a small dose of a stressor producing a beneficial adaptation. Two things follow: At the very least, this means the field is biologically active, which by itself undercuts the regulatory claim that these fields are inert below their thresholds. There is a wealth of literature on PEMF (pulsed EMF) bone regeneration and calcium channel signalling (which is the second mechanims in section one). Here is one. https://www.nature.com/articles/srep13856 At best, it leads us straight to my actual concern, which is that under chronic, chaotic and unregulated exposure, the cell’s antioxidant capacity gets overwhelmed, resulting in oxidative stress. There are plentiful examples of things that are beneficial at controlled doses, but harmful at uncontrolled doses. Excecise is one obvious, uncontroversial example. Botox is perhaps a more interesting example. 6. What about a study that shows EMF causing collagen degradation in humans? As far as I am aware there is not a single study showing EMF-driven oxidative stress degrading collagen in a human, in vivo, or in human tendon in a lab. There are studies involving isolated fibroblasts though, which secrete collagen. The most relevant one showed that human fetal scleral fibroblasts exposed to 50 Hz ELF-EMF showed a significant decrease in collagen synthesis and that MMP-2 expression was upregulated, which is the exact mechanism I described in section 2. https://pmc.ncbi.nlm.nih.gov/articles/PMC3626379/ That’s it! Thanks again for the interview. Best, Peter Anthony Cowan Environmental Health · Wellness Tech · Researcher & Journalist Publisher & Editor, Living Energy Bio: petercowan.comSocial: X · Instagram · TikTokApp: sunlightis.lifePhone: [redacted]
Suki and MedStar Health’s National Center for Human Factors in Healthcare Partner to Pioneer the Science of Ambient AI Adoption
Suki, the leading Ambient Clinical Intelligence (ACI) platform, and MedStar Health’s National Center for Human Factors in Healthcare are announcing a strategic research collaboration. This partnership aims to study the impact of ambient AI on healthcare delivery.
Suki and MedStar Health’s National Center for Human Factors in Healthcare Partner to Pioneer the Science of Ambient AI Adoption
Suki, the leading Ambient Clinical Intelligence (ACI) platform, and MedStar Health’s National Center for Human Factors in Healthcare are announcing a strategic research collaboration. This partnership aims to study the impact of ambient AI on healthcare delivery.
Ultimate Astros Playoff Lineup: Houston’s All-Time October Starting 9
Fret not with that hovering malaise permeating from St. Petersburg’s aftermath. The ambient rawness of a series loss in Tampa is still fresh, but we have the perfect cure. It’s time to unveil my “All October Squad” throughout the various decades. This might be the only list you’ll ever find without the likes of Bagwell […]
The politics and possibilities of ‘AI could kill us all’
I found myself fielding a lot of questions from folks who don’t usually talk much about AI this week. They were mostly along the lines of “do you think AI is going to kill us all?” or “how worried should I be about this human extinction stuff?” Motivating this wave of existential anxiety was the highly dramatic resignation of now-former Anthropic employee Jacob Coxon, who quit his job while publicly sharing his concerns about safety practices at the leading AI companies. More specifically, he declared that almost everyone at OpenAI and Anthropic, the leading AI labs, believes that there’s a decent chance the AI systems they’re producing could “kill us all” by the end of the decade, and the companies aren’t “acting responsibly.” Other AI safety researchers, including those still employed at Anthropic and OpenAI, all confirmed that yes, Coxon is correct, they’re all worried that their company’s products might prove fatal for the entire human race as well. Two more AI employees quit and joined the chorus. Now, the warning shot has been covered everywhere from the Wall Street Journal to Fox News to WIRED to the Guardian. I understand why all this sounds scary, but my response to those who have asked, has generally been: No, you don’t need to worry that AI will kill go rogue and kill us all. But that does not mean we shouldn’t worry, period. Far from it. The companies building AI products are now among the wealthiest and most powerful entities in the world. And they very much are building enormous engines of mass surveillance, extraction, and automation. They can and have allowed their AI systems to carry out felony hacks of other companies, provided the government with autonomously generated kill lists, and sold enterprise technology to firms around the world that is explicitly intended to replace jobs. But “AI” has done these things not because they have all-powerful minds of their own but, ultimately, because people have programmed, calibrated, and directed them to. In other words, it’s not AI we need to worry the most about. It’s the people and corporations working to profit from and gain power by deploying it. The technology is sophisticated, sure, and, especially in cybersecurity contexts, potentially disruptive to plenty of existing systems. But if we want to stop this predatory, profiteering, and extractive form of AI—and it’s worth noting that at this point, most people do—we absolutely can. A quick note/plea: I can only do all of this with the support of readers like you, so if you find value in independent, critical tech journalism and analysis, please consider becoming a paid subscriber. I want to keep as much of this un-paywalled as absolutely possible, and I need your support to do so. Many thanks to all who continue to chip in, it’s very much appreciated. Onward. Subscribe First, some context: AI industry folks like Coxon have been discussing the prospect that AI will destroy humanity for years. Even before the beginning of the AI boom, many working in the industry, from the executive staff to the rank and file researchers, have obsessed over ‘x-risk’, or the possibility that AI will become sentient or semi-sentient and move one way or another to exterminate humanity. This is ostensibly why Elon Musk bankrolled OpenAI in the first place, and is the grounds for his lawsuit alleging OpenAI betrayed its charter by abandoning its nonprofit status to become a commercial enterprise. Many AI engineers and startup founders have calculated their own personal p(doom), or the probability that the tech product they are working on will initiate an actual humanity-extinguishing apocalypse. 10-25% p(doom)s are pretty common. (I wrote about a long weekend I spent among these folks at one of their top conferences here, to give you an idea of their ideas and belief systems.) Sam Altman himself drove the narrative of the imminent rise of a super-powerful AI, or artificial general intelligence, to prominence by declaring that the technology he was building posed an existential risk to humanity. This idea is in other words baked into the DNA of modern AI companies and into the products they engineer. It’s also why the industry is routinely accused, by myself and others, of “doom marketing,” ie, using such proclamations and framings to impart the sheer power of the technology behind your product onto investors, partners, consumers, and the state. Some ambient understanding of this tendency may have helped prevent the press from repeating the claim every time one of the x-risk folks made it over the years, including when they quit their jobs at AI companies while doing so. Yet Coxon’s AI x-risk alarm has broken containment, as they say, and has exposed the idea to the mainstream media once again. This has happened, I think, for a number of reasons. First, when AI CEOs were going around saying AI might kill everyone in 2023, their companies were well-capitalized, but not nearly to the extent they are today. They were more easily dismissed as eccentric geeks of the sort that Silicon Valley is supposed to produce. Now, not only do their products have much greater market saturation, but people are more aware of a) the often unethical ways the executives and companies comport themselves b) the other adverse impacts of AI that have already arrived, and c) the physical cost of building these systems, particularly when it comes to data centers. Finally, toss in the constant stream of headlines in 2026 about AI models going rogue or potentially upending the world’s infrastructure. [ ](https://www.bloodinthemachine.com/p/with-the-backlash-to-data-centers) [ With the backlash to data centers, Flock and AI glasses, a mass opposition to big tech is underway. Silicon Valley is in denial. ](https://www.bloodinthemachine.com/p/with-the-backlash-to-data-centers) Brian Merchant · Aug 27 [ Read full story ](https://www.bloodinthemachine.com/p/with-the-backlash-to-data-centers) As a result, general sentiment was already overwhelmingly skeptical of AI and its overlords, so the table was pretty well set for someone to come along and say ‘just a reminder, the companies that are building the product that promises to take your job and leave a data center in your neighborhood also think that it might exterminate the human race’ and get a strong reaction from the media and the public. The question is: Should we understand this stuff as hype, strategically fanned to feed already swelling valuations? Is it doom marketing? Genuine cause for alarm that the infrastructure that undergirds modern life is facing a novel threat vector? Or reason to be sincerely worried that AI companies are amassing too much power, and that their products are genuinely dangerous? The answer, I’m afraid, is “yes.” Let me try to untangle all of this a bit, because arguments over how to navigate this moment are extremely heated right now, as they are essentially arguments over how to approach the politics of AI at a moment where there may be a unique opening for action. Those sympathetic to AI alignment concerns and x risk arguments—which increasingly includes a faction on the left who want to shut down AI over safety concerns—argue that people who dismiss AI as all hype have their heads in the sand. Meanwhile, critics of the x-risk narrative—which I might note includes a cadre of investors and tech folks on the right, too—argue that it is hype and can be used to further inflate valuations or for pursuing regulatory capture. The challenge is that many feel that dismissing AI as just hype or purely marketing also diminishes the urgency of taking on the AI industry as the novel and threat to labor, civil society, and the public sphere it is; others that by accepting the industry’s own terms, we imbue it with undue power and enable it. But let’s be clear: Declarations that AI is so powerful it might end the world are a kind of marketing, and anyone who says otherwise is just as off base as those who say that’s all that it is. If you don’t think that these sub-trillion dollar companies have higher-ups who noticed that when their founders talked about super-powerful dangerous AI they got spikes in media interest and phone calls from investors, or that those founders didn’t notice that themselves, and lean into certain narratives to advantage their products, then I don’t know what to tell you. Not all marketing is a Pepsi ad campaign with a celebrity spokesperson. Yet confronting the AI industry should certainly be considered an urgent project. Do I share the x-riskers’ fear that out-of-control, super-intelligent AI agents might end the world? I do not. I’ve read a good deal of AI extinction literature over the last couple of years and I have not come across a credible, step-by-step documentation of how exactly AI might move from self-recursively improving AI to killing every single human on the planet. Most of what I’ve read seems predicated on a sort of reverse Ian Malcolmian logic: Eventually, it becomes smart enough and AI, uh, finds a way (to exterminate humanity). Are the AI companies also overstating and dramatizing what their products can do? Yes, pretty much all the time. They’re in a knife fight for market share and are trying to win customers and government contracts before their investors come knocking. And yet. They have concentrated enormous amounts of compute, have extensive data collection and surveillance capacities, have inserted themselves into the state in numerous capacities, including military kill chains, and they are being run by egomaniacal billionaires who are rushing to monopolize an entire new market. The way I think about their most recent frightening-seeming exploits is not as a “swarm of rogue AI agents building a new civilization” or whatever, but as corporations with a hitherto-unimaginable amount of compute at their disposal recklessly experimenting with automation programs, completely unafraid of any repercussions because we have been unwilling or unable to impose any on them. So I think we should welcome any newfound imperative to hold them accountable. I also think that ultimately, the AI critics, Pause AI folks, leftists, doomers, effective altruists, and, honestly, most of the public, want a lot of the same things: legitimate checks and limits on AI companies’ power, actual transparency into what the companies are doing, and for more of AI to be under public control. (Ultimately, a lot of what animates the x-risk fears are rooted in just that: a fear of losing control.) How we move towards all this, exactly, is the question of the day, and while there’s much to be argued over in terms of building a viable political platform to challenge the AI industry’s power, I do want to cast a vote against one particular approach. Not to pick on Chris here, as there are a lot of folks out there proposing stuff like this, and the policy ideas actually stem from AI safety groups. But not only would this be challenging to land politically (I can already hear the ‘China will beat us to AGI’ calls) and all but unworkable in practice, this approach is a) far too limiting, b) fails to address the current harms caused by AI and c) would likely only wind up serving Anthropic and OpenAI; it’s what regulatory capture looks like in action. Full model transparency is the floor for what should be on offer here. If these companies believe their products will kill us, the very least we deserve is to know how. It’s in the public interest. I would also argue we might get a lot of the way to stopping any currently envisioned robot apocalypse simply by forcing AI companies to assume liability, and to submit to the full brunt of the law. If Sam Altman were liable to be charged with a felony for approving the hack on Hugging Face1, if Google was forced to pay defamation fines each time it published a false and injurious AI Overviews, these companies might suddenly find cause to restrain their models’ output, and we might hear less about rogue AI. We would need to introduce new frameworks and available tools for tracking automated lawbreaking, to be sure, but I’d wager that little would frighten the AI companies more than actually being held accountable for what their products enable. To that end, Illinois has passed an AI liability law, which the industry fought tooth and nail, and Florida is considering one. The next steps would be towards moving AI under public control; again, it’s only reasonable, since everyone, not just AI insiders, should get a say over how a technology whose developers say might kill us is developed and deployed. Dismantling the whole industrial project as currently structured should be on the table, too, pending democratic input. But that’s for another post. For now, suffice to say that while I won’t be losing any sleep about an AI-enabled extinction event, Mr. Coxon and co. have given us an opportunity to underscore the urgency of the clear and present damage AI companies are doing, the extreme power they wield and the extent to which they hold themselves unaccountable, and the abundance of political capital there is out there for taking them on. Subscribe 1 Purely speculative! I do not know if he did or not.
This week in Santa Cruz County business: Paystand branches into AI agents; court hearing for former Scotts Valley executive; Barilla snaps up Goodles
In this week's survey of local business, Jessica M. Pasko reports on the rollout of a new AI tool for Santa Cruz-based fintech company Paystand, notes a court date for a former executive of Scotts Valley's Ambient Photonics and runs down other numbers, names and dates to know.
August Monthly Review: ChatGPT In Epic
Death, taxes, another frontier lab healthcare launch inspiring truly insane LinkedIn takes. As much as I want to stay away, I repeatedly am the crewman unplugging his ears whenever we pass these sirens. So it’s not the first and probably not the last time we dial up the typewriter rather than tie ourselves to the mast. The full blow-by-blow timeline: Health API Guy is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber. Subscribe The End of the Standalone PHR (Jan 8): ChatGPT Health arrives for consumers, at the time powered by b.well. I was bullish on the approach in that the best way for the PHR to finally solve distribution was to meet consumers were they already are (i.e. When Horizontal Meets Healthcare (Jan 9): OpenAI for Healthcare puts out the shingle for enterprises, with SharePoint ingestion standing in for the EHR integration the product actually needed. Another One: Anthropic’s Healthcare Debut (Jan 16): Claude's version, on HealthEx rails instead of b.well, with Agent Skills for FHIR development as the one true vertical-specific investment. ChatGPT for Clinicians: The Trap Sprung (Apr 24): OpenAI filled in the missing GTM middle with a free product for verified clinicians, effectively peeling the enterprise wrapper off ChatGPT for Healthcare and taking the PLG fight directly to OpenEvidence. OpenAI’s Second Attempt at Health (Jul 31): a relaunch of their patient specific app, now branded Health in ChatGPT, where the privacy partition came out, the connectors thinned, and b.well disappeared in favor of first-party FHIR work against a smaller network Beyond a Shingle So what was announced now? Today, we’re introducing a new electronic health record integration that brings authorized patient context from Epic into ChatGPT for Healthcare, along with the Healthcare Public Data plugin for direct, structured access to official healthcare datasets like PubMed, DailyMed, and CMS Coverage. Together, these capabilities bring ChatGPT closer to the systems and sources healthcare teams trust, while supporting the controls and compliance healthcare work requires. The core portfolio is unchanged from prior announcements we delineated and discussed (aside from the relaunch of patient-facing). Since trade publications still seem to be confusing them by using the wrong names: Enterprise sales motion: ChatGPT for Healthcare Protecting their core product / PLG: ChatGPT for Clinicians Consumer/patient-facing product: Health in ChatGPT So really, this is a feature release (specifically for ChatGPT for Healthcare when it comes to EHR integration). What’s cool about it, though, is that we are moving beyond just putting out a shingle. Everything in the January enterprise launch was horizontalizable: Horizontal tech companies thus generally start verticalization with their “putting out a shingle phase”. Telling the world you’re open for business as a horizontal tech company reliably attracts early inbound interest from buyers who are already trying to force-fit horizontal tools into domain-specific workflows and are eager for any signal that the vendor intends to support their use case more directly. Nothing was really vertical specific, which is exactly what you'd expect from the ultimate hypergrowth horizontal company dipping their toes into specific industries. But eventually you have to stop changing the sign on the door and start changing the product. Can you guess where the horizontal product was going to run out of road? This is the core dilemma writ large: verticalization requires differentiation, while scale economics of consumer and horizontal push toward unification. I’ve buried the lede so deep here it will be painful to some readers, but what should be shocking to no one is that my perspective is that EHR integration is the only path that meaningfully resolves this tension for ChatGPT for Healthcare. Integration with Microsoft Sharepoint is fine, but it is categorically insufficient for any product that hopes to influence clinical decision-making. SMART Money Well here we are, eight months later! Real vertical investment has begun, which surprised a few people. One friend in the industry messaged me: “Absolutely no way Epic gave ChatGPT API access.” Looking forensically at the announcements, the integration is notably read-only across appointment notes, laboratory results, medications, and specialist documentation. So while I’m not a betting man, I'd wager the house this is a SMART on FHIR launch: That sounds a lot like USCDI! The recommended path for the workflow they outline would be SMART on FHIR Their Health AI lead’s post is evocative of both standalone and EHR launch SMART, which another termed “ChartGPT” and “EHR Plugin” The implementation burden for SMART on FHIR is the lowest of the available integrative paths This is the team who literally did patient-facing SMART on FHIR with Epic last month Most importantly, if you’re a horizontal company, you generally still haven’t taken the full plunge and thus (overly) value reusability. SMART on FHIR is the logical compromise: healthcare-specific enough to matter, but standardized enough to reuse. Nobody Asked Judy Another friend asked “I thought they had to go to each health system, or did they go direct to Epic and now health systems opt in?” Given the trust paradigms in healthcare, this functionally cannot be Epic hoovering up all the data for OpenAI and shoving ChatGPT in their customers’ faces (or they would revolt). However, I do believe the aforementioned terrible coverage by TechCrunch and other outlets is probably responsible for that question, given the 325 million reference. When using FHIR as a business associate to an Epic customer, there is no EHR gatekeeping to speak of, as that isn’t how fhir.epic.com works: You register an app You pick your APIs You test against the sandbox APIs You list as “Ready for Production” Hospitals pick your app You test and go live with them Bluntly, nobody had to say yes or no in Verona (nor were they given the chance). Vendor Services (their next developer tier up that I doubt OpenAI is using quite yet in this initial release) certainly has contractual paperwork that some resent, but even there, the twin pressures of mounting antitrust and information blocking make outright gatekeeping increasingly fraught. My friend’s sentiment is, to me, representative of a broader industry neurosis, perhaps a sort of scar tissue of prior eras: people assume the gate is still there and never actually try the door. There are certainly other ways Epic (and any EHR) can put its thumb on the scale, but they are not so dumb as to stand in front of a federally mandated API and play bouncer at this exact moment in time. So I think they can and probably should go deeper, as this release is at best parity and at worst behind vertical-specific competition. OpenEvidence did a basic SMART launch with Sutter Health in February, allowing for more convenient evidence search by providers. They then add patient-context (the equivalent SMART on FHIR flow to what we see here) when Cedars-Sinai went enterprise-wide in May. UpToDate has four distinct applications across deeper workflows like patient engagement listed in Epic Showroom and announced a partnership with Epic to power Art at UGM Abridge and other ambient scribes have invested deeply into the deepest bidirectional clinical copilot workflow with integrations well beyond SMART on FHIR. In that light, the “Who is OpenAI primarily targeting here?” is clear. This release brings them into striking distance of OpenEvidence, but not the others quite yet. They are the only one of the three you can reach without building something truly Epic-specific. When will they go further? Competition is a great motivator to overcome the horizontal demons and start building things that can’t be reused: not across industries, not across EHRs, maybe not past the customer you built them for. That’s the price of actually verticalizing. The question is if and when OpenAI will be willing to pay it. Month in Review Here is the monthly review. As a reminder, this is a regular round-up of the month’s posts and other content to surface things you may have missed across regulation, litigation, interoperability, and beyond. AI assistance is used in these bullet summaries so I can focus on articles. Articles Published: None this month Video Content: The Information Exchange: Standards-based Thruple Edition (Aug 14): Back to school for us too, with Brad reporting in from the CMS Health Tech Ecosystem’s one year anniversary in DC. We get into the January CMS-0057 deadline, the fall rulemaking reading list, and why enrollment still keeps most apps off FHIR. The Information Exchange: Epic Dúnadan Edition (Aug 25): A UGM roundup with Ryan Brickner joining for the first time to check our takes against what the building actually thinks. Rangers, Ergo sitting on top of EHI, and a down-market lineup that needs some cuts. Regulatory: Stacked Deck, Bad Hand (Aug 05): ONC’s website refresh took the entire HIT Policy Committee record with it, so I rebuilt the archive and went looking for the regulatory capture story everyone assumes is buried in there. Stacking the deck and winning the hand turn out to be very different things. The Sixth Generation of Patient Access (Aug 19): A quick catalog of the five generations of patient access we’ve layered on since HIPAA, and the two candidates now competing to be the sixth. One is planned. The other is the market routing around the plan entirely. Court cases: Three Cases Walk Into a Docket (Aug 06): Two surprise settlements cleared the board in a single week, and then Judge Maddox dropped ninety-four pages on Vyne v. Henry Schein. The sleeper is a DMCA holding that makes direct-to-database a considerably riskier business model. Epic v. Health Gorilla: Into the MDL (Aug 10): Nine class actions are headed to Miami, and the Panel signaled it wants to bring the case that spawned them along too. That would leave Epic arguing the requests were obviously fraudulent in one courtroom and unknowable in the other. Amazon v. Perplexity: Agents Are Legalized! (Aug 11): The Ninth Circuit vacated the injunction against Comet, holding that the user is the one accessing the servers rather than the company that built the agent. A real win for agentic access, and a much narrower one than the headline suggests. Veeva v. Epic: Come At Me, Bro (Aug 26): Epic’s response brief wants the dismissal affirmed and, unusually, wants the opinion published as precedent. Buried in it is Epic’s own description of what its non-competes actually prohibit, which current and former employees should read closely. EHRs: The Contract Epic Would Never Sign Today (Aug 04): A 1999 SEC exhibit catches Epic licensing nearly its entire product line, Tapestry included, to the company that became TriZetto. The marketing services menu attached to it is the part that will make you blink. Forecast from Verona (Aug 07): The Epic Almanac makes one argument six different ways: the AI is only as good as the networks behind it. Emmie headlines, Art’s context stack is the most ambitious part, and Penny finally gets an autonomous coding date on the calendar. Works With Epic MyChart (Aug 17): Epic’s first new Showroom category since the death of Workshop certifies hardware instead of software, badge on the box and all. Made for iPhone, but for blood pressure cuffs, and rough news for anyone selling the RPM stack sitting in between. UGM Hot Takes 2026 (Aug 20): Everyone else covered the AI announcements, so I went after Savvy deleting the payment gateway, Rangers as Boost with the timer removed, and a down-market lineup with too many entries. Plus the Health Grid tidbits I cannot help myself on. MyChart Central Grows Up (Aug 24): Device data and Emmie turn Epic’s identity hub into a full consumer platform, which is both a logical answer to ChatGPT and a bit of a mistake. It also happens to be the best scraping target Epic has ever shipped. Industry Analysis: The Wrong Yardstick (Aug 12): Vertical software keeps getting judged against Superhuman and Notion, which is the wrong bar entirely. Your user is comparing your product to a whiteboard and forty phone calls before lunch. Primitives vs. Abstractions (Aug 27): Developers want building blocks, systems of record prefer to hand out business logic, and both sides have a real case. There’s no test from the outside that separates the engineering reason from the competitive one, which is why this keeps ending up in court. Cross-industry Comparisons: The Two Kinds of Platform Power (Aug 18): Attention power and record power are different problems that keep getting handed the same regulatory toolkit. Congress’s latest swing at Big Tech shows both what’s possible and where it falls apart. The Dogs of (Platform) War (Aug 21): A CourtListener alert turned up a property management fight with healthcare’s exact shape and none of the Cures Act. Shell prospects, ghost accounts, a notetaker bot that came back to haunt someone, and a lawyer arguing both sides of the same theory in two states. Fractals All the Way Down (Aug 31): Yardi dominates property management right up until you zoom into one segment, where AppFolio owns it outright and Yardi doesn’t appear at all. Where you draw the line around a B2B software market is about to decide an awful lot of cases. Other News: If Judy Had the Courage (Aug 13): A short eulogy for the era when software was allowed to look insane: WinAMP, bold colors, and everything the grey chatbot era has taken from us. External Media: Portland Monthly Health Tech Meetup: Erin O’Brien channeled my own feelings - maybe it’s just because it’s August and beautiful, but the monthly edition of the PDX Health community meetup was a ripper. Make sure to reach out if interested to join for the next one. STAT’s Coverage of Epic This Month: Brittany Trang of STAT did a fantastic job of breaking the FTC investigation that’s been lurking, as well as UGM related coverage, so I had to give her her wish of a meme. Fall Conferences: I’m pumped to be kicking off my fall conference season in NYC at Nabla Accelerate next month, which Chrissy provided the link to apply for. Here’s the rest of my schedule in case you want to meet up: Commonwell (Redwood Shores, CA): Oct 13-14 Open@Epic (Madison, WI): Oct 21-22 eHealthExchange (Austin, TX): Oct 27 Sequoia Project (Austin, TX): Oct 28-29 HLTH (Vegas): Nov 15-18 RSNA (Chicago): Nov 29-Dec 3 Posts I Liked: HTI-6 Should Unbundle API Certification: Josh Mandel makes the case that HTI-6 should split (g)(10) into separate authorization and data certifications, so a PACS or a genomics platform can certify only the role it actually performs. Imaging is the urgent example, but the structure solves a much bigger problem. On implementing ePrior Auth with Epic: Scott Rossignol’s field notes from a live ePrior Auth build on Epic, including the two app registrations nobody warns you about and the CPT mapping problem waiting at the end. CMS-0057 implementations are going to be such a beast. Healthcare point solutions are starting to look a lot like streaming services: Spencer Dorn runs the cable-to-streaming arc against health IT and lands squarely on the bundling half of the cycle. Bundling can be good! It can also be bad! Life is nuanced. Health API Guy is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber. Subscribe
Auto review: 2026 Nissan Frontier Pro-4X offers function over flash
There is an arms race underway in the automotive industry. Blackened chrome, LED strips, giant grilles, screens the size of suburban kitchen islands, illuminated logos, animated turn signals, ambient lighting
Artificial Intelligence helps Munson health care provider focus more on patients, less on screens
FORT LEAVENWORTH, Kansas — For Mikaela Altis, a physician assistant in Munson Army Health Center’s Department of Primary Care, adopting ambient listening technology has meant more eye contact with patients, more time for follow-up questions and fewer hours spent completing clinical notes after the workday ends.
iOS 27 beta 3 makes it easier to adjust AirPods Adaptive mode intensity
A new Listening Mode setting lets users more easily adjust how much ambient noise their AirPods allow through in Adaptive mode.
A Doctor At Home: The Rise Of Ambient Home Health Monitoring
There is significant opportunity to improve long term health outcomes with ambient home monitoring.
AI and Telemedicine Can Fill Healthcare Gaps, Execs Say – But Only If Washington Helps
Major health system leaders say investments in virtual care, ambient AI medical scribes, automated referrals and other new tech tools could ease a critical workforce shortage that struggles to keep up with widespread chronic disease and medical deserts. But they still need regulators to revamp ...
Is Abridge’s ‘patient centered’ claim a bridge too far?
In this edition of AI Prognosis, Brittany Trang takes a close look at ambient scribe developer Abridge's claim about being patient-centered.
After hospitals, patients get a turn to bring AI into the doctor’s office
Ambient scribes were the first large-scale application of AI in health care. Now developers are pitching them as diligent note-takers for patients.
Philips partners with Disney to incorporate iconic characters in MRI exams
The Amsterdam-based imaging manufacturer said it will utilize beloved animated characters and stories as part of the Philips Ambient Experience.
How to use ambient AI in healthcare as litigious winds begin to blow: 10 tips from experienced attorneys
As a class-action lawsuit gets rolling in California over the use of ambient AI in healthcare, a national law firm is drawing takeaways for hospitals and other provider organizations. Makes sense: All AI-equipped providers are potential targets for similar litigation now.
Defense Health Network Central rolls out ambient listening technology to enhance patient care
Defense Health Network Central providers are using a new tool to streamline clinical documentation and improve patient-provider interactions.
Ten times worse than benzene — California updates its science on two air contaminants
California health officials have released new scientific findings about health risks from exposure to two air toxics present in California's ambient air, acrolein and ethylene oxide.
How Google Is Moving The Needle On AI, Tony Stark-Style
Google DeepMind's new AI-powered pointer may change how humans interact with computers altogether.
World-renowned ukulele virtuoso Jake Shimabukuro plays the Englert
Jake Shimabukuro’s album “Calm Seas” blends his ukulele mastery with ambient recordings from Hawaii’s natural landscapes, creating a tranquil musical experience inspired by the ocean and forest sounds.
Building Healthcare Infrastructure With AI
AI healthcare uses data, ambient listening, and infrastructure to improve care, reduce workload, ensure privacy.
Photos of Patriots coach Mike Vrabel and NFL reporter at Arizona hotel are misleading, reporter says
In photos published by Page Six, The Athletic reporter Dianna Russini and the New England Patriots head coach are seen hanging out at the Ambiente luxury hotel in Sedona.
The Apple CarPlay Widgets Every iOS 26 User Needs to Enable Right Now
Maximize your dashboard with the best CarPlay widgets for iOS 26. From the new Ambient Music player to AI-powered voice bots and predictive traffic, here is what to install.
iOS 26.4 is here, with Playlist Playground and new emoji
There's also an ambient music widget and bug fixes.
iOS 26.4 adds brand new widgets for your iPhone’s Home Screen
iOS 26.4 comes packed with many new features, including brand new Ambient Music widgets that can be added to the iPhone’s Home Screen.
Greenway Health unveils AI-enabled EHR-RCM platform
Called Novare, it offers ambient note-taking, voice-activated chart search, agentic task helpers, intelligent coding suggestions, automated prior authorization, real-time benefit checks and more.
Greenway Health debuts AI-enabled EHR-RCM platform
Called Novare, it offers ambient note-taking, voice-activated chart search, agentic task helpers, intelligent coding suggestions, automated prior authorization, real-time benefit checks and more.
AI And The Workforce Reset In Healthcare
AI is restructuring healthcare delivery as workforce shortages intensify. From ambient scribes to AI-enabled imaging, leaders redesign care around capacity.
Scientists synthesize stable N₄ radical anions under ambient conditions
A team of scientists from the University of Manchester and Oxford have synthesized stable nitrogen chain radical anions under ambient conditions. These molecules, which are normally too reactive to isolate ...
Samsung announces the start of One UI 8.5 update rollout
While the Galaxy S26, S26+, and S26 Ultra ship with One UI 8.5 out of the box, Samsung has confirmed a sequential update rollout for older devices. It is a visual and AI reset built around two pillars: Ambient Design and a Perplexity-powered Bixby. Samsung confirmed that stable builds will begin rolling out in March […]
This week in Santa Cruz County business: Scotts Valley solar cell company goes dark; passing the torch at Alta Organic Coffee
In her weekly look at Santa Cruz County business, Jessica M. Pasko reports on the demise of Ambient Photonics, notes a generational shift at a local coffee roaster and delivers names, numbers and events to know.
The LG G6 OLED TV is brighter than the G5 and blacker in ambient light – but it doesn’t support Dolby Vision 2
2026 is the year of “Hyper Radiant Colour Technology”
KDE Plasma 6.6 Finally Supporting Ambient Light Sensors, Fixing Windows Games With HDR
There are some nice KDE Plasma 6.6 improvements that were merged ahead of Christmas.
AI Prognosis: Were experts right about their 2025 health AI ‘bingo cards’?
AI Prognosis newsletter readers weigh in on 2025 predictions about ambient scribes, antibody design, AI agents, and more.
LCMC Health Selects Nabla to Power Systemwide Ambient AI Implementation
Nabla, one of the most widely adopted AI assistants in clinical care, has been selected by LCMC Health to power a systemwide rollout of its advanced ambient AI technology across the New Orleans–based health network.