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

Question: Use of Observation.text field.

    XMLWordPrintableJSON

    Details

    • Type: Question
    • Status: Triaged (View Workflow)
    • Priority: Highest
    • Resolution: Considered - Question answered
    • Specification:
      US Breast Cancer Radiology Reporting (FHIR)
    • Raised in Version:
      current
    • Work Group:
      Clinical Interoperability Council
    • Related Artifact(s):
      Mammography Finding
    • Related Section(s):
      13.66.5
    • Grouping:
    • Resolution Description:
      Hide

      The Observation.text field is unchanged in all the Observation derived profiles. This IG does not specify how it should/should not be used, and is left up to the implementer to put any desired human readable text into this location.

      Show
      The Observation.text field is unchanged in all the Observation derived profiles. This IG does not specify how it should/should not be used, and is left up to the implementer to put any desired human readable text into this location.

      Description

      Is Observation.text an expected component of both MGFinding and the abnormality object (ex. Mass)? The field is present in both - should both be populated?

      (Comment 11 - imported by: Jean Duteau)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              bzeug@epic.com Ben Zeug
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: