Closed davidmckillop closed 4 years ago
Work has started on developing a 'shell' ( i.e. must supports, cardinality, fixed values, metadata) StructureDefinition for a Simple Imaging Observation. Progressing content will be in a later phase 2 (i.e. slicing, terminology, invariants).
This shell profile with placeholder introductory content and early known issues will be included in Diagnostic Report FHIR IG. Progressing via CIFMM-3418.
Product owner review passed, now submitted for internal review.
Internal review picked up missing partOf.reference as 1..1. This has now been fixed and flicked back to review.
Passed internal review; rebuilt Diagnostic Report output and on master to include the shell profile with placeholder introductory content. https://github.com/AuDigitalHealth/ci-fhir-r4/commit/fbe16e686a01f33a45c7252ea4455631580264ed Further work expected in a later phase 2 (i.e. slicing, terminology, invariants).
Phase 2 work started. Intending to get to :
Also fix typo in StructureDefinition.description replace 'or' with 'for'
Product owner walkthrough - minor changes to known issues and intro.md. Product owner okayed content.
Sent for internal review with @RichardTON
Issues found:
All OK.
Prerequisites
The feature
Change description
Development of a profile to represent key elements of clinical relevance (such as imaging examination name and image date time) to accompany a rich text representation of a diagnostic imaging report as issued by the diagnostic service provider for the electronic exchange of diagnostic imaging reports between healthcare providers, and between healthcare providers and the My Health Record system infrastructure in Australia.
The main context of this profile is to support the existing requirements for My Health Record Diagnostic Imaging Report content in a FHIR format and drive CDA-based FHIR.
The existing CDA implementation including requirements can be found here: eHealth Diagnostic Imaging Report v1.2.2.
What it actually enables people to do
This profile supports the identification of tests performed for a patient enabling an individual to determine if the Diagnostic Imaging Report is of interest but does not directly support reporting of the actual results of the diagnostic imaging tests (see Atomic Diagnostic Imaging Observation for atomic reporting). The observation may represent the result of a simple test or it may group the set of results produced by a multi-test study. In the latter cases, the observation carries the code of the study / panel and references the individual tests that make up the study / panel as ‘has-member’ child observations.
How awesome would it be?
Workarounds
No good ones, potentially use of AU Diagnostic Observation could offer some value with terminology but meaningful use is not supported without further derivation and guidance.
Additional context
eHealth Diagnostic Imaging Report v1.2.2
View pathology and diagnostic imaging reports
Diagnostic imaging reports in My Health Record