MADCAD.com - The Cloud-Based Reference Library

- Free Trial - Webinar - Feedback

Cart (0)

No items in cart.

Total

There is a technical issue about last added item. You can click "Report to us" button to let us know and we resolve the issue and return back to you or you can continue without last item via click to continue button.

Home

Content

eLibrary

Not a subscriber? Register for a trial account.

Username:
Password:

Incorrect username/password.

Already a subscriber?

MADCAD.com Free Trial

Sign up for a 3 day free trial to explore the MADCAD.com interface, PLUS access the
2009 International Building Code to see how it all works.

If you like to setup a quick demo, let us know at support@madcad.com
or +1 800.798.9296 and we will be happy to schedule a webinar for you.

Email *
Password *
Confirm *
First Name *
Last Name *
Title
Company Name *
Company Size *
Industry *
Address *
Address 2
City *
State *	Zip *
Country *
Phone *
How did you hear about MADCAD.com? *

Print page(s), starting from page (current page)

Continue to Print

Reset password

Enter your personal account email address to request
a password reset:

Reset password

Enter your account email address to request
a password reset:

Save As:

Are you sure you want to delete this group?

Security check

Please check the following box:

Please login to your personal account to use this feature.

Email:

Password:

Forgot your password?

Remember me for one month

Need a login? Register now.

Please login to your authorized staff account to use this feature.

Username:

Password:

Are you sure you want to empty the cart?

There were no books found for the applied search filters.

CLICK TO START OVER

Report To Us

Please fill the form below so that we can contact you.

Full name*
Email*
Phone

Contact us for a custom quote

Please fill the form below and a member of our staff will contact you shortly. The contents of your cart will automatically be sent to us so we can provide an accurate custom quote.

Company*
Full name*
Email*
Phone

⨯To continue with accurate pricing,
please select your company type below:

Large goverment organizations

Large multi-national corporation (more than $5B annual revenue)

None of the above

Your company has a special pricing case for IEEE.
For pricing, please contact us by filling out the form.

Full name*
Email*
Phone
Your selection

⨯We need your input!

Are you a code official in a jurisdiction with less than 300,000 population?

Yes No

This item is only available for the code officials of jurisdictions less then 300K population.

If you do not meet the criteria item will be removed and you will be able to continue shopping other items.

⨯ We need your input!

Your company has a special pricing case for ASME.
Please make sure the information you provide below is accurate.

Company Industry
Number Of Employees
Revenue

Pricing for the ASME publications in the store is for a 1-4 employee company in Construction Industry with revenue under $500,000.
If correct company info does not match what is publicly available info we will suspend the access and contact you for correction.
Please call 1-800-798-9296 if you have any questions.
If your company has more than 5,000 employee or more than 500 mil revenue please email us at info@madcad.com to receive a special quote, use "ASME Quote" on the subject line.

Cart Warning

eLibrary > ISO/IEEE International Standard: Health informatics—Device interoperability—Part 10421: Personal health device communication—Device specialization—Peak expiratory flow monitor (peak flow) (Published) >

ISO/IEEE International Standard: Health informatics—Device interoperability—Part 10421: Personal health device communication—Device specialization—Peak expiratory flow monitor (peak flow) (Published), 2024

This document is reproduced and distributed under license from The Institute of Electrical and Electronics Engineers, Incorporated (IEEE), 445 Hoes Lane, Piscataway, New Jersey 08854 and is protected by United States and international copyright laws and treaties. No part of this publication may be reproduced, in any form and in any medium, without the prior written consent of the IEEE. If you have any questions, please contact MADCAD.com at support@madcad.com or call at 1.800.798.9296.

ISO/IEEE International Standard: Health informatics—Device interoperability—Part 10421: Personal health device communication—Device specialization—Peak expiratory flow monitor (peak flow) (Published), 2024

Notice and Disclaimer of Liability Concerning the Use of IEEE Standards Documents
Translations
Official statements
Comments on standards
Laws and regulations
Data privacy
Copyrights
Photocopies
Updating of IEEE Standards documents
Errata
Patents
IMPORTANT NOTICE
1. Overview [Go to Page]
1.1 Scope
1.2 Purpose
1.3 Word usage
2. Normative references
3. Definitions, acronyms, and abbreviations [Go to Page]
3.1 Definitions
3.2 Acronyms and abbreviations
4. Introduction to ISO/IEEE 11073 personal health devices [Go to Page]
4.1 General
4.2 Introduction to IEEE 11073-20601 modeling constructs [Go to Page]
4.2.1 General
4.2.2 Domain information model
4.2.3 Service model
4.2.4 Communication model
4.2.5 Implementing the models
4.3 Compliance with other standards
5. Peak expiratory flow monitor device concepts and modalities [Go to Page]
5.1 General
5.2 PEF
6. Peak expiratory flow monitor domain information model [Go to Page]
6.1 Overview
6.2 Class extensions
6.3 Object instance diagram
6.4 Types of configuration [Go to Page]
6.4.1 General
6.4.2 Standard configuration
6.4.3 Extended configuration
6.5 Medical device system object [Go to Page]
6.5.1 MDS object attributes
6.5.2 MDS object methods
6.5.3 MDS object events
6.5.4 Other MDS services [Go to Page]
6.5.4.1 GET service
6.5.4.2 SET service
6.6 Numeric objects [Go to Page]
6.6.1 General
6.6.2 PEF
6.6.3 Personal best
6.6.4 FEV1
6.6.5 FEV6 (optional)
6.7 Real-time sample array objects
6.8 Enumeration objects [Go to Page]
6.8.1 Reading status
6.9 PM-store objects
6.10 Scanner objects
6.11 Class extension objects
6.12 Peak expiratory flow monitor information model extensibility rules
7. Peak expiratory flow monitor service model [Go to Page]
7.1 General
7.2 Object access services
7.3 Object access event report services
8. Peak expiratory flow monitor communication model [Go to Page]
8.1 Overview
8.2 Communications characteristics
8.3 Association procedure [Go to Page]
8.3.1 General
8.3.2 Agent procedure—association request
8.3.3 Manager procedure—association response
8.4 Configuring procedure [Go to Page]
8.4.1 General
8.4.2 Peak expiratory flow monitor—standard configuration [Go to Page]
8.4.2.1 Agent procedure
8.4.2.2 Manager procedure
8.5 Operating procedure [Go to Page]
8.5.1 General
8.5.2 GET Peak expiratory flow monitor MDS attributes
8.5.3 Measurement data transmission
8.6 Time synchronization
9. Test associations [Go to Page]
9.1 Behavior with standard configuration
9.2 Behavior with extended configurations
10. Conformance [Go to Page]
10.1 Applicability
10.2 Conformance specification
10.3 Levels of conformance [Go to Page]
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)
10.4 Implementation conformance statements (ICSs) [Go to Page]
10.4.1 General format
10.4.2 General ICS
10.4.3 DIM MOC implementation conformance statement
10.4.4 MOC attribute ICS
10.4.5 MOC notification ICS
10.4.6 MOC nomenclature ICS
Annex A (informative) Bibliography
Annex B (normative) Any additional ASN.1 definitions
Annex C (normative) Allocation of identifiers
Annex D (informative) Message sequence examples
a) When the user connects the medication monitor, the manager does not 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 agent’s configuration, 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 “Remote Operation Invoke | Get” command. Note that the manager may request the MDS object attributes as soon as the agent enters the Ass...
d) As a next step, the user of the agent device takes a single measurement. The measurement data are transmitted to the manager using a confirmed event report. After having successfully received the measurement data, the manager sends a confirmation t...
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 to item d) and item e). The user takes a single confirmed measurement followed by releasing the association.
Annex E (informative) Protocol data unit examples [Go to Page]
E.1 General
E.2 Association information exchange [Go to Page]
E.2.1 General
E.2.2 Extended configuration [Go to Page]
E.2.2.1 General
E.2.2.2 Association request
E.2.2.3 Association response
E.2.3 Previously known extended configuration [Go to Page]
E.2.3.1 General
E.2.3.2 Association request
E.2.3.3 Association response
E.2.4 Standard configuration [Go to Page]
E.2.4.1 General
E.2.4.2 Association request
E.2.4.3 Association response
E.3 Configuration information exchange [Go to Page]
E.3.1 General
E.3.2 Extended configuration [Go to Page]
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
E.3.3 Known configuration [Go to Page]
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 [Go to Page]
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 [Go to Page]
E.4.1 General
E.4.2 Get all MDS attributes request
E.4.3 Get response with all MDS attributes
E.5 Data reporting [Go to Page]
E.5.1 Confirmed measurement data transmission
E.5.2 Response to confirmed measurement data transmission
E.6 Disassociation [Go to Page]
E.6.1 Association release request
E.6.2 Association release response
Annex F (informative) Revision History
Blank Page
C088163e_v2_P17SB2.pdf [Go to Page]
Notice and Disclaimer of Liability Concerning the Use of IEEE Standards Documents
Translations
Official statements
Comments on standards
Laws and regulations
Data privacy
Copyrights
Photocopies
Updating of IEEE Standards documents
Errata
Patents
IMPORTANT NOTICE
1. Overview [Go to Page]
1.1 Scope
1.2 Purpose
1.3 Word usage
2. Normative references
3. Definitions, acronyms, and abbreviations [Go to Page]
3.1 Definitions
3.2 Acronyms and abbreviations
4. Introduction to ISO/IEEE 11073 personal health devices [Go to Page]
4.1 General
4.2 Introduction to IEEE 11073-20601 modeling constructs [Go to Page]
4.2.1 General
4.2.2 Domain information model
4.2.3 Service model
4.2.4 Communication model
4.2.5 Implementing the models
4.3 Compliance with other standards
5. Peak expiratory flow monitor device concepts and modalities [Go to Page]
5.1 General
5.2 PEF
6. Peak expiratory flow monitor domain information model [Go to Page]
6.1 Overview
6.2 Class extensions
6.3 Object instance diagram
6.4 Types of configuration [Go to Page]
6.4.1 General
6.4.2 Standard configuration
6.4.3 Extended configuration
6.5 Medical device system object [Go to Page]
6.5.1 MDS object attributes
6.5.2 MDS object methods
6.5.3 MDS object events
6.5.4 Other MDS services [Go to Page]
6.5.4.1 GET service
6.5.4.2 SET service
6.6 Numeric objects [Go to Page]
6.6.1 General
6.6.2 PEF
6.6.3 Personal best
6.6.4 FEV1
6.6.5 FEV6 (optional)
6.7 Real-time sample array objects
6.8 Enumeration objects [Go to Page]
6.8.1 Reading status
6.9 PM-store objects
6.10 Scanner objects
6.11 Class extension objects
6.12 Peak expiratory flow monitor information model extensibility rules
7. Peak expiratory flow monitor service model [Go to Page]
7.1 General
7.2 Object access services
7.3 Object access event report services
8. Peak expiratory flow monitor communication model [Go to Page]
8.1 Overview
8.2 Communications characteristics
8.3 Association procedure [Go to Page]
8.3.1 General
8.3.2 Agent procedure—association request
8.3.3 Manager procedure—association response
8.4 Configuring procedure [Go to Page]
8.4.1 General
8.4.2 Peak expiratory flow monitor—standard configuration [Go to Page]
8.4.2.1 Agent procedure
8.4.2.2 Manager procedure
8.5 Operating procedure [Go to Page]
8.5.1 General
8.5.2 GET Peak expiratory flow monitor MDS attributes
8.5.3 Measurement data transmission
8.6 Time synchronization
9. Test associations [Go to Page]
9.1 Behavior with standard configuration
9.2 Behavior with extended configurations
10. Conformance [Go to Page]
10.1 Applicability
10.2 Conformance specification
10.3 Levels of conformance [Go to Page]
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)
10.4 Implementation conformance statements (ICSs) [Go to Page]
10.4.1 General format
10.4.2 General ICS
10.4.3 DIM MOC implementation conformance statement
10.4.4 MOC attribute ICS
10.4.5 MOC notification ICS
10.4.6 MOC nomenclature ICS
Annex A (informative) Bibliography
Annex B (normative) Any additional ASN.1 definitions
Annex C (normative) Allocation of identifiers
Annex D (informative) Message sequence examples
a) When the user connects the medication monitor, the manager does not 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 agent’s configuration, 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 “Remote Operation Invoke | Get” command. Note that the manager may request the MDS object attributes as soon as the agent enters the Ass...
d) As a next step, the user of the agent device takes a single measurement. The measurement data are transmitted to the manager using a confirmed event report. After having successfully received the measurement data, the manager sends a confirmation t...
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 to item d) and item e). The user takes a single confirmed measurement followed by releasing the association.
Annex E (informative) Protocol data unit examples [Go to Page]
E.1 General
E.2 Association information exchange [Go to Page]
E.2.1 General
E.2.2 Extended configuration [Go to Page]
E.2.2.1 General
E.2.2.2 Association request
E.2.2.3 Association response
E.2.3 Previously known extended configuration [Go to Page]
E.2.3.1 General
E.2.3.2 Association request
E.2.3.3 Association response
E.2.4 Standard configuration [Go to Page]
E.2.4.1 General
E.2.4.2 Association request
E.2.4.3 Association response
E.3 Configuration information exchange [Go to Page]
E.3.1 General
E.3.2 Extended configuration [Go to Page]
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
E.3.3 Known configuration [Go to Page]
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 [Go to Page]
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 [Go to Page]
E.4.1 General
E.4.2 Get all MDS attributes request
E.4.3 Get response with all MDS attributes
E.5 Data reporting [Go to Page]
E.5.1 Confirmed measurement data transmission
E.5.2 Response to confirmed measurement data transmission
E.6 Disassociation [Go to Page]
E.6.1 Association release request
E.6.2 Association release response
Annex F (informative) Revision History
Blank Page [Go to Page]

About Us / Careers / support@madcad.com / 1.800.798.9296

MADCAD.com Free Trial

Report To Us

Contact us for a custom quote

⨯To continue with accurate pricing, please select your company type below:

⨯We need your input!

⨯ We need your input!

Cart Warning

ISO/IEEE International Standard: Health informatics—Device interoperability—Part 10421: Personal health device communication—Device specialization—Peak expiratory flow monitor (peak flow) (Published), 2024

⨯To continue with accurate pricing,
please select your company type below: