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

Version-management conflict concerns

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 2.0.0
    • Infrastructure & Messaging
    • STU
    • Content Sharing
    • Hide

      > Specifically, if the concept is that a single anchor resource is versioned with everything else as contained resources

      The versionid has been changed from being described as the version of a single anchor resource, but rather is now described as the version of the anchor context.

       

      Show
      > Specifically, if the concept is that a single anchor resource is versioned with everything else as contained resources The versionid has been changed from being described as the version of a single anchor resource, but rather is now described as the version of the anchor context.  
    • Jonathan Whitby/Bas van den Heuvel: 6-0-1
    • Correction
    • Non-compatible
    • Yes

    Description

      I am concerned about the version-management scheme presented here. For example, if a radiologist is 'moving' back and forth between a viewer (creating measurements that translate to FHIR Observations) and the dictation app (describing ROIs that translate to content in the document), I feel that there is a large potential for synchronization errors. Specifically, if the concept is that a single anchor resource is versioned with everything else as contained resources, multiple systems will be changing sections (the contained resources) concurrently.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ginocanessa Gino Canessa
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: