Stream: implementers
Topic: Attachment File Types
Lauren Wolejsza (Mar 28 2017 at 13:07):
Good Morning!
Our developers have a question about the limitations of the Attachment data type. Via our PGHD mobile applications, users will be able to upload various file types including png, jpg, jpeg, rtf, pdf, tif, tiff, doc, docx, xml, xmlx, txt. Can FHIR support this? We are using FHIR DSTU2 and HAPI FHIR API that connects to a MongoDB.
I have tagged one of our developers here who is currently working on this and would appreciate some guidance. @Gang Chen
Thanks again!
John Moehrke (Mar 28 2017 at 13:25):
The specification has no issue. Those would be identified as Binary resources. Use a DocumentReference to record the metadata that you know about the files so that they can be discovered and understood.
Lauren Wolejsza (Mar 28 2017 at 13:27):
Okay, we are using that Resource to store these files. I will let @Gang Chen provide more details about the challenges the developers are facing with this now.
John Moehrke (Mar 28 2017 at 13:42):
This is the method that IHE-MHD uses for Patient specific Documents (for example as a FHIR API to XDS/XCA)... And now IHE is developing a new profile for Files that are not patient specific (for example configuration files, templates, phantoms, etc). The use of DocumentReference resource is key
Lauren Wolejsza (Mar 28 2017 at 13:43):
Thanks! Good to know!
Paul Knapp (Mar 28 2017 at 17:16):
You may also wish to look at the work of the Attachments Work Group which uses CommunicationRequest and Communication for the exchange of information.
Lauren Wolejsza (Mar 28 2017 at 19:32):
@Paul Knapp Thanks for this suggestion, however, we are using DSTU2 and not STU3 at this time so these resources are not available to us. I will look into the work of the Attachments Work Group.
Last updated: Apr 12 2022 at 19:14 UTC
