New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mother to baby and father to baby link - specify which concept to use #38
Comments
Discussed briefly in WG-1 today. Will add snomed codes to the propsal. biological father verified by DNA vs. father by self proclamation - was discussed and thought to be overengineering it. |
I updated the issue with 2 specific codes to use for mother and father |
Hi @vojtechhuser -- in the MotherChildLinkage package which we use at Janssen, we utilize the following query to populate the results into the fact_relationship table:
For mother-child linkages, the above query will use "Person" as the domain concept Id, "Mother of subject" as the relationship concept Id for the moms, "Child of subject" for the kids. We haven't developed father-child linkages yet, but I imagine the SNOMED concept 40478917 ("Father of subject") would be the concept for dads. |
below terms for mother and father do not specifically say 'biological'. http://athena.ohdsi.org/search-terms/terms/40478925 (mother) |
I am making a comment to US Interoperability Standards Advisory (from ONC) to point to this. |
first post was edited to have clearer solution text |
discussed. and advanced to next stage. |
no alterations were raised by the community. Can we decide step 8A or 8B. |
Closing this issue. It is now with the Vocabulary team. |
ITEM: see title
FORUM POST: see below
SOLUTION:
only convention for mother, father is the main scope of this themis proposal. First two conventions. One additional convention tries to guide (to as specifically) other biological relationships.
use concept 4277283 to represent personA is biological mother of personB (in column relationship_concept_id). Use concept 4321888 to represent personC is biological father of personB. Prioritize mother or father relationship (if known) and try to avoid only saying biological parent. Only if parent gender is not known, use 'biological parent' (concept 4029630). Use of biological parent (and not mother or father) triggers a heel data quality notification).
If person A has a recorded biological relationship to person person B (e.g., mother, father, parent), always represent the reverse relationship as well (daughter, son, child). Prioritize biological son (4014096) /biological daughter (4308126) based on sex at birth. Only if child gender is not know, use biological child (4326600). Lack of reverse relationship triggers data quality error. Use of less preferred 'biological child' concept triggers data quality notification.
If you have other biological relationship in source data, use concepts that are descendants of concept_id 4054070 (relative). This convention does not prevent representing other non-biological relationships between persons. The goal of this convention is to restrict the value set of concepts for "encouraged" biological relationships. (heel notification not possible here; no way to distinguish it is biological statement)
see concept_ids discussion below. In your comment, indicate concepts you like the most
NEXT STEPS: add conventions in SOLUTION
HEEL: DQ notification if parent concept id is used (not mother or father)
Current specs do not prescribe specific vocabulary concept to use when linking persons in FACT_RELATIONSHIP
Goal: recommend specific concept for column relationship_concept_id.
Use natural father and natural mother from this parent concept of natural parent
http://athena.ohdsi.org/search-terms/terms/4029630
(reverse relationship is natural child)
http://athena.ohdsi.org/search-terms/terms/4326600
links to forum
http://forums.ohdsi.org/t/voijtechs-question-conventions-for-iological-relationships-in-fact-relationship-table/158
http://forums.ohdsi.org/t/mother-father-and-baby-link/1044
The gap in specs is here
https://github.com/OHDSI/CommonDataModel/wiki/FACT_RELATIONSHIP#conventions
I want to write a Data Quality notification in Achilles but for that it needs to tighter specified.
The text was updated successfully, but these errors were encountered: