2015May core #556 - Why not avoid this problem by requiring contained resources to explicitly state their subject? Why allow this degree of optionality?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Modeling & Methodology
    • References
    • 1.13.0.1.1
    • Hide

      Change to not allow the functionality - say explicitly that contained resources do not inherit any values from their context because of the uncertainty that this introduces. Rewrite section 1.13.0.1.1 accordingly

      7366 & 7385 linked

      Show
      Change to not allow the functionality - say explicitly that contained resources do not inherit any values from their context because of the uncertainty that this introduces. Rewrite section 1.13.0.1.1 accordingly 7366 & 7385 linked
    • Josh Mandel / Ewout Kramer : 10-0-0
    • Clarification
    • Non-compatible
    • DSTU1 [deprecated]

      Existing Wording: However FHIR provides no mechanism for defining or constraining any conduction of "equivalent" properties from a containing resource into any contained resource - not even by declaring the use of a particular profile. Best practice is to explicitly include all known properties on contained resources, even if redundant with properties on the containing resource.

      Comment:

      Why not avoid this problem by requiring contained resources to explicitly state their subject? Why allow this degree of optionality?

            Assignee:
            Unassigned
            Reporter:
            david_tao
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: