Type: Change Request
Status: Triaged (View Workflow)
Specification:FHIR Core (FHIR)
Raised in Version:STU3
Work Group:Patient Administration
In it's current state, Encounter has several issues:
- the history of state class and location, although changing in parallel most of the times are kept seperate, making it hard to see the "whole picture" of what has chanded
* the mechanisms of keeping history of class/status and location are different
* it is currently very difficult to add extensions that need tracking, as this would require multiple or complex entensions to keep both the current value as well as the history
We propose the following changes:
group all elements of Encounter that are time dependent/ may change multiple times during the course of an encounter into a backbone element with an id and a period
and add an element that keeps the history of the backbone element, e.g.\\"encounterHistory"
- encounterPhase 0..*
If in certain usecases only a specific subset of these elements need to be tracked or the elements need to be tracked individually, this could easily be achieved by slicing and constraining the encounterHistory
This would also make it easy for systems to decide whether they only care for the current phase of the encounter (which should be part of the summary) or if they want do process the full stack of historical phase-elements.