Why do encounters point to episoide of care instead of episode of care pointng to encounter

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Administration
    • Encounter
      EpisodeOfCare
    • Hide

      Resources typically point to the thing that exists first, in this case the EpisodeOfCare is on-going and therefore created first.

      Encounters are created, which point to the existing episode. You don't want to have to update the episode every time a new encounter is created.

      In a case where an Encounter is in progress, and a new EpisodeOfCare is identified, then this will be saved and the encounter recorded against this, as will all future encounters.

      (If the link was the other way, every time a new encounter is created, the EpisodeOfCare would need to be updated too)

      Show
      Resources typically point to the thing that exists first, in this case the EpisodeOfCare is on-going and therefore created first. Encounters are created, which point to the existing episode. You don't want to have to update the episode every time a new encounter is created. In a case where an Encounter is in progress, and a new EpisodeOfCare is identified, then this will be saved and the encounter recorded against this, as will all future encounters. (If the link was the other way, every time a new encounter is created, the EpisodeOfCare would need to be updated too)
    • Brian Postlethwaite/Peter Bernhardt: 4-0-0
    • Clarification

      Why do encounters point to episoide of care instead of episode of care pointng to encounter

      "The primary difference between the EpisodeOfCare and the Encounter is that the Encounter records the details of an activity directly relating to the patient, while the *EpisodeOfCare is the container *that can link a series of Encounters together for problems/issues."

      Container to me implies that this resource is pointing to 1 or more other resources. See how is used when defining "contained resources""* Internal "contained references" "references* - references to other resources packaged inside the source resource"

      I Propose either changing the language to "... a series of Encounters together for problems/issues are related to each other by there common link to an Episode of care. (search episode with a reverse include to list them all)

      or..

      keep the text and reverse the linkage make the encounter the leaf node.

            Assignee:
            Unassigned
            Reporter:
            Eric Haas
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: