BS EN ISO 11073-10421:2012
$198.66
Health informatics. Personal health device communication – Device specialization. Peak expiratory flow monitor (peak flow)
Published By | Publication Date | Number of Pages |
BSI | 2012 | 68 |
The scope of this standard is to establish a normative definition of communication between personal telehealth peak flow monitoring devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, and set top boxes) in a manner that enables plug-and-play interoperability. It leverages work done in other ISO/IEEE 11073 standards including existing terminology, information profiles, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting optionality in base frameworks in favor of interoperability. This standard defines a common core of functionality of a peak-flow monitoring device. The use case is restricted to personal respiratory monitoring and therefore does not include hospital-based spirometry. Continuous and high-acuity monitoring (e.g., for emergency response) are outside the scope of the use case.
In the context of personal health devices, a peak flow meter is a device used to measure the respiratory function of those managing respiratory conditions such as asthma and chronic obstructive pulmonary disease. The ability to identify declining respiratory status prior to the need for acute intervention improves the quality of life for the individual while reducing the overall costs of care. Respiratory status data are collected by a personal respiratory monitoring device and forwarded to a central data repository for review and action by a health care provider. The data are episodic in nature and are forwarded at designated intervals or when the person is symptomatic.
This standard provides the data modeling and its transport shim layer according to IEEE Std 11073-20601™-2008 and does not specify the measurement method.
PDF Catalog
PDF Pages | PDF Title |
---|---|
5 | Contents |
7 | Foreword |
9 | Introduction |
11 | 1. Overview 1.1 Scope |
12 | 1.2 Purpose 1.3 Context 2. Normative references |
13 | 3. Definitions, acronyms, and abbreviations 3.1 Definitions 3.2 Acronyms and abbreviations |
14 | 4. Introduction to ISO/IEEE 11073 personal health devices 4.1 General 4.2 Introduction to IEEE 11073-20601 modeling constructs |
15 | 5. Peak expiratory flow monitor device concepts and modalities 5.1 General 5.2 PEF |
17 | 6. Peak expiratory flow monitor domain information model 6.1 Overview 6.2 Class extensions 6.3 Object instance diagram |
19 | 6.4 Types of configuration 6.5 Medical device system object |
23 | 6.6 Numeric objects |
30 | 6.7 Real-time sample array objects 6.8 Enumeration objects |
32 | 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 7.2 Object access services |
33 | 7.3 Object access event report services |
34 | 8. Peak expiratory flow monitor communication model 8.1 Overview 8.2 Communications characteristics 8.3 Association procedure |
36 | 8.4 Configuring procedure |
38 | 8.5 Operating procedure |
39 | 8.6 Time synchronization 9. Test associations 9.1 Behavior with standard configuration |
40 | 9.2 Behavior with extended configurations 10. Conformance 10.1 Applicability 10.2 Conformance specification 10.3 Levels of conformance |
41 | 10.4 Implementation conformance statements |
46 | Annex A (informative) Bibliography |
47 | Annex B (normative) Any additional ASN.1 definitions |
48 | Annex C (normative) Allocation of identifiers |
49 | Annex D (informative) Message sequence examples |
51 | E.2.2.1 General E.2.2.2 Association request Annex E (informative) Protocol data unit examples |
52 | E.2.2.3 Association response E.2.3.1 General E.2.3.2 Association request |
53 | E.2.3.3 Association response E.2.4.1 General E.2.4.2 Association request |
54 | E.2.4.3 Association response E.3.2.1 General E.3.2.2 Remote operation invoke event report configuration |
57 | E.3.2.3 Remote operation response event report configuration E.3.3.1 General E.3.3.2 Remote operation invoke event report configuration E.3.3.3 Remote operation response event report configuration E.3.4.1 General E.3.4.2 Remote operation invoke event report configuration |
58 | E.3.4.3 Remote operation response event report configuration E.4.1.1 General E.4.1.2 Get all medical device system attributes request E.4.1.3 Get response with all MDS attributes |
62 | Annex F (informative) IEEE list of participants |