Skip to content
This repository has been archived by the owner on Jul 4, 2023. It is now read-only.

Conditions for "unanswered" questions should not be generated #13

Open
noemide opened this issue Jan 28, 2021 · 6 comments
Open

Conditions for "unanswered" questions should not be generated #13

noemide opened this issue Jan 28, 2021 · 6 comments
Assignees
Labels
coordination-necessary Further information/coordination is requested

Comments

@noemide
Copy link

noemide commented Jan 28, 2021

Describe the bug
Currently, if questions about the presence of a condition (e.g. chronic lung diseases) are not answered at all, it is still exported without any verification status. Since those conditions are typically interpreted as being present, this leads to false information being exported.

To Reproduce
Export empty for unaswered questions about preexisting Conditions.

Expected behavior
For unanswered questions, no Conditions should be exported.

@makampf

@cerbelding
Copy link
Member

Thank you for your report. I will have a closer look and come back to you.

@holger-stenzhorn
Copy link
Collaborator

@noemide Actually, I had a quite similar question this very morning which I posted on Zulip (https://chat.fhir.org/#narrow/stream/179183-german-%28d-a-ch%29/topic/GECCO-Datensatz/near/224294828) but have not received an answer yet...

@makampf
Copy link

makampf commented Jan 28, 2021

I do not get the differentiation between unknown and not answered.

Why not assuming any unanswered field as unknown, and why not exclusively exporting only known answers like yes/no?

@holger-stenzhorn
Copy link
Collaborator

@makampf Well, technically, if you do not answer a question at all then you do not provide any information but if you answer that you do not know then you provide at least that information... 🙂 How relevant this is in the end and how this should be "modeled" in FHIR is another question. 🤷‍♂️

@cerbelding
Copy link
Member

cerbelding commented Jan 28, 2021

The CodeSystem DataAbsentReason describes the differences. (and also possible different codings)
As @holger-stenzhorn already said, the relevance is indeed questionable.

@cerbelding cerbelding added the coordination-necessary Further information/coordination is requested label Jan 28, 2021
@makampf
Copy link

makampf commented Jan 28, 2021

I wondered about the relevance in cohort identification an thats actually different level of questionable relevance :D

@cerbelding cerbelding self-assigned this Jan 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
coordination-necessary Further information/coordination is requested
Projects
None yet
Development

No branches or pull requests

4 participants