Combine collection types - 2018-Jan Core #51

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Modeling & Methodology
    • (methodology)
    • Hide

      Each resource behaves very differently. Bundle is a technical packaging structure used when there's a need to send multiple resources at once. It's an infrastructure resource. Group is an entity that can be acted upon or observed (herd of cows, cage of mice, females between 40 and 50, Practice Group 5). Group can also be defined intentionally while List cannot. List is a currated collection of clinical items. Every resource has a scope section that clearly differentiates its usage. Each resource serves a different purpose and manifests in applications differently. All are needed.

      This is all clearly documented in the Boundaries and Relationships section of the resources. If you feel the text in this section is insufficient/unclear, please propose specific changes.

      Show
      Each resource behaves very differently. Bundle is a technical packaging structure used when there's a need to send multiple resources at once. It's an infrastructure resource. Group is an entity that can be acted upon or observed (herd of cows, cage of mice, females between 40 and 50, Practice Group 5). Group can also be defined intentionally while List cannot. List is a currated collection of clinical items. Every resource has a scope section that clearly differentiates its usage. Each resource serves a different purpose and manifests in applications differently. All are needed. This is all clearly documented in the Boundaries and Relationships section of the resources. If you feel the text in this section is insufficient/unclear, please propose specific changes.
    • Grahame Grieve/Ron Shapiro: 3-0-0
    • Clarification

      Comment:

      FHIR can represent collections as either Group, List, or Bundle. The three resources look quite similar in structure and also resemble Composition (they are composed of entries though perhaps make no use of sections). At times it is not clear which resource to use for what. Should the result of a query return Bundle or List? Should a catalog of services be expressed using Composition or List? Why could a group of entities not be represented as a list rather than as a Group? Much like the previous comment, perhaps collections should take a more compositional approach (i.e., the choice of metadata structure and entry type define the type of collection one wishes to represent) and be based on the same underlying structure (perhaps Composition). It might even be the case that compositions are special types of collections or collections are simple compositions.

      Summary:

      Combine collection types

            Assignee:
            Unassigned
            Reporter:
            Claude Nanjo (Inactive)
            Claude Nanjo (Inactive)
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: