🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS EN ISO/IEEE 11073-10415:2022:2023 Edition

BS EN ISO/IEEE 11073-10415:2022:2023 Edition

$198.66

Health informatics. Device interoperability – Personal health device communication. Device specialization. Weighing scale

Published By Publication Date Number of Pages
BSI 2023 68
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Categories: ,

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

Within the context of the ISO/IEEE 11073 family of standards for device communication, this document establishes a normative definition of communication between personal telehealth weighing scale 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 document defines a common core of communication functionality for personal telehealth weighing scales.

PDF Catalog

PDF Pages PDF Title
2 undefined
4 European foreword
Endorsement notice
6 Blank Page
9 Notice and Disclaimer of Liability Concerning the Use of IEEE Standards Documents
10 Translations
Official statements
Comments on standards
Laws and regulations
Copyrights
11 Photocopies
Updating of IEEE Standards documents
Errata
Patents
18 1. Overview
1.1 Scope
1.2 Purpose
1.3 Context
19 1.4 Word usage
2. Normative references
20 3. Definitions, acronyms, and abbreviations
3.1 Definitions
3.2 Acronyms and abbreviations
21 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
22 4.2.5 Implementing the models
4.3 Compliance with other standards
5. Weighing scale device concepts and modalities
5.1 General
5.2 Body weight
23 5.3 Body height
5.4 Body mass index
6. Weighing scale domain information model
6.1 Overview
6.2 Class extensions
6.3 Object instance diagram
25 6.4 Types of configuration
6.4.1 General
6.4.2 Standard configuration
6.4.3 Extended configuration
26 6.5 Medical device system object
6.5.1 MDS object attributes
27 6.5.2 MDS object methods
28 6.5.3 MDS object events
29 6.5.4 Other MDS services
6.5.4.1 GET service
6.5.4.2 SET service
6.6 Numeric objects
6.6.1 General
6.6.2 Body weight
32 6.6.3 Body height
33 6.6.4 Body mass index
34 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 Weighing scale information model extensibility rules
35 7. Weighing scale service model
7.1 General
7.2 Object access services
37 7.3 Object access event report services
8. Weighing scale communication model
8.1 Overview
8.2 Communications characteristics
38 8.3 Association procedure
8.3.1 General
8.3.2 Agent procedure—association 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 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 9.
4) The field functional-units may have the test association bits set but shall not have any other bits set.
39 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 weighing scale with which it is associating and, optionally, to implement a sim…
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 weighing scale specialization, then the field indicating the data request modes (data-req-mode-capab) supported by the weighing scale agent shall be set to data-req-supp-init-agent.
9) If the agent supports only the weighing scale specialization, then the data-req-init-manager-count field shall be set to 0, and the data-req-init-agent-count field shall be set to 1.
8.3.3 Manager procedure—association 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 9.
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 field data-req-mode-capab shall be 0.
9) The field data-req-init-*-count shall be 0.
40 8.4 Configuring procedure
8.4.1 General
8.4.2 Weighing scale—standard configuration
8.4.2.1 Agent procedure
41 8.4.2.2 Manager procedure
8.5 Operating procedure
8.5.1 General
8.5.2 GET weighing scale MDS attributes
42 8.5.3 Measurement data transmission
8.6 Time synchronization
9. Test associations
9.1 General
9.2 Behavior with standard configuration
9.3 Behavior with extended configurations
43 10. Conformance
10.1 Applicability
10.2 Conformance specification
10.3 Levels of conformance
10.3.1 General
10.3.2 Conformance level 1: Base conformance
44 10.3.3 Conformance level 2: Extended nomenclature (ASN.1 and/or IEEE Std 11073-10101)
10.4 Implementation conformance statements
10.4.1 General format
10.4.2 General implementation conformance statement
46 10.4.3 DIM MOC implementation conformance statement
47 10.4.4 MOC attribute implementation conformance statement
10.4.5 MOC notification implementation conformance statement
48 10.4.6 MOC nomenclature conformance statement
49 Annex A (informative) Bibliography
50 Annex B (normative) Any additional ASN.1 definitions
51 Annex C (normative) Allocation of identifiers
52 Annex D (informative) Message sequence examples
a) When the user connects the weighing scale, the manager does not yet 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 configuration of the agent, the agent device is ready to send measurements. Both devices enter th…
c) Subsequently, the manager requests 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 Associ…
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’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 as in item d) and item e). The user takes a single confirmed measurement followed by releasing the association.
54 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
55 E.2.2.3 Association response
E.2.3 Previously known extended configuration
E.2.3.1 General
E.2.3.2 Association request
56 E.2.3.3 Association response
E.2.4 Standard configuration
E.2.4.1 General
E.2.4.2 Association request
57 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
E.3.2.2 Remote operation invoke event report configuration
59 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
60 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
62 E.5 Data reporting
E.5.1 Confirmed measurement data transmission
63 E.5.2 Response to confirmed measurement data transmission
E.6 Disassociation
E.6.1 Association release request
E.6.2 Association release response
64 Annex F (informative) Revision history
65 Blank Page

Related products

BS EN ISO/IEEE 11073-10415:2022
$198.66