Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-20760

Workflow pattern for relevantHistory should be explained

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - change required (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive
    • Specification:
      FHIR Core (FHIR)
    • Raised in Version:
      STU3
    • Work Group:
      FHIR Infrastructure
    • Related Page(s):
      Workflow Module
    • Grouping:
    • Resolution Description:
      Hide

      FHIR-I will put together a section (a few paragraphs worth) and some examples that explain how .relevantHistory works - including what it looks like, its ability to draw on Provenance relevant to multiple resources and the reason for 'filtering' what Provenance is deemed "relevant". Will also explain the process by which relevantHistory gets created/updated.

      Will also look at how this pattern is being used in the event space (e.g. MedicationAdministration, MedicationDispense) and look at harmonization with Encounter and whether this should be in Event as well.

      Once the text is created we'll discuss w/ Security about where this should best live.

      Show
      FHIR-I will put together a section (a few paragraphs worth) and some examples that explain how .relevantHistory works - including what it looks like, its ability to draw on Provenance relevant to multiple resources and the reason for 'filtering' what Provenance is deemed "relevant". Will also explain the process by which relevantHistory gets created/updated. Will also look at how this pattern is being used in the event space (e.g. MedicationAdministration, MedicationDispense) and look at harmonization with Encounter and whether this should be in Event as well. Once the text is created we'll discuss w/ Security about where this should best live.
    • Resolution Vote:
      Jose Costa Teixeira/Victor Vaysman: 5-0-0
    • Change Category:
      Enhancement
    • Change Impact:
      Non-substantive

      Description

      The workflow .relevantHistory use of Provenance should be explained. This explaination should be on the workflow pages so as to explain proper use of the workflow pattern specified for .relevantHistory. This could point at the text that GF#20758 is looking to describe this on the Provenance page.

      See chat https://chat.fhir.org/#narrow/stream/179256-Orders-and.20Observation.20WG/topic/relevantHistory

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            john_moehrke John Moehrke
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Vote Date: