Beats Normally — And Still Fails: Soft Robotic Heart Model Created to Study HFpEF, the Most Insidious Form of Heart Failure
Engineers have built a soft robotic heart that can actively alter its stiffness while beating, enabling scientists to study heart failure with preserved ejection fraction (HFpEF) — one of the most common yet poorly understood cardiac conditions.
The new model reproduces the left side of the heart, including the left atrium and left ventricle. Its silicone chambers are surrounded by multiple layers of artificial muscle fibers composed of rubber tubes reinforced with spring-like coils. These fibers replicate the helical architecture of real cardiac muscle and respond to fluid pressure, relaxing during filling and contracting with controllable force.
HFpEF occurs when the heart ejects a normal fraction of blood with each beat, yet the ventricular wall has lost elasticity. Between contractions — during the diastolic phase — the stiff muscle fails to relax properly, so the chamber cannot fill with enough blood. As a result, the body receives insufficient cardiac output while pressures inside the heart and vessels rise.
Approximately half of all heart-failure patients suffer from HFpEF, with more than three million cases in the United States. Existing laboratory setups using rigid pumps and tubes cannot capture the dynamic interplay between wall stiffness and filling, while animal studies are expensive and do not fully mirror human disease progression.
The robotic platform overcomes these limitations through a closed-loop control system. Continuous pressure sensors feed data to a controller that instantly adjusts the resistance of the artificial fibers. Researchers can therefore increase or decrease ventricular compliance on demand, reproducing early-stage delayed relaxation as well as advanced, severely restricted filling.
This tunable stiffness allows scientists to observe how progressive loss of elasticity alters blood flow, chamber pressures, and overall hemodynamics — something impossible with static bench models. The device is expected to help engineers test cardiovascular implants and mechanical support systems under varying degrees of myocardial stiffness and to explore interventions that could restore elasticity before irreversible damage occurs.
Current clinical management of HFpEF focuses mainly on symptoms and comorbidities such as hypertension, obesity, and diabetes. While SGLT2 inhibitors have reduced hospitalizations for many patients, no approved drugs directly restore lost myocardial compliance. The robotic heart remains an experimental tool that will require faster actuators and further validation against patient data, but it is intended to complement — not replace — computational models, animal studies, and clinical trials.
Related articles
MEPhI Opens 2026 Admissions for Online Cybersecurity Master's Program with Yandex Practicum
The National Research Nuclear University MEPhI, in partnership with Yandex Practicum, is accepting applications for its online master's program in Cybersecurity for the 2026 intake. The two-year program leads to a state diploma in Information Security under code 10.04.01 and a professional retraining certificate from Yandex Practicum. Students can choose from four specialized tracks covering AppSec, DevSecOps, network security, and AI security. Admission is fully online and includes document submission via Gosuslugi, an entrance exam, and a motivation letter requiring at least 80 points. The program runs entirely remotely with evening and weekend classes, allowing students to combine studies with work while accessing student benefits and an educational loan at a subsidized 3% rate.
360 Group Launches NanoWork Enterprise AI Platform with Built-in Security and Opens Nationwide Channel Partner Recruitment
On July 28 at the Beijing National Convention Center, 360 Group founder Zhou Hongyi officially unveiled NanoWork, a next-generation enterprise intelligent agent work platform. The platform is designed to bridge the gap between powerful AI models and real-world business tasks by enabling multi-agent collaboration, on-demand model scheduling, and 24/7 cloud operation across diverse scenarios. NanoWork was developed through extensive real-world testing involving 100,000 intelligent agents, coverage of 630 positions over 150 days, consumption of 350 trillion tokens, and collection of 56,000 feedback items. A core emphasis is placed on native security features drawn from 360 Group's two decades of cybersecurity experience to prevent errors that could lead to actual data loss or permission breaches. The company is now actively recruiting city-level channel partners across China to help deploy the solution in local industries and activate existing customer bases with AI capabilities.
Google Enables Document Backup to Drive in Stable Play Services 26.26 Release
Google has rolled out automatic document backup from Android devices to Google Drive in the stable version of Google Play Services 26.26. The feature, which the company prepared for nearly a year, adds a new Documents option in Settings on Pixel phones under Accounts and backup. It remains disabled by default to avoid uploading the Downloads folder without user consent. Once enabled, supported files including PDF, DOC, PPT, XLS, ZIP and even APK files are copied to a new Android backups folder on Drive, with separate subfolders created for each device. The backup consumes storage quota and offers no automatic two-way sync, requiring manual cleanup when disabled. Traces of the capability first appeared in August 2025, followed by an official mention in February 2026 and beta testing before the current stable deployment.
Bridging Manual and Automated Testing: InfoWatch Engineer Outlines Unified Quality Process
InfoWatch senior test engineer Mikhail Shalepo has published a detailed article describing how his team built a reproducible process that links manual and automated testing into a single quality system. The approach addresses the growing complexity of server-side products that undergo quarterly releases and require extensive matrix testing across multiple operating systems and installation scenarios. Shalepo explains that the regulation focuses on decision points rather than prescribing exact test volumes, ensuring that choices about automation candidates, smoke-test gates, failure ownership, and manual compensation are documented and visible to the entire team. The framework divides work into two main blocks—feature development and pre-release regression—each containing preparation, execution, and completion stages. Key outputs include linked artifacts in TMS Scale, explicit Definition of Done criteria, and traceable coverage data that prevents reliance on individual knowledge. The article also shares practical lessons, including why separate mind maps and tables failed to stay current and how the team now integrates automation status directly with test cases.