IEEE 11073 10207 2017:2018 Edition
$149.50
IEEE Health informatics–Point-of-care medical device communication Part 10207: Domain Information and Service Model for Service-Oriented Point-of-Care Medical Device Communication
| Published By | Publication Date | Number of Pages |
| IEEE | 2018 | 437 |
New IEEE Standard – Active. Within the context of the ISO/IEEE 11073™ family of standards for point-of-care medical device communication, a Participant Model derived from the ISO/IEEE11073-10201 Domain Information Model is provided in this standard. The Participant Model specifies the structure of medical information objects. This standard also defines an abstract Communication Model to support the exchange of medical information objects. All elements of the Participant Model and Communication Model are specified using XML Schema. Core subjects of the Participant Model comprise modelling of medical device-related data, e.g., measurements and settings, alert systems, contextual information (e.g., patient demographics and location information), remote control, and archival information. Model extensibility is provided inherently through the use of XML Schema.textual information like patient demographics and location information, remote control, and archival. Model extensibility is provided inherently through the use of XML Schema. (Additional files are available for this standard at http://standards.ieee.org/downloads/11073/)
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 1 | IEEE Std 11073-10207™- 2017 Front cover |
| 2 | Title page |
| 4 | Important Notices and Disclaimers Concerning IEEE Standards Documents |
| 7 | Participants |
| 8 | Introduction |
| 9 | Contents |
| 22 | 1. Overview 1.1 Scope 1.2 Purpose |
| 23 | 2. Normative references |
| 24 | 3. Definitions and notational conventions 3.1 Definitions |
| 26 | 3.2 Notational conventions 3.2.1 General |
| 27 | 3.2.2 XML Schema namespaces 3.2.3 XML Schema referencing 3.2.4 XML Schema type description |
| 29 | 4. Introduction to BICEPS |
| 31 | 5. Participant Model 5.1 Overview 5.2 Background 5.2.1 General 5.2.2 Handle |
| 32 | 5.2.3 Coded value |
| 33 | 5.2.4 Instance identifier 5.2.4.1 General 5.2.4.2 Encoding of unknown elements 5.2.5 MDIB versioning 5.2.5.1 General 5.2.5.2 Descriptor version |
| 34 | 5.2.5.3 State version 5.2.5.4 MdDescription version 5.2.5.5 MdState version 5.2.5.6 MDIB version |
| 35 | 5.3 Descriptive part 5.3.1 General |
| 36 | 5.3.2 MDIB 5.3.3 MdDescription 5.3.4 MDS 5.3.5 Clock 5.3.6 Battery 5.3.7 SystemContext |
| 38 | 5.3.8 SCO 5.3.9 Operation |
| 39 | 5.3.10 VMD 5.3.11 Channel 5.3.12 Metric 5.3.12.1 General |
| 40 | 5.3.12.2 Time-related attributes |
| 41 | 5.3.12.3 Detect obsolete metric values 5.3.13 AlertSystem |
| 42 | 5.4 State part 5.4.1 General 5.4.2 Mapping between descriptor and state 5.4.3 Single state vs. multi-state |
| 43 | 5.4.4 Context state 5.4.5 BindingMdibVersion and UnbindingMdibVersion |
| 44 | 5.4.6 Device component and metric activation |
| 45 | 5.4.7 Metric activation state |
| 46 | 5.4.8 SCO operation activation state |
| 47 | 5.4.9 Alert state 5.4.9.1 General 5.4.9.2 Alert condition presence 5.4.9.3 Present alarm conditions |
| 48 | 5.4.9.4 Valid alert attribute combinations |
| 50 | 6. Alert signal delegation 6.1 General 6.2 Delegable alert signals 6.2.1 Advertisement of a delegable alert signal |
| 51 | 6.2.2 Generating a delegable alert signal 6.2.3 Consecutive generation trigger of a delegable alert signal 6.2.4 Invalid delegable alert signal generation 6.2.5 Exceeding the confirmation timeout 6.2.6 Mutual exclusion of participants |
| 52 | 6.2.7 Avoiding superfluous SCO operation calls 6.2.8 Setting the signal generation delay and presence of a delegable alert signal 6.2.8.1 Being ready to generate a delegable alert signal 6.2.8.2 Generating a delegable alert signal 6.2.8.3 Setting the presence of a delegable alert signal to latched or acknowledged |
| 53 | 6.3 Fallback alert signals 6.3.1 Advertisement of a fallback alert signal 6.3.2 System signal activation 6.3.3 Setting the fallback alert signal when a delegable alert signal is deactivated |
| 54 | 7. Communication Model 7.1 General 7.2 Message exchange patterns 7.2.1 General 7.2.2 Request-Response 7.2.3 Publish-Subscribe |
| 55 | 7.2.4 Streaming 7.3 Service Model 7.3.1 General 7.3.2 GET SERVICE |
| 56 | 7.3.3 SET SERVICE |
| 57 | 7.3.4 DESCRIPTION EVENT SERVICE 7.3.5 STATE EVENT SERVICE |
| 58 | 7.3.6 CONTEXT SERVICE 7.3.7 WAVEFORM SERVICE 7.3.8 CONTAINMENT TREE SERVICE |
| 59 | 7.3.9 ARCHIVE SERVICE 7.3.10 LOCALIZATION SERVICE |
| 60 | 7.4 Message Model 7.4.1 General 7.4.2 Additional requirements |
| 61 | 7.4.3 Operation-invoked report |
| 63 | 8. Extension Model |
| 64 | 9. Discovery Model 9.1 General 9.2 Implicit discovery 9.3 Explicit discovery |
| 65 | 10. Nonfunctional requirements 10.1 General 10.2 Patient safety considerations 10.3 Cybersecurity considerations |
| 66 | 10.4 Clinical effectiveness 10.5 Regulatory considerations |
| 67 | 11. Conformance 11.1 Overview 11.2 General format |
| 68 | 11.3 ICS tables |
| 71 | Annex A (normative) Extension Model |
| 73 | Annex B (normative) Participant Model |
| 339 | Annex C (normative) Message Model |
| 425 | Annex D (informative) Examples D.1 Containment tree D.2 MDIB versioning |
| 430 | D.3 MDIB sequencing |
| 431 | D.4 BICEPS discovery |
| 433 | D.5 Remote control |
| 434 | D.6 Alert signal generation |
| 436 | Annex E (informative) Bibliography |
Related products
-
IEEE 11073-10207-2019
ISO/IEEE International Standard – Health informatics–Point-of-care medical device communication – Part 10207: Domain Information and…
-
BS ISO/IEEE 11073-10207:2019
Health informatics. Personal health device communication – Domain information and service model for service-oriented point-of-care…
-
IEEE/ISO 11073 10207 2019
ISO/IEEE International Standard – Health informatics–Point-of-care medical device communication – Part 10207: Domain Information and…
