BS EN ISO 11073-10472:2012
$215.11
Health Informatics. Personal health device communication – Device specialization. Medication monitor
Published By | Publication Date | Number of Pages |
BSI | 2012 | 80 |
Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between medication monitoring devices and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes) in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology and information models. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting ambiguity in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for medication monitors. In this context, medication monitors are defined as devices that have the ability to determine and communicate (to a manager) measures of a user’s adherence to a medication regime.
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 3. Definitions, acronyms, and abbreviations |
13 | 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 4.2.1 General 4.2.2 Domain information model 4.2.3 Service model 4.2.4 Communication model |
15 | 4.2.5 Implementing the models 5. Medication monitor device concepts and modalities 5.1 General |
16 | 5.2 Model usage examples 5.2.1 General 5.2.2 Sequenced medication monitor example types |
17 | 5.2.3 Non-sequenced medication monitor example types 5.3 Medication dispensed |
18 | 5.4 Status reporter 5.5 User feedback |
19 | 5.6 Usage patterns 6. Medication monitor domain information model 6.1 Overview 6.2 Class extensions |
20 | 6.3 Object instance diagram |
21 | 6.4 Types of configuration 6.4.1 General 6.4.2 Standard configuration |
22 | 6.4.3 Extended configuration 6.5 Medical device system object 6.5.1 MDS object attributes |
23 | 6.5.2 MDS object methods |
24 | 6.5.3 MDS object events |
25 | 6.5.4 Other MDS services |
26 | 6.6 Numeric objects 6.6.1 General 6.6.2 Fixed-dosage medication dispensed |
28 | 6.6.3 Variable-dosage medication dispensed |
30 | 6.6.4 User feedback |
32 | 6.7 Real-time sample array objects 6.8 Enumeration objects 6.8.1 General |
33 | 6.8.2 Status reporter |
37 | 6.9 PM-store objects 6.9.1 General |
38 | 6.9.2 Persistent store model 6.9.3 PM-store object attributes |
39 | 6.9.4 PM-store object methods 6.9.5 PM-store object events |
40 | 6.9.6 PM-store object services 6.9.7 PM-segment objects 6.10 Scanner objects |
41 | 6.11 Class extension objects 6.12 Medication monitor information model extensibility rules 7. Medication monitor service model 7.1 General 7.2 Object access services |
42 | 7.3 Object access event report services |
43 | 8. Medication monitor communication model 8.1 Overview 8.2 Communications characteristics 8.3 Association procedure 8.3.1 General 8.3.2 Agent procedure—association request |
44 | 8.3.3 Manager procedure—association response |
45 | 8.4 Configuring procedure 8.4.1 General 8.4.2 Medication monitor—standard configurations |
51 | 8.5 Operating procedure 8.5.1 General 8.5.2 GET medication monitor MDS attributes |
52 | 8.5.3 Measurement data transmission 8.6 Time synchronization 9. Test associations 9.1 Behavior with standard configuration |
53 | 9.2 Behavior with extended configurations 10. Conformance 10.1 Applicability 10.2 Conformance specification |
54 | 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:2004 [B1]) 10.4 Implementation conformance statements 10.4.1 General format |
55 | 10.4.2 General implementation conformance statement |
57 | 10.4.3 DIM MOC implementation conformance statement 10.4.4 MOC attribute ICS |
58 | 10.4.5 MOC notification implementation conformance statement |
59 | 10.4.6 MOC nomenclature conformance statement |
60 | Annex A (informative) Bibliography |
61 | Annex B (normative) Any additional ASN.1 definitions |
62 | Annex C (normative) Allocation of identifiers |
63 | Annex D (informative) Message sequence examples |
65 | 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 |
66 | E.2.2.3 Association response E.2.3.1 General E.2.3.2 Association request |
67 | E.2.3.3 Association response E.2.4 Standard configuration E.2.4.1 General E.2.4.2 Association request |
68 | E.2.4.3 Association response E.3 Configuration information exchange E.3.1 General |
69 | E.3.2 Extended configuration E.3.2.1 General E.3.2.2 Remote operation invoke event report configuration E.3.2.3 Remote operation response event report configuration |
70 | E.3.3 Known 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 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 |
71 | E.4 GET MDS attributes service 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 |
72 | E.5 Data reporting E.5.1 Confirmed measurement data transmission 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) IEEE list of participants |