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

Contained resource mandated?

    XMLWordPrintableJSON

Details

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

      We will add a header at the top of this page saying that this page is non-normative, because all the pages under Scenarios are intended to be non-normative. We will do the same for Multi-anchor. 

      We will remove this sentence: 

      Exchanged content need not have an independent existence. For the purposes of a working session in FHIRcast, they are all “contained” in one resource (the DiagnosticReport anchor context). For example, a radiologist may use the PACS viewer to create a measurement. The PACS application sends this measurement as an Observation to the other subscribing applications for consideration. If the radiologist determines the measurement is useful in another application (and accurate), it may then become an Observation to be included in the diagnostic report. Only when that diagnostic report becomes an official signed document would that Observation possibly be maintained with an independent existence. Until that time, FHIR domain resources serve as a convenient means to transfer data within a FHIRcast context.

      Show
      We will add a header at the top of this page saying that this page is non-normative, because all the pages under Scenarios are intended to be non-normative. We will do the same for Multi-anchor.  We will remove this sentence:  Exchanged content need not have an independent existence. For the purposes of a working session in FHIRcast, they are all “contained” in one resource (the  DiagnosticReport  anchor context). For example, a radiologist may use the PACS viewer to create a measurement. The PACS application sends this measurement as an  Observation  to the other subscribing applications for consideration. If the radiologist determines the measurement is useful in another application (and accurate), it may then become an  Observation  to be included in the diagnostic report. Only when that diagnostic report becomes an official signed document would that  Observation  possibly be maintained with an independent existence. Until that time, FHIR domain resources serve as a convenient means to transfer data within a FHIRcast context.
    • Jonathan Whitby/Bas van den Heuvel: 6-0-1
    • Clarification
    • Non-substantive

    Description

      Exchanged content need not have an independent existence. For the purposes of a working session in FHIRcast, they are all "contained" in one resource (the

      Is this mandated or guidance? What happens if I do not want this? E.g. because the data is stored in a FHIR server or the Observation is used in ImagingStudy-update and DiagnosticReport-updated and hence has an independent lifecycle.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: