Observation – Family History of about themis HOT 15 CLOSED

@schuemie we basically used the same logic when creating this approach. On the other hand, we still want to keep precoordinated SNOMED concepts for two main reasons:

1. When we break down source concepts it occurs as a quite time-consuming task. Not all are prepared to that, especially taking into account that this time can be allocated to more important and clinically relevant mappings.
2. Usagi will map source concepts to the direct SNOMED counterparts, which will be useless and will need manual review; this again leads us to the first paragraph.

from themis.

@chandryou:

Not a good decision, but unless we fix the vocabulary and get SNOMED on board I am afraid that's what it is. Will bring it up with them as one of the issues.

from themis.

Could someone explain the rationale for this solution?

I can think of two reasons why we'd instead always want to use 4210989:

1. Consistency for all family history. As an application developer, that would make my life a lot easier. I can pull all family history in with one query.

2. Explicit link between the disease concept and the family history.

from themis.

Moving this conversation to the Wiki:
http://forums.ohdsi.org/t/how-to-represent-family-history/3386/7

from themis.

@aostropolets Have these mappings been created yet to the concept 4210989? Right now I still see V17.5 mapping to 4167217.

from themis.

I don't think that ICD9CM has been reviewed recently, so it will probably be done as a part of this review. Thanks for the reminder!

from themis.

Yeah, right now it's mapped to Family history
and maps to value to "Asthma".
Is it the final decision?
"If we have a matching concept in SNOMED, then use the respective observation_ concept_id. If we do NOT have a matching SNOMED code, then observation_concept_id should be ‘4210989 Family history with explicit context’ and value_as_concept_id should be the related procedure, condition etc."

from themis.

It is the final decision

from themis.

Good, thanks @aostropolets.
We'll change this

from themis.

ICD10 mappings are already done in this way:

"If we have a matching concept in SNOMED, then use the respective observation_ concept_id. If we do NOT have a matching SNOMED code, then observation_concept_id should be ‘4210989 Family history with explicit context’ and value_as_concept_id should be the related procedure, condition etc."

Waiting for release, just day or two.

ICD10CM and ICD9CM are in still the backlog.
The update takes time as we updating not only the links mentioned above, but reviewing the whole corpus of manual mappings

from themis.

Can someone summarize the final design with an example from ICD9CM and ICD10CM?

from themis.

V17.5 is a interesting - asthma hx became bicycle injury

from themis.

@vojtechhuser please, look at the diagram below to see the final mapping design of ICD concepts indicating a history:

Examples:

At the present time, we are implementing such a model toward all history-related ICD concepts to increase the number of equivalent mappings.
The current state is the following:

from themis.

It seems that we did have the final decision for this problem
"If we have a matching concept in SNOMED, then use the respective observation_ concept_id. If we do NOT have a matching SNOMED code, then observation_concept_id should be ‘4210989 Family history with explicit context’ and value_as_concept_id should be the related procedure, condition etc."

Is there anyone teach me why this issue is open now?

from themis.

Closing issue. Vocabulary has been updated.

from themis.