Scar Tissue
The medical device industry doesn't want you to read this. Every adverse event, every recall, every late report — graded, graphed, and named.
Channel: Scar Tissue Tagline: The medical device industry doesn’t want you to read this. Every adverse event, every recall, every late report — graded, graphed, and named. Niche: Consumer-facing medical device adverse event and recall accountability intelligence — automated manufacturer report cards, per-device safety scorecards, late-reporting surveillance, 510(k)-vs-PMA approval pathway risk analysis, Class I recall alerts, and weekly “Incident Report” dispatches that translate raw FDA MAUDE data into gorgeous, opinionated, name-and-shame data journalism. Not scare content. Evidence content. Target audience: Patients with implanted or wearable medical devices (100M+ Americans), caregivers researching devices for family members, healthcare professionals tracking safety signals, medical device litigation attorneys, health journalists, patient advocates, biomedical engineers, and the 1.2-million-people-per-year whose adverse event reports were filed late by manufacturers and never knew it. Also: anyone who’s ever Googled “[device name] recall” or “is my [device] safe?” — a search pattern that generates millions of queries per year. Why now: A landmark BMJ study (March 2025) revealed that 1.2 million+ adverse event reports were filed late by device manufacturers — some years after patients were injured or killed. The FDA’s MAUDE database receives ~500,000+ reports per year, growing rapidly. The EU’s EUDAMED database is going public (2025-2026), enabling cross-jurisdiction transparency for the first time. Meanwhile, the 510(k) “substantially equivalent” clearance pathway — which lets devices reach market without clinical trials by claiming similarity to a predicate device — is under increasing scrutiny. ICIJ’s “Implant Files” investigation (2018) proved massive public interest, but it was a one-time project. Nobody is doing this continuously, automatically, with data-first rigor. The openFDA API makes all of this free and machine-readable.
Content Example:
Headline: Intuitive Surgical’s Stapler Problem Is Worse Than the Recall Suggests — A MAUDE Deep Dive
Incident Report #47 — April 2026
On March 19, 2026, Intuitive Surgical issued a Class II recall for its 8mm SureForm 30 curved-tip stapler reload cartridges after reports of four serious injuries and one death. The company described a manufacturing defect where staple legs could separate, causing tissue damage during robotic surgery.
That’s what the recall notice says. Here’s what the data says.
Scar Tissue pulled every MAUDE adverse event report mentioning Intuitive Surgical stapler systems filed in the last 36 months. The numbers tell a different story than a single recall notice:
By the numbers:
- 247 adverse event reports involving Intuitive Surgical stapler/reload devices since January 2023
- 14 reports coded as “death” — meaning the device was at least a contributing factor
- 89 reports coded as “injury” — requiring surgical intervention, transfusion, or extended hospitalization
- 144 reports coded as “malfunction” — device failed during procedure but patient outcome unclear
- Average reporting lag: 47 days — nearly 7 weeks between when Intuitive learned of the event and when FDA received the report. Legal requirement: 30 days for deaths, 30 days for serious injuries
- 12% of reports filed after the 30-day legal deadline — including 3 death reports
The predicate chain problem: The SureForm stapler system was cleared through the 510(k) pathway in 2018. Its predicate device? An earlier Intuitive stapler. That stapler’s predicate? A non-robotic Ethicon stapler from 2004. Three generations of “substantially equivalent” clearances — meaning no independent clinical trial data was required to put this device inside patients. The FDA never required Intuitive to prove the robotic stapler was safe. They only required Intuitive to show it was similar enough to a previous device. This is how the system works. This is the system.
Manufacturer Report Card — Intuitive Surgical (Q1 2026):
| Category | Score | Detail |
|---|---|---|
| Total MAUDE reports (12mo) | 🔴 1,847 | Top-10 device manufacturer by volume |
| Death reports (12mo) | 🟡 23 | Above median for surgical device makers |
| Late filing rate | 🟡 11.3% | Industry average: ~9% |
| Active Class I recalls | 🟢 0 | No highest-severity recalls active |
| Active Class II recalls | 🔴 3 | Including the stapler reload |
| 510(k) reliance | 🟡 87% | High proportion of devices cleared without clinical trials |
| Overall Grade | C+ | Below industry median for large-cap surgical device companies |
What should patients do? If you have a robotic surgery scheduled using the da Vinci system with SureForm staplers, you deserve to ask your surgeon: “Are you using the recalled reload lot?” Your surgeon might not know — hospitals manage their own inventory. The recalled lots (listed below) cover cartridges distributed between October 2024 and February 2026. Print this page. Bring it to your pre-op appointment.
Sources: All data from openFDA Device Adverse Event API (MAUDE), openFDA Device Recall API, and FDA 510(k) clearance database. Methodology and raw query parameters published on our Transparency page. Scar Tissue does not provide medical advice.
Data Sources:
- openFDA Device Adverse Events API —
https://api.fda.gov/device/event.json— millions of MAUDE reports with device name, manufacturer, event type (death/injury/malfunction), dates, narrative text. Free API key: 240 req/min, 120K/day - openFDA Device Recall API —
https://api.fda.gov/device/recall.json— all FDA device recalls with class, reason, distribution, manufacturer - openFDA 510(k) API —
https://api.fda.gov/device/510k.json— clearance history, predicate device chains, applicant info - openFDA PMA API —
https://api.fda.gov/device/pma.json— pre-market approval data for comparison - openFDA Device Classification API —
https://api.fda.gov/device/classification.json— device types, risk classes - FDA MDR Bulk Data Files — quarterly CSV dumps for historical database building
- PubMed E-utilities API — for linking adverse events to peer-reviewed failure studies
- OpenAlex API — for scholarly research context on device safety
- EU EUDAMED — European device registration and emerging vigilance data for cross-jurisdiction comparison
Automation Pipeline:
- Schedule: GitHub Actions runs daily at 06:00 UTC (catches overnight FDA data updates)
- Collect:
- Query openFDA adverse event API for new MAUDE reports filed since last run
- Query openFDA recall API for new/updated recalls
- Query 510(k) API for new clearances (to build predicate chain analysis)
- Check PubMed for new publications mentioning devices with active safety signals
- Pull quarterly MDR bulk files when available (for database refresh)
- Process:
- Classify new adverse events by severity, device type, manufacturer
- Calculate manufacturer “late filing” rates (compare event date to report date)
- Update rolling manufacturer scorecards (12-month window)
- Identify emerging safety signals (statistical spike detection on per-device adverse event rates)
- Build/update predicate device chain graphs for flagged devices
- AI generates weekly narrative dispatch from highest-signal events
- AI writes per-device deep dives when a new Class I recall drops or death cluster appears
- Generate:
- Manufacturer report card graphics (SVG letter-grade cards with stat breakdown)
- Adverse event trend charts (D3.js line charts per device/manufacturer)
- Recall severity timeline visualizations
- Late-reporting gap analysis charts (event date vs. report date histograms)
- Body-region heatmap for injury locations
- 510(k) predicate chain diagrams (graph visualizations showing how devices trace back through decades of “equivalent” claims)
- Publish: Astro static site build → Cloudflare Pages deploy. RSS feed. Email newsletter via Buttondown.
Tech Stack:
- Static site: TypeScript + Astro (content collections for each device/manufacturer/dispatch)
- Image generation: D3.js for charts/graphs, SVG template renderer for report cards, Mermaid for predicate chain diagrams
- Data collection: TypeScript scripts using openFDA REST API with pagination
- Database: SQLite for local MAUDE event storage and deduplication
- CI/CD: GitHub Actions (daily collection + weekly dispatch build)
- Hosting: Cloudflare Pages (free tier, global CDN, generous limits)
- Newsletter: Buttondown (free up to 100 subscribers, then $9/mo)
Monetization Model:
- Donations/Tips: Buy Me a Coffee, GitHub Sponsors, Ko-fi — “keep the lights on for device safety journalism”
- Newsletter Premium Tier: Free weekly dispatch for everyone. Paid tier ($5/mo) gets: manufacturer deep-dive reports, custom device watchlists with email alerts, early access to analysis
- Professional/Legal Tier: $29/mo — API access to processed MAUDE analysis, bulk manufacturer report cards, expert witness research packages. Medical device lawyers spend $50K+ per case on exactly this kind of analysis
- Affiliate: Medical alert services, patient advocacy organization memberships
- Sponsorship: Patient advocacy orgs, health journalism foundations (unlikely to get device manufacturer sponsors — and we don’t want them)
- Projected month-1 revenue: $200-500 (donations from early passionate users, especially from device-specific communities)
- Projected month-6 revenue: $3,000-8,000 (newsletter premium uptake + first legal professional subscribers + growing SEO traffic)
- Projected month-12 revenue: $8,000-20,000 (the legal/professional tier alone could drive this — one law firm subscription = $348/year, and there are thousands of med-mal firms)
Launch Complexity: 3/5 — openFDA APIs are well-documented and generous. Main complexity is building the statistical analysis pipeline and the predicate chain graph builder. Astro static site is straightforward. Estimated: 2-3 weeks to MVP.
Content Quality Score: 5/5 — This is investigative data journalism powered by government transparency data. The BMJ study proving late reporting gives instant credibility anchor. Every claim sourced to a federal database. The “manufacturer report card” format is genuinely novel and useful.
Automation Score: 4/5 — Daily data collection fully automated. Weekly dispatch generation fully automated. Deep-dive articles on new Class I recalls need AI synthesis but can be templated. Only manual element: occasional editorial review of AI-generated narratives for sensitive death reports.
Revenue Potential: 5/5 — The legal professional audience alone is a goldmine. Lawyers pay $500/hour and spend weeks doing manual MAUDE research. A $29/mo tool that automates it is a no-brainer. Add consumer donations, premium newsletter, and the inevitable media citations (journalists will link to your manufacturer report cards), and this has strong multi-stream revenue.
Total: 17/20
Soul & Character:
- Name: Scar Tissue — evocative, memorable, implies both the physical scars from device failures and the institutional scar tissue of a regulatory system that favors speed over safety
- Mascot: A scarred anatomical heart illustration rendered in blueprint/technical drawing style — medical meets mechanical. The heart has visible suture lines and a small barcode on it. It’s beautiful and unsettling.
- Voice: The voice of a veteran medical device engineer who quit the industry because they couldn’t stomach the 510(k) loopholes anymore. Precise. Clinical. Occasionally furious — but always backed by data. Never hysterical, never conspiratorial. The kind of person who says “let me show you the numbers” and then the numbers are devastating.
- Opinion: Scar Tissue believes the 510(k) “substantially equivalent” pathway is the biggest consumer safety loophole in American regulation. It believes manufacturers who file adverse event reports late should face automatic penalties. It believes patients have a right to know the full safety profile of every device in their body. It is not anti-device or anti-technology — it celebrates the devices that work. It just believes transparency is non-negotiable.
- Running segments:
- “The Incident Report” — weekly dispatch covering the most significant adverse events and recalls
- “Report Card Day” — quarterly manufacturer grades with trend arrows
- “The Predicate Chain” — monthly deep-dive tracing a device’s 510(k) ancestry back to its original predicate, revealing how far the device has drifted from what was actually tested
- “Late Notice” — the late-reporting accountability segment. When we catch a manufacturer filing months late, we publish the gap timeline
- “The Device Autopsy” — detailed failure-mode analysis when a specific device causes a cluster of adverse events
- Visual style: Clinical white backgrounds with red accent highlights (#CC0000). Blueprint-style technical illustrations. Data-heavy but clean. Monospaced font for data callouts. The aesthetic of a declassified government report redesigned by a world-class graphic designer.
Why This Will Work:
- The data is free, rich, and machine-readable — openFDA gives you 120K API calls/day for free. MAUDE alone has millions of records with structured fields plus narrative text for NLP analysis
- The ICIJ proved the demand — “Implant Files” was one of their most-read investigations. But it was a one-time project. This is the always-on version
- Long-tail SEO is massive — every device recall, every adverse event cluster, every manufacturer generates specific search queries. Thousands of auto-generated pages, each targeting real search intent
- The legal profession will pay — med-mal and mass tort attorneys need exactly this data, analyzed and presented. They currently pay consultants thousands for manual MAUDE analysis
- Trust through transparency — every claim links to the specific API query that produced it. Methodology page shows the code. This builds the kind of trust that generates donations
- Emotional resonance — these aren’t abstract statistics. Every death report in MAUDE is a person. The narrative excerpts are gut-wrenching. People share this content because it matters
Risk & Mitigation:
- Legal risk from manufacturers: Mitigation: every claim sourced directly to federal government data. We’re not making allegations — we’re presenting the FDA’s own records. This is the strongest possible legal shield
- AI generating insensitive content about deaths: Mitigation: death-related dispatches get an extra review template that ensures respectful, factual tone. No sensationalism
- FDA data quality issues (MAUDE has known reporting inconsistencies): Mitigation: transparent methodology page explaining limitations. We note when data quality may affect analysis. This actually builds credibility — acknowledging limitations shows rigor
- Industry pushback/SLAPP threats: Mitigation: all data is federal public records. Scar Tissue is a publication, protected by First Amendment. Consider incorporating as a 501(c)(3) for additional protection and donation tax-deductibility
- Competition emerging: Mitigation: first-mover advantage in automated analysis. The data pipeline and historical database create a compounding moat. New entrants would need months to build comparable historical analysis