Skip to content
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

IRI patterns on the mapping tool and Variables in the DTS #22

Open
Wenjie225 opened this issue Feb 8, 2024 · 0 comments
Open

IRI patterns on the mapping tool and Variables in the DTS #22

Wenjie225 opened this issue Feb 8, 2024 · 0 comments

Comments

@Wenjie225
Copy link
Collaborator

For UM's data (breast cancer case), we could have the same IRI pattern (source) for multiple nodes depending on the variables in DTS. To some extent, it shows the difficulty to link some variables from DTS to current classes in SPHN schema.

Example: In discharge summary (UM's data), we only have variable names called "ALLERGIES_TYPE" and "ALLERGIES_DATE" for allergy information, while in the SPHN schema, there are classes such as "Allergy", "Allergen", and "Allergy Episode". We added a data node called "Allergy", linked it to the "ALLERGIES_TYPE" at first. But when we added a connection "has allergen" and tried to link it to a new data node called "Allergy type", we needed to type in the same IRI pattern as in the node "Allergy". Then we created another connection between "Allergy type" and a new node "Food allergy" to show the exact allergy type, with the same IRI pattern as in "Allergy".

Finally when we tried to complete the mapping, the system showed an error: "Multiple sources on Value field found"

So in this case, will there be any effect on the further knowledge graph when we use the same IRI pattern (source) for several data nodes? If so, we may have to consider solving this by either adjusting variables in DTS to make it more compatible with the current ontology, or extending/changing classes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant