| Keynote Presentations | |
|---|---|
| Evolution, survival, revolution and growth: An everyday story of terminology folk | |
| Improving the health care system with eHealth – the Swedish case | |
| Resources to Support Implementers | |
| Documentation and Resources to Support SNOMED CT Implementation | |
| Review of training and other related materials for the Implementation of SNOMED CT | |
| Practical Use Cases | |
| A UMLS and SNOMED CT-encoded differential diagnosis time-series knowledge base for self-administered patient interviews | |
| Implementation of SNOMED CT in Quality Measures | |
| Strategies to Improve Problem List Management within Clinical EHR Workflow | |
| European Projects | |
| epSOS make sense of Cross border Health care | |
| SNOMED CT mapping in the epSOS project | |
| Semantic Interoperability for Health Network (SemanticHealthNet) | |
| Clinical Specialties | |
| A SNOMED CT linked diagnosis coding scheme for European Renal Medicine | |
| SNOMED CT in Anatomic Pathology | |
| Laboratory Medicine | |
| Meeting terminology requirements for order entry and result reporting | |
| UK National Laboratory Medicine Catalogue | |
| Canadian Experience Supporting the Implementation of SNOMED CT for the Reporting of Microbiology Laboratory Result Values | |
| Browsers and Searching | |
| Searching SNOMED CT | |
| Terminology Explorer | |
| Terminology Services | |
| SNOMED CT and Common Terminology Services (CTS2) | |
| Our experience developing a terminology server | |
| Data Entry | |
| Using SNOMED CT to code free text in the clinical interface | |
| Freedom of Clinical Expression versus Record Standardization - Having Your Cake and Eating It | |
| EHR Design | |
| An integrated Expression Repository EHR system | |
| Terminology Binding | |
| The Logical Model Designer - Binding Information Models to Terminology | |
| Implementing post-coordinated SNOMED CT bindings using an interface terminology in clinical data capture forms | |
| Retrieval and Queries | |
| Semantic Query | |
| Leveraging SNOMED CT in Healthcare Analytics | |
| Decision Support | |
| Clinical Decision Support Using openEHR Archetypes and SNOMED CT | |
| Development of a SNOMED CT based, national, centralized medication decision support system | |
| Interoperability | |
| Planning for adoption of SNOMED CT in a Health Information Exchange | |
| Mapping to Classifications | |
| How the SNOMED CT to ICD-10 Map facilitated the map to a national extension of ICD-10 | |
| Transitioning from an IHTSDO SNOMED CT to ICD-10 Mapping Project to the IHTSDO Mapping Service | |
| Progress report on the IHTSDO/Wonca Family/General Practice Refset and ICPC-2 mapping project | |
| Data Migration | |
| Mapping Legacy Terms to SNOMED CT - Challenges and Lessons Learned | |
| Mapping legacy termsets to SNOMED CT: Experiences and outcomes, tools and guidance | |
| Migrating post-coordinated SNOMED CT between systems: a case study converting a GE electronic health record to Epic | |
| Translation | |
| IHTSDO support for translation | |
| Content Development | |
| IHTSDO Content Development process - moving forwards | |
| Description Logic | |
| Semantic Annotations | |
| Negation, Disjunction and Union Set Enhancement for the IHTSDO Workbench | |
| Extension Management | |
| Using Snow Owl to Maintain Singapore's SNOMED CT Extension and Drug Dictionary | |
| Integrating SNOMED CT-AU and the Australian Medicines Terminology (AMT) | |
| Reference Sets | |
| Canadian Experience Developing Primary Care Reference Sets | |
| Education | |
| Introduction to SNOMED CT | |
| IHTSDO Quality Framework - sharing of practice across the community | |
| IHTSDO Workbench | |
| IHTSDO Workbench Managed Service | |
| IHTSDO Workbench Arena | |
| IHTSDO Workbench Utilities |
Overview
Content Tools
Apps