ITU-T H 812 3-2015 Interoperability design guidelines for personal health systems WAN interface Capability exchange certified device class (Study Group 16)《个人健康系统互操作性设计指南 广域网接口：能力交.pdf

《ITU-T H 812 3-2015 Interoperability design guidelines for personal health systems WAN interface Capability exchange certified device class (Study Group 16)《个人健康系统互操作性设计指南 广域网接口：能力交.pdf》由会员分享，可在线阅读，更多相关《ITU-T H 812 3-2015 Interoperability design guidelines for personal health systems WAN interface Capability exchange certified device class (Study Group 16)《个人健康系统互操作性设计指南 广域网接口：能力交.pdf（28页珍藏版）》请在麦多课文档分享上搜索。

1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T H.812.3 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (11/2015) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS E-health multimedia services and applications Personal health systems Interoperability design guidelines for per

2、sonal health systems: WAN interface: Capability exchange certified device class Recommendation ITU-T H.812.3 ITU-T H-SERIES RECOMMENDATIONS AUDIOVISUAL AND MULTIMEDIA SYSTEMS CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS H.100H.199 INFRASTRUCTURE OF AUDIOVISUAL SERVICES General H.200H.219 Transmission

3、 multiplexing and synchronization H.220H.229 Systems aspects H.230H.239 Communication procedures H.240H.259 Coding of moving video H.260H.279 Related systems aspects H.280H.299 Systems and terminal equipment for audiovisual services H.300H.349 Directory services architecture for audiovisual and mult

4、imedia services H.350H.359 Quality of service architecture for audiovisual and multimedia services H.360H.369 Telepresence H.420H.429 Supplementary services for multimedia H.450H.499 MOBILITY AND COLLABORATION PROCEDURES Overview of Mobility and Collaboration, definitions, protocols and procedures H

5、.500H.509 Mobility for H-Series multimedia systems and services H.510H.519 Mobile multimedia collaboration applications and services H.520H.529 Security for mobile multimedia systems and services H.530H.539 Security for mobile multimedia collaboration applications and services H.540H.549 Mobility in

6、terworking procedures H.550H.559 Mobile multimedia collaboration inter-working procedures H.560H.569 BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES Broadband multimedia services over VDSL H.610H.619 Advanced multimedia services and applications H.620H.629 Ubiquitous sensor network applicati

7、ons and Internet of Things H.640H.649 IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV General aspects H.700H.719 IPTV terminal devices H.720H.729 IPTV middleware H.730H.739 IPTV application event handling H.740H.749 IPTV metadata H.750H.759 IPTV multimedia application frameworks H.760H.769 IPTV s

8、ervice discovery up to consumption H.770H.779 Digital Signage H.780H.789 E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS Personal health systems H.810H.819 Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) H.820H.859 Multimedia e-health data exchange services

9、H.860H.869 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T H.812.3 (11/2015) i Recommendation ITU-T H.812.3 Interoperability design guidelines for personal health systems: WAN interface: Capability exchange certified device class Summary The Continua Design Guideli

10、nes (CDG) define a framework of underlying standards and criteria that are required to ensure the interoperability of devices and data used for personal connected health. They also contain design guidelines (DGs) that further clarify the underlying standards or specifications by reducing options or

11、by adding missing features to improve interoperability. This specification defines the additional design guidelines for the Capability exchange-enabled AHD and WAN device certified device class (CDC). The purpose of the capability exchange is to reduce the amount of information that must be pre-conf

12、igured on a device in order to obtain plug and play interoperability. Specifically, capability exchange enables application hosting devices (AHDs) to know what types of messages it can send to the WAN device, by identifying its Continua CDCs. Likewise, capability exchange provides a mechanism for th

13、e AHD to inform the WAN device of its capabilities, to enable the WAN device to tailor its communication with the AHD. Capability exchange is mandatory for all WAN devices while it is optional for AHDs. It is assumed that the AHD is pre-provisioned with a URL, or a set of URLs, denoting the service

14、endpoint of one or more WAN devices. The capability exchange process takes place when the AHD first contacts a WAN device. It may also take place intermittently, to update the information received in the first capability exchange. In most cases, the set of Continua CDCs implemented at a WAN device c

15、hanges slowly, if at all. Therefore, it is expected that the AHD can store the information about WAN capabilities, and optionally, implement a policy for periodically updating that cache. An AHD might identify several WAN devices in this way, and communicate with one or more for different purposes.

16、The WAN device describes the information about its supported CDCs in a file called “root file“. The root file is a special resource that describes the properties of CDCs and how AHD can start information exchange with these CDCs. The root file and other features of the exchange come from an HL7 stan

17、dard called hData . It not only defines the root file format, but also defines the operations for exchanging root files, using HTTP using GET and POST operations, often referred to as “REST“ (for representational state transfer). Each Continua CDC (in addition to capability exchange) will use the ro

18、ot file to document information relevant to that capability, including the capability name, the information that can be exchanged under the capability and its format, and URLs for REST operations, if supported by that capability. Details are given in the documentation for the respective Continua CDC

19、s. Recommendation ITU-T H.812.3 is part of the “ITU-T H.810 interoperability design guidelines for personal health systems“ subseries, which is outlined in the table below: ii Rec. ITU-T H.812.3 (11/2015) Mapping of CDG 2013, ITU-T H.810 and restructured ITU-T H.810-series Part Elements Clauses in t

20、he 2013 CDG “Endorphin“ Clauses in ITU-T H.810 (2013) Restructured H.810-series (2015) Part 0 System overview Up to clause 3, plus Annex A and Appendix G Up to clause 6, plus Annex A and Appendix V ITU-T H.810 System overview Part 1 TAN/PAN/LAN Clauses 4 to 7, Appendices C, D, M Clauses 7 to 10, App

21、endices I, II, XI ITU-T H.811 TAN-PAN-LAN interface Part 2 WAN Clause 8, Appendices H, I, J, K Clause 11; Appendices VI, VII, VIII, IX ITU-T H.812 WAN interface ITU-T H.812.1 Observation upload ITU-T H.812.2 Questionnaires ITU-T H.812.3 Capability exchange ITU-T H.812.4 Authenticated persistent sess

22、ion Part 3 HRN Clause 9, Appendices E, F, L Clause 12, Appendices III, IV, X ITU-T H.813 HRN interface History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T H.812.3 2015-11-29 16 11.1002/1000/12656 * To access the Recommendation, type the URL http:/handle.itu.int/ in the address f

23、ield of your web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. Rec. ITU-T H.812.3 (11/2015) iii FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, informa

24、tion and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a world

25、wide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WT

26、SA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication adminis

27、tration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provis

28、ions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTSITU draws attention to

29、the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside

30、 of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the lates

31、t information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2016 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. iv Rec. ITU-T H.812.3 (11/2015) Table

32、of Contents Page 0 Introduction vi 0.1 Organization vi 0.2 CDC guideline releases and versioning vii 0.3 Whats new vii 1 Scope . 1 2 References . 1 3 Definitions 1 4 Abbreviations and acronyms 1 5 Conventions 1 6 Use cases . 1 6.1 AHD obtains WAN device information . 1 6.2 WAN device receives AHD in

33、formation . 2 7 Behavioural models 2 8 Implementation . 3 8.1 Overview 3 8.2 Root file exchange 3 8.3 Contents of the root file 4 8.4 Optional JSON version of root file . 5 Annex A Normative guidelines. 6 Appendix I Root file inclusions for capability exchange (This appendix does not form an integra

34、l part of this Recomemndation.) 10 I.1 Required root file inclusions for WAN device 10 I.2 Schema for the root.xml 10 I.3 Required root file inclusions for AHD 12 Appendix II hData (This appendix does not form an integral part of this Recomemndation.) 13 Bibliography. 16 Rec. ITU-T H.812.3 (11/2015)

35、 v List of Tables Page Table A-1 Normative guidelines for WAN devices 6 Table A-2 Normative guidelines for AHD device 9 Table II-1 Types of operations 14 List of Figures Page Figure 7-1 Transactions between AHD and WAN device related to capability exchange . 2 Figure II-1 hData Interoperability fram

36、ework 15 vi Rec. ITU-T H.812.3 (11/2015) 0 Introduction The Continua Design Guidelines (CDG) define a framework of underlying standards and criteria that are required to ensure the interoperability of devices and data used for personal connected health. They also contain additional design guidelines

37、 that further clarify the underlying standards or specifications by reducing options or by adding missing features to improve interoperability. These guidelines define the additional design guidelines for the Capability exchange-enabled AHD and WAN device certified device class (CDC). The purpose of

38、 the capability exchange is to reduce the amount of information that must be pre-configured on a device in order to obtain plug and play interoperability. Specifically, capability exchange enables application hosting devices (AHDs) to know what types of messages it can send to the WAN device, by ide

39、ntifying its Continua CDCs. Likewise, capability exchange provides a mechanism for the AHD to inform the WAN device of its capabilities, to enable the WAN device to tailor its communication with the AHD. Capability exchange is mandatory for all WAN devices while it is optional for AHDs. It is assume

40、d that the AHD is pre-provisioned with a URL, or a set of URLs, denoting the service endpoint of one or more WAN devices. The capability exchange process takes place when the AHD first contacts a WAN device. It may also take place intermittently, to update the information received in the first capab

41、ility exchange. In most cases, the set of Continua CDCs implemented at a WAN device changes slowly, if at all. Therefore, it is expected that the AHD can store the information about WAN capabilities, and optionally, implement a policy for periodically updating that cache. An AHD might identify sever

42、al WAN devices in this way, and communicate with one or more for different purposes. The WAN device describes the information about its supported CDCs in a file called “root file“. The root file is a special resource that describes the properties of CDCs and how AHD can start information exchange wi

43、th those CDCs. The root file and other features of the exchange come from an HL7 standard called hData HL7 V3 HRF OMG/hData RESTful Trans. hData not only defines the root file format, but also defines the operations for exchanging root files, using HTTP using GET and POST operations, often referred

44、to as “REST“ (for representational state transfer). Each Continua CDC (in addition to capability exchange) will use the root file to document information relevant to that capability, including the capability name, the information that can be exchanged under the capability and its format, and URLs fo

45、r REST operations, if supported by that capability. Details are given in the documentation for the respective Continua CDCs. This Recommendation is part of the ITU-T H.810 sub-series “H.810 Interoperability design guidelines for personal health systems“. See ITU-T H.810 for more details. 0.1 Organiz

46、ation This CDC guideline is organized in the following manner. Clauses 0 to 5: Introduction and terminology These clauses provide overview information which help in comprehending the remainder of the document. Clause 6: Use cases This clause provides motivating examples. Clause 7: Behavioural model

47、This clause is an overview of sequences of interactions and summarizes typical iterations, constraints and exceptions. Clause 8: Implementation guidance This clause provides an informative description of the implementation of the Capability exchange CDC. Annex A: Normative guidelines This clause spe

48、cifies the normative requirements that must be followed by the Capability exchange CDC. Rec. ITU-T H.812.3 (11/2015) vii 0.2 CDC guideline releases and versioning See clause 0.2 of ITU-T H.810 for release and versioning information. 0.3 Whats new To see what is new in this release of the design guid

49、elines refer to clause 0.3 of ITU-T H.810. Rec. ITU-T H.812.3 (11/2015) 1 Recommendation ITU-T H.812.3 Interoperability design guidelines for personal health systems: WAN interface: Capability exchange certified device class 1 Scope This Recommendation specifies design guidelines for the Capability exchange-enabled AHD and Capability exchange-enabled WAN CDCs. The design guidelines specify the testable requirements that must be implemented by the AHD in order to classify it as a Capability exchang