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

Ability to include interpretation text/findings and recommendations to Observation

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Triaged (View Workflow)
    • Priority: Medium
    • Resolution: Considered for Future Use
    • Specification:
      Genomics Reporting (FHIR)
    • Work Group:
      Clinical Genomics
    • Related Page(s):
      (profiles)
    • Resolution Description:
      Hide

      Currently able to send this information without extensions, using Observation.note, method.text, and interpretation.text. Work group will considerĀ use cases in the future and identify opportunities to encode information further in one or more extensions.

      Previous proposal:
      Add a new complex Extension (AdditionalGuidance) (0..*), with two attributes:

      • type (CodeabeConcept), binding = example, unbound
      • content (Annotation)

      Associate extension to GenomicsBase profile, making it available on any Observation profiles.

      Show
      Currently able to send this information without extensions, using Observation.note, method.text, and interpretation.text. Work group will considerĀ use cases in the future and identify opportunities to encode information further in one or more extensions. Previous proposal: Add a new complex Extension (AdditionalGuidance) (0..*), with two attributes: type (CodeabeConcept), binding = example, unbound content (Annotation) Associate extension to GenomicsBase profile, making it available on any Observation profiles.
    • Change Category:
      Enhancement

      Description

      As highlighted in the attached test reports, we include textual findings/interpretations and recommendations in a genetic report. For the eMERGE reports, while mapping to draft CG IG spec, these textual interpretations span multiple FHIR Observation profiles in our implemention e.g. Referencing file "highlighted..." test report, text highlighted in grey and yellow would be a fit for general profiles like obs-overall and obs-inh-dis-path; text highlighted in green would be a fit for PGx profiles and the recommendations text highlighted in blue is a recommendation for the provider but not exactly a recommended action; it would be up to the provider to decide on the recommended action.

      Considering the need for including this kind of interpretative/summary text (this is not the same as the "text" narrative element) spans multiple Observation resources, it would be very helpful if Interpretation Text and Recommendations were added as Narrative or String elements to the obs-base resource itself.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              mullai murugan Mullai Murugan
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: