AU Core Encounter: Encounter.period should be optional
dt-r opened this issue · comments
Why have we made period mandatory whereas US Core hasn't? This will limit the use of core encounter when the period isn't known.
Originally posted by @gonatf in #30 and moved by @dbojicic to #62 (comment)
Responses to #62 (comment)
dt-r on Nov 30, 2023
One of the main sources for the currently baseline of AU Core for community engagement comes from event-driven patient summary implementation guides like Discharge Summary. I expect that to be the source of this cardinality.
Can you describe your use of encounter information and the need to support encounter but without an encounter period?
gonatf on Nov 30, 2023
Given both start and end are optional in period, I guess including a period with no start/end makes it all a bit strange to be mandatory. My use case is things like creating a request within an encounter that hasn't ended or not knowing the when a previous encounter occurred but knwoing something that resulted from it or is linked to it.
For TDG consideration - Encounter.period changed from 1..1 to be 0..1.
HL7 Jira is now used for specification feedback. This issue has been moved to HL7 Jira issue #FHIR-43832.