pptx SLIDE 1 IEEE Application Profile - Common Network Services - UML adaptation Vivek Kamath, Jan Wittenber,
pptx SLIDE 2 IEEE Project (PAR) Scope: Within the framework of IEEE standards, this standard will define a common, transport neutral set of networking services that will enable plug- and-play interoperability of medical devices. This project shall not address quality of service over RF wireless network connections.
pptx SLIDE 3 Scope Summary: l Define common set of networking services l Transport Neutral l Enable plug-and-play l For medical devices
pptx SLIDE 4 Aspects of CNS l Describes topological framework to standardize network semantics for networked medical devices l Enables profiling of clinical scenarios from communication perspective. l Defines Transport Independent System Layer (TISL) as a standard interface to upper layers
pptx SLIDE 5
pptx SLIDE 6 Clinical Scenarios - ENV Annex E 2.1 ScenarioCommunication Requirements Emergency Situation – One of the main scenarios is alarm (2.1.1) Plug and Play - the device communication must start immediately after device connection without any further user intervention. That implies e.g. automatic device recognition, identification, and initialization of communication. Safety and reliability of communication and network - connection of a new device must not influence the communication of other devices connected earlier Unique device identification Normal patient nursing condition in ICU, non emergency situations (2.2) Same as above
pptx SLIDE 7 Application Scenarios ENV Annex E 3 ScenarioCommunication Requirements Data Logger ( 3.1)Graphic parameter data volumes can require high bandwidth Loose device time stamp synchronization, in the order of 0.01 second, is required. Real Time Data Display (3.2) Latency of data between amplifier output and display on screen must be less than 0.2 seconds to be invisible for user. Patient Alarm Monitoring (3.3) The communication of alarm related information must be expedited, in order to be processed prior to other data, and must be reliable. Display Device must be able to detect when a Data Agent is removed. Ideally it should be able to distinguish between an intentional disconnection and unintentional disconnection. The latency of occurrence of alarm and signaling to user must be less than 0.25 seconds.
pptx SLIDE 8 Application Scenarios ScenarioCommunication Requirements Remote Control (3.4)In a remote control system, the communication must fulfill a higher level of reliability, because of a higher risk for the patient. This includes the needs for comprehensive message validation, data verification, message retries, and notification of communication system failures. This implies the need for system management functionality. A mechanism to send control data to the data agent and acknowledge receipt is required. In some cases manual control of the device should be precluded. Patient Viewing Interoperability (3.5) There must be some level of control such that a remote user (i.e. outside the care unit) cannot change the settings established by a nurse at the bedside. Harmonization of communication methods for RF telemetry systems would be required in order to support interoperable telemetry systems. Bandwidth management may become a big issue. The issue of managing multiple associations between a Data Agent and multiple Data Loggers or Data Dis - play needs attention.
pptx SLIDE 9 ScenarioCommunication Requirements Patient Monitoring Interoperability (3.6) Communication over different hospital LANs and maybe even on the Internet. Ordering of physiological data is important. Latency from Data Agent to Remote Monitoring Device must be controlled and specified. Generally, this should be less than one second to be acceptable. Maintenance and Configuration Support (3.8) Physical connect/disconnect sensing for devices. System management protocol Intrabed Symmetric Data Exchange between DCC and BCC (4.1) Interbed Symmetric Data Exchange over an "Interbed Network (4.2) Symmetry in communication between device (DCC) and BCC Symmetry in data propagation in through the BCC - from device (DCC) through BCC to Application System and vice versa Propagation of a containment tree of a remote device to the receiver (DCC)
pptx SLIDE 10 Transport Stack View ethernet upper layers Wi-Fi Cellular Data Wi-Max /100/ 1000BT RF GPRS EDGE 1xRTT 4G /LTE RF RF IP RTP TCPUDPSCTP IrLAP IR IrLMP TinyTP RS-232 IP Support Services config service assoc service DHCP DNS Net. capacity service LDAP NTP Radius Location services Presence services SNMP 802.1x NAT USB BlueTooth PHDC MDP currentshort term point to point links short termpossible future IP centric links USB ether class drv BlueTooth IP profile MICS WMTS ZigBee possible future Link Profile Link Profile TISL Link Profile Note: this slide is adapted from the UML F&O UML F&O.UML F&O
pptx SLIDE 11 TISL l Provides uniform interface to upper layers l Has following services l Discovery of services and devices l Connectivity l Provisioning l Security l Quality Of Service (QoS)
pptx SLIDE 12 CNS Framework
pptx SLIDE 13 Whats next … l Next steps: o Align with IHE DPI Thursdays 11:00 AFC Pacific o Core content ready by 2013 September WGM o Draft ready by 2014 January WGM l Questions?
pptx SLIDE 14 TISL – connectivity primitives l TISL_connectivity_init l TISL_connectivity_get_providers l TISL_connectivity_set_provider l TISL_connectivity_set_callback l TISL_connectivity_set_mode l TISL_connectivity_connect l TISL_connectivity_disconnect l TISL_connectivity_accept l TISL_connectivity_listen
pptx SLIDE 15 TISL connectivity primitives continued l TISL_connectivity_send l TISL_connectivity_receive l TISL_connectivity_uninit l Preferred transport based on underlying layer support.
pptx SLIDE 16 TISL – Discovery of services and devices primitives l TISL_discovery_init l TISL_discovery_get_providers l TISL_discovery_set_provider l TISL_discovery_set_service_callback l TISL_discovery_set_device_callback l TISL_discovery_start l TISL_discovery_cancel l TISL_discovery_uninit l Preferred provider SSDP
pptx SLIDE 17 TISL provisioning primitives l TISL_provisioning_init l TISL_provisioning_get_providers l TISL_provisioning_set_provider l TISL_provisioning_add_item l TISL_provisioning_remove_item l TISL_provisioning_get_item l TISL_provisioning_uninit Preferred provider based on type of transport – can be DHCP, directory or some other mechanism
pptx SLIDE 18 TISL security primitives l TISL_security_init l TISL_security_get_providers l TISL_security_set_provider l TISL_security_select_key l TISL_security_encrypt l TISL_security_decrypt l TISL_security_sign l TISL_security_verify_signature
pptx SLIDE 19 CNS UML modeling l The following set of diagrams show initial mapping/transformation of previous UML, as follows: l MDC CNS - UML l Topological Framework and Overview. l Application Profiling l TISL Profiling – Link-level Profile topology l TILS Profiling – Primitives l Heuristics Profiles
pptx SLIDE 20 MDC - UML- Topological Framework and Overview (F&O) The CNS Framework mapped to UML. The constructs at left are Profile [compositions], and the ones at top to the right, are use cases (of composite Profiles); the lower set are MDS-level, and the upper set are composites. The initial exemplar Profiles are at lower left, e.g. Monitor, Infusor, and Ventilator in the Critical-Acute Care [Unit] scopes.
pptx SLIDE 21 MDC CNS - UML- Application Profiling APPLication-level CNS Profiling characterizes the key semantics relative to the x73 harmonization definitions (see Wiki for Harmonization Framework documents).Harmonization Framework
pptx SLIDE 22 MDC CNS - UML- TISL/Link-level component mapping topology Link-level Profiles are typed and related to a normalized set of TISL Primitives.
pptx SLIDE 24 MDC CNS - UML- Heuristic Profiles This diagram will be used to overlay particular Profiles for heuristic purposes, generally trying to select Profile components to show typical variations in the highlighted topological scope. Link-level notations are productions of [w][P/L]AN, e.g. PAN, LAN, P/LAN, wPAN, wP/LAN, and wLAN. See shaded areas on the following diagram (F&O) for key heuristics, highlighting key variations. Mgr Agent[s] Agent Mgr P/LAN [w]PLAN wPAN Mgr P/LAN _jw2a