Difference between revisions of "XCA Implementation"

From IHE Wiki
Jump to navigation Jump to search
 
(12 intermediate revisions by 5 users not shown)
Line 1: Line 1:
−
After publication of the August 2007 Trial Implementation version of Cross Community Access (XCA) profile several issues have come to light.  These issues are documented in Change Proposals (CPs) which will be completed during the year and integrated in August 2008.  Prior to August 2008 this page will list the issues and their expected resolution, both short term and long term.
+
= XCA Onion References =
 +
Because XCA builds upon a large body of prior work it seems like an onion of specifications, where each layer of specification contains only a thin layer of content and then refers to the lower layer.  This section lays out the onion and attempts to link directly into the sections being referenced.  It is an in trial section since the direct referencing is a pilot and not fully tested yet.
  
−
== Typos ==
+
The XCA Onion looks like the following:
−
CP 256 contains a couple of small typos. One of which is to change the name to be grammatically correct, from Cross Community to Cross-Community. Please communicate any further typos discovered in the XCA profile to the CP auther for inclusion in this CP. The current version of the CP can be accessed in the [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2006-2007/CPs/Assigned Assigned] directory.
+
* XCA Profile Specification - [http://www.ihe.net/Technical_Framework/upload/IHE_ITI_Suppl_XCA_Rev2-1_TI_2010-08-10.pdf#page=14 XCA Supplement Vol. 1 Section 18 page 14]
 +
** Cross Gateway Query - [http://www.ihe.net/Technical_Framework/upload/IHE_ITI_Suppl_XCA_Rev2-1_TI_2010-08-10.pdf#page=36 XCA Supplement Vol. 1 Section 3.38 page 36]
 +
*** Registry Stored Query - [http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev7-0_Vol2a_FT_2010-08-10.pdf#page=94 ITI TF Vol. 2a Section 3.18 page 94]
 +
**** XDS Metdata Model - [http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev7-0_Vol3_FT_2010-08-10.pdf#page=3 ITI TF Vol. 3 Section 4.1 page 3], [http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev7-0_Vol3_FT_2010-08-10.pdf#page= 13 4.1.7 page 13], [http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev7-0_Vol3_FT_2010-08-10.pdf#page=31 4.1.8 page 31]
 +
**** ebRS
 +
** Cross Gateway Retrieve - [http://www.ihe.net/Technical_Framework/upload/IHE_ITI_Suppl_XCA_Rev2-1_TI_2010-08-10.pdf#page=42 XCA Supplement Vol. 1 Section 3.39 page 42]
 +
*** Retrieve Document Set - [http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev7-0_Vol2b_FT_2010-08-10.pdf#page=115 ITI TF Vol. 2b Section 3.43 page 115]
  
−
== Missing Web Services protocol information ==
+
== See Also ==
−
CP 257 contains the missing web services protocol information (WSDL and examples).  Please use this information for your implementations.  The latest version of the CP can be accessed in the [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2006-2007/CPs/Assigned Assigned] directory.  The example files and WSDL are also available in the [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr5-2007-2008/Technical_Cmte/SupportMaterial SupportMaterial] directory.
+
The [[IT Infrastructure]] Domain manages this profile.
  
−
== Implied assumption of Responding Gateway URLs ==
+
The [http://www.ihe.net/Technical_Framework/index.cfm#IT ITI Technical Framework] is the official master document for this Profile.  
−
The design of XCA has an unstated assumption that a Responding Gateway will use the same URL for responding to Cross Gateway Retrieve transactions as it does for Cross Gateway Query transactions. The homeCommunityId attribute is associated with the url that responded to a Cross Gateway Query. This association is used in subsequent requests to determine which url to use to communicate to get more detailed information regarding elements returned in the previous request.  This assumes that the same url will be used for subsequent query requests as well as retrieve requests.  This assumption is not stated clearly.  It poses a restriction on the design of a Responding Gateway that should be reviewed to verify that it is reasonable.  Also, this mapping does not handle movement of service or changes in url values.
 
  
−
For this year we will require that Responding Gateways support query and retrieve from the same URL.  CP 258 documents this issue.  The long term resolution of this problem is not defined yet but will include either an update to the document to make the requirement clear or a change in the requirement.
+
The [[Cross-Comunity Access]] page is an overview of the Profile.  
−
 
 
−
The latest version of the CP can be accessed in the [ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2006-2007/CPs/Assigned Assigned] directory.
 
  
  
 
[[Category:Profile Implementations]]
 
[[Category:Profile Implementations]]

Latest revision as of 09:37, 6 December 2010

XCA Onion References

Because XCA builds upon a large body of prior work it seems like an onion of specifications, where each layer of specification contains only a thin layer of content and then refers to the lower layer. This section lays out the onion and attempts to link directly into the sections being referenced. It is an in trial section since the direct referencing is a pilot and not fully tested yet.

The XCA Onion looks like the following:

See Also

The IT Infrastructure Domain manages this profile.

The ITI Technical Framework is the official master document for this Profile.

The Cross-Comunity Access page is an overview of the Profile.

Retrieved from "http://wiki.ihe.net/index.php?title=XCA_Implementation&oldid=46757"