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
Other Diagnostic Reports - URI of location of referred to content? #107
[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
Some consideration required for if we want to support in other diagnostic reports (DiagnosticReport profiles) how to store one URI per report or test referencing the externally images or other useful content. Where a URI is not available, additional narrative might be included stating a phone number or other contact details for further enquiry.
This is a requirement in My Health Record Diagnostic Imaging Report but still under consideration as to whether or not this is to be supported for Pathology Reports.
Possibly an endPoint extension may be useful, possibly a simple extension for only the use case is appropriate.
What it actually enables people to do
Clarification will enable modelers to design appropriately for the desired content.
Mockups
n/a
How awesome would it be?
It would be great to have to have clarity on the details on the URI of location of referred content.
Workarounds
Without a clear modelling input the URI of location of referred content may be non standardised or non-functional and thereby impede interoperability and the clarity of the report.
Prerequisites
The issue
Change description
Some consideration required for if we want to support in other diagnostic reports (DiagnosticReport profiles) how to store one URI per report or test referencing the externally images or other useful content. Where a URI is not available, additional narrative might be included stating a phone number or other contact details for further enquiry.
This is a requirement in My Health Record Diagnostic Imaging Report but still under consideration as to whether or not this is to be supported for Pathology Reports.
Possibly an endPoint extension may be useful, possibly a simple extension for only the use case is appropriate.
What it actually enables people to do
Clarification will enable modelers to design appropriately for the desired content.
Mockups
n/a
How awesome would it be?
It would be great to have to have clarity on the details on the URI of location of referred content.
Workarounds
Without a clear modelling input the URI of location of referred content may be non standardised or non-functional and thereby impede interoperability and the clarity of the report.
Additional context
n/a