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

Remove redundant text and impossible situation

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 2.1.0-ballot [deprecated]
    • Infrastructure & Messaging
    • STU
    • DiagnosticsReport open event [deprecated]
    • Hide

      Will remove descriptive paragraph

      Show
      Will remove descriptive paragraph
    • Catie Ladd / Nick Radov : 6-0-1
    • Clarification
    • Non-substantive
    • Yes

    Description

      When a DiagnosticReport-open event is received by an application, the application should respond as is appropriate for its clinical use. For example, an image reading application may respond to a DiagnosticReport-open event posted by a reporting application by opening any imaging study(ies) specified in the context. A reporting application may want to respond to a DiagnosticReport-open event posted by an image reading application by creating a new or opening an existing report.

      An application that listens to DiagnosticReport events is mandated to follow the requirements of this spec. Repeating this is confusing.

      A diagnosticreport-open event can never trigger a new report as it refers to an existing one.

      Attachments

        Activity

          People

            Unassigned Unassigned
            bvdh Bas van den Heuvel
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: