Stream: ihe
Topic: MHD DocumentReference profile attachment restriction
Wolfgang Kronseder (Aug 27 2020 at 10:32):
Hello, I'm trying to use the https://build.fhir.org/ig/IHE/ITI.MHD/IHE.MHD.Provide.Comprehensive.DocumentReference.html profile in context of a german telematic infrastructure (TI) project. It fit's quite well because parts of the TI specification are referring to XDS.b
One thing troubles me at the moment, is that DocumentReference.content.attachment.data is not allowed in this profile.
While this isn't an issue when retrieving documents, it would might be easier to provide a document as base64 encoded data instead of only linking it.
Our use case is the following:
- We download a document from an external repository and creating it on the FHIR server with a PUT request containing also the document data (base64 encoded)
- While storing the data the FHIR server takes the inline data and stores it in separate place (file system,...) other than the FHIR meta data.
- When a client is requesting the document later on, now the FHIR server provides only the url to the document in the DocumentReference resource.
Is there a reason whyDocumentReference.content.attachment.data is not allowed?
Oliver Egger (Aug 27 2020 at 10:57):
When providing a document you can embed it in the bundle as a Binary Resource (MHD line 683: When the DocumentReference.content.attachment.url points at a Binary Resource, the
Binary Resource shall be in the Bundle). This does not answer your question directly why it is now allowed though, I think it is for consistency reason that you always can expect the reference to the doc in attachment.url as ITI-67 Find Document Reference is requesting.
Wolfgang Kronseder (Aug 27 2020 at 11:24):
Thanks for the hint!
I missed that part in the specs and I also didn't thought of solving it this way.
You might not directly answer my question, but you helped me a lot. :smile:
Last updated: Apr 12 2022 at 19:14 UTC
