IEEE 11073-10421-2024
$50.38
ISO/IEEE International Standard: Health informatics—Device interoperability—Part 10421: Personal health device communication—Device specialization—Peak expiratory flow monitor (peak flow) (Published)
| Published By | Publication Date | Number of Pages |
| IEEE | 2024 | 76 |
Adoption Standard – Active. Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of communication is established in this standard between personal telehealth peak expiratory flow monitor devices and compute engines (e.g., cell phones, personal computers, personal health appliances, and set-top boxes) in a manner that enables plug-and-play interoperability. Appropriate portions of existing standards are leveraged, including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. The use of specific term codes, formats, and behaviors is specified in telehealth environments restricting optionality in base frameworks in favor of interoperability. A common core of communication functionality is defined for personal telehealth peak expiratory flow monitor devices.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 7 | Notice and Disclaimer of Liability Concerning the Use of IEEE Standards Documents |
| 8 | Translations Official statements Comments on standards Laws and regulations |
| 9 | Data privacy Copyrights Photocopies Updating of IEEE Standards documents Errata |
| 10 | Patents IMPORTANT NOTICE |
| 17 | 1. Overview 1.1 Scope 1.2 Purpose |
| 18 | 1.3 Word usage 2. Normative references 3. Definitions, acronyms, and abbreviations 3.1 Definitions |
| 19 | 3.2 Acronyms and abbreviations |
| 20 | 4. Introduction to ISO/IEEE 11073 personal health devices 4.1 General 4.2 Introduction to IEEE 11073-20601 modeling constructs 4.2.1 General |
| 21 | 4.2.2 Domain information model 4.2.3 Service model 4.2.4 Communication model 4.2.5 Implementing the models 4.3 Compliance with other standards |
| 22 | 5. Peak expiratory flow monitor device concepts and modalities 5.1 General 5.2 PEF |
| 24 | 6. Peak expiratory flow monitor domain information model 6.1 Overview 6.2 Class extensions 6.3 Object instance diagram |
| 26 | 6.4 Types of configuration 6.4.1 General 6.4.2 Standard configuration 6.4.3 Extended configuration 6.5 Medical device system object 6.5.1 MDS object attributes |
| 28 | 6.5.2 MDS object methods 6.5.3 MDS object events |
| 29 | 6.5.4 Other MDS services 6.5.4.1 GET service |
| 30 | 6.5.4.2 SET service 6.6 Numeric objects 6.6.1 General 6.6.2 PEF |
| 33 | 6.6.3 Personal best |
| 36 | 6.6.4 FEV1 |
| 39 | 6.6.5 FEV6 (optional) |
| 40 | 6.7 Real-time sample array objects 6.8 Enumeration objects 6.8.1 Reading status |
| 43 | 6.9 PM-store objects 6.10 Scanner objects 6.11 Class extension objects 6.12 Peak expiratory flow monitor information model extensibility rules 7. Peak expiratory flow monitor service model 7.1 General |
| 44 | 7.2 Object access services |
| 45 | 7.3 Object access event report services 8. Peak expiratory flow monitor communication model 8.1 Overview 8.2 Communications characteristics |
| 46 | 8.3 Association procedure 8.3.1 General 8.3.2 Agent procedure—association request |
| 47 | 8.3.3 Manager procedure—association response |
| 48 | 8.4 Configuring procedure 8.4.1 General 8.4.2 Peak expiratory flow monitor—standard configuration 8.4.2.1 Agent procedure |
| 50 | 8.4.2.2 Manager procedure 8.5 Operating procedure 8.5.1 General |
| 51 | 8.5.2 GET Peak expiratory flow monitor MDS attributes 8.5.3 Measurement data transmission 8.6 Time synchronization 9. Test associations 9.1 Behavior with standard configuration |
| 52 | 9.2 Behavior with extended configurations 10. Conformance 10.1 Applicability 10.2 Conformance specification |
| 53 | 10.3 Levels of conformance 10.3.1 General 10.3.2 Conformance level 1: Base conformance 10.3.3 Conformance level 2: Extended nomenclature (ASN.1 and/or ISO/IEEE 11073-10101) 10.4 Implementation conformance statements (ICSs) 10.4.1 General format |
| 54 | 10.4.2 General ICS |
| 55 | 10.4.3 DIM MOC implementation conformance statement |
| 56 | 10.4.4 MOC attribute ICS 10.4.5 MOC notification ICS |
| 57 | 10.4.6 MOC nomenclature ICS |
| 58 | Annex A (informative) Bibliography |
| 59 | Annex B (normative) Any additional ASN.1 definitions |
| 60 | Annex C (normative) Allocation of identifiers |
| 61 | Annex D (informative) Message sequence examples a) When the user connects the medication monitor, the manager does not recognize the agent’s configuration and sends a response to the agent’s association request with the result accepted-unknown-config. See E.2.2.2 and E.2.2.3 for the corresponding P… b) As a consequence of this, the agent negotiates its configuration information to the manager. After getting confirmation from the manager accepting the agent’s configuration, the agent device is ready to send measurements. Both devices enter the Ope… c) Subsequently, the manager may request the MDS object attributes of the agent by sending a data message with the “Remote Operation Invoke | Get” command. Note that the manager may request the MDS object attributes as soon as the agent enters the Ass… d) As a next step, the user of the agent device takes a single measurement. The measurement data are transmitted to the manager using a confirmed event report. After having successfully received the measurement data, the manager sends a confirmation t… e) The user ends the measurement session (e.g., by pushing a proper button on the device or just by not using the device for a duration longer than a certain time period). As a consequence, the agent disassociates from the manager by sending an associ… f) When the agent requests to associate to the manager for the next measurement session (e.g., the next day), the result in the manager’s response is accepted, as it already knows the agent’s configuration from the previous measurement session. Both d… g) Finally, the last two steps shown are similar to item d) and item e). The user takes a single confirmed measurement followed by releasing the association. |
| 63 | Annex E (informative) Protocol data unit examples E.1 General E.2 Association information exchange E.2.1 General E.2.2 Extended configuration E.2.2.1 General E.2.2.2 Association request |
| 64 | E.2.2.3 Association response E.2.3 Previously known extended configuration E.2.3.1 General E.2.3.2 Association request |
| 65 | E.2.3.3 Association response E.2.4 Standard configuration E.2.4.1 General E.2.4.2 Association request |
| 66 | E.2.4.3 Association response E.3 Configuration information exchange E.3.1 General E.3.2 Extended configuration E.3.2.1 General |
| 67 | E.3.2.2 Remote operation invoke event report configuration |
| 69 | E.3.2.3 Remote operation response event report configuration E.3.3 Known configuration E.3.3.1 General E.3.3.2 Remote operation invoke event report configuration |
| 70 | E.3.3.3 Remote operation response event report configuration E.3.4 Standard configuration E.3.4.1 General E.3.4.2 Remote operation invoke event report configuration E.3.4.3 Remote operation response event report configuration E.4 GET MDS attributes service E.4.1 General E.4.2 Get all MDS attributes request |
| 71 | E.4.3 Get response with all MDS attributes E.5 Data reporting E.5.1 Confirmed measurement data transmission |
| 72 | E.5.2 Response to confirmed measurement data transmission |
| 73 | E.6 Disassociation E.6.1 Association release request E.6.2 Association release response |
| 74 | Annex F (informative) Revision History |
| 75 | Blank Page |
