Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Epic's electronic patient record systems use SNOMED CT as a reference terminology through the following mechanisms:
Mappings between a subset of Epic's standard data elements and SNOMED CT concepts;
Mappings between diagnoses imported from other code systems (e.g. those used in Intelligent Medical Object's and Health Language's products) and SNOMED CT concepts;
Mappings from additional data elements to SNOMED CT concepts that can be created by clients using an External Concept Mapping activity.
These mechanisms provide linking behind the scenes, so when clinicians add a diagnosis to the problem list by selecting a familiar term, for example, they automatically select the corresponding SNOMED CT concept. This SNOMED CT encoding creates powerful possibilities within Epic's decision support and reporting facilities.
The Epic system calls its decision support alerts 'Best Practice Advisories'. These customized alerts are programmed to fire according to predetermined triggers, such as specific chief complaints, vital signs, diagnoses or medications, either individually or in combination using inclusionary or exclusionary logic. Best Practice Advisories can thus be used to notify clinicians to tend to important tasks, such as reviewing a patient's allergies, writing orders, and completing charting. They can also present order sets and links to third party information sources refined using the clinical context of the patient record being reviewed.
Epic customers can use SNOMED CT's hierarchical structure to group related records, making the setup for clinical decision support much simpler than would be possible if users had to select records or clinical concepts individually. For example, an administrator creating Best Practice Advisories for diabetic patients could use 73211009 |diabetes mellitus| within the SNOMED CT hierarchy as one of the criteria instead of identifying every subtype of diabetes individually.
Within Epic's integrated analytics and reporting suite (i.e. Cogito) customers have achieved benefits by using SNOMED CT's clinical finding hierarchy to aggregate local diagnosis concepts.
The capability has for example been used by oncologists working with cancer-related ICD codes which are unsuited to grouping diagnoses by stage. Using the mapped SNOMED CT codes they are able to facilitate the reporting of staging data by utilizing the SNOMED CT hierarchy.
The 3M Healthcare Data Dictionary (HDD) is a controlled medical vocabulary server. The HDD has been continuously expanded and maintained for over 15 years, both as a standalone product and embedded within several of 3M's core products and services. The 3M HDD enables mapping and management of medical terminologies, integration of content and standardization of healthcare data. The 3M Healthcare Data Dictionary incorporates a selection of standard healthcare terminologies, including (but not limited to) SNOMED CT, LOINC, RxNorm, ICD-9-CM and ICD-10-CM.
Concepts in the HDD are grouped and organized using both hierarchical and non-hierarchical relationships. One of the hierarchical relationships in the HDD is SNOMED CT's 'is a' relationship which allows users to programmatically use and analyze SNOMED CT concepts captured at various levels of granularity. The analytics capabilities of the HDD are also extended through the use of other relationship types.
The content within the HDD makes a key contribution to analytics in several settings. For example one large academic research institution uses the HDD to integrate over 100,000 medication concepts from disparate systems for comprehensive data assimilation. Many of the medication concepts are mapped to RxNorm codes and linked through a 'has ingredient' relationship to SNOMED CT codes.
The 3M HDD has a knowledge base and poly-hierarchical structure that defines the relationships between each clinical drug.The following figure shows the relationships that exist for Ramipril including the links to SNOMED CT content, which can be used to query the data warehouse. The knowledge base allows the hospital's researchers to customize their searches by various levels of granularity and organize their clinical content into meaningful relationships.
The HDD supports researchers in performing data mining by:
Extracting and mapping clinical metadata using a streamlined, systematic approach;
Translating diverse clinical terminologies using a coded medical vocabulary;
Egton Medical Information Systems (EMIS) began in the 1980s in a rural practice in Egton in North Yorkshire, United Kingdom. The founders, Dr Peter Sowerby and Dr David Stables, wrote the software and adopted the NHS Read Code system during the 1980s. A series of systems have since been deployed in over half of England's primary care practices. The latest product (EMIS Web) moved to a data center based architecture, thin client front end and built in secure web based patient access facilities.
EMIS software looks after the patient records of nearly 40 million people in the UK (30 million using EMIS Web). More than 2 in 3 of those patients can book appointments and order repeat medications online, and more than 1 in 3 can view their own medical record.
EMIS Web features significant advances in terminology use with EMIS adopting a phased approach to SNOMED CT. EMIS Web displays a familiar coding structure based on the construction of a Read Version 2 navigational hierarchy within SNOMED CT. The principle design objective has been to enable SNOMED CT within the clinical system to meet specific requirements, including:
Supporting advanced decision support capabilities;
Snow Owl is a clinical terminology platform developed by B2i Healthcare. The Snow Owl technology family is deployed in over 2,500 locations in 83+ countries worldwide. The Snow Owl® terminology server has been licensed by SNOMED International to form the basis of SNOMED International Terminology Server.
The Snow Owl® terminology server scales from a small kernel embedded in single-user products to n-tier clusters supporting hundreds of concurrent users. Clients can easily access and query SNOMED CT, LOINC, ATC, ICD-10, and dozens of additional terminologies via REST or Java APIs. Collaborative distributed authoring is also supported, including creating and maintaining local code systems, mapping between terminologies, and creating terminology subsets.
Terminology server features include:
Extensive support for expression constraints and semantic queries, including Extended SNOMED CT Compositional Grammar and Groovy scripts.
1
This section includes brief reviews of a variety of commercial tools which support analytics over SNOMED CT enabled data. These reviews focus predominantly on those tooling features that are relevant to supporting analytics services.
We welcome additional input to this section and anticipate updates to this report as new information becomes available.
1

Supporting interoperability within healthcare through the sharing of coded data;
Supporting standards required in NHS General Practice Systems of Choice (e.g. the NHS mandates SNOMED CT coding within the National Summary Care Record service);
Broadening the scope of terminology use to support the recording of encounters in disciplines such as dentistry and community healthcare;
Supporting the mandatory requirement for the Electronic Prescription Service to natively use the UK SNOMED CT drug extension (i.e. NHS dictionary of medicines and devices, dm+d).
By using coded structured records and providing access to the specialist domain terminology available in SNOMED CT, EMIS has been able to extend the user base of EMIS Web by more than 20,000 new NHS users over the last year. These include practice nurses, community matrons, child health and mental health nurses, palliative care clinicians, diabetes specialists, physiotherapists and psychologists.
1
Full support for SNOMED CT logical definitions (OWL 2 EL) with extended support for extensions using advanced description logic features (OWL 2 DL) including datatype properties, universal restriction, disjunction, etc.
Standard distribution formats (e.g. SNOMED RF2, ICD-10 ClaML, LOINC csv)
Traditional, white-label (embedded within client product), and source code licenses available.
The Singapore Drug Dictionary (SDD) is the biggest SNOMED CT extension - larger than SNOMED CT International release itself. To support medication safety initiatives like medication management and adverse drug event surveillance, the drug ontology makes use of Snow Owl's extended description logic support.
The Snow Owl IDE (Integrated Development Environment) simplifies developer tasks related to terminology tooling. The architecture allows customized extensions to integrate tooling needs within a single platform.
The IDE embeds a terminology server and simplifies common terminology maintenance, ETL, and other tasks. Customized authoring environments support developing a library of queries (SNOMED CT expression constraints) using the Simple or Extended SNOMED CT Compositional Grammars and Groovy scripting. Files can be exported in a variety of formats like OWL 2, SNOMED CT RF1 and RF2, ClaML, spreadsheets and text files. Custom formats can also be created that support direct import and export to proprietary EHR and terminology applications.
Typical vendor deployments: EHR vendors use Snow Owl to create and maintain their local terminologies and mappings to reference terminologies like SNOMED CT. Snow Owl IDE allows exporting this in a format consumable by the proprietary EHR system format. The Snow Owl IDE has been built into proprietary tooling combining information modelling with ontology development.
Snow Owl's collaborative terminology authoring platform maintains terminology artefacts developed by a team and supported by business workflows. The platform consists of the terminology server with remote clients collaborating with independent authoring workflows. The platform integrates with external task management systems like Bugzilla and JIRA.
Features:
Full support for creating SNOMED CT extensions, including RF1 and RF2, all subset and mapping RF2 reference set types, modules, and full change history to 2002.
Support for dozens of terminologies and any local code systems.
Creation of value sets including mixing and matching codes from different code systems.
Import existing value sets from the USA National Library of Medicine's Value Set Authority Center.
Creation of mapping sets between any two terminologies or mapping local code systems to reference terminologies like SNOMED CT and LOINC.
Configurable workflow support for authoring use cases like single, dual, and dual independent authoring.
Support for terminology-specific workflows and editing restrictions.
The Singapore Ministry of Health Holdings uses Snow Owl to maintain their national SNOMED CT extension and local code systems as well as multi-terminology value sets and mappings used in their National Healthcare Data Dictionary.
The international adoption of SNOMED CT and related healthcare ontologies has provided the logical definitions that enable a new breed of queries. Unfortunately, it's challenging to run ad hoc queries that make use of the full semantics of the underlying EHRs. Operational stores have the data, but in a variety of structures that can't act on the semantic relationships between healthcare terms. Data warehouses can query only aggregated data that has been placed into predefined buckets which don't provide the scale of complexity inherent in the original data. And multiple information models represent the same semantic meaning in different ways.
Snow Owl Meaningful Query (MQ) allows semantic EHR queries on operational data stores without requiring predefined structures like data warehouses or the presence of a single unified healthcare information model. The system is optimized specifically for ad hoc queries of hundreds of millions of electronic health records. We combine ontological reasoning over the EHRs with more traditional query methods to incorporate demographic and ancillary data.
This query interface is being rolled out to all Singapore public hospitals and the national procurement office to allow search and retrieval of pharmaceuticals contained within the Singapore Drug Dictionary ontology. All lexical and semantic properties can be searched, including datatype properties and mappings to local code systems, external terminologies like ATC, and internal procurement codes.
1
Building on the capabilities of its CLiX Clinical Natural Language Processing (CNLP) platform, Clinithink has created a solution to enable the analysis of healthcare data sourced directly from clinical narrative called CLiX ENRICH. This technology can be integrated into existing healthcare solutions to process any relevant narrative and encode the key clinical elements – medications, diagnoses, procedures, symptoms and findings – using SNOMED CT. These features can then be queried using powerful, user-definable SNOMED CT queries to present structured data in a form that can be easily consumed by existing BI platforms.
For example, when the narrative text below is typed into diagnosis and observation fields (respectively), Clinithink is able to provide a list of possible coding options for manual confirmation (as shown below).
SNOMED CT plays a central role in many Apelon products and projects. Apelon tools feature navigation and visualization tools to support SNOMED CT in a variety of ways. Apelon also undertakes bespoke content development and consultancy work in healthcare and biomedicine using SNOMED CT.
The Apelon Terminology Development Environment (TDE) software was used by the College of American Pathologists to build and maintain the SNOMED CT International Edition prior to the formation of IHTSDO. Apelon software continues to be used by major healthcare organizations and some National Release Centers to maintain SNOMED CT extensions, maps and subsets.
The Apelon Distributed Terminology System (DTS) offers a variety of human and computer interfaces to navigate, visualize and query SNOMED CT. DTS allows users to create custom extensions to SNOMED CT and perform incremental description logic classification to ensure that the extensions are consistent with the base version of SNOMED CT. DTS permits navigation, and side-by-side comparison of concepts across multiple SNOMED CT versions. Features of Apelon DTS supporting analytics and data retrieval include:
Subsetting : DTS allows users to create customized SNOMED CT subsets using advanced logic techniques. The user is able to create extensional and intentional value sets of concepts for queries based on both hierarchical and non-hierarchical relationships.
Data normalization : DTS supports the matching of text input to standardized terms and concepts via word order analysis, word stemming, spelling correction and term completion
Code translation : DTS supports the mapping of clinical data to standard coding systems such as SNOMED CT, ICD-9, 10 and CPT
Apelon frequently choose to rely upon SNOMED CT in their consulting work as the overarching reference terminology. Recent projects using SNOMED CT include:
Work with a major performance measure developer to create a large number of SNOMED CT value sets representing the inclusion and exclusion criteria for quality measures. SNOMED CT supplies the expressivity for the detailed distinctions amongst disorders and patient characteristics that is essential for this work.
Use of SNOMED CT as the "backbone" terminology in a number of mapping projects for Health Information Exchanges. A small value set of SNOMED CT concepts serves as the "source of truth" for determining appropriate maps, and then codes from other terminologies are assigned based on whether they are a good fit with the SNOMED CT concept. This strategy provides a way to capture the precise intent behind the often-fuzzy language found in clinical documents.
Use of SNOMED CT to index patient education materials for a major content provider. Documents are retrieved via an 'Infobutton' request in the EMR based on codes found in the patient record.
Allscripts released their first version of Vocabulary Management utilizing SNOMED CT in 2005. Since then Allscripts systems have been able to utilize SNOMED CT for clinical decision support and reporting. Allscripts uses a common terminology platform for all three electronic health record systems: Sunrise Clinical Managerâ„¢, Sunrise Acute Careâ„¢ and Sunrise Ambulatory Careâ„¢.
When a query is performed over a health record that requires clinical terminology, the terminology service always returns a SNOMED CT code. If the primary code stored in the health record is not SNOMED CT (e.g. ICD-9 or ICD-10), then the terminology service performs the mapping to SNOMED CT, saves the SNOMED CT code in the health record next to the original code (to make future queries more efficient), and returns the SNOMED CT code.
Allscripts Sunrise applications are able to link SNOMED CT to all orders, order form pick lists, observations pick lists and results.
Sunrise Clinical Manager integrates reference content from medical publishers into clinician workflow. The Sunrise InfoButtonâ„¢ feature provides clinicians access to relevant medical reference content wherever patient care decisions are made, without requiring them to log into or visit another site. Sunrise InfoButton uses encoded patient problem lists and medication data elements to query third-party medical content selected by the clinician. Several healthcare reference content providers index their content using SNOMED CT. This enables the delivery of on-topic information without manual searching. Resources with SNOMED CT indexed content include Wolters Kluwer Clin-eguide which provides context-specific evidence on particular medical issues and diseases and Lexi-Comp, providing drug and drug-interaction information, diagnosis and disease management, formulary services, patient-education resources and clinical support tools.
The Allscripts Clinical Quality Management (CQM) is an automated chart abstraction and analytics system. CQM is able to create population sets with SNOMED CT encoded patient records and use these patient sets for reporting. CQM is a flexible, powerful reporting and analytics system presenting information in a variety of formats ranging from simple list style reports, to Online Analytical Processing (OLAP) Data Cubes with Pivot reports.
Allscripts Clinical Performance Management (CPM) is a business intelligence solution for monitoring clinical performance, improving patient outcomes and reducing costs. With prebuilt or customized reporting and dashboards, healthcare leaders have powerful access to performance information enabling quality improvement across the health enterprise.
Applications include:
Alert usage analysis: User-customizable reports drill down into clinical decision support usage data revealing the reasons and circumstances for bypassed or overridden alerts. Seeing the impact of decision support enables a sharper focus on patient outcomes and supports the refinement of rule logic.
Order-set usage analysis: Organizations can evaluate their order set usage patterns of computerized provider order entry. By observing order set configuration, deployment and use, organizations can revise them to enhance their effectiveness and usability.
Clinician utilization analysis: Clinicians can examine the vast array of health issues and clinical observations for discharged patients to support patient treatment decisions and protocol implementation. In addition, patient cohorts can be tracked over time to determine if the proper treatments are being delivered.
The Cambio COSMIC® Electronic Patient Record system has been under continuous development since 1993. Cambio has applied innovations within healthcare informatics in areas such as information models, clinical terminology and formal languages for expressing clinical decision support rules. The COSMIC® EPR combines openEHR archetypes, SNOMED CT terminology and Guideline Definition Language rules in implementations which benefit patients, clinical staff and healthcare enterprise management. Using these technologies, their system is able to incorporate advanced analytics capabilities.
Cambio uses the Guideline Definition Language (GDL) to combine archetypes, terminologies and clinical decision support rules. GDL provides:
Bindings between archetype elements and variables in the rules;
Rule expressions that are easily converted to industry rule engine languages;
Cerner Corporation's Millennium healthcare system manages terminologies, classifications and other code systems within a terminology service - the Cerner Millennium Terminology (CMT) package. CMT accommodates and integrates SNOMED CT International Release data and National extension content - such as concepts, relationships, descriptions, subsets, maps etc.
At the Cerner Millennium user interface, content can be captured at point of care as SNOMED CT codes. Modules used with SNOMED CT include: Problems and Diagnoses, Allergies, Procedures, Pharmacy Orders, Radiology Orders and Cellular Pathology Reports.
Either Cerner or third party clinical encoding software can process SNOMED CT Diagnoses and Procedures captured in Millennium and suggest ICD-10 and other classification codes to Clinical Coders for activity reporting and billing.
SNOMED CT is also used extensively behind the scenes to support more sophisticated analytic facilities within their Natural Language Processing (NLP) tools and reporting tools. These Cerner products and services exploit unique features and content of SNOMED CT to extend the power of these applications.
The Cerner product suite includes two data warehousing applications. These applications share much of their terminology-related technology, including supporting subsumption queries with the CMT Concept Explode/Transitive Closure facility, which utilizes the SNOMED 'is a' relationships.
The PowerInsight® Data Warehouse (PIDW) is an enterprise level data warehouse which updates on a nightly basis from the live electronic patient record. PIDW services standard operational reporting, mandatory reports (e.g. for National or State governments and regulatory bodies), and
1
1
1

Bindings between local concepts used in the rules and concepts from SNOMED CT.
GDL rules can be used to trigger a variety of system actions, including pre-filling a form, proposing a test or prescription, or sending a notification to the system user. The criteria for triggering actions from GDL rules may be based on demographics data, the context of care (e.g. clinic or inpatient), current medications and diagnoses, or observation values (e.g. lab results).
Decision support rules created in COSMIC® are authored using an editor. The next figure1 shows the high level view of a rule for calculating a complex clinical risk-score (CHA2DS2-VASc Score for stroke risks stratification in atrial fibrillation).
At the more detailed level, criteria may be defined using SNOMED CT concepts and subsets of concepts (as simple refsets). The figure below shows a section of a decision support rule which identifies patients with heart failure
Identification of suitable patients for research studies is a particular challenge to clinicians working in a routine clinic setting. A clinician may encounter eligible cases very rarely or simply not be familiar with the specific study selection criteria. In order to study diseases, their courses and causes, what causes or affects a particular condition, and the effects of different medications, researchers need trial subjects to meet specific criteria.
COSMIC Intelligence is a data warehouse and reporting application. Analyses and reports that do not require real time information are produced within this separate analysis system. COSMIC Intelligence is a data store optimized for queries, retrieval and output of data. Data is periodically retrieved from the 'live' clinical system, transformed and loaded into the data store.
1
The Health Facts® Reporting supports the pooling of anonymized data from different healthcare organizations. Health Facts data warehouse represents information of electronic records from millions of inpatient, emergency department, and outpatient visits from participating U.S. health care organizations. (Data are encrypted and secured to ensure patient confidentiality in compliance with HIPAA privacy regulations.) The reporting facilities enable the analysis of patient care and process trends within a facility and provide comparisons to other Health Facts contributors.
The Cerner data warehouse query tools include simple graphical user interfaces which directly create powerful reports using the SNOMED CT hierarchy content. The screenshot below shows a report of attendances with diagnoses which are a descendent of the SNOMED CT concept 417746004 | traumatic injury| .
Other Applications
Cerner's Natural Language Processing (NLP) technology interprets the content of clinical notes through a complex understanding of grammar, syntax, synonymy and phraseology. SNOMED CT's semantic content and concept model enriches the analysis of the text in several ways including
Concept recognition using synonyms – for example: |heart attack| is a synonym of |myocardial infarction|;
The hierarchical relationships between concepts – for example: |pneumonia||is a||respiratory disease|;
The identification of context, such as negation, certainty, subject and timing;
Computer Assisted Coding allows the extraction of appropriate SNOMED CT codes for automating coding and billing processes.
Chart Search/Semantic Search is a tool that enables clinicians at the point of care to search in real time through a patient's multiple charts, pathology reports and other documents, for topics such as 'heart disease' and 'diabetes'. The interface, as shown below has the look and feel of a World Wide Web search engine.
The searches can be filtered by date, document type etc. However the power of this approach is extended beyond conventional search engine indexing by using SNOMED CT. Cerner's tools index SNOMED CT findings (including diseases and symptoms) and procedures to make searches and queries over these domains faster. Cerner also hand curates exceptions and associations between related concepts. A Clinical Significance Score is assigned to each concept to allow documents to be sorted based on the probable relevance of the concepts in the document given their context of use.
As shown below for example, when given the search term 'heart disease', the 'is a' hierarchies of SNOMED CT enable recognition and return of documents which reference 'sinus bradycardia' and 'dilated cardiomyopathy'.
IMO produces a medical terminology service for healthcare solutions, allowing over 2,500 hospitals and 350,000 clinicians to focus on patient care. IMO bridges the information gap between clinicians, coders, and patients in the US and internationally. IMO enable and support the accurate capture and preservation of clinical intent for clinical documentation, decision support, reimbursement, reporting, data analysis, research, and health education.'
IMO's clinical interface terminology is designed pragmatically to capture clinical intent at point of care. However it is also intended to enable and simplify the adoption of standard ontologies by vendor partners.
By choice, the editorial process requires all IMO interface terms to have one or many qualified maps to SNOMED CT. Clients can then use SNOMED CT to drive reporting, analytics, clinical decision support, and research.
The following examples demonstrate how IMO uses SNOMED CT for analytical purposes:
Helping patients find health professionals who have expertise or interest in specific areas of medicine. These areas include disorders, procedures, devices, medications, patient demographics, and medical specialties. These areas of expertise or interest include those that are self-reported by clinicians and those documented in clinical encounters. The search algorithms use hierarchies in SNOMED CT to retrieve and rank search results.
Helping clinicians use patient diagnoses and procedures documented at varying levels of granularity to find appropriate patient education materials using SNOMED CT is-a hierarchies.
Grouping together related clinical concepts in patient records for creating focused patient reports and driving clinical workflows.
Forming subsumption queries for cohort selection within patient data repositories and document libraries.
IMO uses natural language processing (NLP) to extract information coded in SNOMED CT from clinical narratives.
Caradigm is a joint venture between Microsoft and GE Healthcare, which is dedicated to population health management. Caradigm's cornerstone product is the Intelligence Platform. This platform can connect over 295 types of source systems, including Allscripts, Athenahealth, Cerner, Epic, GE, McKesson and Meditech. Data from disparate systems within one or more healthcare organizations is collected, normalized and standardized to enable applications to leverage this data in a unified and consistent way.
Caradigm's solutions provide explorative, comparative, predictive and guided elements aimed at analyzing the disparate data and driving the insight that is gained into action. Caradigm's three main solution areas are:
Healthcare analytics (including clinical, operational and financial analytics);
Coordination management; and
Wellness promotion and patient engagement.
Some of Caradigm's customers use SNOMED CT natively in their clinical systems, while others use natural language and other code systems. In order to aggregate data from disparate sources, it must first be standardized by mapping into a common code system. Code systems used to standardize the disparate data include SNOMED CT, ICD-9 and ICD-10. By standardizing the data, users are able to leverage the analytics tools - for example, to understand trends within different diagnoses, to look at a comprehensive list of everything that has happened to a patient in a longitudinal patient record, and to support care management by displaying the different diagnoses or problems of a patient in a consistent manner.
Caradigm currently implements an approach to SNOMED CT based analytics using clinical value sets. These value sets are developed manually by a team of clinical analysts for topics such as diabetes and heart disease. Clinical users are then able to create queries in a user friendly interface, which allows them to (for example) define cohorts built on criteria such as age, gender, specific diseases, conditions, medication or other treatments. These queries are then converted behind the scenes into SQL statements which are executed against a SQL Server database and return records containing data in the selected clinical value sets.
Caradigm also has Natural Language Processing (NLP) tools, which are able to extract and encode data, such as problems and medications, from natural language notes within documents such as discharge summaries and radiology reports.
As part of their strategic roadmap, Caradigm are exploring ways to enhance the capabilities of their tooling platforms by leveraging the architecture of the terminology sets that they are using for analytics. In particular, they are planning to start utilizing the hierarchical and non-hierarchical relationships of SNOMED CT to enable more powerful query capabilities and to extend NLP processing options.
First DataBank (FDB) were in the first wave of suppliers to recognize the potential of SNOMED CT and begin to integrate support for SNOMED CT into their existing clinical decision support solutions. Their primary use of SNOMED CT in the patient's electronic health record (EHR) is to detect safety issues arising from certain combinations of medications, diagnoses and drug adverse reaction histories. In 2006 FDB introduced support for products and packs encoded using the NHS SNOMED CT UK Drug Extension. In the following year FDB launched new modules within the Multilex drug knowledge base supporting Drug-Condition Checking and Drug Sensitivity (Allergy) checking for the SNOMED CT EHR.
System vendors implementing Multilex decision support within SNOMED CT-enabled medical record applications include CSC (Lorenzo system), EPIC and JAC in secondary care, and CSE Servelec (RiO system) in community/mental health. Currently only pre-coordinated expressions are supported by the live Multilex SNOMED CT based decision support solutions.
The contraindications module alerts the clinician when a medication proposed to treat a disorder is incompatible with another of the patient's disorders or clinical states. For example a beta blocker like propranolol might be prescribed to treat someone with high blood pressure. However if that patient also has asthma, their asthma might significantly worsen or a dangerous acute attack might be produced by the drug.
Thousands of such drug-condition contraindications exist and nearly all medications have at least one. Without point of care decision support, the clinician must rely on memory or search reference sources for each drug prescribed. Also there is a risk that a contraindicating condition may be in the record but unknown to the prescribing clinician.





Internally FDB maintain their own local ontology representing only those conditions relevant to prescribing decision support (e.g. asthma, gastric ulcer, heart disease, pregnancy). The items in this ontology are linked to SNOMED CT codes as required to support this (contraindication checking) use case. These SNOMED CT links range from the obvious, such as linking to FDB's 'asthma', to the more subtle, such as linking to FDB's 'pregnancy'.
FDB reviews the relevant SNOMED CT domains (i.e. , and ) for concepts applicable to drug-condition checking. The FDB linking tool uses the SNOMED CT hierarchy and a SNOMED CT derived transitive closure table to locate and suggest links from the FDB ontology to SNOMED CT concepts. Other SNOMED CT relationships also help find related concepts via the browser but discovery is mainly by clinical knowledge combined with description based searches assisted by the rich synonym content of SNOMED CT.
The sensitivities module alerts the clinician when a proposed drug for a patient is either stated in that patient's record to have caused a previous adverse reaction or when an adverse reaction has occurred to a similar drug and thus likely to elicit a similar adverse response. For example, a patient allergic to penicillin is likely to react to most other drugs containing a β-lactam ring in their molecular structures.
In a similar way to how FDB links SNOMED CT conditions to its own internal ontology, SNOMED CT concepts which suggest allergy or previous adverse reactions to a medication are also linked to an internal FDB ontology for representing medication ingredients. This ontology is designed specifically to support allergic and adverse reaction cross-reactivity.
1
1
1