EN ISO 11073-10471:2011

SLOVENSKI STANDARD
01-maj-2011
Zdravstvena informatika - Komunikacija osebnih medicinskih naprav - 10471. del:
Specialne naprave - Sistem hišnih naprav za samostojno življenje starejših in
bolnih (ISO/IEEE 11073-10471:2010)
Health Informatics - Personal health device communication - Part 10471: Device
specialization - Independant living activity hub (ISO/IEEE 11073-10471:2010)
Medizinische Informatik - Kommunikation von Geräten für die persönliche Gesundheit -
Teil 10471: Gerätespezifikation - Schnittstellenkonzentrator und umsetzer für
assistierende Systeme (ISO/IEEE 11073-10471:2010)
Informatique de santé - Communication entre dispositifs de santé personnels - Partie
10471: Spécialisation des dispositifs - Concentrateur d'activité pour une vie autonome
(ISO/IEEE 11073-10471:2010)
Ta slovenski standard je istoveten z: EN ISO 11073-10471:2011
ICS:
11.180.99 'UXJLVWDQGDUGLY]YH]LV Other standards related to
SULSRPRþNL]DLQYDOLGH aids for disabled and
handicapped people
35.240.80 Uporabniške rešitve IT v IT applications in health care
zdravstveni tehniki technology
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN ISO 11073-10471
NORME EUROPÉENNE
EUROPÄISCHE NORM
March 2011
ICS 35.240.80
English Version
Health Informatics - Personal health device communication -
Part 10471: Device specialization - Independant living activity
hub (ISO/IEEE 11073-10471:2010)
Informatique de santé - Communication entre dispositifs de Medizinische Informatik - Kommunikation von Geräten für
santé personnels - Partie 10471: Spécialisation des die persönliche Gesundheit - Teil 10471:
dispositifs - Concentrateur d'activité pour une vie autonome Gerätespezifikation - Schnittstellenkonzentrator und -
(ISO/IEEE 11073-10471:2010) umsetzer für assistierende Systeme (ISO/IEEE 11073-
10471:2010)
This European Standard was approved by CEN on 23 April 2010.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European
Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national
standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN member.

This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management Centre has the same
status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland,
Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.

EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2011 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 11073-10471:2011: E
worldwide for CEN national Members.

Contents Page
Foreword .3

Foreword
The text of ISO/IEEE 11073-10471:2010 has been prepared by Technical Committee ISO/TC 215 “Health
informatics” of the International Organization for Standardization (ISO) and has been taken over as EN ISO
11073-10471:2011 by Technical Committee CEN/TC 251 “Health informatics” the secretariat of which is held
by NEN.
This European Standard shall be given the status of a national standard, either by publication of an identical
text or by endorsement, at the latest by September 2011, and conflicting national standards shall be
withdrawn at the latest by September 2011.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights.
According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following
countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech
Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain,
Sweden, Switzerland and the United Kingdom.
Endorsement notice
The text of ISO/IEEE 11073-10471:2010 has been approved by CEN as a EN ISO 11073-10471:2011 without
any modification.
INTERNATIONAL ISO/IEEE
STANDARD 11073-10471
First edition
2010-05-01
Health informatics — Personal health
device communication —
Part 10471:
Device specialization — Independant
living activity hub
Informatique de santé — Communication entre dispositifs de santé
personnels —
Partie 10471: Spécialisation des dispositifs — Concentrateur d'activité
vivante indépendante
Reference number
ISO/IEEE 11073-10471:2010(E)
©
ISO 2010
©
IEEE 2010
ISO/IEEE 11073-10471:2010(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. Neither the ISO Central
Secretariat nor IEEE accepts any liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies
and IEEE members. In the unlikely event that a problem relating to it is found, please inform the ISO Central Secretariat or IEEE at the
address given below.
©  ISO 2010
©  IEEE 2010
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO or IEEE at the respective
address below.
ISO copyright office Institute of Electrical and Electronics Engineers, Inc.
Case postale 56 • CH-1211 Geneva 20 3 Park Avenue, New York • NY 10016-5997, USA
Tel. + 41 22 749 01 11 E-mail stds.ipr@ieee.org
Fax + 41 22 749 09 47 Web www.ieee.org
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © IEEE 2010 – All rights reserved

ISO/IEEE 11073-10471:2010(E)
Contents Page
Foreword. v
Introduction.vii
1. Overview. 1
1.1 Scope. 1
1.2 Purpose. 2
1.3 Context. 2
2. Normative references . 2
3. Definitions, acronyms, and abbreviations. 2
3.1 Definitions. 3
3.2 Acronyms and abbreviations. 3
4. Introduction to ISO/IEEE 11073 personal health devices. 3
4.1 General. 3
4.2 Introduction to IEEE Std 11073-20601 modeling constructs. 4
5. Independent living activity hub device concepts and modalities . 5
5.1 General. 5
5.2 Concepts. 5
5.3 Collected data. 5
6. Independent living activity hub domain information model . 7
6.1 Overview. 7
6.2 Class extensions . 7
6.3 Object instance diagram. 7
6.4 Types of configuration . 9
6.5 MDS object . 10
6.6 Numeric objects . 13
6.7 Real-time sample array objects . 13
6.8 Enumeration objects. 13
6.9 PM-store objects . 26
6.10 Scanner objects . 26
6.11 Class extension objects . 26
6.12 Independent living activity hub information model extensibility rules. 26
7. Independent living activity hub service model . 27
7.1 General. 27
7.2 Object access services. 27
7.3 Object access event report services. 29
© IEEE 2010 – All rights reserved iii

ISO/IEEE 11073-10471:2010(E)
8. Independent living activity hub communication model. 29
8.1 Overview. 29
8.2 Communication characteristics . 29
8.3 Association procedure. 30
8.4 Configuring procedure . 31
8.5 Operating procedure. 32
8.6 Time synchronization. 32
9. Test associations . 32
9.1 Behavior with standard configuration . 33
9.2 Behavior with extended configurations. 33
10. Conformance. 33
10.1 Applicability. 33
10.2 Conformance specification. 33
10.3 Levels of conformance. 34
10.4 ICSs. 34
Annex A (informative) Bibliography. 39
Annex B (normative) Any additional ASN.1 definitions. 40
Annex C (normative) Allocation of identifiers . 43
Annex D (informative) Message sequence examples . 45
Annex E (informative) Protocol data unit examples. 47

iv © IEEE 2010 – All rights reserved

ISO/IEEE 11073-10471:2010(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national
standards bodies (ISO member bodies). The work of preparing International Standards is
normally carried out through ISO technical committees. Each member body interested in a
subject for which a technical committee has been established has the right to be represented on
that committee. International organizations, governmental and non-governmental, in liaison with
ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical
Commission (IEC) on all matters of electrotechnical standardization.
IEEE Standards documents are developed within the IEEE Societies and the Standards
Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The
IEEE develops its standards through a consensus development process, approved by the
American National Standards Institute, which brings together volunteers representing varied
viewpoints and interests to achieve the final product. Volunteers are not necessarily members of
the Institute and serve without compensation. While the IEEE administers the process and
establishes rules to promote fairness in the consensus development process, the IEEE does not
independently evaluate, test, or verify the accuracy of any of the information contained in its
standards.
The main task of technical committees is to prepare International Standards. Draft International
Standards adopted by the technical committees are circulated to the member bodies for voting.
Publication as an International Standard requires approval by at least 75 % of the member bodies
casting a vote.
Attention is called to the possibility that implementation of this standard may require the use of
subject matter covered by patent rights. By publication of this standard, no position is taken with
respect to the existence or validity of any patent rights in connection therewith. ISO/IEEE is not
responsible for identifying essential patents or patent claims for which a license may be required,
for conducting inquiries into the legal validity or scope of patents or patent claims or determining
whether any licensing terms or conditions provided in connection with submission of a Letter of
Assurance or a Patent Statement and Licensing Declaration Form, if any, or in any licensing
agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that
determination of the validity of any patent rights, and the risk of infringement of such rights, is
entirely their own responsibility. Further information may be obtained from ISO or the IEEE
Standards Association.
ISO/IEEE 11073-10471 was prepared by the 11073 Committee of the Engineering in Medicine
and Biology Society of the IEEE (as IEEE Std 11073-10471-2008). It was adopted by Technical
Committee ISO/TC 215, Health informatics, in parallel with its approval by the ISO member
bodies, under the “fast-track procedure” defined in the Partner Standards Development
Organization cooperation agreement between ISO and IEEE. Both parties are responsible for the
maintenance of this document.
ISO/IEEE 11073 consists of the following parts, under the general title Health informatics —
Personal health device communication (text in parentheses gives a variant of subtitle):
— Part 10101: (Point-of-care medical device communication) Nomenclature
— Part 10201: Domain information model
— Part 10404: Device specialization — Pulse oximeter
© IEEE 2010 – All rights reserved v

ISO/IEEE 11073-10471:2010(E)
— Part 10407: Device specialization — Blood pressure monitor
— Part 10408: (Point-of-care medical device communication) Device specialization —
Thermometer
— Part 10415: (Point-of-care medical device communication) Device specialization — Weighing
scale
— Part 10417: Device specialization — Glucose meter
— Part 10471: (Point-of-care medical device communication) Device specialization —
Independant living activity hub
— Part 20101: (Point-of-care medical device communication) Application profiles — Base
standard
— Part 20601: (Point-of-care medical device communication) Application profile — Optimized
exchange protocol
— Part 30200: (Point-of-care medical device communication) Transport profile — Cable
connected
— Part 30300: (Point-of-care medical device communication) Transport profile — Infrared
wireless
vi © IEEE 2010 – All rights reserved

ISO/IEEE 11073-10471:2010(E)
Introduction
ISO/IEEE 11073 standards enable communication between medical devices and external computer systems. This
a
document uses the optimized framework created in IEEE Std 11073-20601 and describes a specific, interoperable
communication approach for independent living activity hubs. These standards align with, and draw upon, the existing
clinically focused standards to provide support for communication of data from clinical or personal health devices.

a
For information on references, see Clause 2.
© IEEE 2010 – All rights reserved vii

INTERNATIONAL STANDARD ISO/IEEE 11073-10471:2010(E)

Health informatics — Personal health device
communication —
Part 10471:
Device specialization — Independant living activity hub
IMPORTANT NOTICE: This standard is not intended to assure safety, security, health, or
environmental protection in all circumstances. Implementers of the standard are responsible for
determining appropriate safety, security, environmental, and health practices or regulatory requirements.

This IEEE document is made available for use subject to important notices and legal disclaimers. These
notices and disclaimers appear in all publications containing this document and may be found under the
heading “Important Notice” or “Important Notices and Disclaimers Concerning IEEE Documents.”
They can also be obtained on request from IEEE or viewed at http://standards.ieee.org/IPR/disclaimers.html.
1. Overview
1.1 Scope
Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard
establishes a normative definition of the communication between independent living activity hubs 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 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 independent
living activity hubs. In this context, independent living activity hubs are defined as devices that
communicate with simple situation monitors (binary sensors), normalize information received from the
simple environmental monitors, and provide this normalized information to one or more managers. This
information can be examined (for example) to determine when a person’s activities/behaviors have
deviated significantly from what is normal for them such that relevant parties can be notified. Independent
living activity hubs will normalize information from the following simple situation monitors (binary
sensors) for the initial release of the proposed standard: fall sensor, motion sensor, door sensor, bed/chair
occupancy sensor, light switch sensor, smoke sensor, (ambient) temperature threshold sensor, personal
emergency response system (PERS), and enuresis sensor (bed-wetting).

© IEEE 2010 – All rights reserved

ISO/IEEE 11073-10471:2010(E)
1.2 Purpose
This standard addresses a need for an openly defined, independent standard for controlling information
exchange to and from personal health devices and managers (e.g., cell phones, personal computers,
personal health appliances, and set top boxes). Interoperability is the key to growing the potential market
for these devices and to enabling people to be better informed participants in the management of their
health.
1.3 Context
TM
See IEEE Std 11073-20601 for an overview of the environment within which this standard is written.

This document, IEEE Std 11073-10471, defines the device specialization for the independent living activity
hub, being a specific agent type, and it provides a description of the device concepts, its capabilities, and its
implementation according to this standard.

This standard is based on IEEE Std 11073-20601, which in turn draws information from both
ISO/IEEE 11073-10201:2004 [B3] and ISO/IEEE 11073-20101:2004 [B4]. The medical device encoding
rules (MDERs) used within this standard are fully described in IEEE Std 11073-20601.

This standard reproduces relevant portions of the nomenclature found in ISO/IEEE 11073-10101:2004 [B2]
and adds new nomenclature codes for the purposes of this standard. Between this standard and
IEEE Std 11073-20601 all required nomenclature codes for implementation are documented.

NOTE— In this standard, IEEE Std 11073-104zz is used to refer to the collection of device specialization standards
that utilize IEEE Std 11073-20601, where zz can be any number from 01 to 99, inclusive.

2. Normative references
The following referenced documents are indispensable for the application of this document (i.e., they must
be understood and used, so that each referenced document is cited in text and its relationship to this
document is explained). For dated references, only the edition cited applies. For undated references, the
latest edition of the referenced document (including any amendments or corrigenda) applies.

TM
IEEE Std 11073-20601 -2008, Health informatics—Personal health device communication—Part 20601:
3,4
Application profile—Optimized Exchange Protocol.
See Annex A for all informative material referenced by this standard.
3. Definitions, acronyms, and abbreviations
For the purposes of this standard, the following terms and definitions apply. The Authoritative Dictionary
of IEEE Standards [B1] should be referenced for terms not defined in this clause.

The numbers in brackets correspond to those of the bibliography in Annex A.
Notes in text, tables, and figures are given for information only and do not contain requirements needed to implement the standard.
The IEEE standards or products referred to in this clause are trademarks of the Institute of Electrical and Electronics Engineers, Inc.
IEEE publications are available from the Institute of Electrical and Electronics Engineers, 445 Hoes Lane, Piscataway, NJ 08854,
USA (http://standards.ieee.org/).
© IEEE 2010 – All rights reserved

ISO/IEEE 11073-10471:2010(E)
3.1 Definitions
3.1 agent: A node that collects and transmits personal health data to an associated manager.
3.2 class: In object-oriented modeling, it describes the attributes, methods, and events that objects
instantiated from the class utilize.

3.3 compute engine: See: manager.
3.4 device: A term used to refer to a physical apparatus implementing either an agent or a manager role.
3.5 handle: An unsigned 16-bit number that is locally unique and identifies one of the object instances
within an agent.
3.6 manager: A node receiving data from one or more agent systems. Some examples of managers include
a cellular phone, health appliance, set top box, or a computer system.
3.7 obj-handle: See: handle.
3.8 object: In object-oriented modeling, a particular instantiation of a class. The instantiation realizes
attributes, methods, and events from the class.
3.9 personal health device: A device used in personal health applications.
3.10 personal telehealth device: See: personal health device.
3.11 sensor: An apparatus that measures physical properties. These comprise the primary inputs to an
independent living activity hub agent.
3.2 Acronyms and abbreviations
APDU application protocol data unit
ASN.1 Abstract Syntax Notation One
DIM domain information model
EUI-64 extended unique identifier (64 bits)
ICS implementation conformance statement
MDC medical device communication
MDER medical device encoding rules
MDS medical device system
MOC managed object class
PDU protocol data unit
PERS personal emergency response system
PHD personal health device
RT-SA real-time sample array
VMO virtual medical object
VMS virtual medical system
4. Introduction to ISO/IEEE 11073 personal health devices
4.1 General
This standard and the remainder of the series of ISO/IEEE 11073 personal health device (PHD) standards
fit in the larger context of the ISO/IEEE 11073 series of standards. The full suite of standards enables
agents to interconnect and interoperate with managers and with computerized health-care information
systems. See IEEE Std 11073-20601 for a description of the guiding principles for this series of
ISO/IEEE 11073 personal health device standards.
© IEEE 2010 – All rights reserved

ISO/IEEE 11073-10471:2010(E)
IEEE Std 11073-20601 supports the modeling and implementation of an extensive set of personal health
devices. This standard defines aspects of the independent living activity hub device. It describes all aspects
necessary to implement the application layer services and data exchange protocol between an
ISO/IEEE 11073 PHD independent living activity hub agent and a manager. This standard defines a subset
of the objects and functionality contained in IEEE Std 11073-20601 and extends and adds definitions where
appropriate. All new definitions are given in Annex B in abstract syntax notation one (ASN.1) [B5].
Nomenclature codes referenced in this standard, which are not defined in IEEE Std 11073-20601, are
normatively defined in Annex C.
4.2 Introduction to IEEE Std 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 object-
oriented 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 are 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-20601.
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, “utilize” 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.
© IEEE 2010 – All rights reserved

ISO/IEEE 11073-10471:2010(E)
5. Independent living activity hub device concepts and modalities
5.1 General
This clause presents the general concepts of independent living activity hub devices. In the context of
personal health devices in this family of standards, an independent living activity hub is a device that
aggregates activity data sensor events from multiple sensor data sources, all of which are used in the
support of the independent living of one or more occupants. The occupants’ environment may vary greatly
and encompass a varying mixture of sensors; therefore, the activity data sensor events reported by any
particular agent have a corresponding variance.
5.2 Concepts
While there are many data generating sensors, they have a number of properties in common that influence
the design of this standard. Note that these are only generalities employed in the design and there may be
instances where an activity data generating sensor exceeds these properties.

⎯ Price: usually they are very inexpensive sensors.
⎯ Power: typically they are very low power sensors.
⎯ Communication: typically they use a very inexpensive communication technique and are quite
often wireless.
⎯ Frequency: typically they communicate very infrequently or only when an event occurs.
⎯ Quantity: there may be a wide range of sensors and many instances of any one sensor type.

It is the responsibility of the independent living activity hub agent to manage all these sensors.
Management of the sensors is likely to be within the proprietary purview of the agent both because there is
no acceptable existing industry standard and the desire to integrate existing legacy solutions with the
IEEE Std 11073-20601 framework. Therefore, this responsibility is outside the scope of this standard. Only
the communication between the independent living activity hub agent and the manager are covered by this
standard.
Additionally, due to the many different types of sensors that may be employed in any particular installation,
there is a range of functionality that the corresponding independent living activity hub agent presents to the
manager. On the one hand, a fully functional independent living activity hub agent could represent a
significant number of sensors and have a complex conversation with the associated manager. On the other
hand, a subset of this protocol could be employed by just one sensor such that it would appear to a manager
as an independent living activity hub agent with a single sensor.
5.3 Collected data
5.3.1 General
This clause provides an overview of the kinds of sensors and activity data that could be collected. This is
not to imply that all independent living activity hub agents would necessarily report values for all of these
sensors. Furthermore, this standard is not concerned with the form of the data nor the communication
between any actual sensor and the independent living activity hub; rather only the activity data sensor
events derived as a result of that data are considered part of this standard. See Clause 6 for the normative
definition of this derived data.
© IEEE 2010 – All rights reserved

ISO/IEEE 11073-10471:2010(E)
5.3.2 Fall sensor
This sensor is used to notify the monitoring system that a fall sensor event has taken place. This could take
the form of a sensor of the type that detects a person’s fall and automatically generates the event.
5.3.3 PERS sensor
This sensor is used to notify the monitoring system that a personal emergency sensor event has taken place.
This would typically take the form of a button that the person presses to indicate some sort of perceived
emergency (“panic button”).
5.3.4 Environmental sensors
These sensors generate a sensor event whenever they sense an environmental aspect that is beyond a preset
threshold. Examples include smoke sensors, carbon monoxide sensors, water sensors, and natural gas/LP
gas sensors.
5.3.5 Motion sensor
This sensor generates a sensor event whenever it has sensed movement within its range above a preset level.
This type of sensor is typically employed in two manners: general motion and intruder detection.

In the case of general motion, the detection of the motion causes an immediate generation of a sensor event
and subsequent action. This may be used for tracking the activity level of the occupant to discern whether
behavior patterns have altered.

In the case of intruder detection, the motion sensor event could be used to trigger intruder detection actions.

Optionally, in the case of the primary entrances to the building, for example, the subsequent action to the
sensor event may be delayed for some period before taken. This is to allow for an authorized person to
enter the premises and to disable the sensor event before the action is taken (e.g., in the case where a
triggered sensor event will generate an intruder alert). Should the proper disabling not take place within the
expected delay time period, the normal subsequent action would take place. There may also be a sensor
event for the case when the motion sensor detects someone attempting to tamper with its function.
5.3.6 Property exit sensor
This sensor generates a sensor event whenever it has sensed the exit of an occupant from the premises. This
is commonly employed when there is an occupant with some cognitive issues who would encounter
difficulties in an unfamiliar environment. There may also be a sensor event for the case where the premises’
exit is left open.
5.3.7 Enuresis sensor
This sensor generates a sensor event when it detects occurrences of involuntary urination or bed-wetting.
This sensor could be utilized in a range of settings such as a bed, chair, or any similar structure.
5.3.8 Contact closure sensor
This sensor issues a sensor event whenever a contact is opened or closed. This sensor reports the state of
the contact after a transition, either from closed to open or from open to closed. Only a single sensor event
is sent for each transition. Examples of where this sensor would be deployed are passageway doors,
cupboard doors, drawers, windows, and pressure mats.
© IEEE 2010 – All rights reserved

ISO/IEEE 11073-10471:2010(E)
5.3.9 Usage sensor
This sensor issues a sensor event to denote the start of use (into a bed/chair, for example) or the end of use
(out of a bed/chair, for example). It also issues a sensor event for an anticipated usage not occurring by an
expected preset time (expected use start violation) as well as a sensor event for the usage continuing
beyond an expected preset time (expected use stop violation). Additionally, there would be a sensor event
generated if during an expected usage time, the usage is discontinued for longer than a preset period of time
(intermittent absence violation). An example would be that during a normal sleep period, a person got out
of the bed and did not return in an expected period of time.
5.3.10 Switch use sensor
This sensor issues a sensor event for a switch changing states either to the used state (ON) or to the unused
state (OFF). Examples of this are light switches, fan switches, and other similar switches that control
electrical apparatus.
5.3.11 Simple medication dispenser
The dispenser is a container that contains doses of one or more medications. The medications are to be
taken in predetermined doses at predetermined times. A sensor event is generated for a presented dosage
being taken from the dispenser (dosage taken) and/or for a dose not being taken after a predetermined
amount of time (dosage missed).

NOTE—The sensor description presented here is of a conceptual model to aid in understanding. Be aware that the
same derived sensor events could be generated through many other means (such as a user interaction with some screen
interface). This standard is only concerned with the generated sensor events.
5.3.12 Temperature sensor
This sensor monitors the temperature in an environment. It issues sensor events based on the sensor value
being outside of a preset temperature limit. The sensor events could be that the ambient temperature has
risen above a certain level (high threshold) or dropped below a certain level (low threshold), or that the
rate-of-change is faster than a predetermined expected rate (rate-of-change). This can be used for detecting
conditions such as the temperature of a dwelling being dangerously high/low or that stove elements have
been left on after cooking has been completed.
6. Independent living activity hub domain information model
6.1 Overview
This clause describes the domain information model of the independent living activity hub.
6.2 Class extensions
In this standard, no class extensions are defined with respect to IEEE Std 11073-20601.
6.3 Object instance diagram
The object instance diagram of the independent living activity hub domain information model, defined for
the purposes of this standard, is shown in Figure 1.

The generic DIM of the independent living activity hub that is presented in Figure 1 defines all possible
data objects. However, it would be expected that most independent living activity hubs would implement
© IEEE 2010 – All rights reserved

ISO/IEEE 11073-10471:2010(E)
only a restricted subset of the data objects. An independent living activity hub shall implement at least one
sensor instance.
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 (see 6.5), the numeric objects (see 6.6), the real-time sample array (RT-SA) objects
(see 6.7), the enumeration objects (see 6.8), the PM-store objects (see 6.9), and the scanner objects (see
6.10). See 6.12 for rules for extending the independent living activity hub information model beyond
elements as described in this standard. Each clause that describes an object of the independent living
activity hub 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 activity data generating sensor 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
communication services such as GET and SET. Attributes types are defined using ASN.1. The
ASN.1 definitions
...