Adoption Standard – Active. Within the context of the ISO\/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of communication between personal telehealth thermometer 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. It leverages appropriate portions of existing standards including ISO\/IEEE 11073 terminology, information models, 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 communication functionality for personal telehealth thermometer devices.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 4<\/td>\n | Blank Page <\/td>\n<\/tr>\n | ||||||
| 7<\/td>\n | Notice and Disclaimer of Liability Concerning the Use of IEEE Standards Documents <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | Translations Official statements Comments on standards Laws and regulations Copyrights <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | Photocopies Updating of IEEE Standards documents Errata Patents <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 1. Overview 1.1 Scope 1.2 Purpose 1.3 Context <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 1.4 Word usage 2. Normative references <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 3. Definitions, acronyms, and abbreviations 3.1 Definitions 3.2 Acronyms and abbreviations <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 4.2.5 Implementing the models 4.3 Compliance with other standards 5. Thermometer device concepts and modalities 5.1 General <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 5.2 Body temperature 6. Thermometer domain information model 6.1 Overview 6.2 Class extensions 6.3 Object instance diagram <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 6.4 Types of configuration 6.4.1 General <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 6.4.2 Standard configuration 6.4.3 Extended configuration 6.5 Medical device system object 6.5.1 MDS object attributes <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 6.5.2 MDS object methods <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 6.5.3 MDS object events <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 6.5.4 Other MDS services 6.5.4.1 GET service <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 6.5.4.2 SET service 6.6 Numeric objects 6.6.1 General 6.6.2 Temperature <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 6.7 Real-time sample array objects 6.8 Enumeration objects 6.9 PM store objects 6.10 Scanner objects 6.11 Class extension objects 6.12 Thermometer information model extensibility rules <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 7. Thermometer service model 7.1 General 7.2 Object access services <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | 7.3 Object access event report services 8. Thermometer communication model 8.1 Overview 8.2 Communications characteristics <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | 8.3 Association procedure 8.3.1 General 8.3.2 Agent procedure\u2014association request a) The version of the association procedure used by the agent shall be set to assoc-version1 (i.e., assoc-version = 0x80000000). b) The DataProtoList structure element of the data protocol identifier shall be set to data-proto-id-20601 (i.e., data-proto-id = 0x5079). c) The data-proto-info field shall contain a PhdAssociationInformation structure that shall contain the following parameter values: 1) The version of the data exchange protocol shall be set to protocol-version4 (i.e., protocol-version = 0x10000000). Support for any other version may be indicated by setting additional bits. When protocols lower than protocol-version4 are used, the … 2) At least the MDER encoding rules shall be supported (i.e., encoding-rules = 0x8000). 3) The protocol version bits and nomenclature version bits shall consist of valid combinations of bits as defined in Table 8. 4) The field functional-units may have the test association bits set but shall not have any other bits set. 5) The field system-type shall be set to sys-type-agent (i.e., system-type = 0x00800000). 6) The system-id field shall be set to the value of the System-Id attribute of the MDS object of the agent. The manager may use this field to determine the identity of the thermometer with which it is associating and, optionally, to implement a simple… <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | 7) The dev-config-id field shall be set to the value of the Dev-Configuration-Id attribute of the MDS object of the agent. 8) If the agent supports only the thermometer specialization, then the data-req-mode-capab field shall be set to data-req-supp-init-agent, the data-req-init-manager-count shall be set to zero, and the data-req-init-agent-count shall be set to 1. 8.3.3 Manager procedure\u2014association response a) The result field shall be set to an appropriate response from those defined in IEEE Std 11073-20601. For example, if all other conditions of the association protocol are satisfied, accepted is returned when the manager recognizes the dev-config-id … b) In the DataProtoList structure element, the data protocol identifier shall be set to data-proto-id-20601 (i.e., data-proto-id = 0x5079). c) The data-proto-info field shall be filled in with a PhdAssociationInformation structure that shall contain the following parameter values: 1) The manager following this specialization shall support protocol-version4. The manager may support additional protocol versions and select them if the agent offers them. When protocols lower than protocol-version4 are used, the manager shall use on… 2) The manager shall respond with a single selected encoding rule that is supported by both agent and manager. The manager shall support at least the MDER. 3) The manager shall select a valid combination of protocol version and nomenclature version as defined in Table 8. 4) The field functional-units shall have all bits reset except for those relating to a test association. 5) The field system-type shall be set to sys-type-manager (i.e., system-type = 0x80000000). 6) The system-id field shall contain the unique system ID of the manager device, which shall be a valid EUI-64 type identifier. 7) The field dev-config-id shall be manager-config-response (0). 8) The fields data-req-mode-capab, data-req-init-agent, and data-req-init-manager-count shall be 0. If the agent supports only the thermometer specialization, data-req-init-agent-count shall be 1. 8.4 Configuring procedure 8.4.1 General <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 8.4.2 Thermometer\u2014standard configuration 8.4.2.1 Agent procedure 8.4.2.2 Manager procedure <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | 8.5 Operating procedure 8.5.1 General 8.5.2 GET thermometer MDS attributes 8.5.3 Measurement data transmission <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | 8.6 Time synchronization 9. Test associations 9.1 General 9.2 Behavior with standard configuration 9.3 Behavior with extended configurations 10. Conformance 10.1 Applicability <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | 10.2 Conformance specification 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 IEEE Std 11073-10101) <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | 10.4 Implementation conformance statements 10.4.1 General format 10.4.2 General implementation conformance statement <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | 10.4.3 DIM MOC implementation conformance statement 10.4.4 MOC attribute ICS <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | 10.4.5 MOC notification implementation conformance statement <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | 10.4.6 MOC nomenclature conformance statement <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | Annex A (informative) Bibliography <\/td>\n<\/tr>\n | ||||||
| 46<\/td>\n | Annex B (normative) Any additional ASN.1 definitions <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | Annex C (normative) Allocation of identifiers <\/td>\n<\/tr>\n | ||||||
| 48<\/td>\n | Annex D (informative) Message sequence examples a) When the user connects the thermometer, the manager does not yet know the configuration of the agent and sends a response to the agent\u2019s association request with the result accepted-unknown-config. See E.2.2.2 and E.2.2.3 for the corresponding PDU … b) As a consequence of this, the agent sends its configuration information to the manager. After getting confirmation from the manager accepting the configuration of the agent, 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 \u201cRemote Operation Invoke | Get\u201d command. As a response, the agent reports its MDS object attributes to the manager using a data message … d) As a next step, the user of the agent device takes a single measurement. The measurement data is transmitted to the manager using a confirmed event report. After having successfully received the measurement data, the manager sends a confirmation to… 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\u2019s response is accepted, as it already knows the configuration of the agent from the previous measurement session. B… g) Finally, the last two steps shown are similar as in item d) and item e). The user takes a single confirmed measurement followed by releasing the association. <\/td>\n<\/tr>\n | ||||||
| 50<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 51<\/td>\n | E.2.2.3 Association response E.2.3 Previously known extended configuration E.2.3.1 General E.2.3.2 Association request E.2.3.3 Association response <\/td>\n<\/tr>\n | ||||||
| 52<\/td>\n | E.2.4 Standard configuration E.2.4.1 General E.2.4.2 Association request E.2.4.3 Association response <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | E.3 Configuration information exchange E.3.1 General E.3.2 Extended configuration E.3.2.1 General E.3.2.2 Remote operation invoke event report configuration <\/td>\n<\/tr>\n | ||||||
| 54<\/td>\n | 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 E.3.3.3 Remote operation response event report configuration <\/td>\n<\/tr>\n | ||||||
| 55<\/td>\n | 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 medical device system attributes request E.4.3 Get response with all MDS attributes <\/td>\n<\/tr>\n | ||||||
| 56<\/td>\n | E.5 Data reporting E.5.1 Confirmed measurement data transmission <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | E.5.2 Response to confirmed measurement data transmission E.6 Disassociation E.6.1 Association release request E.6.2 Association release response <\/td>\n<\/tr>\n | ||||||
| 58<\/td>\n | Annex F (informative) Revision history <\/td>\n<\/tr>\n | ||||||
| 59<\/td>\n | Blank Page <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" IEEE\/ISO International Standard–Health informatics–Device interoperability–Part 10408: Personal health device communication–Device specialization–Thermometer (Published)<\/b><\/p>\n |