ArticleslgStudy

computer science

IEEE 11073 service-oriented device connectivity

IEEE 11073 service-oriented device connectivity is a computer science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand IEEE 11073 service-oriented device connectivity rather than just read about it. In short: The IEEE 11073 service-oriented device connectivity (SDC) family of standards defines a communication protocol for point-of-care (PoC) medical devices. The main purpose is to enable manufacturer-independent medical device-to-device interoperability.

IEEE 11073 service-oriented device connectivity — main illustration
IEEE 11073 service-oriented device connectivity — illustration

Key takeaways

  • IEEE 11073 service-oriented device connectivity belongs to computer science; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect IEEE 11073 service-oriented device connectivity to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of IEEE 11073 service-oriented device connectivity from memory before moving on to harder problems.

Reference excerpt

The IEEE 11073 service-oriented device connectivity (SDC) family of standards defines a communication protocol for point-of-care (PoC) medical devices. The main purpose is to enable manufacturer-independent medical device-to-device interoperability. Furthermore, interconnection between medical devices and medical information systems is enabled. However, IEEE 11073 SDC does not compete with established and emerging standards like HL7 v2 or HL7 FHIR. IEEE 11073 SDC is part of the established ISO/IEEE 11073 family of standards. IEEE 11073 SDC is based on the paradigm of a service-oriented architecture (SOA). The IEEE 11073 SDC family of standards currently comprises three parts: Core Standards, Participant Key Purpose (PKIP) standards, and Devices Specialisation (DevSpec) standards. The Core Standards consist of a transport standard, ISO/IEEE 11073-20702, called Medical Devices Communication Profile for Web Services, a Domain Information and Service Model (ISO/IEEE 11073-10207), and Architecture and Binding definition (ISO/IEEE 11073-20701). While the three core standards have been approved and published by the IEEE as well as by ISO, PKIPs and DevSpecs are currently under development. The concepts have been technically and clinically evaluated. Comprehensive demonstrators were shown, for example, at the conhIT exhibitions 2016 and 2017.

IEEE 11073 SDC Core Standards

ISO/IEEE 11073-20702 The standard "ISO/IEEE International Standard for Health informatics - Point-of-care medical device communication - Part 20702: Medical devices communication profile for web services" (short Medical DPWS or MDPWS) enables the foundational interoperability between medical devices. This includes the ability of medical devices to exchange data safely in a distributed system and the ability to discover network participants dynamically. MDPWS is derived from the OASIS standard Devices Profile for Web Services (DPWS). It defines extensions and restrictions to meet safety requirements of medical devices for high acuity environments.

ISO/IEEE 11073-10207 The standard "ISO/IEEE International Standard - Health informatics--Point-of-care medical device communication - Part 10207: Domain Information and Service Model for Service-Oriented Point-of-Care Medical Device Communication" is derived from the IEEE 11073-10201 Domain Information Model. It is designed to meet the requirements of networked systems of medical devices establishing multipoint-to-multipoint communication. The Domain Information Model defines the capability description of the medical devices as well as the representation of the current state. The Service Model specifies the way in which a service consumer can interact with medical devices, implementing the role of a service provider. IEEE 11073-10207 enables the structural interoperability between medical devices. The non-normative name is Basic Integrated Clinical Environment Protocol Specification (BICEPS).

ISO/IEC/IEEE 11073-20701 The "ISO/IEC/IEEE International Standard for Health informatics - Device interoperability - Part 20701:Point-of-care medical device communication--Service oriented medical device exchange architecture and protocol binding" defines the allover service-oriented architecture, specifies the binding between IEEE 11073-20702 and IEEE 11073–10207, and specifies the binding to other standards like Network Time Protocol (NTP) or Differentiated Services (DiffServ) for aspects like time synchronization and Quality of Service (QoS) requirements. Together with the usage of terminology standards (like IEEE 11073-10101), this standard contributes to the semantic interoperability of medical devices. Due to its nature of binding the other SDC standards together, it is often referred to as "SDC GLUE".

IEEE 11073-1070X Participant Key Purpose (PKP) Series PKPs describe process requirements according to the role of a network participant. While P11073-10700 defines the Base PKP with basic requirements for participating providers and consumers, the three additional PKP standards focus on specific functionalities:

Providing and consuming information in terms of metric data (IEEE P11073-10701), Providing and consuming alerts (IEEE P11073-10702), and Providing and consuming external control functionalities (IEEE P11072-10703). PKPs are thus independent from the particular medical devices and their concrete medical use case. However, they mainly restrict the IEEE 11073 SDC Core standards to enable safe and interoperable medical device systems and to facilitate the approval process.

IEEE 11073-1072X Devices Specialisation (DevSpec) Series In contrast to PKPs, the DevSpecs are standards for particular classes of medical devices. DevSpecs describe the way the devices are modelled in the network representation and define requirements for the interaction of provider and consumer via SDC, if necessary. Currently, the PoCSpec project develops DevSpecs for High-Frequency Surgical Equipment (IEEE P11073-10721), endoscopic camera and light source (IEEE P11073-10722 and -10723), insufflator (IEEE P11073-10724), and medical suction and irrigation pump (IEEE P11073-10725). Modules that can be used by different types of device are defined in the so-called Module Specifications (ModSpecs, IEEE P11073-10720).

Open Source Implementations There are open source libraries available implementing the IEEE 11073 SDC standards:

SDCLib/C (written in C++, formerly known as OSCLib) SDCLib/J (written in Java, formerly known as SoftICE) SDCLib/J (fork) (written in Java, fork of the former main author which implements the latest features) SDCri (SDC Reference Implementation) (written in Java) sdc11073 (written in Python, formerly known as pySDC) protoSDC-rs (written in Rust) openSDC (written in Java, not maintained since 2019)

References

Illustrations

IEEE 11073 service-oriented device connectivity: Demonstrator at conhIT trade fair 2016 showing manufacturer-independent medical device interoperability based on IEEE 11073 SDC standards family.
Demonstrator at conhIT trade fair 2016 showing manufacturer-independent medical device interoperability based on IEEE 11073 SDC standards family.

Worked examples

Example 1 — a first encounter with IEEE 11073 service-oriented device connectivity

Start with the simplest possible case. Write down what IEEE 11073 service-oriented device connectivity claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In computer science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to IEEE 11073 service-oriented device connectivity before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about IEEE 11073 service-oriented device connectivity ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of IEEE 11073 service-oriented device connectivity

In research
IEEE 11073 service-oriented device connectivity appears in computer science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses IEEE 11073 service-oriented device connectivity in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
IEEE 11073 service-oriented device connectivity is common in secondary-school and first-year university syllabi. It links to neighbouring topics Computing in medical imaging, Health standards, IEEE standards, so understanding it makes those chapters shorter.
In everyday life
Look for IEEE 11073 service-oriented device connectivity outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study IEEE 11073 service-oriented device connectivity in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what IEEE 11073 service-oriented device connectivity means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain IEEE 11073 service-oriented device connectivity out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is IEEE 11073 service-oriented device connectivity in simple terms?

The IEEE 11073 service-oriented device connectivity (SDC) family of standards defines a communication protocol for point-of-care (PoC) medical devices. The main purpose is to enable manufacturer-independent medical device-to-device interoperability.

Why does IEEE 11073 service-oriented device connectivity matter?

Because it connects several computer science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study IEEE 11073 service-oriented device connectivity?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on IEEE 11073 service-oriented device connectivity.

Tags

  • Computing in medical imaging
  • Health standards
  • IEEE standards
  • ISO standards

Keep exploring