Working drafts of HL7™ FHIR® Release 4 (R4) artefacts authored and maintained by the Informatics Architecture team at the Australian Digital Health Agency.
Other
14
stars
3
forks
source link
Packaging attachments in FHIR payload for MHR system - unknown requirements #74
[X] I have searched open and closed issues to make sure it isn't already requested or reported
[X] I have written a descriptive issue title
The issue
Change description
Not yet clear what the packaging requirements are for attachments when sending FHIR to the My Health Record system infrastructure.
In lieu of a FHIR equivalent of the Clinical Documents - CDA Package v1.0 specification, examples for this profile will include workarounds (e.g. absolute url to a placholder repository for attachment) or inclusion as base64 binary in a bundle.
What it actually enables people to do
Clear instructions on the packaging of attachments will enable implementers to be able to correctly reference/attachments to the MHR.
How awesome would it be?
Clear instructions are much better than leaving no details about how a referenced or attached report is to be handled when sending FHIR to the MHR.
Workarounds
When the process is not clear, implementers will create their own process that suits their needs and may not not be the best interoperable solution.
Prerequisites
The issue
Change description
Not yet clear what the packaging requirements are for attachments when sending FHIR to the My Health Record system infrastructure.
In lieu of a FHIR equivalent of the Clinical Documents - CDA Package v1.0 specification, examples for this profile will include workarounds (e.g. absolute url to a placholder repository for attachment) or inclusion as base64 binary in a bundle.
What it actually enables people to do
Clear instructions on the packaging of attachments will enable implementers to be able to correctly reference/attachments to the MHR.
How awesome would it be?
Clear instructions are much better than leaving no details about how a referenced or attached report is to be handled when sending FHIR to the MHR.
Workarounds
When the process is not clear, implementers will create their own process that suits their needs and may not not be the best interoperable solution.
Additional context
Clinical Documents - CDA Package v1.0