Combine collection types - 2018-Jan Core #216

XMLWordPrintableJSON

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

      Each collection serves very different purposes. And each is differentiated in the Scope section of the resource. We have not encountered any issues thus far with interoperability issues caused by different choices of resource - the nature of the resource generally makes the choice obvious and in the few cases where multiple resources could theoretically be used, the guidance text has been sufficient to ensure the correct selection is made.

      More work will be done on explaining the relationship between Composition.section and List.entry and DiagnosticReport.

      Show
      Each collection serves very different purposes. And each is differentiated in the Scope section of the resource. We have not encountered any issues thus far with interoperability issues caused by different choices of resource - the nature of the resource generally makes the choice obvious and in the few cases where multiple resources could theoretically be used, the guidance text has been sufficient to ensure the correct selection is made. More work will be done on explaining the relationship between Composition.section and List.entry and DiagnosticReport.
    • Grahame Grieve/Ron Shapiro: 3-0-0
    • Correction
    • Non-substantive
    • STU3

      Comment:

      FHIR has many resources that represent collections of resources including Composition, Document, Bundle, List, DiagnosticReport, Questionnaire. This is an extremely confusing situation that begs to be simplified. As it stands, there will be huge variation in the way these resources are used to represent the same real-world situation. Example: Build a catalogue - a document that has many entries of similar type. There are simply too many options.

      Summary:

      Combine collection types

            Assignee:
            Unassigned
            Reporter:
            Mark Kramer
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: