CT Technologist

Kettering Health opens new Health Center in Fayette County. August 21, 2026 - Read time: 1 min Kettering Health is celebrating the grand opening of the new Fayette County Health Center on Tuesday, August 25. Kettering Health is celebrating the grand opening of the new Fayette County Health Center, located at 1270 US-62, Washington Court House, OH, 43160, with a grand opening celebration on Tuesday, August 25. A ribbon cutting ceremony will begin at 4:30 p.m., followed by a community open house. The open house will feature a meet-and-greet with the physicians providing care at the new health center, guided facility tours, giveaways, and complimentary ice cream and pizza provided by Mister Twisty Ice Cream and Super Sport Pizza. The renovated 21,000-square-foot health center will expand access to care in Fayette County by offering primary care, imaging, and laboratory services. The month's most popular health news, stories, and tips in your inbox.

WC and Kettering Health sign partnership for on-campus services. Published on Aug 21, 2026 Wilmington College and Kettering Health have entered into an agreement that provides medical services for students at the campus Health & Wellness Center and gives students more direct access to Kettering's newly expanded medical services in Wilmington. Kettering Health will provide a nurse practitioner on-site for 20 hours each week. Dr. Kevin Sharrett, medical director of rural health services at Kettering Health, will oversee the medical center's services at the College. "Wilmington College already has a strong and dedicated health and wellness team in place, and we're pleased to provide additional physician oversight and additional medical services that build on that foundation," he said. "Together, we are enhancing access to care and further supporting student well-being." WC President Corey Cockerill spoke of the partnership between one of the community's oldest and one of its newest entities. "Wilmington College and Kettering Health share a deep commitment to this community and the people who call it home," she said. "We are grateful for Kettering Health's partnership in providing quality healthcare to our students right here on campus." Sigrid Solomon, vice president/chief student affairs officer, expressed her excitement about the new partnership, "as we continue to prioritize" the health and well-being of WC students. "This partnership will complement the work of our internal team and expand the resources and support available to our students," she said. "Together, we can help ensure that our students have access to quality medical and mental health services that support them not only in their academic journey, but in their overall well-being and success." The College's partnership with Kettering Health will work in conjunction with existing health and wellness services at WC, which include physical, reproductive and mental health services. The WC staff features a director of health services, a registered nurse, a director of counseling services and two mental health counselors. During the 2025-26 academic year, the Health & Wellness Center had 990 total visits by students and employees. As a faith-based, nonprofit health system, Kettering Health strives to live God's love by promoting and restoring health. Kettering Health is made up of 14 medical centers and more than 120 outpatient locations throughout western Ohio, as well as Kettering Health Medical Group - with more than 700 board-certified providers dedicated to elevating the health, healing and hope of the community. Kettering College, a division of Kettering Health Main Campus, is a fully accredited college that specializes in health science education. For more, visit ketteringhealth.org.

IoMT defense: securing CardioMEMS EHR integration and wireless implantable data. Security Arsenal Team April 30, 2026 Kettering Health has recently advanced its cardiac care capabilities by integrating Abbott's CardioMEMS HF System directly into its Electronic Health Record (EHR) platform. This implantable wireless sensor monitors pulmonary artery pressure, transmitting critical data to guide clinical decisions for heart failure patients. While this integration promises significant improvements in patient outcomes and volume management, it represents a critical expansion of the Internet of Medical Things (IoMT) attack surface. For defenders, the integration of an implantable device with the central EHR creates a high-stakes cyber-physical convergence. Compromised data integrity or availability here is not merely a privacy breach; it directly impacts patient physiology and treatment protocols. Security teams must immediately understand the data flow and enforce strict segmentation to protect this telemetry from interception or manipulation. Technical analysis. The integration involves a complex chain of connectivity that moves data from inside the human body to the central clinical record. * Affected Products & Platforms: * Abbott CardioMEMS HF System: Implantable sensor and the Merlin(TM)@home Transmitter (patient bedside unit). * EHR Platform: (Implied Epic/Cerner/Meditech based on market share) acting as the central repository for PA pressure readings. * Network Infrastructure: Wi-Fi/Cellular gateways used by the transmitter to upload data to the vendor cloud (Merlin.net), which then pushes data to the hospital EHR via APIs. * Attack Surface & Vulnerability Exposure: * Data Integrity Risks: The primary concern is the manipulation of pressure readings. If an attacker intercepts the transmission between the Merlin transmitter, the vendor cloud, or the API ingress to the EHR, they could alter pressure values. Clinicians relying on this data for diuretic dosing could inadvertently induce hypovolemia or exacerbate heart failure. * EHR API Abuse: The integration relies on HL7 FHIR or proprietary APIs to ingest data. Unsecured API endpoints could be targeted for data exfiltration (PHI theft) or injection attacks. * Device Association Attacks: While the implant-to-transmitter link is proprietary and generally secure, the transmitter-to-cloud link traverses the public internet (often via standard broadband). This exposes the transmission to Man-in-the-Middle (MitM) attacks if the TLS tunneling is not rigorously validated or if the patient unit is compromised by malware. * Exploitation Status: Currently, there is no active zero-day exploit specific to CardioMEMS publicized in this context. However, IoMT devices are frequent targets for nation-state actors (e.g., Volt Typhoon) probing healthcare infrastructure. The risk here is "theoretical" but "imminent" due to the criticality of the data and the increasing connectivity of these systems. Executive takeaways. Given the architectural nature of this integration, specific IOC-based detection (Sigma/KQL) is not applicable without a specific threat signature. Instead, defensive focus must shift to configuration hygiene and architectural monitoring. * Rigorous API Segmentation and Authentication: Ensure that the API endpoint receiving CardioMEMS data into the EHR is not hosted on the general hospital LAN. It should reside in a dedicated DMZ or isolated VLAN with strict allow-listing for the vendor's IP ranges only. * Implement Ingest anomaly Monitoring: Configure the EHR or a middleware SIEM rule to alert on "impossible" physiologic data. For example, a sudden drop in pulmonary artery pressure to 0 mmHg or a massive spike inconsistent with the patient's trend could indicate a data feed hack or sensor failure. * Fourth Party Risk Management: The data flows through Abbott's Merlin.net cloud. Validate the vendor's SOC2 Type II reports and ensure Business Associate Agreements (BAA) explicitly cover data integrity, not just confidentiality. * Asset Discovery and Correlation: The CardioMEMS system introduces "grey assets" (the home transmitters) that touch your network. Ensure your asset inventory tracks these indirect connections and monitors for unauthorized devices attempting to masquerade as valid medical gateways. Remediation. To secure the CardioMEMS integration and similar IoMT workflows, healthcare security teams must implement the following controls: * Network Hardening: * Segmentation: Isolate the VLANs used for clinical workstations viewing this data from the general guest and administrative Wi-Fi. Ensure the server-side ingestion point is in a management DMZ. * Egress Filtering: Strictly control outbound traffic from clinical systems to prevent beaconing if a workstation accessing the data is compromised. * Data Integrity Controls: * Hash Verification: If the EHR integration supports it, ensure that incoming HL7/FHIR messages include digital signatures or checksums verified by the receiving interface engine to detect tampering in transit. * Access Control: * Role-Based Access Control (RBAC): Restrict access to the hemodynamics trends within the EHR to strictly the Cardiology and Heart Failure teams. Audit logs quarterly to ensure no "super-user" accounts are viewing patient data without clinical justification. * Vendor Coordination: * Request the specific TLS version and cipher suite configurations used by the Merlin@home transmitters. Ensure your network intrusion detection systems (NIDS) are tuned to allow and inspect, rather than block, these specific encrypted streams to avoid availability issues, while logging all handshake anomalies. Related resources. healthcare-cybersecurity hipaa-compliance healthcare-ransomware ehr-security medical-data-breach iomt abbott-cardiomems healthcare-it Is your security operations ready? Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.