We need the inference so that we can know equivalence between classes and subclass relationships (eg "type 2 diabetes" is still "diabetes" because it's is a subclass of diabetes).
Another dataset that I've never been able to get to load with any inference enabled is SNOMED CT. Even when removing all of the owl inference that they have in their dataset and pre-calculating the direct subclass relationships, not even the transitive reasoner will load the dataset (without modification at runtime) once the first query is submitted after startup of Fuseki. Granted it's it significantly larger than ICD-10 CM. But still, not being able to load it with even pre-calculated direct subclass relationships is a huge deal breaker. Not to mention the fact that the real power of that dataset comes when the owl inference built into it can actually be used. With it, inference on patient data can reveal potential diagnoses that would not be inferred without and owl reasoning. No PHI in Email: PointClickCare and Collective Medical, A PointClickCare Company, policies prohibit sending protected health information (PHI) by email, which may violate regulatory requirements. If sending PHI is necessary, please contact the sender for secure delivery instructions. Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
