BS ISO/IEEE 11073-10207:2019
$215.11
Health informatics. Personal health device communication – Domain information and service model for service-oriented point-of-care medical device communication
| Published By | Publication Date | Number of Pages |
| BSI | 2019 | 442 |
The scope of this standard is the definition and structuring of information that is communicated in a distributed system of point-of-care medical devices and medical information technology (IT) systems in which medical data needs to be exchanged or networked point-of-care medical devices need to be controlled. The standard provides a Participant Model and Communication Model derived from the IEEE 11073™ Domain Information Model (IEEE 11073-10201™ DIM). Furthermore, it utilizes the IEEE 11073 Nomenclature (IEEE 11073-10101™) and supports other coding systems to convey the semantics of any information elements.1
The definition of network transport mechanisms is outside the scope of this standard.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 2 | undefined |
| 3 | IEEE Std 11073-10207™- 2017 Front cover |
| 5 | Blank Page |
| 6 | ISO Foreword |
| 8 | Important Notices and Disclaimers Concerning IEEE Standards Documents |
| 11 | Participants |
| 12 | Introduction |
| 13 | Contents |
| 26 | Title page 1. Overview 1.1 Scope 1.2 Purpose |
| 27 | 2. Normative references |
| 28 | 3. Definitions and notational conventions 3.1 Definitions |
| 30 | 3.2 Notational conventions 3.2.1 General |
| 31 | 3.2.2 XML Schema namespaces 3.2.3 XML Schema referencing 3.2.4 XML Schema type description |
| 33 | 4. Introduction to BICEPS |
| 35 | 5. Participant Model 5.1 Overview 5.2 Background 5.2.1 General 5.2.2 Handle |
| 36 | 5.2.3 Coded value |
| 37 | 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 |
| 38 | 5.2.5.3 State version 5.2.5.4 MdDescription version 5.2.5.5 MdState version 5.2.5.6 MDIB version |
| 39 | 5.3 Descriptive part 5.3.1 General |
| 40 | 5.3.2 MDIB 5.3.3 MdDescription 5.3.4 MDS 5.3.5 Clock 5.3.6 Battery 5.3.7 SystemContext |
| 42 | 5.3.8 SCO 5.3.9 Operation |
| 43 | 5.3.10 VMD 5.3.11 Channel 5.3.12 Metric 5.3.12.1 General |
| 44 | 5.3.12.2 Time-related attributes |
| 45 | 5.3.12.3 Detect obsolete metric values 5.3.13 AlertSystem |
| 46 | 5.4 State part 5.4.1 General 5.4.2 Mapping between descriptor and state 5.4.3 Single state vs. multi-state |
| 47 | 5.4.4 Context state 5.4.5 BindingMdibVersion and UnbindingMdibVersion |
| 48 | 5.4.6 Device component and metric activation |
| 49 | 5.4.7 Metric activation state |
| 50 | 5.4.8 SCO operation activation state |
| 51 | 5.4.9 Alert state 5.4.9.1 General 5.4.9.2 Alert condition presence 5.4.9.3 Present alarm conditions |
| 52 | 5.4.9.4 Valid alert attribute combinations |
| 54 | 6. Alert signal delegation 6.1 General 6.2 Delegable alert signals 6.2.1 Advertisement of a delegable alert signal |
| 55 | 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 |
| 56 | 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 |
| 57 | 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 |
| 58 | 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 |
| 59 | 7.2.4 Streaming 7.3 Service Model 7.3.1 General 7.3.2 GET SERVICE |
| 60 | 7.3.3 SET SERVICE |
| 61 | 7.3.4 DESCRIPTION EVENT SERVICE 7.3.5 STATE EVENT SERVICE |
| 62 | 7.3.6 CONTEXT SERVICE 7.3.7 WAVEFORM SERVICE 7.3.8 CONTAINMENT TREE SERVICE |
| 63 | 7.3.9 ARCHIVE SERVICE 7.3.10 LOCALIZATION SERVICE |
| 64 | 7.4 Message Model 7.4.1 General 7.4.2 Additional requirements |
| 65 | 7.4.3 Operation-invoked report |
| 67 | 8. Extension Model |
| 68 | 9. Discovery Model 9.1 General 9.2 Implicit discovery 9.3 Explicit discovery |
| 69 | 10. Nonfunctional requirements 10.1 General 10.2 Patient safety considerations 10.3 Cybersecurity considerations |
| 70 | 10.4 Clinical effectiveness 10.5 Regulatory considerations |
| 71 | 11. Conformance 11.1 Overview 11.2 General format |
| 72 | 11.3 ICS tables |
| 75 | Annex A (normative) Extension Model |
| 77 | Annex B (normative) Participant Model |
| 343 | Annex C (normative) Message Model |
| 429 | Annex D (informative) Examples D.1 Containment tree D.2 MDIB versioning |
| 434 | D.3 MDIB sequencing |
| 435 | D.4 BICEPS discovery |
| 437 | D.5 Remote control |
| 438 | D.6 Alert signal generation |
| 440 | Annex E (informative) Bibliography |
Related products
-
BS EN ISO 11073-10407:2011
Health informatics. Personal health device communication – Device specialization. Blood pressure monitor Published By Publication…
-
BS ISO/IEEE 11073-10207:2019
Health informatics. Personal health device communication – Domain information and service model for service-oriented point-of-care…
-
BS EN ISO/IEEE 11073-10407:2022:2023 Edition
Health informatics. Device interoperability – Personal health device communication. Device specialization. Blood pressure monitor Published…
