ITU-T H 830 12-2017 Conformance of ITU-T H 810 personal health system Services interface Part 12 Questionnaires Health & Fitness Service receiver (Study Group 16).pdf

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.830.12 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (04/2017) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS E-health multimedia services and applications Interoperability compliance testing of personal health systems (H

2、RN, PAN, LAN, TAN and WAN) Conformance of ITU-T H.810 personal health system: Services interface Part 12: Questionnaires: Health Part 12: Questionnaires: HFS Receiver (Version 1.2, 2017-03-14). This Recommendation includes an electronic attachment with the protocol implementation conformance stateme

3、nts (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T H.830.12 2015-11-29 16 11.1002/1000/12677 2.0 ITU-T H.830.12 2016-07-14 16 11.1002/1000/12932 3.0 ITU-

4、T H.830.12 2017-04-13 16 11.1002/1000/13207 Keywords Conformance testing, Continua Design Guidelines, e-health, Health Part 12: Questionnaires: HFS Receiver (Version 1.2, 2017-03-14), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this tes

5、t specification; it may contain versions that existed before transposition. Version Date Revision history 1.0 2015-07-01 Initial release for Test Tool DG2015 based on the requirements in b-ITU-T H.810 (2015)/b-CDG 2015. 1.1 2016-09-20 Initial release for Test Tool DG2016. It implements changes accor

6、ding to ITU-T H.810 (2016)/b-CDG 2016 (Iris + Errata) refreshments. 1.2 2017-03-14 Editorial: added insulin pump and continuous glucose monitor specializations to the TSS list in clause 6. Rec. ITU-T H.830.12 (04/2017) 1 Recommendation ITU-T H.830.12 Conformance of ITU-T H.810 personal health system

7、: Services interface Part 12: Questionnaires: Health users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly pub

8、lished. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T H.810 (2016) Recommendation ITU-T H.810 (2016), Interoperability design guidelines for personal health systems. ITU-T H.811 Recommendation ITU-T H.811 (20

9、16), Interoperability design guidelines for personal health systems: Personal health devices interface. ITU-T H.812 Recommendation ITU-T H.812 (2016), Interoperability design guidelines for personal health systems: Services interface: Common certified capability class. 1 This Recommendation includes

10、 an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. 2 Rec. ITU-T H.830.12 (04/2017) ITU-T H.812.1 Recommendation ITU-T H.812.1 (2016), Interoperabili

11、ty design guidelines for personal health systems: Services interface: Observation upload certified capability class. ITU-T H.812.2 Recommendation ITU-T H.812.2 (2016), Interoperability design guidelines for personal health systems: Services interface: Questionnaires certified capability class. ITU-T

12、 H.812.3 Recommendation ITU-T H.812.3 (2016), Interoperability design guidelines for personal health systems: Services interface: Capability exchange certified capability class. ITU-T H.812.4 Recommendation ITU-T H.812.4 (2016), Interoperability design guidelines for personal health systems: Service

13、s interface: Authenticated persistent session certified capability class. ITU-T H.813 Recommendation ITU-T H.813 (2016), Interoperability design guidelines for personal health systems: Healthcare information system interface. HL7 CDA QFD Health Level Seven (2014), HL7 Implementation Guide for CDA, R

14、elease 2: Questionnaire Form Definition Document, Release 1. http:/www.hl7.org/dstucomments/showdetail.cfm?dstuid=116 HL7 CDA QRD Health Level Seven (2014), HL7 Implementation Guide for CDA, Release 2: Questionnaire Response Document, Release 1. http:/www.hl7.org/dstucomments/showdetail.cfm?dstuid=1

15、17 HL7 V3 HRF Health Level Seven (2014), HL7 Version 3 Specification: hData Record Format, Release 1. http:/www.hl7.org/documentcenter/private/standards/v3/V3_ITS_HDATA_RF_R1_2014JUN.pdf IETF RFC 3339 IETF RFC 3339 (2002), Date and Time on the Internet: Timestamps. https:/datatracker.ietf.org/doc/rf

16、c3339 3 Definitions 3.1 Terms defined elsewhere None. 3.2 Terms defined in this Recommendation None. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: AHD Application Hosting Device ATS Abstract Test Suite ATNA Audit Trail and Node Authentication CDG Con

17、tinua Design Guidelines CGM Continuous Glucose Monitor DUT Device Under Test GUI Graphical User Interface HFS Health M RESTSec 8;M CommonReq 5;M Spec ITU-T H.812.2 Testable items Question 3;M Question 4;M Question 5;M Test purpose Check that: The simulated HFS application retrieves from the SUT a li

18、st of to-be-completed questionnaires and an actual to-be-completed questionnaire document. Applicability C_REC_000 AND C_REC_GEN_004 AND C_REC_GEN_006 Other PICS C_REC_GEN_005 Initial condition The HFS receiver under test provides a list of to-be-completed questionnaires with at least one entry cont

19、aining a link to an actual to-be-completed questionnaire document. Test procedure 1. The simulated HFS application uses an HTTP GET request without query parameters at the URL representing the patients questionnaire hData root section path (continua/questionnaires) using a secure hData connection in

20、 order to retrieve an atom feed containing a list of to-be-completed questionnaire documents containing at least one document. 2. The simulated HFS application retrieves the actual to-be-completed questionnaire document using the value of the “link” element contained in the atom feed retrieved in st

21、ep 1. “Link” element may be a relative path to baseURL or a full path. Pass/Fail criteria The HFS receiver under test supports capability exchange as specified in ITU-T H.812.3. The HFS receiver under test provides a list of to-be-completed questionnaires with at least one entry. The atom entry elem

22、ent of the questionnaire list shall contain the dueDate extension element in the Continua namespace, the content of which shall conform to the “date-time“ production in IETF RFC 3339. The HFS receiver under test allows the retrieval of the actual to-be-completed questionnaire document using the cont

23、ent of the “link” element in the atom feed. Notes TP Id TP/HFS/REC/QUE/GEN/BV-001 TP label Questionnaire response submitting. HFS Receiver. Coverage Spec ITU-T H.812 Testable items RESTSec 7;M RESTSec 8;M CommonReq 5;M Spec ITU-T H.812.2 Testable items Question 6;M Question 9;M Question 13;M 10 Rec.

24、 ITU-T H.830.12 (04/2017) Test purpose Check that: The simulated HFS application posts a questionnaire response document to the HFS receiver under test. Applicability C_REC_000 AND C_REC_GEN_004 AND C_REC_GEN_006 Other PICS C_REC_GEN_005 Initial condition The HFS receiver under test is ready to rece

25、ive a questionnaire response document from the simulated HFS sender. Test procedure 1. The simulated HFS application uses HTTP POST with the following URL for posting a questionnaire response document to the HFS receiver under test: baseURL/continua/questionnaireResponse using a secure hData connect

26、ion. Pass/Fail criteria The HFS receiver under test supports capability exchange as specified in ITU-T H.812.3. Questionnaire Enabled HFS Device validates the received document and sends the HTTP 201 (Created) as a response. Notes TP Id TP/HFS/REC/QUE/GEN/BV-002 TP label Questionnaire HTTP responses

27、. HFS Receiver. Coverage Spec ITU-T H.812 Testable items RESTSec 7;M RESTSec 8;M CommonReq 5;M Spec ITU-T H.812.2 Testable items Question 14;M Question15;M Question 16;M Test purpose Check that: The HFS receiver under test returns appropriate HTTP return codes to several HTTP operations. Applicabili

28、ty C_REC_000 AND C_REC_GEN_004 AND C_REC_GEN_006 Other PICS C_REC_GEN_005 Initial condition The Questionnaire Enabled HFS receiver under test is ready to receive HTTP operations. Test procedure 1. The Questionnaire Enabled HFS receiver under test receives an HTTP POST request on questionnaire sectio

29、n path from the simulated HFS application. 2. The Questionnaire Enabled HFS receiver under test receives an HTTP PUT request on questionnaire section path. 3. The Questionnaire Enabled HFS receiver under test receives an HTTP PUT request on questionnaire response section path. 4. The Questionnaire E

30、nabled HFS receiver under test receives an HTTP DELETE request on questionnaire section path. 5. The Questionnaire Enabled HFS receiver under test receives an HTTP DELETE request on questionnaire response section path. Pass/Fail criteria The HFS receiver under test supports capability exchange as sp

31、ecified in ITU-T H.812.3. Rec. ITU-T H.830.12 (04/2017) 11 The Questionnaire Enabled HFS receiver under test does not support the creation of new questionnaire record via the hData interface and returns HTTP 405 Method Not Allowed as a response to HTTP POST request on questionnaire section path. The

32、 Questionnaire Enabled HFS receiver under test does not support the modification of an existing questionnaire or questionnaire response record and shall return HTTP 405 Method Not Allowed as a response to HTTP PUT request on questionnaire and questionnaire response section paths. The Questionnaire E

33、nabled HFS receiver under test does not support the deletion of an existing questionnaire or questionnaire response record and shall return HTTP 405 Method Not Allowed as a response to HTTP DELETE request on questionnaire and questionnaire response section paths. Notes TP Id TP/HFS/REC/QUE/GEN/BV-00

34、3 TP label Questionnaire response retrieval. HFS Receiver. Coverage Spec ITU-T H.812 Testable items RESTSec 7;M RESTSec 8;M CommonReq 5;M Spec ITU-T H.812.2 Testable items Question 7;M Question 8;M Test purpose Check that: The simulated HFS application retrieves from the SUT a list of questionnaire

35、responses and an actual questionnaire response document. Applicability C_REC_000 AND C_REC_GEN_004 AND C_REC_GEN_006 Other PICS C_REC_GEN_005 Initial condition The HFS receiver under test provides a list of questionnaire responses with at least one entry containing a link to an actual questionnaire

36、response document. Test procedure 1. The simulated HFS application uses an HTTP GET request without query parameters at the URL representing the patients questionnaire hData root section path (continua/questionnaires) using a secure hData connection in order to retrieve an atom feed containing a lis

37、t of to-be-completed questionnaire documents containing at least one document. 2. The simulated HFS application retrieves the actual to-be-completed questionnaire document using the value of the “link” element contained in the atom feed retrieved in step 1. “Link” element may be a relative path to b

38、aseURL or a full path. Pass/Fail criteria The HFS receiver under test supports capability exchange as specified in ITU-T H.812.3. The HFS receiver under test provides a list of to-be-completed questionnaires with at least one entry. The HFS receiver under test allows the retrieval of the actual to-b

39、e-completed questionnaire document using the content of the “link” element in the atom feed. Notes 12 Rec. ITU-T H.830.12 (04/2017) A.3 Subgroup 2.7.2: CDA validation (CDA) TP Id TP/HFS/REC/QUE/CDA/BV-000 TP label Questionnaire CDA syntactic and semantic validation. HFS Receiver Coverage Spec HL7 CD

40、A QFD Testable items CONF-Q-1; M CONF-Q-2;R CONF-Q-3;M CONF-Q-4;M CONF-Q-5;M CONF-Q-6;M CONF-Q-7;M CONF-Q-8;M CONF-Q-10;M CONF-Q-13 ; R CONF-Q-14;M CONF-Q-15;M CONF-Q-16 ; M CONF-Q-17;M CONF-Q-18 ;M CONF-Q-19;M CONF-Q-20;M CONF-Q-21;M CONF-Q-22;M CONF-Q-23 ;M CONF-Q-24;M CONF-Q-25;M CONF-Q-26;M CONF

41、-Q-27;M CONF-Q-28 ;M CONF-Q-29;M CONF-Q-30;R CONF-Q-31;M CONF-Q-32;R CONF-Q-33 ;M CONF-Q-34;M CONF-Q-35;M CONF-Q-36;M CONF-Q-37;M CONF-Q-38 ;M CONF-Q-39;M CONF-Q-40;M CONF-Q-41;R CONF-Q-42;M CONF-Q-43;M CONF-Q-44;M CONF-Q-45;M CONF-Q-46;M CONF-Q-47;M CONF-Q-48 ;M CONF-Q-49;M CONF-Q-50;M CONF-Q-51;M

42、CONF-Q-52;M CONF-Q-53 ;M CONF-Q-54;M CONF-Q-55;R CONF-Q-56;M CONF-Q-57;M CONF-Q-58 ;M CONF-Q-59;M CONF-Q-60;M CONF-Q-61;M CONF-Q-62;M CONF-Q-63 ;R CONF-Q-64;M CONF-Q-65;R CONF-Q-66;M CONF-Q-67;M CONF-Q-68 ;M CONF-Q-69;M CONF-Q-70;M CONF-Q-71;M CONF-Q-72;M CONF-Q-73 ;M CONF-Q-74;R CONF-Q-75;M CONF-Q-

43、76;M CONF-Q-77;O CONF-Q-78 ;M CONF-Q-79;M CONF-Q-80;M CONF-Q-81 ;M CONF-Q-82;M CONF-Q-83 ;M CONF-Q-84;M CONF-Q-85;M CONF-Q-86;O CONF-Q-87;M CONF-Q-88 ;M CONF-Q-89;M CONF-Q-90 ;M Rec. ITU-T H.830.12 (04/2017) 13 CONF-Q-91;M CONF-Q-92;O CONF-Q-93 ;M CONF-Q-94;M CONF-Q-95;M CONF-Q-96 ;M CONF-Q-97;M CON

44、F-Q-98 ;M CONF-Q-99;M CONF-Q-100;M CONF-Q-101;M CONF-Q-102;M CONF-Q-103 ;M CONF-Q-104;M CONF-Q-105 ;M CONF-Q-106;M CONF-Q-107;M CONF-Q-108 ;M CONF-Q-109;M CONF-Q-110;R CONF-Q-111 ;M CONF-Q-112;M CONF-Q-113 ;M CONF-Q-114;M CONF-Q-115;O CONF-Q-116; M CONF-Q-117;M CONF-Q-118;M CONF-Q-119; M CONF-Q-120

45、;M CONF-Q-121;M CONF-Q-122;M CONF-Q-123 ;M CONF-Q-124;M CONF-Q-125;M CONF-Q-126 ;M CONF-Q-127;M CONF-Q-128;M CONF-Q-129 ;M CONF-Q-130;M CONF-Q-131;M CONF-Q-132 ;M CONF-Q-133;M CONF-Q-134;M CONF-Q-135 ;M CONF-Q-136;M CONF-Q-137;R CONF-Q-138 ;R CONF-Q-139;M CONF-Q-140,M CONF-Q-141 ;M CONF-Q-142;M CONF

46、-Q-143;M CONF-Q-144 ;M CONF-Q-145;M CONF-Q-146;M CONF-Q-147 ;M CONF-Q-148;R CONF-Q-149;M CONF-Q-150;M CONF-Q-151;M CONF-Q-152;M CONF-Q-153;M CONF-Q-154;M CONF-Q-155;M CONF-Q-156;M CONF-Q-157;M CONF-Q-158;R CONF-Q-159;O CONF-Q-160;M CONF-Q-161;M CONF-Q-162;M CONF-Q-163;M CONF-Q-164;M CONF-Q-165;M CON

47、F-Q-166;R CONF-Q-167;R CONF-Q-168;M CONF-Q-169;M CONF-Q-70;M CONF-Q-171;M CONF-Q-172;M CONF-Q-173;M CONF-Q-174;M CONF-Q-175;M CONF-Q-176,M CONF-Q-177;R CONF-Q-178;M CONF-Q-179;M CONF-Q-180;M CONF-Q-181;M CONF-Q-182;M CONF-Q-183;R CONF-Q-184;M CONF-Q-185;M CONF-Q-186;M 14 Rec. ITU-T H.830.12 (04/2017

48、) CONF-Q-187;R CONF-Q-188;M CONF-Q-189;M CONF-Q-190;R CONF-Q-191;M CONF-Q-192;M CONF-Q-193;R CONF-Q-194;M CONF-Q-195;M CONF-Q-196;R CONF-Q-197;M CONF-Q-198;M CONF-Q-199;M CONF-Q-200;R CONF-Q-201;M CONF-Q-202;M CONF-Q-203;M CONF-Q-204;M CONF-Q-205;M CONF-Q-206;R CONF-Q-207;O CONF-Q-208;M CONF-Q-209;M

49、 CONF-Q-210;R CONF-Q-211;M CONF-Q-212;M CONF-Q-213;R CONF-Q-214;M CONF-Q-215;M CONF-Q-216;M CONF-Q-217;M CONF-Q-218;M CONF-Q-219;M CONF-Q-220;M CONF-Q-221;M CONF-Q-222;M CONF-Q-223;M CONF-Q-224;M CONF-Q-225;M CONF-Q-226;M CONF-Q-227;M CONF-Q-228;M CONF-Q-229;M CONF-Q-230;M CONF-Q-231;M CONF-Q-232;M CONF-Q-233;O CONF-Q-234;R CONF-Q-235;M CONF-Q-236;M CONF-Q-237;M CONF-Q-238;M CONF-Q-239;M CONF-Q-240;M CONF-Q-241;M CONF-Q-242;R CONF-Q-243;M CONF-Q-244;M CONF-Q-245;M CONF-Q-246;M CONF-Q-247;M CONF-Q-248;M