Nurses Say Hospital Adoption of Half-Cooked ‘AI’ Is Reckless

An anonymous reader quotes a report from Techdirt: Last week, hundreds of nurses protested the implementation of sloppy AI into hospital systems in front of Kaiser Permanente. Their primary concern: that systems incapable of empathy are being integrated into an already dysfunctional sector without much thought toward patient care: “No computer, no AI can replace a human touch,” said Amy Grewal, a registered nurse. “It cannot hold your loved one’s hand. You cannot teach a computer how to have empathy.”

There are certainly roles automation can play in easing strain on a sector full of burnout after COVID, particularly when it comes to administrative tasks. The concern, as with other industries dominated by executives with poor judgement, is that this is being used as a justification by for-profit hospital systems to cut corners further. From a National Nurses United blog post (spotted by 404 Media): “Nurses are not against scientific or technological advancement, but we will not accept algorithms replacing the expertise, experience, holistic, and hands-on approach we bring to patient care,” they added.

Kaiser Permanente, for its part, insists it’s simply leveraging “state-of-the-art tools and technologies that support our mission of providing high-quality, affordable health care to best meet our members’ and patients’ needs.” The company claims its “Advance Alert” AI monitoring system — which algorithmically analyzes patient data every hour — has the potential to save upwards of 500 lives a year. The problem is that healthcare giants’ primary obligation no longer appears to reside with patients, but with their financial results. And, that’s even true in non-profit healthcare providers. That is seen in the form of cut corners, worse service, and an assault on already over-taxed labor via lower pay and higher workload (curiously, it never seems to impact outsized high-level executive compensation).

Read more of this story at Slashdot.

PFAS Increase Likelihood of Death By Cardiovascular Disease, Study Shows

New submitter berghem shares a report from The Guardian: For the first time, researchers have formally shown that exposure to toxic PFAS increases the likelihood of death by cardiovascular disease, adding a new level of concern to the controversial chemicals’ wide use. The findings are especially significant because proving an association with death by chemical exposure is difficult, but researchers were able to establish it by reviewing death records from northern Italy’s Veneto region, where many residents for decades drank water highly contaminated with PFAS, also called “forever chemicals.” Records further showed an increased likelihood of death from several cancers, but stopped short of establishing a formal association because of other factors. […]

Veneto’s drinking water was widely contaminated by a PFAS-production plant between 1985 and 2018. Researchers first found an excess of about 4,000 deaths during this period, or about one every three days. Part of the region was supplied with water from a different source, giving researchers the opportunity to compare records for tens of thousands of people who drank contaminated water and lived near those who did not. Though PFAS can affect the cardiovascular system in different ways, it is largely a problem because it produces stubbornly high and dangerous levels of cholesterol. The levels are difficult to control because they aren’t caused by dietary or lifestyle choices that can be addressed with adjustments, but hormonal changes that affect the metabolism and the body’s ability to control plaque in arteries. The study’s authors suspect that post-traumatic stress disorder caused by the environmental disaster, which upended lives across the region, may also be contributing to circulatory disease. The evidence of a jump in kidney cancer was also “very clear,” [said Annibale Biggeri, the peer-reviewed study’s lead author, and a researcher with the University of Padua]. In the study’s first five years, 16 cases were recorded, while 65 were recorded in the last five years. It also found elevated levels of testicular cancer during some time periods.

The records “showed clearly” that earlier life exposures led to higher levels of mortality, except for women who have multiple children. Previous research has found levels were higher in women with only one child. The chemicals accumulate in placentas and are passed on to children during pregnancy, which reduces levels in the body. Mortality levels among women who were of child-bearing age were generally lower, but increased in older women. The chemicals will be passed down to children for generations, said Laura Facciolo, a Veneto resident who drank contaminated water. She said the findings underscore the need to ban PFAS, and the disaster’s injustice. The findings have been published in the journal Environmental Health.

Read more of this story at Slashdot.

Google Lays Off Hundreds of ‘Core’ Employees, Moves Some Positions To India and Mexico

According to CNBC, Google is laying off at least 200 employees from its “Core” teams and moving some roles to India and Mexico. From the report: The Core unit is responsible for building the technical foundation behind the company’s flagship products and for protecting users’ online safety, according to Google’s website. Core teams include key technical units from information technology, its Python developer team, technical infrastructure, security foundation, app platforms, core developers, and various engineering roles. At least 50 of the positions eliminated were in engineering at the company’s offices in Sunnyvale, California, filings show. Many Core teams will hire corresponding roles in Mexico and India, according to internal documents viewed by CNBC.

Asim Husain, vice president of Google Developer Ecosystem, announced news of the layoffs to his team in an email last week. He also spoke at a town hall and told employees that this was the biggest planned reduction for his team this year, an internal document shows. “We intend to maintain our current global footprint while also expanding in high-growth global workforce locations so that we can operate closer to our partners and developer communities,” Husain wrote in the email. […] “Announcements of this sort may leave many of you feeling uncertain or frustrated,” Husain wrote in the email to developers. He added that his message to developers is that the changes “are in service of our broader goals” as a company. The teams involved in the reorganization have been key to the company’s developer tools, an area Google is streamlining as it incorporates more artificial intelligence into the products.

Read more of this story at Slashdot.

Unity Appoints Ex-Zynga Exec Matthew Bromberg As CEO

Unity has appointed Matthew Bromberg, former CEO of Zynga, as its new CEO, president and board member. “Filling a role that has been temporarily filled by former Red Hat CEO Jim Whitehurst, Bromberg will formally join Unity as CEO on May 15,” reports VentureBeat. “Whitehurst will serve as executive chair of the Unity board, and Roelof Botha will transition from chairman to lead independent board member.” From the report: Bromberg fills a slot vacated by John Riccitiello, who resigned last fall after a pricing debacle that left game developers extremely angry at Unity. They calmed down after Unity walked back major parts of the price increase. It’s an important time for Unity as it is about to ship Unity 6, the latest version of its game engine, in competition with Epic Games’ Unreal Engine 5.4. Whitehurst will also return to Silver Lake, one of Unity’s two largest shareholders, where he had previously been a senior advisor and will now join as a managing director leading both operating and investment team initiatives.

Bromberg brings over 20 years of experience across the gaming industry, having previously served as Chief Operating Officer of leading mobile game developer and publisher Zynga, where he played a key role in the company’s turnaround, and was responsible for Zynga’s game studios globally, while also overseeing product development and design, technology, data, and analytics. Bromberg also held multiple leadership roles at Electronic Arts, where he helped scale the company’s mobile division and led teams on four continents that built popular games across all major genres.

Read more of this story at Slashdot.

13.4 Million Kaiser Insurance Members Affected by Data Leak to Online Advertisers

Kaiser Permanente is the latest healthcare giant to report a data breach. Kaiser said 13.4 million current and former insurance members had their patient data shared with third-party advertisers, thanks to an improperly implemented tracking code the company used to see how its members navigated through its websites. Dark Reading reports: The shared data included names, IP addresses, what pages people visited, whether they were actively signed in, and even the search terms they used when visiting the company’s online health encyclopedia. Kaiser has reportedly removed the tracking code from its sites, and while the incident wasn’t a hacking event, the breach is still concerning from a security perspective, according to Narayana Pappu, CEO at Zendata.

“The presence of third-party trackers belonging to advertisers, and the oversharing of customer information with these trackers, is a pervasive problem in both health tech and government space,” he explains. “Once shared, advertisers have used this information to target ads at users for complementary products (based on health data); this has happened multiple times in the past few years, including at Goodrx. Although this does not fit the traditional definition of a data breach, it essentially results in the same outcome — an entity and the use case the data was not intended for has access to it. There is usually no monitoring/auditing process to identify and prevent the issue.”

Read more of this story at Slashdot.

Google Removes RISC-V Support From Android Common Kernel, Denies Abandoning Its Efforts

Mishaal Rahman reports via Android Authority: Earlier today, a Senior Staff Software Engineer at Google who, according to their LinkedIn, leads the Android Systems Team and works on Android’s Linux kernel fork, submitted a series of patches to AOSP that “remove ACK’s support for riscv64.” The description of these patches states that “support for risc64 GKI kernels is discontinued.”

ACK stands for Android Common Kernel and refers to the downstream branches of the official kernel.org Linux kernels that Google maintains. The ACK is basically Linux plus some “patches of interest to the Android community that haven’t been merged into mainline or Long Term Supported (LTS) kernels.” There are multiple ACK branches, including android-mainline, which is the primary development branch that is forked into “GKI” kernel branches that correspond to a particular combination of supported Linux kernel and Android OS version. GKI stands for Generic Kernel Image and refers to a kernel that’s built from one of these branches. Every certified Android device ships with a kernel based on one of these GKI branches, as Google currently does not certify Android devices that ship with a mainline Linux kernel build.

Since these patches remove RISC-V kernel support, RISC-V kernel build support, and RISC-V emulator support, any companies looking to compile a RISC-V build of Android right now would need to create and maintain their own fork of Linux with the requisite ACK and RISC-V patches. Given that Google currently only certifies Android builds that ship with a GKI kernel built from an ACK branch, that means we likely won’t see certified builds of Android on RISC-V hardware anytime soon. Our initial interpretation of these patches was that Google was preparing to kill off RISC-V support in Android since that was the most obvious conclusion. However, a spokesperson for Google told us this: “Android will continue to support RISC-V. Due to the rapid rate of iteration, we are not ready to provide a single supported image for all vendors. This particular series of patches removes RISC-V support from the Android Generic Kernel Image (GKI).” Based on Google’s statement, Rahman suggests that “there’s still a ton of work that needs to be done before Android is ready for RISC-V.”

“Even once it’s ready, Google will need to redo the work to add RISC-V support in the kernel anyway. At the very least, Google’s decision likely means that we might need to wait even longer than expected to see commercial Android devices running on a RISC-V chip.”

Read more of this story at Slashdot.