Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
FHIR Core (FHIR)
-
R4
-
Patient Administration
-
Encounter
-
-
Brian Postlethwaite / Reinhard Egelkraut : 7-0-0
-
Enhancement
-
Non-compatible
-
R5
Description
It's not clear whether it's legitimate to specify a "forecast" end date for an encounter as the Encounter.period.end or not, nor is it clear how to distinguish an estimated end date from an actual end date given that there's no date on the Encounter that says when it was last changed. (_lastUpdated is a technical date and wouldn't necessarily imply that 'estimated' end had been replaced with 'actual' end.)
Attachments
Issue Links
- relates to
-
FHIR-44805 Encounter plannedStart and plannedEndData are better represented by a Period
- Resolved - No Change
-
FHIR-22766 Encounter.period needs to allow flagging admission/discharge dates as "planned"
- Published