FHIR Chat · Symptoms · implementers

Stream: implementers

Topic: Symptoms


view this post on Zulip Grahame Grieve (Aug 07 2018 at 22:57):

http://community.fhir.org/t/right-resource-field-for-symptoms/919 - not sure what we should do about the inconsistency, nor do I know the answer to the question?

view this post on Zulip Richard Townley-O'Neill (Aug 07 2018 at 23:30):

Are symptoms like head ache patient reported observations?

view this post on Zulip Richard Townley-O'Neill (Aug 07 2018 at 23:30):

Fever in a child could be a carer reported observation.

view this post on Zulip Lloyd McKenzie (Aug 07 2018 at 23:59):

@Michelle M Miller @Eric Haas Care to take a stab? :)

view this post on Zulip Abbie Watson (Aug 08 2018 at 00:57):

I've wondered about this as well (for maybe obvious reasons, considering). Should also add ClinicalImpression (possibly self-reported) to the mix of possible approaches.

view this post on Zulip Abbie Watson (Aug 08 2018 at 04:08):

Actually... after mulling on this for 6+ months, and considering that ClinicalImpression is still Maturity level 0, I think I'll take the position that we ought to change ClinicalImpression.investigation to ClinicalImpression.symptom. 'Investigation' is nicely congruent with Observation and the scientific method; but 'symptom' is more relevant to clinical workflow.

Also, there's a typo in the spec..."One or more sets of investigations (signs, symptions, etc.)". :)

view this post on Zulip Michelle (Moseman) Miller (Aug 08 2018 at 12:51):

@Grahame Grieve , @Lloyd McKenzie I will respond. PC attempted to clarify this as a result of GF#8872 and GF#15970, which led to http://build.fhir.org/condition.html#bnr. As an implementer, I agree that symptoms can appear in both resources -- and I don't think FHIR can change that reality.

view this post on Zulip Eric Haas (Aug 08 2018 at 16:35):

in OO we actually acknowledge this overlap in our example for findings right up front in the scope and usage section as well as in the boundaries.


Last updated: Apr 12 2022 at 19:14 UTC