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

Is DiagnosticReport-open too Radiology-centric?

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Considered - Question answered
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 2.0.0
    • Infrastructure & Messaging
    • DiagnosticsReport open event [deprecated]
    • 3.6.1
    • Hide

      Elliot, we're continuing to discuss this question. Eric's answer from comments:

      The normative portions of the content section have been separated into Section 2.6 Content Sharing.  In this section content sharing is discussed in a generic, non-report centric manner (using [FHIR resource]-* used in other parts of the specification.  This separation recognizes that the mechanisms used in context sharing are application to situations other than Radiology reporting.

      In the non-normative Scenario section of the specification, Section 4.6 covers the use case of Radiology reporting as an example scenario.  Even in the Radiology reporting scenario, additional implementation guides on top of the more generic FHIRcast specification will help normalize implementations of content sharing.  For example, the IHE Radiology technical committee has started work on such an implementation guide.

      Show
      Elliot, we're continuing to discuss this question. Eric's answer from comments: The normative portions of the content section have been separated into Section 2.6 Content Sharing.  In this section content sharing is discussed in a generic, non-report centric manner (using  [FHIR resource] -* used in other parts of the specification.  This separation recognizes that the mechanisms used in context sharing are application to situations other than Radiology reporting. In the non-normative Scenario section of the specification, Section 4.6 covers the use case of Radiology reporting as an example scenario.  Even in the Radiology reporting scenario, additional implementation guides on top of the more generic FHIRcast specification will help normalize implementations of content sharing.  For example, the IHE Radiology technical committee has started work on such an implementation guide.

    Description

      Is the DiagnosticReport-open event too tailored to Radiology reporting? Are there other specialties that might want other content beyond an imagingstudy? Why is the context key "study" rather than following the "imagingstudy" pattern?

      Also section 4.6.1 ("a Hub could validate that the content in a DiagnosticReport anchor context always includes at least one primary imaging study" precludes use of DiagnosticReport for non-imaging uses), section 4.6.3.2 ("These changes usually include adding/removing imaging studies"), and more.

      Do we need "profiles" of events for particular uses?

      (Comment 32 - imported by: Lloyd McKenzie)

      Attachments

        Activity

          People

            Unassigned Unassigned
            esilver Elliot Silver
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: