Stream: implementers
Topic: Condition Onset/Abatement
Stephen Royce (Jul 29 2016 at 05:46):
In our current logical model for Problem/Diagnosis (Condition) we have 2 elements for onset: Date of Onset and Age at Onset; and 2 element for abatement: Date of Resolution/Remission and Age at Resolution/Remission. These are separate, optional elements, so, in theory you could have both date and age for onset, and date and age for abatement. The Condition resource allows for just 1 of each. I don't think it was ever our intention that a system would send both date and age for either onset or abatement, but I have to ask: can anyone think of a use case where having both would be important?
Jeffrey Chen (Jul 29 2016 at 07:45):
If you have the date already, then age should be a calculated value. Why do you want to save two piece of information and one could be incorrect?
Stephen Royce (Jul 31 2016 at 22:25):
I don't think we do, but our current logical model technically allows it. I'm pretty sure that it was never our intention that you would ever actually use both at the same time, but it's not documented (
), so now I have to make double sure that no use case for both exists. 
Last updated: Apr 12 2022 at 19:14 UTC
