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

Add instantiates, basedOn and encounter to AuditEvent and Provenance

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • Security
    • AuditEvent
      Provenance
    • Hide

      add to Provenance and AuditEvent - basedOn and encounter elements following the Event pattern, and define search parameters for both

      Place them after activity and before agent

      • baseOn 0..* Reference(Request) - workflow authorization which this event occurred
        • Allows tracing of authorization for the events and tracking whether proposals/recommendations were acted upon.
      • encounter 0..1 Reference(Encounter) - Encounter within which this event occurred or which the event is tightly associated.
        • This will typically be the encounter the event occurred, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission lab tests).
      Show
      add to Provenance and AuditEvent - basedOn and encounter elements following the Event pattern, and define search parameters for both Place them after activity and before agent baseOn 0..* Reference(Request) - workflow authorization which this event occurred Allows tracing of authorization for the events and tracking whether proposals/recommendations were acted upon. encounter 0..1 Reference(Encounter) - Encounter within which this event occurred or which the event is tightly associated. This will typically be the encounter the event occurred, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission lab tests).
    • Jose Costa Teixeira / Carie Hammond: 7-0-3
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      Proposal comes from the FHIR workflow project.

      We want to be able to search on all events (creates, updates, deletes, etc.) that happened during a given encounter, that happened based on a particular protocol or as a result of a particular order.  These should be exposed in the same way as they are on the Event and Request patterns (so instantiatesCanonical, instantiatesUri, basedOn and encounter).  Explicit search parameters should be created for them as well, also following the patterns.  We feel that 'encounter' should be part of core.  The other two could be core or extensions.  Note that these elements should NOT be reflected using Entity as this would create different representation in these two resources.

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: