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
OAuth Authorization Server Built Without Storing User Profiles
The article details the evolution of an OAuth Authorization Server that deliberately avoids storing user profiles, relying instead on external identity providers for authentication. It addresses three core constraints: hundreds of dynamically created isolated APIs, a public SPA client without a BFF, and the inability of resources to query the AS on every request. The design separates concerns so the AS handles only clients, tenants, grants, audiences, scopes, keys, sessions, and token issuance while the Main API owns profiles and roles. Tokens are managed securely inside a Service Worker using a custom FedCM grant, eliminating races across tabs and reducing XSS exposure. The approach minimizes blast radius, simplifies compliance, and keeps the AS replaceable without affecting product domain logic.
Why a 202-Character License Key Uses ECDSA P-256 Instead of Ed25519 or RSA
A developer building offline license verification for a .NET desktop application evaluated Ed25519, RSA, and ECDSA P-256 before selecting the last option. The decision was driven by the requirement for zero external dependencies, keys short enough for manual entry from email, and support for key rotation without breaking existing licenses. Although Ed25519 offers faster verification and a smaller public key, it is absent from System.Security.Cryptography in both .NET 8 and .NET 10, with API approval only targeted for version 11. RSA-2048 produces signatures too long for practical use, resulting in a 571-character Base32 string that users would find cumbersome. ECDSA P-256 with SHA-256 delivers a fixed 64-byte signature that becomes a manageable 202-character key when encoded in Base32, while remaining fully available in the runtime. The article also covers performance measurements, the risks of ECDSA nonce generation, and the deliberate choice of the IEEE P1363 signature format to guarantee fixed-length output.
Pilcrow Publishes Free Comprehensive Guide on Web Authentication
Author Pilcrow has released a detailed, ad-free handbook covering authentication and authorization practices for web applications. The resource draws on personal experience and includes practical examples in JavaScript and Go. It examines password-based methods, email verification, multi-factor authentication, passwordless flows, and passkeys while highlighting associated risks and usability trade-offs. The book also provides in-depth guidance on session management, token security, expiration policies, and email address handling as account identifiers. Recommendations emphasize choosing methods that match application security requirements and user expectations. Additional context is given on OWASP resources and community support channels.
redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem
redb 3.4.0 delivers operational improvements for the .NET integration platform that includes typed storage over Postgres, MSSQL and SQLite, the redb.Route engine modeled after Apache Camel, the Tsak runtime with dashboard and clustering, and redb.Identity for OIDC and OAuth 2.1. The release focuses on post-deployment resilience with replay checkpoints that capture message state at named points inside routes, allowing safe re-execution of downstream steps without duplicating side effects. A shared runtime layer moves framework assemblies into a separate Libs/shared directory so that individual DLLs can be replaced without rebuilding or redeploying the entire Tsak or Identity packages. Secrets are now declared with a [Sensitive] attribute on endpoint options, ensuring URIs containing passwords or keys are sanitized before they reach logs, metrics or health checks. Additional controls include role-based access to management APIs, persistent audit trails and cryptographic signing of dynamically loaded modules. All Pro features remain free on the entire 3.x line with no licensing server required.