Stream: implementers
Topic: Risk factors
Jose Costa Teixeira (Dec 22 2020 at 19:14):
What to use for risk factors like "obesity", "smoker",...?
David Pyke (Dec 22 2020 at 19:14):
Those tend to be observations
Jose Costa Teixeira (Dec 22 2020 at 19:15):
I'm inclined for that as well, just wanted to hear more opinions
David Pyke (Dec 22 2020 at 19:17):
More detail on the use case might get you better opinions
Jose Costa Teixeira (Dec 22 2020 at 19:17):
(thanks)
Jose Costa Teixeira (Dec 22 2020 at 19:18):
that is it, actually: "Obesity" may be a basis for a higher risk of diabetes, cancer, etc. but I want to capture the obesity part
Lloyd McKenzie (Dec 22 2020 at 19:58):
Could also be Condition - if it's something that you're tracking over time.
Jose Costa Teixeira (Dec 22 2020 at 21:07):
But some factors may not be Conditions - e.g. " sex worker", "homeless", ..
Lloyd McKenzie (Dec 22 2020 at 21:11):
Homeless is a Condition. Sex worker could theoretically be a Condition I suppose. Might be more common as we start tracking social determinants of health better.
Richard Townley-O'Neill (Dec 23 2020 at 02:02):
Would stone mason be a condition? It is associated with high rates of silicosis.
Lloyd McKenzie (Dec 23 2020 at 02:26):
Hard to say. @Michelle (Moseman) Miller - thoughts on how this sort of thing would typically manifest in the record?
Michelle (Moseman) Miller (Jan 06 2021 at 22:11):
I agree with Lloyd's earlier comments that Condition can be used for anything that rises to a level of concern or situations that may require ongoing monitoring and/or management per http://build.fhir.org/condition.html#scope.
Risks (such as risk of silicosis) could be considered a condition as well. Risks are used as examples in the condition scope as well as in http://build.fhir.org/condition.html#9.2.4.3 where it says
It can also be used to capture "risk of" and "fear of", in addition to physical conditions, as well as "no known problems" or "negated" conditions
Jose Costa Teixeira (Jan 06 2021 at 23:56):
I understand "at risk of silicosis" as a condition, but "stone mason"..?
Lloyd McKenzie (Jan 07 2021 at 03:03):
But would you bother to capture "stone mason" if you weren't interested in it from the perspective of the risk? I doubt very much EHRs would capture "Healthcare IT Architect" in their problem list either :)
Jose Costa Teixeira (Jan 07 2021 at 06:58):
Right. We can express the risks known at a given time, but that is different from risk factors/causes.
Jose Costa Teixeira (Jan 07 2021 at 07:03):
"Healthcare IT Architect" is different from
"Healthcare IT Architect - at risk of burnout" i.e. "Risk of burnout because profession is Healthcare IT Architect"
Jose Costa Teixeira (Jan 07 2021 at 07:07):
(replace burnout by any ICD-10 F30 to F69)
Craig Newman (Jan 07 2021 at 13:33):
the Occupational Data for Health IG contains Observation profiles for past and present job and industry. I suspect that is how "stone mason" would be captured. There still may be a Condition for exposure to workplace substances, but the job itself I suspect should be an Observation
Jose Costa Teixeira (Jan 08 2021 at 22:41):
If "Patient is transgender" is intended to indicate risk factor, is it still a condition?
Lloyd McKenzie (Jan 08 2021 at 22:58):
It's certainly a condition, though it might not always be represented that way. It might also be captured as an Observation and/or a Flag (though a Flag should always have an underlying resource with the details
Jose Costa Teixeira (Jan 08 2021 at 23:19):
great, thanks. What about "patient got infected because of exchanging of syringes"? It is slightly related to the risk, but it is more about the Condition, right?
Lloyd McKenzie (Jan 09 2021 at 03:00):
Use this: https://build.fhir.org/extension-condition-dueto.html - most likely just specifying a code.
Last updated: Apr 12 2022 at 19:14 UTC
