ITU-T H 830 11-2017 Conformance of ITU-T H 810 personal health system Services interface Part 11 Questionnaires Health & Fitness Service sender (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.11 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 11: Questionnaires: Health Part 11: Questionnaires: HFS Sender (Version 1.2, 2017-03-14). This Recommendation includes an electronic attachment with the protocol implementation conformance statement

3、s (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.11 2015-11-29 16 11.1002/1000/12676 2.0 ITU-T H.830.11 2016-07-14 16 11.1002/1000/12931 3.0 ITU-T

4、H.830.11 2017-04-13 16 11.1002/1000/13206 Keywords Conformance testing, Continua Design Guidelines, e-health, Health Part 11: Questionnaires: HFS Sender (Version 1.21, 2017-03-14), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test s

5、pecification; 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 accordin

6、g 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.11 (04/2017) 1 Recommendation ITU-T H.830.11 Conformance of ITU-T H.810 personal health system: S

7、ervices interface Part 11: 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 publis

8、hed. 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 (2016)

9、, Interoperability design guidelines for personal health systems: Personal health devices interface. 1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required f

10、or the implementation of Annex A. 2 Rec. ITU-T H.830.11 (04/2017) ITU-T H.812 Recommendation ITU-T H.812 (2016), Interoperability design guidelines for personal health systems: Services interface: Common certified capability class. ITU-T H.812.1 Recommendation ITU-T H.812.1 (2016), Interoperability

11、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 H.

12、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: Services i

13、nterface: 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, Rele

14、ase 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=117

15、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 DUT Device Un

16、der Test CDG Continua Design Guidelines CGM Continuous Glucose Monitor GUI Graphical User Interface HFS Health M RESTSec 4;M RESTSec 5;M CommonReq 5;M Spec ITU-T H.812.2 Testable items Question 1;M Question 3;M Question 5;M Test purpose Check that: SUT retrieves a list of to-be-completed questionnai

17、res from simulated HFS application and an actual to-be-completed questionnaire document. Applicability C_SEN_000 AND C_SEN_GEN_004 AND C_SEN_GEN_006 Other PICS C_SEN_GEN_005 Initial condition The simulated HFS receiver provides a list of to-be-completed questionnaires with a single entry containing

18、a link to an actual to-be-completed questionnaire document. Test procedure 1. An 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

19、 an atom feed containing a list of to-be-completed questionnaire documents containing one document. 2. An 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 content will be a

20、 relative path to baseURL (WanReceiver). 3. An HFS application validates received document according to Questionnaire Form Definition Document HL7 CDA QFD. Pass/Fail criteria An HFS application under test supports capability exchange as specified in ITU-T H.812.3. An HFS application successfully ret

21、rieves the list of to-be-completed questionnaires from the simulated HFS application. An HFS application successfully retrieves the actual to-be-completed questionnaire document using the content of the “link“ element in the atom feed. An HFS application confirms that the questionnaire document has

22、been validated. Notes TP Id TP/HFS/SEN/QUE/GEN/BV-001 TP label Questionnaire response submitting. HFS Sender. Coverage Spec ITU-T H.812 Testable items RESTSec 3;M RESTSec 4;M RESTSec 5;M CommonReq 5;M Spec ITU-T H.812.2 10 Rec. ITU-T H.830.11 (04/2017) Testable items Question 6;M Test purpose Check

23、that: SUT posts a questionnaire response document to the simulated HFS receiver. Applicability C_SEN_000 AND C_SEN_GEN_004 AND C_SEN_GEN_006 Other PICS C_SEN_GEN_005 Initial condition The simulated HFS receiver is ready to receive a questionnaire response document from the HFS sender under test. Tes

24、t procedure 1. A questionnaire-enabled HFS sender under test uses HTTP POST with the following URL for posting a questionnaire response document to the simulated HFS Device: baseURL/continua/questionnaireResponse. Connection uses TLSv1.1 and an Oauth2 bearer token. Pass/Fail criteria An HFS applicat

25、ion under test supports capability exchange as specified in ITU-T H.812.3. An HFS application successfully posts a questionnaire response document to the HFS receiver under test. Notes TP Id TP/HFS/SEN/QUE/GEN/BV-002 TP label Questionnaire response retrieval. HFS Sender. Coverage Spec ITU-T H.812 Te

26、stable items RESTSec 3;M RESTSec 4;M RESTSec 5;M CommonReq 5;M Spec ITU-T H.812.2 Testable items Question 1;M Question 7;M Question 8;M Test purpose Check that: SUT retrieves a list of completed questionnaires from simulated HFS application and an actual questionnaire response document. Applicabilit

27、y C_SEN_000 AND C_SEN_GEN_004 AND C_SEN_GEN_006 Other PICS C_SEN_GEN_005 Initial condition The simulated HFS receiver provides a list of completed questionnaires with a single entry containing a link to an actual questionnaire response document. Test procedure 1. An HFS application uses an HTTP GET

28、request without query parameters at the URL representing the patients questionnaire response hData path (continua/questionnaireResponses) using a secure REST connection in order to retrieve an atom feed containing a list of questionnaire response documents containing one single document. 2. An HFS a

29、pplication retrieves the questionnaire response document using the value of the “link“ element contained in the atom feed retrieved in step 1. “Link“ element content will be a relative path to baseURL (WanReceiver). 3. An HFS application validates received document according to Questionnaire Respons

30、e Document HL7 CDA QRD. Rec. ITU-T H.830.11 (04/2017) 11 Pass/Fail criteria An HFS application under test supports capability exchange as specified in ITU-T H.812.3. An HFS application successfully retrieves the list of completed questionnaires from the simulated HFS application. An HFS application

31、successfully retrieves the actual questionnaire response document using the content of the “link“ element in the atom feed. An HFS application confirms that the questionnaire response document has been validated. Notes A.3 Subgroup 1.7.2: CDA validation (CDA) TP Id TP/HFS/SEN/QUE/CDA/BV-000 TP label

32、 Questionnaire Response CDA syntactic and semantic validation. HFS Sender. Coverage Spec HL7 CDA QRD Testable items CONF-QR-1; M CONF-QR-2;R CONF-QR-3;M CONF-QR-4;M CONF-QR-5;M CONF-QR-6;M CONF-QR-7;M CONF-QR-8;M CONF-QR-9;M CONF-QR-11;M CONF-QR-14;M CONF-QR-15;M CONF-QR-16 ; M CONF-QR-17;M CONF-QR-

33、18 ;M CONF-QR-19;M CONF-QR-20;M CONF-QR-21;M CONF-QR-22;M CONF-QR-23 ;M CONF-QR-24;M CONF-QR-25;M CONF-QR-26;M CONF-QR-27;M CONF-QR-28 ;M CONF-QR-29;M CONF-QR-30;M CONF-QR-31;M CONF-QR-32;M CONF-QR-33 ;R CONF-QR-34;M CONF-QR-35;M CONF-QR-36;M CONF-QR-37;M CONF-QR-38 ;M CONF-QR-39;R CONF-QR-40;M CONF

34、-QR-41;R CONF-QR-42;M CONF-QR-43;M CONF-QR-44;M CONF-QR-45;O CONF-QR-46;M CONF-QR-47;M CONF-QR-48 ;M CONF-QR-49;M CONF-QR-50;M CONF-QR-51;M CONF-QR-52;O CONF-QR-53 ;O CONF-QR-54;M CONF-QR-55;R CONF-QR-56;M CONF-QR-57;M CONF-QR-58 ;O CONF-QR-59;R CONF-QR-60;M CONF-QR-61;M CONF-QR-62;M CONF-QR-63 ;M C

35、ONF-QR-64;M CONF-QR-65;M CONF-QR-66;R CONF-QR-67;M CONF-QR-68 ;O CONF-QR-69;M 12 Rec. ITU-T H.830.11 (04/2017) CONF-QR-70;R CONF-QR-71;O CONF-QR-72;M CONF-QR-73 ;O CONF-QR-74;M CONF-QR-75;R CONF-QR-76;M CONF-QR-77;M CONF-QR-78 ;M CONF-QR-79;M CONF-QR-80;M CONF-QR-81 ;O CONF-QR-82;M CONF-QR-83 ;M CON

36、F-QR-84;M CONF-QR-85;M CONF-QR-86;O CONF-QR-87;M CONF-QR-88 ;M CONF-QR-89;M CONF-QR-90 ;M CONF-QR-91;M CONF-QR-92;O CONF-QR-93 ;M CONF-QR-94;M CONF-QR-95;R CONF-QR-96 ;R CONF-QR-97;M CONF-QR-98 ;O CONF-QR-99;O CONF-QR-100;M CONF-QR-101;M CONF-QR-102;R CONF-QR-103 ;M CONF-QR-104;M CONF-QR-105 ;O CONF

37、-QR-106;M CONF-QR-107;M CONF-QR-108 ;M CONF-QR-109;M CONF-QR-110;R CONF-QR-111 ;R CONF-QR-112;M CONF-QR-113 ;M CONF-QR-114;M CONF-QR-115;M CONF-QR-116; CONF-QR-117;M CONF-QR-118;M CONF-QR-119; CONF-QR-120 ;M CONF-QR-121;M CONF-QR-122;R CONF-QR-123 ;M CONF-QR-124;R CONF-QR-125;M CONF-QR-126 ;M CONF-Q

38、R-127;M CONF-QR-128;M CONF-QR-129 ;M CONF-QR-130;M CONF-QR-131;M CONF-QR-132 ;M CONF-QR-133;R CONF-QR-134;M CONF-QR-135 ;M CONF-QR-136;M CONF-QR-137;M CONF-QR-138 ;M CONF-QR-139;M CONF-QR-140,M CONF-QR-141 ;M CONF-QR-142;M CONF-QR-143;M CONF-QR-144 ;M CONF-QR-145;M CONF-QR-146;M CONF-QR-147 ;M CONF-

39、QR-148;M CONF-QR-149;M CONF-QR-150;M CONF-QR-151;M CONF-QR-152;M CONF-QR-153;O CONF-QR-154;M CONF-QR-155;M CONF-QR-156;M CONF-QR-157;M CONF-QR-158;M CONF-QR-159;M CONF-QR-160;M CONF-QR-161;M CONF-QR-162;M CONF-QR-163;M CONF-QR-164;M CONF-QR-165;M Rec. ITU-T H.830.11 (04/2017) 13 CONF-QR-166;M CONF-Q

40、R-167;R CONF-QR-168;M CONF-QR-169;M CONF-QR-170;M CONF-QR-171;M CONF-QR-172;O CONF-QR-173;M CONF-QR-174;M CONF-QR-175;R CONF-QR-176,M CONF-QR-177;M CONF-QR-178;R CONF-QR-179;M CONF-QR-180;M CONF-QR-181;M CONF-QR-182;M CONF-QR-183;M CONF-QR-184;M CONF-QR-185;M CONF-QR-186;M CONF-QR-187;M CONF-QR-188;

41、M CONF-QR-189;M CONF-QR-190;M CONF-QR-191;M CONF-QR-192;M CONF-QR-193;M CONF-QR-194;M CONF-QR-195;M CONF-QR-196;R CONF-QR-197;M CONF-QR-198;M CONF-QR-199;M CONF-QR-200;R CONF-QR-201;M CONF-QR-202;M CONF-QR-203;M CONF-QR-204;M CONF-QR-205;M CONF-QR-206;M CONF-QR-207;M CONF-QR-208;M CONF-QR-209;M CONF

42、-QR-210;M CONF-QR-211;M CONF-QR-212;M CONF-QR-213;R CONF-QR-214;M CONF-QR-215;M CONF-QR-216;M CONF-QR-217;M CONF-QR-218;M CONF-QR-219;M CONF-QR-220;M CONF-QR-221;R CONF-QR-222;M CONF-QR-223;M CONF-QR-224;M CONF-QR-225;M CONF-QR-226;M CONF-QR-227;M CONF-QR-228;M CONF-QR-229;M CONF-QR-230;M CONF-QR-23

43、1;M CONF-QR-232;M CONF-QR-233;M CONF-QR-234;M CONF-QR-235;M CONF-QR-236;M CONF-QR-237;M CONF-QR-238;M CONF-QR-239;M CONF-QR-240;M Test purpose Check that: SUT has submitted a syntactically correct questionnaire response document , so that: ClinicalDocument element SHALL contain exactly one 11 realmC

44、ode. AND ClinicalDocument element SHOULD be selected from HL7 ValueSet BindingRealm 2.16.840.1.113883.1.11.20355 from codesystem hl7Realm 2.16.840.1.113883.5.1124 STATIC 2010-11-11. AND ClinicalDocument element SHALL contain exactly one 11 typeId. AND ClinicalDocument/typeId element SHALL contain ex

45、actly one 11 14 Rec. ITU-T H.830.11 (04/2017) root=“2.16.840.1.113883.1.3“. AND ClinicalDocument/typeId element SHALL contain exactly one 11 extension=“POCD_HD000040“. AND ClinicalDocument SHALL contain at least one 1* header-level templateId. AND ClinicalDocument/templateId SHALL contain exactly on

46、e 11 root=”2.16.840.1.113883.10.20.29” . AND ClinicalDocument/templateId SHALL contain exactly one 11 root=”2.16.840.1.113883.10.20.33” . AND ClinicalDocument SHALL contain exactly one 11 id. AND ClinicalDocument SHALL contain exactly one 11 code. AND ClinicalDocument SHALL contain exactly one 11 ti

47、tle. AND ClinicalDocument SHALL contain exactly one 11 effectiveTime. AND ClinicalDocument SHALL contain exactly one 11 confidentialityCode, which SHALL be selected from ValueSet HL7 BasicConfidentialityKind 2.16.840.1.113883.1.11.16926 STATIC 2010-04-21. AND ClinicalDocument SHALL contain exactly o

48、ne 11 languageCode, which SHALL be selected from ValueSet Language 2.16.840.1.113883.1.11.11526 DYNAMIC. AND ClinicalDocument SHALL contain exactly one 11 recordTarget. AND Such recordTargets SHALL contain exactly one 11 patientRole. AND This patientRole SHALL contain at least one 1* id. AND This pa

49、tientRole SHALL contain at least one 1* addr. AND This patientRole SHALL contain at least one 1* telecom. AND This patientRole SHALL contain exactly one 11 patient. AND This patient SHALL contain exactly one 11 name. AND This patient SHALL contain exactly one 11 administrativeGenderCode. AND This patient SHALL contain exactly one 11 birthTime. AND Rec. ITU-T H.830.11 (04/2017) 15 Patient/birthTime SHALL be precis