1 / 13

IHE ITI Profile Development XCA Query-and-Retrieve

IHE ITI Profile Development XCA Query-and-Retrieve. Fraunhofer ISST epSOS Consortium epSOS Industry Team. Option 1: XCA Query + async. XDR. Initiating Gateway. Responding Gateway. Document Registry. Document Consumer. Cross-Gateway Query Request. (XCA extension needed). Document

galia
Download Presentation

IHE ITI Profile Development XCA Query-and-Retrieve

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IHE ITI Profile DevelopmentXCA Query-and-Retrieve Fraunhofer ISST epSOS Consortium epSOS Industry Team

  2. Option 1: XCA Query + async. XDR Initiating Gateway Responding Gateway Document Registry DocumentConsumer Cross-Gateway Query Request (XCA extension needed) Document Recipient Document Repository Cross-Gateway Query Response (XCA “full” response or just flagthat indicates that docs follow) Provide and Register Document Set-b Document Source

  3. Option 1: XCA Query + async. XDR Initiating Gateway Responding Gateway Document Registry DocumentConsumer Cross-Gateway Query Request (XCA extension needed) PEP Document Recipient Document Repository Cross-Gateway Query Response (XCA “full” response or just flagthat indicates that docs follow) state redundancy audit trail Provide and Register Document Set-b addressing? Document Source firewall

  4. Option 2a: XCA Query + Result Set Initiating Gateway Responding Gateway DocumentConsumer Document Registry Cross-Gateway Query Request (ebXML Standard; MTOM) Document Repository metadata documents Cross-Gateway Query Response (XCA extended query response with docs attached via XOP/MTOM)

  5. Option 2a: XCA Query + Result Set Initiating Gateway Responding Gateway DocumentConsumer Document Registry Cross-Gateway Query Request (ebXML Standard; MTOM) PEP Document Repository metadata redundancy(in case of CDA) documents audit trail Cross-Gateway Query Response (XCA extended query response with docs attached via XOP/MTOM)

  6. Option 2b: XCA Query + min. Result Initiating Gateway Responding Gateway DocumentConsumer Document Registry Cross-Gateway Query Request (specific returnType; MTOM) Document Repository documents Cross-Gateway Retrieve Response (no extension needed...)

  7. Option 2b: XCA Query + min. Result Initiating Gateway Responding Gateway DocumentConsumer Document Registry Cross-Gateway Query Request (specific returnType; MTOM) PEP extension to ebXML query needed Document Repository documents audit trail Cross-Gateway Retrieve Response (no extension needed...)

  8. XCA XGateway-Query Extension Option 2a Option 1 cross-gateway Query XDR result submission cross-gateway Queryreturning XCA retrieve Option 2b

  9. Option 2a: XCA Extension • The query request message XML is syntactically identical to that of IHE Cross Community Query request with two extensions:. • The <ws:Action/> is “urn:ihe:iti:2010:CrossGatewayQueryRetrieve” • Inside the @AdhocQueryRequest/ResponseOption, the returnType “LeafClassWithRepositoryItem” MUST be used. This value, specified by ebRS version 3.0, indicates that both the full metadata plus the document contents are to be returned.

  10. Option 2a: XCA Extension • The query response includes metadata and documents <rim:ExtrinsicObject> <!-- lots of stuff missing here --> <xdsext:Document> ... <!-- base64 coded document --> </xdsext:Document> </rim:ExtrinsicObject>.... - wire-format as for retrieve response message (MTOM/XOP)

  11. Profile Short Description This profile supports means to access medical data from an SOA entity service. In contrast to a HIN node an SOA entity service is derived from one or more related business entities (see section 2.4.2 in IHE White Paper “An SOA View on IHE Profiles”). An entity service offers its consumers operations for retrieving views and derivations on the business’ entities information and data model. This profile defines means to implement SOA entity service consumers and providers on top of IHE gateway actors. A “query and retrieve” transaction provides direct access to a business entity. By grouping the respective actors with XUA actors, the shared business objects can be safeguarded by policy based access control in a straightforward manner (see IHE White Paper “Access Control”).

  12. Actors and Transactions

  13. Options and Groupings • Options • async messaging (see XCA) • Groupings described in the profile • XUA • XDS • BPPC • XCPD

More Related