# healthtech Published articles for healthtech. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Yandex Cloud and ASPiRRe Develop an AI Agent for Remote Monitoring in Pediatric Rheumatology DevFeed: [Yandex Cloud and ASPiRRe Develop an AI Agent for Remote Monitoring in Pediatric Rheumatology]() Original publisher: [Read original article]() Author: yuliabusygina (Яндекс, Yandex Cloud & Yandex Infrastructure) Published: 2026-08-11T10:42:22Z Content type: article Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [Cloud]() Tags: [cloud](), [healthtech](), [llm](), [rag](), [tag-4e98b1137df6](), [tag-73eb9b712998](), [tag-cfc8bc61862b]() ### AI overview The article describes an AI agent developed by Yandex Cloud, the Association of Pediatric Rheumatologists (ASPiRRe), and an ITMO student for a remote-monitoring system in pediatric rheumatology. The available evidence says the model is limited to two narrow tasks, while risk decisions are handled by deterministic rules. ### Source excerpt В России около 70 тысяч детей и подростков страдают от ревматических патологий. Это группа заболеваний, при которых иммунная система даёт сбой и атакует собственные ткани -- чаще всего суставы. Примерно раз в год ребёнку положена госпитализация в федеральный центр, чтобы проверить состояние и убедиться, что конкретный тип терапии работает. Однако, когда ребёнок возвращается в родной город, рядом может не быть ни одного врача, который знает, что делать с этой терапией. На связи Юлия Шеянова, менеджер проектов в здравоохранении, Центр технологий для общества Yandex Cloud. В этой статье расскажу, как мы в Yandex Cloud вместе с Ассоциацией детских ревматологов (ASPiRRe) и студентом ИТМО сделали ИИ-агента для системы дистанционного мониторинга. Ниже -- как он устроен и почему мы доверили модели только две узкие задачи, а все решения о рисках вынесли в детерминированные правила. Читать далее ## Reframing Healthcare Technology in the AI Era DevFeed: [Reframing Healthcare Technology in the AI Era]() Original publisher: [Read original article]() Author: Jon Wettersten Published: 2026-03-06T22:14:00Z Content type: opinion Language: en Sources: [8th Light](), [8th Light Insights]() Topics: [Artificial Intelligence](), [Generative AI](), [Automation](), [decision-making](), [trust](), [digital]() Tags: [ai](), [automation](), [decision-making](), [generative-ai](), [governance](), [healthcare](), [healthtech](), [human-centered-design](), [safety](), [technology](), [transparency](), [trust]() ### AI overview This article argues that healthcare organizations should approach AI adoption through human-centered design, stronger governance, transparency, and alignment with clinical standards. It emphasizes that clinicians need technology to reduce administrative burden and support patient care without compromising safety, trust, or practical and ethical readiness. ### Source excerpt At 8th Light, we help healthcare organizations design and build AI-enabled systems that put people first, combining product strategy, human-centered design, and technology leadership to create innovative solutions that work for clinicians as well as patients. Why This Matters Although AI continues to dominate healthtech headlines, many frontline clinicians are still battling clunky systems, fragmented workflows, and administrative overload. The reality? Healthcare practitioners are not asking for more technology, they're asking for more time with patients. The tension between innovation and adoption continues to shape healthcare's digital transformation. As AI tools quickly evolve and adapt to revolutionize diagnosis, documentation, and decision-making, many healthcare providers remain cautious. Their questions are not about the potential of technology, but about its practical and ethical readiness for real-world care. For instance: How do we vet these tools? Can we trust the outcomes? Will this actually improve care or just add more work? Will this solution deliver measurable ROI without compromising patient safety? These are not questions of resistance, they're questions of responsibility. As healthcare systems race to deploy generative AI, predictive analytics, and automation, clinicians and administrators are demanding stronger governance, transparency, and alignment with clinical standards. Their goal isn't to slow innovation, but to ensure technology protects both patients and the licensed physicians who care for them. Behind these questions lies a workforce already under significant strain, and technology that fails to ease that burden risks making it worse. The Urgent Need for Human-Centered Healthtech The U.S. is already experiencing workforce strain across many health professions, driven by geographic maldistribution, burnout, and demographic pressures. Federal workforce projections show ongoing gaps across multiple professions, with non-metro communities ## From ePA 2.6 to 3.0 : Healthcare Data Integration for Electronic Patient Records at HelloBetter DevFeed: [From ePA 2.6 to 3.0 : Healthcare Data Integration for Electronic Patient Records at HelloBetter]() Original publisher: [Read original article]() Author: Anna J McDougall Published: 2025-05-20T09:27:30Z Content type: tutorial Language: en Sources: [Anna J McDougall]() Topics: [data](), [implementation](), [Authentication](), [Back end](), [Front end](), [XML](), [pdf]() Tags: [authentication](), [backend](), [data](), [electronic-patient-record](), [engineering-management](), [export](), [frontend](), [germany](), [healthcare](), [healthtech](), [integration](), [pdf](), [pipeline](), [platform](), [product](), [project](), [software-architecture](), [technical](), [terminal]() ### AI overview This technical post describes HelloBetter's implementation journey from Germany's ePA 2.6 to ePA 3.0. It covers HealthID login, ePA data export, PDF and XML document writing, and the frontend and backend integrations used to connect therapeutic data across systems. The implementation was completed pending BfArm approval. ### Source excerpt From ePA 2.6 to 3.0: A Technical Journey in Healthcare Data Integration for Electronic Patient Records...so far Germany has a bad reputation for digitalisation, so the government's push to implement an electronic patient record ("elektronische Patientenakte" or ePA) for its citizens and residents is a step in the right direction. As an official digital health application ("digitale Gesundheitsapplikation" or "DiGA"), we are obligated to shift to the ePA 3.0 implementation. The government rollout has been plagued with technical difficulties and delays, but we're now at a point where we have completed our implementation successfully, pending BfArm approval. In this post, I want to cover the exact steps we and had to take to achieve this. I want to thank Senior Product Manager Tanja Lembcke and Senior Backend Engineer Chaythanya Sivakumar for their contributions to this piece. The Challenge: Connecting Patient Data Across Systems The electronic patient record (ePA) and HealthID integration project had a clear mission: we wanted to give our patients the ability to log into the HelloBetter platform using their HealthID (which they access through their insurance company) and export their HelloBetter data into their ePA. A successful implementation would mean that both doctors and patients can electronically access therapeutic data whenever they need it. To make this happen for the patient data at HelloBetter, we partnered with two key players: RISE for ePA system access and Azuma for HealthID system access. Our journey began in 2024 when our backend team laid the groundwork for ePA 2.6, setting up the pipeline and data export in our staging environment. We successfully implemented both PDF and XML document writing capabilities, along with the frontend and backend integrations for HealthID login. How It All Works: The Architectural SideHealthID Authentication The first piece of the puzzle is connecting to and authorising the user's HealthID. This part of the system has remai ## Securing Infrastructure in Healthcare: Reducing Breaches and Building Resiliency DevFeed: [Securing Infrastructure in Healthcare: Reducing Breaches and Building Resiliency]() Original publisher: [Read original article]() Author: jack.pitts@goteleport.com (Jack Pitts) Published: 2024-09-03T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [Security, Privacy and Abuse Prevention](), [Security](), [Access Control](), [audit](), [resiliency](), [Databases](), [Network](), [Server]() Tags: [access-control](), [audit](), [data](), [data-privacy](), [healthcare](), [healthtech](), [hipaa](), [infrastructure](), [network](), [resiliency](), [security]() ### AI overview This article examines infrastructure, security, privacy, and compliance challenges faced by digital healthcare companies operating telehealth and remote patient monitoring systems. It uses a fictional company to discuss remote device access, data transmission, role-based access control, databases, and audit logging for HIPAA compliance, and describes how Teleport is presented as a solution. ### Source excerpt Ensure HIPAA compliance, protect patient data, and streamline telehealth access. Learn how HealthTech Innovations uses Teleport to overcome infrastructure challenges.