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

Observation.encounter should be context and support EpisodeOfcare

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Orders & Observations
    • Observation
    • Hide

      We will update the short display text of Observation.encounter to read "If you need to place the observation within one or more episodes of care, use the workflow-episodeOfCare extension."

      Show
      We will update the short display text of Observation.encounter to read "If you need to place the observation within one or more episodes of care, use the workflow-episodeOfCare extension."
    • Marti Velezis / Dan Rutz : 18 - 0 - 0
    • Clarification
    • Non-substantive
    • R6

    Description

      FHIR#17901 was snuck in before Observation, moving EpisodeOfCare to an extension, and renaming Observation.context to Observation.encounter.

       

      That tracker (or related set of trackers) spawned FHIR#19513 for PA to update some of our resources (specifically, ChargeItem) to align with the pattern in Observation.

      We (PA) are going to reject that proposal, and keep ChargeItem.context (Encounter | EpisodeOfCare).  However, when looking at the issue history, the change in FHIR#17901 (also discussed in this chat.fhir topic) seemed odd.

       

      The 2021 Argo Write project is working on an IG to support patients writing data to EHRs.  This would be items like steps, or vitals collected at home.  This data fits directly into Observations that have no encounter, but may have an EpisodeOfCare.

       

      We think O&O should revisit the Observation.encounter/context change.  I get that Observation is normative, but as I've said on chat.fhir, at some point we (FHIR) will need to figure out how to make normative updates...

       

       

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            cooper.thompson Cooper Thompson
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: