Query+for+Documents+Page+5

 = 6 Design Considerations and Assumptions = = = = 7 Referenced Documents and Standards = The following documents and standards were referenced during the development of this specification. Specific deviations from or constraints upon these standards are identified below. 1) ** Org/SDO name: ** HITSP ** Reference # / Spec Name: ** TP13 / Manage Sharing of Documents Transaction Package  ** Version #: ** v2.6  ** Underlying Specs: **   · IHE ITI TF Supplement XCA TI (2009-8-10)   · IHE ITI TF Vol. 1 & 2a, 2b, 2x, 3 Revision 6.0 (2009-8-10)  ** NHIN Deviations or Constraints: **see entry for IHE ITI TF Supplement XCA TI (2009-8-10)  ** Link: **[]  2) ** Org/SDO name: ** HITSP ** Reference # / Spec Name: ** C80/ Clinical Document and Message Terminology Component ** Version #: ** v1.1.1 ** NHIN Deviations or Constraints: ** ** Underlying Specs: ** ** Link: **[] 3) ** Org/SDO name: ** IHE ** Reference # / Spec Name: ** ITI TF Supplement XCA TI  ** Version #: ** 2009-8-10  ** NHIN Deviations or Constraints: **   · IHE XCA 3.38 -. This specification allows return of -1 in hash and size to indicate "not available" to support dynamic documents. The use of availabilityStatus=”urn:ihe:iti:2010:StatusCode:DeferredCreation” indicates that the document creation has been deferred until a retrieve is received. Further explanation is given in sections 2.3 “Transaction Standard” and 3.3 “Query Parameters”.   · IHE XCA 3.38 - Document identifiers may be only valid for a limited time period – IHE makes no statement about this.   · IHE XCA 3.38 – XCA does not currently support the XDSUnknownPatientId to be used in a response to Cross Gateway Query. This specification allows this error to be used to indicate that a previously valid patient identifier is no longer valid. This deviation from XCA increases the risk of a spoofing attack as it is easier for an attacker to identify an invalid patient identifier. Rather than use this error, XCA requires that invalid identifiers result in the return of an empty list. ** IHE Change Proposal 450 ** has been submitted to request a change of the IHE requirement and is expected to be approved by Spring 2010. ** Underlying Specs: ** ** Link: **[] ** Change Proposals Adopted by NHIN: ** a. ** // Change Proposal Name: // ** IHE Change Proposal 420 ** // Change Proposal Description: // ** Updates XCA to use a single Action value for both synchronous and asynchronous interactions. This balloted and approved Change Proposal will integrate into the XCA Supplement in August 2010 and is adopted by the NHIN now because of its importance. ** // Change Proposal Link: // ** [] b. ** // Change Proposal Name: // ** IHE Change Proposal 403, 429 ** // Change Proposal Description: // ** Minor updates to audit requirements. ** // Change Proposal Links: // ** [], ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2009/CPs/FinalText/CP-ITI-429-FT.doc c. ** // Change Proposal Name: // ** IHE Change Proposal 413 ** // Change Proposal Description: // ** Clarification of calculation of hash. ** // Change Proposal Link: // ** [] d. ** // Change Proposal Name: // ** IHE Change Proposal 415 ** // Change Proposal Description: // ** Defines an error in the case where a list of document unique ID’s in a query without patient identifier reference different patients ** // Change Proposal Link: // ** [] 4) ** Org/SDO name: **IHE ** Reference # / Spec Name: ** ITI TF Vol. 1 & 2a, 2b, 2x, 3  ** Version #: ** Revision 6.0 (2009-8-10)  ** NHIN Deviations or Constraints: **  ** Underlying Specs: **  ** Links:  **  · []  · []  · []  · []  · [] 5) ** Org/SDO name: ** OASIS ** Reference # / Spec Name: ** ebRIM: OASIS/ebXML Registry Information Model  ** Version #: ** v 3.0  ** NHIN Deviations or Constraints: **  ** Underlying Specs: **  ** Link:  **  []  6) ** Org/SDO name: ** OASIS ** Reference # / Spec Name: ** ebRS: OASIS/ebXML Registry Services Specifications ** Version #: ** v 3.0 ** NHIN Deviations or Constraints: ** ** Underlying Specs: ** ** Link: ** [] = 8 Appendices =

8.3 Appendix C- Data Dictionary
 2. It is an optional parameter to Registry Stored Query requests, not requiring a patient id parameter, and Retrieve Document Set requests to indicate which community to direct the request. ||
 * Data Element Name ||  Definition  ||  Rule  ||
 * homeCommunityId ||  The homeCommunityId value is a globally unique identifier for a community and is used to obtain Web Services endpoint of services that provide access to data in that community. It is used by Initiating Gateways to direct requests to the community where the initial data originated  ||  1. Document Consumers process the value in the response as an opaque unique identifier.
 * patienId ||   ||   ||