Stream: united states
Topic: Condition.abatement[x]'s effect on validity
Eric Lehner (Mar 22 2021 at 19:47):
Reviewing the description of the Condition.abatement[x] property, there's a note in the comments that
If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid.
What does valid mean here? Is it related to clinicalStatus or verificationStatus in some way?
Lloyd McKenzie (Mar 22 2021 at 21:12):
I think it's saying "If no one's declared the Condition has abated, proceed on the assumption it might not have"
Lloyd McKenzie (Mar 22 2021 at 21:13):
Though of course, whether that makes sense or not will depend on the nature of the condition. A record of a broken arm from 5 years ago with no abatement recorded probably doesn't mean there's still a problem.
Eric Lehner (Mar 22 2021 at 21:23):
So would that mean in the case where clinicalStatus and abatement[x] aren't set, the condition is tentatively considered "active"? Or is the intent that these resources are understood as having an unknown status, but should be reviewed as they may still be relevant?
Lloyd McKenzie (Mar 22 2021 at 21:44):
I'd say the latter
Eric Haas (Mar 22 2021 at 22:23):
better to post this in #implementers since Condition.abatement is not part of a US Realm specific profile ( AFAIK) and a good question for the broader FHIR community.
Eric Lehner (Mar 24 2021 at 03:54):
That makes sense. I'll rewrite this question a little and move it over to that stream to get their thoughts as well
Last updated: Apr 12 2022 at 19:14 UTC
