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

Is the Breast Density Score important to include in the breast diagnostic report?

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Considered - Question answered
    • Icon: Highest Highest
    • US Breast Cancer Radiology Reporting (FHIR)
    • current
    • Clinical Interoperability Council
    • Mammography Density
    • 13.69.1
    • Hide

      The Breast Density Score was indeed defined in ValueSet-MGDensityVS, and was referenced as a component in each of the abnormality findings. Another commenter pointed out that the location in each abnormality was incorrect, so it was made its own observation and referenced in 'Findings Left Breast' and/or 'Findings Right Breast' and/or 'Findings BiLateral Breast' allowing a breast density score for each breast or both.

      This change is included in the current release.

       

      Show
      T he Breast Density Score was indeed defined in ValueSet-MGDensityVS, and was referenced as a component in each of the abnormality findings. Another commenter pointed out that the location in each abnormality was incorrect, so it was made its own observation and referenced in 'Findings Left Breast' and/or 'Findings Right Breast' and/or 'Findings BiLateral Breast' allowing a breast density score for each breast or both. This change is included in the current release.  

    Description

      Is the Breast Density Score (BiRad A, B, C, D or score 1-4) important to include in the brest diagnostic report? Is it covered here in the Mammography Density ValueSet http://hl7.org/fhir/us/breast-radiology/2020MAY/ValueSet-MGDensityVS.html?

      (Comment 64 - imported by: Jean Duteau)

      Attachments

        Activity

          People

            Unassigned Unassigned
            Gonzaga Zabrina Gonzaga
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: