Stream: implementers
Topic: Document reference for XDS document
Sven Christiansen (Oct 13 2017 at 11:44):
Does anyone have an example of a DocumentReference that holds the necessary parameters to be used to retrieve a document by the service XDS.b RetrieveDocumentSet? (I.e. the RepositoryUniqueID and the DocumentUniqueID)
Ex soap body:
<RetrieveDocumentSetRequest xmlns="urn:ihe:iti:xds-b:2007"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DocumentRequest>
<RepositoryUniqueId>1.19.6.24.109.42.1.5</RepositoryUniqueId>
<DocumentUniqueId>2009.9.1.1573</DocumentUniqueId>
</DocumentRequest>
</RetrieveDocumentSetRequest>
John Moehrke (Oct 13 2017 at 12:55):
Hi Sven, You would be best first looking at the IHE Profile for this use-case. See MHD http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD)
John Moehrke (Oct 13 2017 at 12:55):
I am the author of that profile, and of the DocumentReference in FHIR.
John Moehrke (Oct 13 2017 at 13:01):
The solution that you will find in MHD is a recognition that the DocmentReference is crafted by a service that chooses how to encode those elements in to the URL that is placed into the DocumentReference.content.attachment.url. This is based on the recognition that when using FHIR as an API to XDS/XCA; one must proxy both the Registry and Repositories through that API service, thus that service can manipulate the URL at the same time it manipulates the DocumentEntry. And that manipulation algorithm does not need to be understood by anyone other than that API service. Thus the algorithm does not need to be standardized or publicized. This allows that API service to be as creative as it needs/wants to be. The client side behaves the same.
Last updated: Apr 12 2022 at 19:14 UTC
