Interoperabilität von patientennahen Medizingeräten

openSDC Update

Joint meeting of IEEE EMBS 11073 & HL7 Health Care Devices (DEV) WG, 2014/05/27, Stefan Schlichting

openSDC UpdateAgenda

1. openSDC Update2. Convergence Project3. Standardization Roadmap

An architecture for distributed systems of medical devices in high acuity environments2 |

openSDC updateHistory

An architecture for distributed systems of medical devices in high acuity environments3 |

Last WG Meeting we proposed“an architecture for distributed systems of medical devices in high acuity

environments” for standards adoption.

openSDC updateWhat is openSDC?

Extensible openSDC protocol stack for clinical workplace service-oriented medical device architectures

• BICEPS (Message & Service Model)• MDPWS & DPWS (Transport)

An architecture for distributed systems of medical devices in high acuity environments4 |

openSDC updateopenSDC Reference Implementation

openSDC downloads since January WG MeetingNew Version beta03 will be out end of Q2/2014

See http://sourceforge.net/projects/opensdc/

An architecture for distributed systems of medical devices in high acuity environments5 |

openSDC updateBICEPS changes since last WG Meeting

Update of the BICEPS model V2• Get closer to the classic DIM• Incorporate change request from OR.NET• Bug fixes

The BICEPS model V3 will be published in openSDC beta03.

Expect a BICEPS V3.1 in Q3/2014 (openSDC beta04)• Optimized representation of the transmitted messages

An architecture for distributed systems of medical devices in high acuity environments6 |

openSDC UpdateAgenda

1. openSDC Update2. Convergence Project3. Standardization Roadmap

An architecture for distributed systems of medical devices in high acuity environments7 |

Convergence Project

Summary of the convergence project

An architecture for distributed systems of medical devices in high acuity environments8 |

Convergence ProjectUse Cases

An architecture for distributed systems of medical devices in high acuity environments9 |

Convergence ProjectWhat is Common?

Example for DiscoveryopenSDC may use DNS, but only with the

focus of name resolution.

An architecture for distributed systems of medical devices in high acuity environments10 |

Discussed• Discovery• Security: IPSec vs TLS/DTLS• QoS for Transport: IntServ vs DiffServ

Convergence ProjectHarmonization potential

Convergence vs. Coexistence?

An architecture for distributed systems of medical devices in high acuity environments11 |

Convergence ProjectCoexistence - Multi-protocol Gateway model

Medical Device Standards-based Clinical “Ecosystem” (aka Clinical Gateway) integrating an IEEE 11073 Mgr-Agt pair with a BICEPS-based Proxy-Supervisor pair.

An architecture for distributed systems of medical devices in high acuity environments12 |

Common MDIB

Convergence ProjectCoexistence - Multi-protocol Gateway model

BICEPS Clinical Gateway part

An architecture for distributed systems of medical devices in high acuity environments13 |

Common MDIB

BUS-API

BICEPS Supervisor Proxy BICEPS Supervisor

Convergence ProjectCommon MDIB - Alert models

An architecture for distributed systems of medical devices in high acuity environments14 |

11073 Alert Package model BICEPS model

AlertSystemDetects AlertConditions and - as appropriate - generates AlertSignals.

ALARM SYSTEM (From 60601-1-8)

parts of ME EQUIPMENT or a ME SYSTEM that detect ALARM CONDITIONS and, as appropriate, generate ALARM SIGNALS

An architecture for distributed systems of medical devices in high acuity environments15 |

Convergence ProjectCommon MDIB – Alert Models

An architecture for distributed systems of medical devices in high acuity environments16 |

AlertConditionContains the information about a potentially or actually hazardous situation.Example: An AlertLimit has been exceeded, or a Sensor has been unplugged.LimitAlertCondition is derived from AlertCondition

ALARM CONDITION(From 60601-1-8)

state of the ALARM SYSTEM when it has determined that a potential or actual HAZARD exists

Convergence ProjectCommon MDIB – Alert Models

An architecture for distributed systems of medical devices in high acuity environments17 |

AlertSignalContains information about the way an AlertCondition is communicated to someone.It is generated by an AlertSystem to indicate the presence or occurence of an AlertCondition.

ALARM SIGNAL(From 60601-1-8)

type of signal generated by the ALARM SYSTEM to indicate the presence (or occurrence) of an ALARM CONDITION

Convergence ProjectCommon MDIB – Alert Models

An architecture for distributed systems of medical devices in high acuity environments18 |

AlertSignal Example

AlertSignal could be a lamp (-> Visible Manifestation) on a remote device, suchas the nurses handheld (-> SignalDelegationSupported), which starts flashingwhen the heart rate is exceeding 150bmp (-> ConditionSignaled) for more than2 seconds (-> DefaultSignalGenerationDelay) and keeps flashing, until thenurse confirms the alarm, even if the AlarmCondition is not present anymore(-> Latching).

Convergence ProjectCommon MDIB – Alert Models

AlertStates for • AlertSystem• AlertCondition• AlertSignalAlert ProcessingIn order to retrieve the overall alert state of an MDS, a client has to subscribe to all AlertSystems.

• An AlertCondition has a rank that represents the overall rank of the Alarm Condition in the MDS.

• An AlertSignal has a slot that represents the overall ordering number of the signal in the MDS.

In order to retrieve the overall alert condition state of an MDS, a client has to subscribe to all AlertConditions. In order to retrieve the overall alert signal state of an MDS including remote signals, a client has to subscribe to all AlertSignals.

An architecture for distributed systems of medical devices in high acuity environments19 |

Convergence ProjectSummary

http://mdcx73-working.wikispaces.com/MDCx73_UseCases-UCsAn architecture for distributed systems of medical devices in high acuity environments20 |

Stefan’s View• Clinical Gateway seems feasible incl. a common MDIB.• Only limited value for a real “converged” network specification

• NTP is essential even for a Clinical Gateway• Security Infrastructure including role model should be harmonized• Common Requirements Glossary• + recommendations for Transport QoS, Security,.. based on UC

More Info

openSDC UpdateAgenda

1. openSDC Update2. Convergence Project3. Standardization Roadmap

An architecture for distributed systems of medical devices in high acuity environments21 |

Standardization RoadmapOR.NET project

An architecture for distributed systems of medical devices in high acuity environments22 |

OR.NET Partners http://www.ornet.org/

Standardization RoadmapOR.NET project

An architecture for distributed systems of medical devices in high acuity environments23 |

Source: http://ws4d.e-technik.uni-rostock.de/2014/or-net-and-ws4d-org-at-cebit-2014/

Standardization RoadmapopenSDC & OR.NET

Summary of a telco in April

The OR.NET standardization project & Dräger closely work together to publish a technical specification for a service-oriented architecture implementation for a distributed system of medical devices in the OR and related areas.

The technical specification for medical device communication should be published under the umbrella of IEEE 11073.

The technical specification is based on “openSDC” & OR.NET work

An architecture for distributed systems of medical devices in high acuity environments24 |

DeviceConnectivity

OR W

orks

tatio

n

Medical Devices

OR table

Light srcs

Navigation

Tracking

Imaging

HF dissector

Insufflator

Endos. Cams

Media Ctrl

Standardization RoadmapOR.NET project – Protocol View

IT (E

HR, P

DMS,

…)

Device 2 Enterprise (HL7, DICOM,…)

According to J. Dehm (OR.NET – Standardization)

Standardization Roadmap

An architecture for distributed systems of medical devices in high acuity environments26 |

• openSDC/OR.NET Technical Specification• Nomenclature Additions

• Device Specializations• Clinical Gateway Spec• ICE Implementation Guide

MDPWS + BICEPS Spec 2012

MDPWS + BICEPS Spec 2014

Thank you for your attention.

ContactDr. Stefan SchlichtingResearch Unit, Drägerwerk AGstefan.schlichting@draeger.com

Use case discussion with MDPnPFollow-up discussion on the HIMSS 2014

An architecture for distributed systems of medical devices in high acuity environments28 |