Add guidance for how content can be identified as having same source - 2018-Jan Core #194

XMLWordPrintableJSON

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

      Will add a discussion of this issue to Managing Resource Identity. Will include talking about both shared identifiers as well as use of Provenance and when each is appropriate. Will include a link to this from resource versioning, Identifier, logical references & provenance.

      Show
      Will add a discussion of this issue to Managing Resource Identity. Will include talking about both shared identifiers as well as use of Provenance and when each is appropriate. Will include a link to this from resource versioning, Identifier, logical references & provenance.
    • Grahame Greive/Louis Bedor: 6-0-0
    • Clarification
    • Non-substantive
    • STU3

      Proposed Wording: Where the same source data can be represented in multiple ways, provide clear guidance on how they should be identified as coming from the same source data. For example, medication orders can be represented as MedicationRequest and MedicationStatement. Because each can carry somewhat different information, in practice we have to pull both. To figure out which MedicationRequests match with which MedicationStatements, we have to do attribute-level comparisons and hope we got the duplicates identified. This would be much easier and more reliable if there was clear guidance on how to identify resources coming from the same data – e.g., use of the same order ID.

      Summary:

      Add guidance for how content can be identified as having same source

            Assignee:
            Unassigned
            Reporter:
            Kensaku Kawamoto
            Kensaku Kawamoto
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: