Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-26362

What is an appropriate resource and element to include addendum text?

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Considered - Question answered
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • Orders & Observations
    • DiagnosticReport
      Observation
    • Hide

      There is no clearly identified singular way to provide such data.  However, these are the options to consider:

      Observation.note - it can repeat and reflect context for a change made.

      Observation for a separately documented note using Observation.focus to reference the one it is about.  Not as clean as the one above.

      DiagnosticReport.note - Similar as above when revising the DiagnosticReport the note could reflect context.

      One could consider an Observation referenced in DiagnosticReport.result, but that becomes far less clean similar to creating a separate Observation above.

      Provenance may be viable as well where you may need to track more about the revision in a structured fashion beyond describing the context.  However, Provenance.activity would likely be limited.

      Commonly agreed to guidance is not yet available with no clear time when that may occur.

      2023-05-09 - Reviewed and agreed that better guidance is required here. There are extensions for replaces and addendum on DiagnosticReport, but these may also be more appropriately addressed in the core. Will create a new ticket to review, which will be handled in the COW workflow project effort. This will be Jira-41241

      Show
      There is no clearly identified singular way to provide such data.  However, these are the options to consider: Observation.note - it can repeat and reflect context for a change made. Observation for a separately documented note using Observation.focus to reference the one it is about.  Not as clean as the one above. DiagnosticReport.note - Similar as above when revising the DiagnosticReport the note could reflect context. One could consider an Observation referenced in DiagnosticReport.result, but that becomes far less clean similar to creating a separate Observation above. Provenance may be viable as well where you may need to track more about the revision in a structured fashion beyond describing the context.  However, Provenance.activity would likely be limited. Commonly agreed to guidance is not yet available with no clear time when that may occur. 2023-05-09 - Reviewed and agreed that better guidance is required here. There are extensions for replaces and addendum on DiagnosticReport, but these may also be more appropriately addressed in the core. Will create a new ticket to review, which will be handled in the COW workflow project effort. This will be Jira-41241

    Description

      Hello,

      In case of corrected reports, we generally include addendum text i.e. text with date indicating the change between the corrected report and the previous one. What would be the resource and the element(s) to include this kind of information?

      Thanks,

      Mullai

      Attachments

        Activity

          People

            Unassigned Unassigned
            mullai murugan Mullai Murugan
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: