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

Clarify profile specific implementation guidance for US Core DiagnosticReport Profile for Report and Note exchange

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • US Core (FHIR)
    • 4.0.0
    • Cross-Group Projects
    • US Core DiagnosticReport Profile for Report and Note Exchange
    • Profile specific implementation guidance
    • Hide

      see FHIR-34759

       

      Since we are removing Must Support for ImagingStudy we will remove this implementation Guidance.

      Show
      see FHIR-34759   Since we are removing Must Support for ImagingStudy we will remove this implementation Guidance.
    • Isaac Vetter / Floyd Eisenberg : 13-0-0
    • Correction
    • Compatible, substantive

    Description

      Please clarify the "must support" note regarding DocumentReference.imagingStudy and DocumentReference.media
      "• the server system is not required to support both, but SHALL support at least one of these elements. • The client application SHALL support both elements and target resources."

      It would make more sense for the server system to support both, and depending on ancillary workflow and client capabilities, require the client to support one.
      For example, a VNA in radiology (as a client) is likely to POST ImagingStudy, whereas a non-DICOM point of care imaging device is likely to POST media.

      Attachments

        Activity

          People

            Unassigned Unassigned
            steven_nichols Steven Nichols
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: