Encrypted Device Visibility Demo
What happened
Claroty and BD demonstrated encrypted medical‑device visibility at HIMSS26 using the IHE MEM‑DMC profile — a privacy‑first approach that showed device telemetry without exposing PHI, reported. The demo is a concrete example vendors can cite when negotiating with hospital IT and security stakeholders after recent high‑profile hacks.
Why it matters
The IHE MEM‑DMC profile (trial implementation Rev. 1.5, dated Sept. 19, 2024) ihe.net specifies an HL7 v2 message format for reporting medical‑device configuration, status and event information to systems such as CMMSs. wiki.ihe.net MEM‑DMC is scoped to device metadata and lifecycle telemetry rather than patient context — technical alarms are routed via the separate IHE ACM profile — making the profile suitable for sharing device observability without embedding PHI. wiki.ihe.net Claroty’s healthcare product set (Claroty xDome / Medigate) documents device discovery methods including passive monitoring and safe queries and claims hundreds of device‑specific attributes for enriched asset profiles. claroty.com BD listed an on‑site presence at HIMSS26 (March 10–12, 2026) at booth #12723, where vendor interoperability and device management demonstrations were scheduled. bd.com Claroty’s Team82 report “State of CPS Security: Healthcare Exposures 2025” (published Mar. 26, 2025) quantified high‑risk device exposures that buyers cite when demanding visibility tools that minimize PHI exposure. claroty.com
Key numbers
- Claroty and BD demonstrated encrypted medical‑device visibility at HIMSS26 using the IHE MEM‑DMC profile — a privacy‑first approach that showed device telemetry without exposing PHI, reported.
- 19, 2024) ihe.net specifies an HL7 v2 message format for reporting medical‑device configuration, status and event information to systems such as CMMSs.
- claroty.com BD listed an on‑site presence at HIMSS26 (March 10–12, 2026) at booth #12723, where vendor interoperability and device management demonstrations were scheduled.
- bd.com Claroty’s Team82 report “State of CPS Security: Healthcare Exposures 2025” (published Mar.
What happens next
- claroty.com BD listed an on‑site presence at HIMSS26 (March 10–12, 2026) at booth #12723, where vendor interoperability and device management demonstrations were scheduled.
Quick answers
What happened in Encrypted Device Visibility Demo?
Claroty and BD demonstrated encrypted medical‑device visibility at HIMSS26 using the IHE MEM‑DMC profile — a privacy‑first approach that showed device telemetry without exposing PHI, reported. The demo is a concrete example vendors can cite when negotiating with hospital IT and security stakeholders after recent high‑profile hacks.
Why does Encrypted Device Visibility Demo matter?
The IHE MEM‑DMC profile (trial implementation Rev. 1.5, dated Sept. 19, 2024) ihe.net specifies an HL7 v2 message format for reporting medical‑device configuration, status and event information to systems such as CMMSs. wiki.ihe.net MEM‑DMC is scoped to device metadata and lifecycle telemetry rather than patient context — technical alarms are routed via the separate IHE ACM profile — making the profile suitable for sharing device observability without embedding PHI. wiki.ihe.net Claroty’s healthcare product set (Claroty xDome / Medigate) documents device discovery methods including passive monitoring and safe queries and claims hundreds of device‑specific attributes for enriched asset profiles. claroty.com BD listed an on‑site presence at HIMSS26 (March 10–12, 2026) at booth #12723, where vendor interoperability and device management demonstrations were scheduled. bd.com Claroty’s Team82 report “State of CPS Security: Healthcare Exposures 2025” (published Mar. 26, 2025) quantified high‑risk device exposures that buyers cite when demanding visibility tools that minimize PHI exposure. claroty.com
