4 ms·
Snomed CT Entity Linking Challenge
- westurner 3y ago> The objective of this competition is to link spans of text in clinical notes with specific topics in the SNOMED CT clinical terminology. Participants will train models based on real-world doctor's notes which have been de-identified and annotated with SNOMED CT concepts by medically trained professionals. This is the largest publicly available dataset of labelled clinical notes, and you can be one of the first to use it! NER: Named Entity Recognition: https://en.wikipedia.org/wiki/Named-entity_recognition https://en.wikipedia.org/wiki/Named-entity_recognition awsome-medical-coding-nlp: https://github.com/acadTags/Awesome-medical-coding-NLP https://github.com/acadTags/Awesome-medical-coding-NLP awesome-ehr-deep-learning: https://github.com/hurcy/awesome-ehr-deeplearning https://github.com/hurcy/awesome-ehr-deeplearning awesome-ner: https://github.com/smiyawaki0820/awesome-ner https://github.com/smiyawaki0820/awesome-ner awesome-bioie > Research groups: https://github.com/caufieldjh/awesome-bioie#groups-active-in-the-field https://github.com/caufieldjh/awesome-bioie#groups-active-in... SNOMED-CT as RDF: https://sphn-semantic-framework.readthedocs.io/en/latest/external_resources/snomed-ct.html#snomed-ct https://sphn-semantic-framework.readthedocs.io/en/latest/ext... ... SNOMED-CT is a Medical Terminology. SNOMED-CT: https://en.wikipedia.org/wiki/SNOMED_CT https://en.wikipedia.org/wiki/SNOMED_CT Traditionally, a Terminology Service provides a query endpoint over a schema like SNOMED-CT (which is a nonredistributable medical XML schema, which is challenging for Open Linked Data): https://github.com/NCIP/lexevs https://github.com/NCIP/lexevs https://github.com/OpenConceptLab https://github.com/OpenConceptLab https://openconceptlab.org/terminology-service/ https://openconceptlab.org/terminology-service/ https://github.com/MedevaKnowledgeSystems/pymedtermino/blob/master/doc/tuto_en.rst https://github.com/MedevaKnowledgeSystems/pymedtermino/blob/... : > For SNOMED CT, ICD10 and MedDRA, the data are not included (because they are not freely redistribuable) but they can be downloaded in XML format. PyMedTermino includes scripts for exporting these data into SQLite3 databases.
- westurner 3y agoTangentially, but also to the point, Software Development IDEs have (optional) autocomplete; Unstructured Medical Coding interfaces could also have autocomplete, such that when you type `icd:` or `snomed:` it presents a search interface for that particular medical terminology / vocabulary / system of classification / categories. GNU Health > Issue tracker > "Freetext ICD-10 references as URIs (e.g. icd10:A01)" (2013) https://lists.gnu.org/archive/html/health-dev/2013-12/msg00003.html https://lists.gnu.org/archive/html/health-dev/2013-12/msg000...
- nradov 3y agoI'm not convinced that auto complete would add much value to clinical workflows. Clinicians typically don't enter the codes themselves. In order to write those unstructured narrative blocks they might type them in manually, fill in the blanks on a template, or dictate. But in any case the clinician typically isn't entering billing or clinical codes. Usually certified medical coders add codes afterwards using specialized interfaces, often with some kind of NLP assistance.
- westurner 3y agoYeah, so it's at that workflow where they're not getting linked data edges out of their own unstructured data input. To prompt them at that time for whether or not this referenced thing in a dictated .txt file is actually a thing with a URI and have them confirm that those are the correct annotations for their input would save a lot of time and money. Requisite study for Linked Data clinical coding / informatics: - HIPAA and unstructured notes, HIPAA and Linked Data; Informed Consent; Precision Medicine - Tokens; NLP, stemming, conceptual entity recognition - The LODcloud; a great big graph of Linked Open Data (that our data does not yet link to, is siloed separately from, does not yet have references to existing URIs in) - RDFa: RDF-in-html-Attributes - JSON-LD: JSON Linked Data - Schema.org/MedicalEntity ; /docs/schemas.html -> "Health and medical types" https://schema.org/docs/meddocs.html https://schema.org/docs/meddocs.html - TTS Text-to-Speech, Speech-to-Text; Multimodal models with RAG, LORA, RLHF, Transformer Self Attention tensor Networks, Benchmarking OpenAI Whisper with relative performance metrics, ONNX - FHIR for EHR data portability (JSON-LD,) UX Improvements: - More IDE-like unstructured data entry - Auto-annotate this text field in place - Auto-annotate this pasted text - Auto-annotate this text field and display the linked data annotations - Display the revisions of the unstructured note -> annotated linked data document - Autocomplete with search from e.g. icd: - Frequently used annotations per Clinician/Provider - Recently used annotations per Clinician/Provider - Hover over visually distinguished auto-recognized entities and approve/clarify/reject - Indicate which prov:Agent added which annotations; human (name(s)), AI (signed git revision of repo URI) - Indicate degree of confidence in annotation (note that AGI hypergraph systems have TruthValue and also AttentionValue, like attention networks; and that AGI systems may someday also support CDSS: Clinical Decision Support Systems and Health Decision Support Systems)