IEEE 11073-10415-2010 pdf download

IEEE 11073-10415-2010 pdf download.Health informatics一Personal health device communication -Part 10415:Device specialization一Weighing scale.
4.2 Introduction to IEEE 11073-20601 modeling constructs
4.2.1 General
The ISO/IEEE 11073 series of standards. and in particular IEEE Std 11073-20601, is based on an objectoriented systems management paradigm. The overall system model is divided into three principal components: the domain information model (DiM), the service model, and the communication model. See IEEE Std 11073-20601 for a detailed description of the modeling constructs.
4.2.2 Domain information model
The DIM is a hierarchical model that describes an agent as a set of objects. These objects and their attributes represent the elements that control behavior and report on the status of the agent and data that an agent can communicate to a manager. Communication between the agent and the manager is defined by the application protocol in IEEE Std 11073-20601.
4.2.3 Service model
The service model defines the conceptual mechanisms for the data exchange services. Such services are mapped to messages that are exchanged between the agent and the manager. Protocol messages within the ISO/IEEE 11073 series of standards arc defined in ASN.1. The messages defined in IEEE Std 11073-20601 can coexist with messages defined in other standard application profiles defined in the ISO/IEEE 11073 series of standards.
4.2.4 Communication model
In general, the communication model supports the topology of one or more agents communicating over logical point-to-point connections to a single manager. For each logical point-to-point connection, the dynamic system behavior is defined by a connection state machine as specified in IEEE Std 11073-2060 1.
4.2.5 Implementing the models
An agent implementing this standard shall implement all mandatory elements of the information, service, and communication models as well as all conditional elements where the condition is met. The agent should implement the recommended elements, and it may implement any combination of the optional elements. A manager implementing this standard shall utilize at least one of the mandatory, conditional, recommended, or optional elements. In this context, butilize means to use the element as part of the primary function of the manager device. For example, a manager whose primary function is to display data would need to display a piece of data in the element in order to utilize it.
5. Weighing scale device concepts and modalities
5.1 General
This clause presents the general concepts of weighing scale devices. In the context of personal health devices in this family of standards, a weighing scale is a device that measures the body weight of a person and, optionally, determines other physiological quantities (e.g., the body mass index or the height of a person). Weighing scale devices considered in this standard are typically placed on the floor with a person stepping on the device to perform a weight measurement, with the result being converted into mass internally of the device.
6.3 Object instance diagram
The object instance diagram of the weighing scale domain information model, defined for the purposes of this standard, is shown in Figure 1.
The objects of the DIM, as shown in Figure 1, are described in 6.4 to 6.12. This includes the medical device system (MDS) object (sec 6.5), the numeric objects (sec 6.6), the real-time sample array (RT-SA) objects (sec 6.7), the enumeration objects (sec 6.8), the PM-store objects (see 6.9). and the scanner objects (see 6.10). See 6.11 for rules for extending the weighing scale information model beyond elements as described in this standard. Each clause that describes an object of the weighing scale contains the following information:
— The nomenclature code used to identify the class of the object. One example of where this code is used is the configuration event, where the object class is reported for each object. This allows the manager to determine whether the class of the object being specified is a numeric, real-time sample array, enumeration, scanner, or PM-store class.
— The attributes of the object. Each object has attributes that represent and convey information on the physical device and its data sources. Each object has a Handle attribute that identifies the object instance within an agent. Attribute values are accessed and modified using methods such as GET and SET. Attributes types are defined using ASN.1. The ASN.1 definitions for new attribute types specific to this standard are in Annex B, and the ASN. 1 definitions for existing attribute types referenced in this standard are in IEEE Std 11073-20601.
— The methods available on the object.
— The potential events generated by the object. Data are sent to the manager using events.
— The available services such as getting or setting attributes.