You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
With reference to the discussion thread in #89, we want to ensure multiple namespaces aren't created for the same use case.
Currently, Forte-Medicine has its own medical oriented ontology (ftx.medicine.clinical). Forte-wrappers, too works with a couple of ontology classes like MedicalEntityMention and UMLSConceptLink, but uses these from Forte (ftx.onto.clinical). These are used solely in the SpacyProcessor wrapper to work with umls_link flag. Hence, we need to modify SpacyProcessor in a way that it can use dynamically provided ontologies instead of having a hard dependency on Forte for medical related ontologies. This would ensure consistent package namespacing for all medical use cases going forward, especially as Forte-Medical grows.
The text was updated successfully, but these errors were encountered:
Describe the bug
With reference to the discussion thread in #89, we want to ensure multiple namespaces aren't created for the same use case.
Currently, Forte-Medicine has its own medical oriented ontology (
ftx.medicine.clinical
). Forte-wrappers, too works with a couple of ontology classes likeMedicalEntityMention
andUMLSConceptLink
, but uses these from Forte (ftx.onto.clinical
). These are used solely in theSpacyProcessor
wrapper to work withumls_link
flag. Hence, we need to modifySpacyProcessor
in a way that it can use dynamically provided ontologies instead of having a hard dependency on Forte for medical related ontologies. This would ensure consistent package namespacing for all medical use cases going forward, especially as Forte-Medical grows.The text was updated successfully, but these errors were encountered: