FHIR should look to use the same attribution patten in every resource - 2018-Jan Core #214

XMLWordPrintableJSON

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

      Inclusion of data elements is based on "what do most systems do". Not all attribution elements are relevant (or at least commonly supported) for all resources. Nor are the same types, cardinalities or sometimes even names the same. We have instituted the use of patterns (Fivews, Definition, Request and Event) to try to drive additional consistency where implementer need does not drive divergence (and are tightening expectations for conscious divergence rather than spontaneous non-alignment). As well, mappings to patterns should aid those who desire a review of the resources that provides greater consistency.

      If you have thoughts on how to make these patterns and their mappings more useful for your use-case, feedback is welcome.

      Show
      Inclusion of data elements is based on "what do most systems do". Not all attribution elements are relevant (or at least commonly supported) for all resources. Nor are the same types, cardinalities or sometimes even names the same. We have instituted the use of patterns (Fivews, Definition, Request and Event) to try to drive additional consistency where implementer need does not drive divergence (and are tightening expectations for conscious divergence rather than spontaneous non-alignment). As well, mappings to patterns should aid those who desire a review of the resources that provides greater consistency. If you have thoughts on how to make these patterns and their mappings more useful for your use-case, feedback is welcome.
    • Grahame Grieve/Ron Shapiro: 3-0-0
    • Enhancement

      Comment:

      Many or all entries in a health record share the same set of attribution attributes (author, recorder, verifier, etc.). FHIR is all over the map in terms of how attributions are represented across resources. FHIR should look to use the same attribution patten in every resource.

      Summary:

      FHIR should look to use the same attribution patten in every resource

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

              Created:
              Updated:
              Resolved: