Stream: implementers
Topic: uploading a documents
Jeremy Chapman (Sep 17 2019 at 17:28):
I want to provide a service that can upload a collection of documents. So I want to encapsulate things using a DocumentManifest that has content references to DocumentReferences. The trick is I need to supply the content as well, and I don't want to base64 encode anything, so I want to use multipart mime. I suspect this might massively break the rules, but the thought was to include the FHIR resources in the first part, then subsequent parts would include the raw binary content of each file. Terrible idea? If not, then how does the DocumentReference somehow reference the binary content in the subsequent parts? is it sufficient to use the DocumentReference.content.attachment.url with a guid or something that can correlate to the name of the one of the parts?
David Pyke (Sep 17 2019 at 17:42):
You should probably look at the IHE MHD profile which covers your case.
Jeremy Chapman (Sep 17 2019 at 21:52):
ok thanks. IHE.... is it just me or does anyone else find the IHE documentation painfully challenging to read?
Michele Mottini (Sep 18 2019 at 12:28):
(I refuse to read them)
David Pyke (Sep 18 2019 at 12:32):
All the FHIR enabled profiles are being moved to the FHIR IG Publisher so, soon, they will be a joy to have.
Lloyd McKenzie (Sep 18 2019 at 12:42):
Not good to throw stones. HL7 has a lot to do in improving the accessibility/friendliness of our documentation too. The good news is that with a shared tooling stack, we can help each other.
Grahame Grieve (Sep 18 2019 at 12:43):
y. I really needed :joy-with-a-serving-of-irony: there
Kevin Mayfield (Sep 18 2019 at 13:47):
Just look at the pictures..TLDR :)
Jeremy Chapman (Sep 18 2019 at 15:22):
Regarding the IHE MHD profile, I'm reading http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_MHD.pdf volumne2c - Transactions where it takes about the Document Source providing a Document Bundle to a Document Recipient. I am assuming this is the interaction you are referriing to. The documentation points to https://www.ihe.net/fhir/StructureDefinition/IHE_MHD_Provide_Minimal_DocumentBundle and https://www.ihe.net/fhir/StructureDefinition/IHE_MHD_Provide_Comprehensive_DocumentBundle which just return a page not found. I've also looked at the wiki https://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD) which does not seem to point to any actual documentation that shows how the messaging actually looks. Where should I be looking for this information?
David Pyke (Sep 18 2019 at 16:48):
@John Moehrke
John Moehrke (Sep 18 2019 at 17:34):
I will echo what has been said... The most formal thing I can point you at is the GitHub repository where ALL of the conformance resources for all of the IHE based Implementation Guides (profiles) are published.
https://github.com/IHE/fhir
John Moehrke (Sep 18 2019 at 17:35):
For MHD there is a mixture of the old STU3 versions, and the new R4. The new R4 do validate.
John Moehrke (Sep 18 2019 at 17:35):
Although I do know of some fixes that will be published later.
John Moehrke (Sep 18 2019 at 17:37):
Yes, IHE is working hard at moving to the tooling that HL7 has created for publication of IG in html form with packages and common look and feel where it is best. That will be a focus of the comming months
Jeremy Chapman (Oct 01 2020 at 17:48):
Is there any update on this? Earlier in the thread, @David Pyke said that the FHIR enabled profiles are being moved to the FHIR IG Publisher. I am hopeful that this suggested that the IHE documentation would be become easier to find and consume. Has anything happened on that front?
David Pyke (Oct 01 2020 at 17:52):
Yep, github.com/ihe has the source code for most
John Moehrke (Oct 02 2020 at 14:00):
well, not quite as optimistic as that. IHE has been working with github, and with the IG publisher.. but there are no finally and approved IG published works other than the FormatCode vocabulary http://profiles.ihe.net/fhir/ihe.formatcode.fhir/
John Moehrke (Oct 02 2020 at 14:03):
I have a MHD that is my personal work, and thus not complete or formal.. but does have signfiant number of examples --- warning, that it also includes an additional (experimental) beyond what the IHE committees have agreed to (like using List rather than Manifest) http://build.fhir.org/ig/IHE/ITI.MHD/branches/master/index.html
Oliver Egger (Oct 02 2020 at 14:39):
@John Moehrke what would be required steps to create mhd, pmir, restful atna implementation guides by ihe? we made an mhd / pmir based implementation guide for switzerland see https://github.com/ehealthsuisse/ch-epr-mhealth using the available ihe conformance resources. if we could contribute back the parts to base ihe mhd pmir ig's this would be very helpful. in addition this ig's could then also be used for connectathon testing.
John Moehrke (Oct 02 2020 at 14:59):
@Oliver Egger they need to be defined as new work items, that are proposed and prioritized by the ITI Planning. I have MHD in the queue already. I expect the group of them will be accepted as new work items at the November meeting. So, propose them, and show up at the next planning meeting to voice your interest.
Oliver Egger (Oct 03 2020 at 07:00):
@John Moehrke the october 20th planning meeting? count me in!
Last updated: Apr 12 2022 at 19:14 UTC
