-1Question(s):
28/16
Study Group: 16
Meeting, date:
Working Party:
2/16 Intended type of document(R-C-D-TD):
TD
Source:
Title:
A.5 justification information for draft new H.812.2 (ex H.81x-WAN-IF.2)
Contact:
<Name>
<Organization>
<Country>
Contact:
Tel:
Fax:
Email:
Tel:
Fax:
Email:
Please don't change the structure of this table, just insert the necessary information.
1
Introduction
According to ITU procedures, as described in ITU-T Recommendation A.5, any normative
reference to documentation produced outside the ITU (other than ISO and IEC texts) needs to be
evaluated by the study group or working party before a decision is made to incorporate the
reference in an ITU-T Recommendation.
This TD contains the A.5 justification information for new H.812.2 (ex H.81x-WAN-IF.2).
2
Referred documents and respective justifications
- HL7 V3 HRF (2014): HL7 Version 3 Specification: hData Record Format, Release 1
- Specification approved by HL7 in 2014-06.
- This HL7 specification is needed for questionnaire-enabled application host devices (AHDs)
for the representation of questionnaire and questionnaire response.
NOTE - A.5 justification entered after Consent.
- Complete A.5 justification information can be found in Annex 1.
- OMG hData BIND (2011): OMG hData REST Binding for RLUS
- Approved by OMA as a Standard on 2011-08.
- This OMG Standard is needed for questionnaire-enabled application host devices (AHDs).
NOTE - A.5 justification entered after Consent.
- Complete A.5 justification information can be found in Annex 2.
- OMG hData RLUS (2011): OMG Retrieve, Locate, and Update Service (RLUS) Specification
1.0.1
- Approved by OMG on July 2011.
- This OMG Standard is needed for questionnaire-enabled application host devices (AHDs).
NOTE - A.5 justification entered after Consent.
- Complete A.5 justification information can be found in Annex 3.
-2-
Annex 1
A.5 justification information for the reference to HL7 V3 HRF (2014)
1
Clear description of the referenced document:
HL7 V3 HRF (2014): HL7 Version 3 Specification: hData Record Format, Release 1
2
Status of approval:
Specification approved by HL7 in 2014-06.
3
Justification for the specific reference:
This HL7 specification is needed for questionnaire-enabled application host devices (AHDs) for the
representation of questionnaire and questionnaire response.
NOTE - A.5 justification entered after Consent.
4
Current information, if any, about IPR issues:
N/A
5
Other useful information describing the "Quality" of the document:
This was approved by HL7 as a Draft Standard for Trial Use (DSTU) in December 2011. And final
specification was approved in 2014-06. The HL7 FHIR initiative occurred subsequent to the initial
version of hData and adopted many of the ideas of hData.
6
The degree of stability or maturity of the document:
See 5. above.
7
Relationship with other existing or emerging documents:
See 5. above.
8
Any explicit references within that referenced document should also be listed:
[1] Health Level 7 International, "Clinical Document Architecture Release 2," May 2005. [Online].
Available: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=7.
[Accessed July 2013].
[2] R. Fielding, "Architectural Styles and the Design of Network-based Software Architectures,"
Irvine, 2000.
[3] IETF Network Working Group, "The Atom Syndication Format," December 2005. [Online].
Available: http://www.ietf.org/rfc/rfc4287. [Accessed 1 July 2013].
[4] G. Grieve, E. Kramer and L. Mckenzie, "FHIR v0.09," 2013. [Online]. Available:
http://hl7.org/implement/standards/fhir/. [Accessed 1 July 2013].
[5] G. Beuchelt and et al., "hData RESTful Transport v 1.0," 2012. [Online]. Available:
http://www.omg.org/spec/HData/1.0/Beta2.
-3-
[6] Health Level Seven International, "HL7 Resource Location and Updating Service," 2006.
[7] Health Level Seven International, "HL7 Version 3 Normative Edition, 2011," 2011. [Online].
Available:
http://www.hl7.org/documentcenter/private/standards/v3/edition2011/HL7_V3_NormativeEdition2
011_2CDset.zip. [Accessed September 2013].
[8] Health Level Seven International, "HL7 Version 3 Implementation Guide: Medication
Statement Service Profile using hData, Release 1 – Universal Realm," April 2013. [Online].
Available: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=299. [Accessed
September 2013].
[9] G. Beuchelt, R. Dingwell, A. Gregorowicz and H. Sleeper, "hData - A Simple XML Framework
for Health Data Exchange," in Proceedings of Balisage: The Markup Conference 2009, Montréal,
2009.
[10] IETF Network Working Group, " The application/json Media Type for JavaScript Object
Notation (JSON)," July 2006. [Online]. Available: http://tools.ietf.org/html/rfc4627. [Accessed July
2013].
[11] American Health Information Management Association, "Retention and Destruction of Health
Information," 2011. [Online]. Available:
http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_049252.hcsp?dDocName=bo
k1_049252. [Accessed September 2013].
[12] Office of the National Coordinator for Health Information Technology Standards and
Interoperability Framework, "RESTful Health Exchange (RHEx)," 2012. [Online]. Available:
HL7 hData Record Format, Release 1 Page 43
June 2014 © 2014 Health Level Seven International. All rights reserved.
http://wiki.siframework.org/RHEx. [Accessed July 2013].
[13] Integrating the Healthcare Enterprise, "Consistent Time Integration Profile," July 2010.
[Online]. Available: http://wiki.ihe.net/index.php?title=Consistent_Time.
[14] IETF Network Working Group, "Key words for use in RFCs to Indicate Requirement Levels,"
March 1997. [Online]. Available: http://www.ietf.org/rfc/rfc2119.txt. [Accessed 1 July 2013].
-4-
[15] IETF, "URI Generic Syntax," January 2005. [Online]. Available:
http://tools.ietf.org/html/rfc3986. [Accessed July 2013].
[16] International Organization for Standarization (ISO), "Date and Time Format - ISO 8601,"
December 2004. [Online]. Available: http://www.iso.org/iso/home/standards/iso8601.htm.
[Accessed 1 July 2013].
[17] National Electrical Manufactureres Association (NEMA), "Digital Imaging and
Communications in Medicine (DICOM)," Medial Imaging & Technology Alliance, August 2011.
[Online]. Available: http://medical.nema.org/standard.html. [Accessed 1 July 2013].
[18] IETF Network Working Group, "The Atom Publishing Protocol," October 2007. [Online].
Available: http://www.ietf.org/rfc/rfc5023. [Accessed July 2013].
[19] Health Level Seven International, "CDA Relase 2," [Online]. Available:
http://www.hl7.org/implement/standards/product_brief.cfm?product_id=7.
[20] Health Level Seven International, "HL7 EHR System Functional Model, R1.1," July 2012.
[Online]. Available: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=269.
[Accessed July 2013].
[21] W3C Consortium, "W3C XML Signature Syntax and Processing (Second Edition)," June
2008. [Online]. Available: http://www.w3.org/TR/xmldsig-core. [Accessed July 2013].
9
Qualification of HL7:
Health Level 7 meets the qualifying criteria for normative referencing as per Recommendation ITUT A.5.
10
N/A
Other (for any supplementary information):
-5-
Annex 2
A.5 justification information for the reference to OMG hData BIND (2011)
1
Clear description of the referenced document:
OMG hData BIND (2011): OMG hData REST Binding for RLUS
2
Status of approval:
Approved by OMA as a Standard on 2011-08.
3
Justification for the specific reference:
This OMG Standard is needed for questionnaire-enabled application host devices (AHDs).
NOTE - A.5 justification entered after Consent.
4
Current information, if any, about IPR issues:
N/A
5
Other useful information describing the "Quality" of the document:
N/A
6
The degree of stability or maturity of the document:
N/A
7
Relationship with other existing or emerging documents:
N/A
8
Any explicit references within that referenced document should also be listed:
Annex A - Bibliography
[1] G. Beuchelt et al., "hData Record Format", The MITRE Corporation, 2011.
[2] IETF RFC 4345 •³Transport Layer Security (TLS) 1.1•´, online at
http://tools.ietf.org/html/rfc4346
[3] IETF Network Working Group. (2005, Dec.) IETF. [Online]. http://www.ietf.org/rfc/rfc4287.txt
[4] IETF Network Working Group •³S/MIME 3.2 Message Specification•´, online at
http://tools.ietf.org/html/
rfc5751
[5] IETF Network Working Group, •³Storing Certificates in the Domain Name System (DNS)•´,
online at http://
-6-
tools.ietf.org/html/rfc4398
[6] IETF Network Working Group, •³HTTP Authentication: Basic and Digest Access
Authentication•´, online at
http://tools.ietf.org/html/rfc2617
[7] IETF Network Working Group •³The TLS Protocol•´, online at
http://tools.ietf.org/html/rfc2246
[8] IETF Network Working Group •³Hypertext Transfer Protocol •¶ HTTP 1.1•´, online at
http://tools.ietf.org/html/
rfc2616
[9] HL7 Resource Location and Updating Service (RLUS), DSTU Release 1, Health Level Seven,
Inc., December
2006
[10] "Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message
Specification", RFC 3851,
The Internet Society, July 2004, online at http://www.rfc-editor.org/rfc/rfc3851.txt
[11] •³Cookbook:Preparing the IHE Profile Security Section•´, IHE International, October 2008,
online at http://
www.ihe.net/Technical_Framework/upload/IHE_ITI_Whitepaper_Security_Cookbook_2008-1110.pdf
[12] Retrieve, Locate, and Update Service (RLUS) 1.0.1, formal/2011-07-02
[13] "POST Once Exactly", Mark Nottingham, 2005, https://github.com/mnot/ID/blob/master/poe/draft-nottingham-httppoe01.xml
-7-
[14] http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm
9
Qualification of OMG:
OMG is recognized under the provisions of ITU-T Recommendations A.5 and A.4. Qualifying
information is on file at TSB.
10
N/A
Other (for any supplementary information):
-8-
Annex 3
A.5 justification information for the reference to OMG hData RLUS (2011)
1
Clear description of the referenced document:
OMG hData RLUS (2011): OMG Retrieve, Locate, and Update Service (RLUS) Specification 1.0.1
2
Status of approval:
Approved by OMG on July 2011.
3
Justification for the specific reference:
This OMG Standard is needed for questionnaire-enabled application host devices (AHDs).
NOTE - A.5 justification entered after Consent.
4
Current information, if any, about IPR issues:
N/A
5
Other useful information describing the "Quality" of the document:
N/A
6
The degree of stability or maturity of the document:
N/A
7
Relationship with other existing or emerging documents:
N/A
8
Any explicit references within that referenced document should also be listed:
Web Services Description Language (WSDL) 1.1, W3C Note 15 March 2001,
http://www.w3.org/TR/wsdl
Simple Object Access Protocol (SOAP) 1.1, W3C Note 08 May 2000,
http://www.w3.org/TR/SOAP
XML Schema Part 2: Datatypes, W3C Recommendation 02 May 2001,
http://www.w3.org/TR/xmlschema-2
9
Qualification of OMG:
OMG is recognized under the provisions of ITU-T Recommendations A.5 and A.4. Qualifying
information is on file at TSB.
10
N/A
Other (for any supplementary information):