Why no duplicates in Document or message - 2018-May Core Norm Infrastructure #253

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Bundle
    • Hide

      There are valid use cases for including multiple versions of a resource. Remove the rules barring multiple versions, and document the potential risk around unversioned references (e.g. if you have an unversioned reference to a resource where multiple versions exist in the bundle - that is ambiguous). Also document limitations around transactions make server obligations and functionality clear. Document that Provenance tracking may necessitate multiple versions in a bundle.

      Update the resolution algorithm to note that references may be version specific.

      n.b. Committee does not endorse any particular pattern for handling conditions

      Show
      There are valid use cases for including multiple versions of a resource. Remove the rules barring multiple versions, and document the potential risk around unversioned references (e.g. if you have an unversioned reference to a resource where multiple versions exist in the bundle - that is ambiguous). Also document limitations around transactions make server obligations and functionality clear. Document that Provenance tracking may necessitate multiple versions in a bundle. Update the resolution algorithm to note that references may be version specific. n.b. Committee does not endorse any particular pattern for handling conditions
    • Chris Grenz / Christiaan Knaap: 11-0-1
    • Correction
    • Compatible, substantive
    • STU3

      Comment:

      If a document can't have duplicates, how can a document handle statements where the version matters? E.g. where the admission condition says one thing and the discharge condition says something else but they both point to the same Condition record - which evolved over the course of the encounter? Same issue holds for .

      Summary:

      Why no duplicates in Document or message

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: