SNOMED CT April 2016 LOINC - SNOMED CT Cooperative package Alpha (phase 3) release - OWL format Release notes
Date | 20160401 |
Version | 1.0 |
Status | Final |
Approvals
Final Version | Date | Approver | Comments |
1.0 | 20160331 | Ian Green | Final Version |
Draft Amendment History
Version | Date | Editor | Comments |
0.01 | 20160209 | Suzanne Santamaria Farzaneh Ashrafi | First draft for comments |
0.02 | 20160303 | Ian Green | Revised/Additional updates |
© International Health Terminology Standards Development Organisation 2016. All rights reserved. SNOMED CT® was originally created by The College of American Pathologists.
This document forms part of the LOINC - SNOMED CT Cooperative Project Edition release of SNOMED CT® distributed by International Health Terminology Standards Development Organisation (IHTSDO), which is subject to IHTSDO’s SNOMED CT® Affiliate License, details of which may be found at http://www.ihtsdo.org/snomed-ct/get-snomed-ct/.
No part of this document may be reproduced or transmitted in any form or by any means, or stored in any kind of retrieval system, except by an Affiliate of IHTSDO in accordance with the SNOMED CT® Affiliate License. Any modification of this document (including without limitation the removal or modification of this notice) is prohibited without the express written permission of IHTSDO.
Any copy of this document that is not obtained directly from IHTSDO [or a Member of IHTSDO] is not controlled by IHTSDO, and may have been modified and may be out of date. Any recipient of this document who has received it by other means is encouraged to obtain a copy directly from IHTSDO [or a Member of IHTSDO. Details of the Members of IHTSDO may be found at http://www.ihtsdo.org/members/].
This material contains content from LOINC® (http://loinc.org) that is used by permission from the Regenstrief Institute. The LOINC table, LOINC codes, and LOINC panels and forms file are copyright © 1995-2016, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and available in perpetuity at no cost under the license at http://loinc.org/terms-of-use.
Table of Contents
- 1 1 Introduction
- 1.1 1.1 Background
- 1.2 1.2 Purpose
- 1.3 1.3 Scope
- 1.4 1.4 Audience
- 2 2 Feedback for the Alpha release
- 3 3 Consuming the OWL file
- 4 4 Content Development Activity
- 4.1 4.1 Overview
- 4.2 4.2 Content detail
- 4.3 4.3 Content usage
- 5 6 Mapping and Modeling Guidelines Used
- 6 7 Quality Assurance
- 7 8 Classifying Expressions with SNOMED CT
- 8 9 Next Steps
- 9 10 References
1 Introduction
1.1 Background
A cooperative agreement [3] was signed between the Regenstrief Institute and the IHTSDO in July 2013. The agreement details how SNOMED CT and LOINC will be linked through:
a map of LOINC Terms to post-coordinated SNOMED CT expressions
a map of LOINC Parts to SNOMED CT concepts
a map between LOINC Terms and existing pre-coordinated SNOMED CTconcepts
LOINC Answer sets mapped to SNOMED CT codes
addition of new content in either terminology
See Figure 1 for an illustration of these connections. The Alpha release includes artifacts related to items 1, 2, and 5 above. Note that this OWL file includes content for item 1 above (LOINC terms mapped to SNOMED CT expressions following the SNOMED CT Observables model).
Figure 1. Diagram showing an overview of maps, Expression Associations and content additions that form part of the Cooperative Works of the Agreement [3].
1.2 Purpose
This document is intended to give a brief description, background context and explanatory notes on the OWL file release associated with the LOINC - SNOMED CT Cooperative Project Alpha Release - phase 3.
This OWL file version is for reviewing an ontology containing LOINC Terms defined by post-coordinated SNOMED CT expressions.
It is being released for additional input on content being developed for this project.
It should be opened with an ontology viewing/editing software such as Protege and classified with an ontology reasoner.
A hierarchy is created between some LOINC Terms after classification.
This is not an official release format for IHTSDO.
This file does not contain metadata such as refset identifier and correlation designation which are present in the official IHTSDO RF2 release files.
This is not a detailed technical document about the release file formats or on implementing LOINC and SNOMED CT together. See “Guidelines for using SNOMED CT and LOINC together - Phase 2 Draft” [1] for information about implementation of LOINC and SNOMED CT together.
All content will be released in parallel by IHTSDO and the Regenstrief Institute through their distribution channels, e.g. IHTSDO Confluence site, LOINC website.
Two other file formats are available for review of content in the Alpha release. Information about these files is provided in separate documents [2].
RF2 release format .txt files: these files are the official IHTSDO RF2 release files. This is the format intended to be continually distributed for implementation.
Excel spreadsheet: for reviewing the map of LOINC Terms to SNOMED CT expressions in a human-readable tabular format. This is not an official release format for IHTSDO. The map from LOINC Parts to SNOMED CT is not included as the Parts are not publicly released by the Regenstrief Institute.
1.3 Scope
This document is written for the purpose described above and is not intended to provide details of the technical specifications for SNOMED CT or encompass every change made during the release.
1.4 Audience
The audience includes National Release Centers, vendors of electronic health records, terminology developers and managers who wish to partake in the review of the LOINC - SNOMED CT Cooperative project edition Alpha release.
2 Feedback for the Alpha release
2.1 Desired feedback
Please provide feedback by 31 May, 2016 at https://jira.ihtsdotools.org/projects/LOINC.
Reviewers of the OWL file are asked to please review the LOINC term definitions and the inferred hierarchy under “Observable entity” which results from running the reasoner. We are seeking feedback regarding any existing issues (with the exception of spelling mistakes, minor formatting) that you can identify. We are also seeking specific feedback on some issues that we believe may be problematic:
We are unsure if some of the inferences are correct, e.g. should the LOINC terms with specific methods be subsumed by the methodless LOINC term?
3 Consuming the OWL file
3.1 Where to find the OWL file
The OWL file is available for download here: https://mlds.ihtsdotools.org/#/ihtsdoReleases/ihtsdoRelease/50041. Please download this file, extract the OWL file and save it on your computer.
3.2 Why is an OWL file being released?
One of the benefits of creating the content as an ontology in an OWL file is the application of description logic to LOINC terms and use of a reasoner to highlight additional classifications of terms. We will work to correct the identified issues as the project progresses. This is expected to help people apply LOINC lab codes more correctly to existing test dictionaries because we will identify and correct semantic issues that could not be found through manual review. The alpha prototype release of the project in May 2014 consisted of an OWL file. We received numerous requests to release an OWL file alongside the Alpha release files.
3.3 How to view the OWL file
You will need a piece of software capable of importing OWL data. Most commonly people use a free open source package called Protege. It can be installed on your computer to view the file and classify the content. To get Protege, go to http://protege.stanford.edu/ and navigate to Downloads. You will need to pick the correct download version for your computer (Mac vs PC, with or without Java Virtual Machine, etc.). Information about which version to choose are available on this site.
Open Protege on your computer and go to File - Open then find the OWL file wherever you stored it on your computer. Once the file opens click on the Entities tab - Class hierarchy to see the concepts in the file. Note that the LOINC terms are subtypes of “Observable entity” in this file. Concepts used to define the LOINC terms are subtypes of other hierarchies in this file (e.g. “Organism”.)
Click open the arrows next to the concepts to view subtypes. Click on a concept to highlight it and then look at that concept definitions in the right hand side of the screen. These definitions align with the draft SNOMED CT Observables model. Information about the LOINC terms can be seen on the right hand side of the screen under “Class Annotations.”
Classify the content with a reasoner
At the top of frame go to Reasoner and choose a reasoner (e.g. Hermit, Snorocket, ELK). Note that the reasoner may need to install updates the first time you open Protege. It will likely be necessary to close Protege and reopen it for the updates to take effect.
Go to Reasoner and click Start reasoner. When the reasoner finishes classifying, click on the Entities tab - Class hierarchy (inferred) to see the results of the classification. You will now see that some concepts inferred a different (more specific) concept as a supertype. See the example below where a test with a specific method (Albumin:MCnc:Pt:Synv fld:Qn:Electrophoresis) is now a subtype of “Albumin:MCnc:Pt:Synv fld:Qn” whereas prior to reasoning they were siblings.
4 Content Development Activity
4.1 Overview
This OWL file is based on the 20160131 version of the IHTSDO International release of SNOMED CT and Version 2.54 of LOINC released December 2015.
This release includes a majority (around 75%) of the Top 2000 LOINC Lab Observations and LOINC Parts needed to represent these LOINC Terms. Some LOINC Terms on the Top 2000 list were excluded from the scope of the Alpha release for various reasons:
We have not yet mapped all the LOINC Parts associated with the Top 2000 LOINC Terms to SNOMED CT concepts (or have not created the SNOMED CT concepts). The main reason for this exclusion is the requirement for further clarification with the Substance Project, RII, and Observable Model Redesign Project.
There are Terms being discussed internally for modelling reconsiderations and possible modification (e.g. susceptibility testing and genetic testing)
Panels are not in the scope of the Cooperative Agreement
Veterinary specific terms are not considered in the scope of SNOMED CT and this project
Over 1500 concepts were added to SNOMED CT to produce this Alpha release.
This file does not represent a set of data ready for clinical use within a system. It has been made available at this time for review and evaluation purposes only.
USE WITHIN A CLINICAL SYSTEM CANNOT BE SUPPORTED AT THIS TIME
4.2 Content detail
The OWL file contains 13756 active LOINC Terms associated with post-coordinated SNOMED CT expressions.
All of the LOINC Terms are subclasses of 363787002 | Observable entity (observable entity) in SNOMED CT and the expressions follow the draft SNOMED CT Observables model in a flattened form (no nesting of attributes as in previous Alpha releases of this project) [4,5].
See Figure 2 for a diagram of the Observables model used in this work.
Section “Mapping and Modeling Guidelines Used” contains general rules on the mapping and exceptions.
The majority of the expressions included are fully defined and are an exact match with a LOINC Term, with a few exceptions.
The expressions are represented in the stated form with no hierarchy included.
4.3 Content usage
The main purposes for the mapping are to (a) link the laboratory coverage of LOINC with the SNOMED CT concept model to provide a consistent model rather than having divergent representation of similar concepts, (b) limit duplication of effort related to overlapping areas, and (c) focus resources on common and collaborative effort rather than the competing activities of the past. In practical terms there are a variety of ways to deploy and benefit from the resulting products. These are explored in the current draft of the document “Guidance on Use of SNOMED CT and LOINC Together.” It is available on Confluence at ttp://snomed.org/snomedloinc.”
5 Draft SNOMED CT Observables model
Linking LOINC terms to SNOMED CT concepts in this project comports with the draft SNOMED CT Observables model. A diagram of the model is shown below in Figure 2. Note that this Alpha release contains a flattened model whereas the final product of this work may or may not contain nesting.
A.
B.
Figure 2. Flattened Observables model showing the relationship of SNOMED CT attributes (in yellow) and values (in blue) used in creating the post-coordinated expressions in the LOINC Term to SNOMED CT Expression Refset. “A” shows the model for quality observables and “B” shows the model for process observables.
6 Mapping and Modeling Guidelines Used
When preparing this content we utilized the draft flattened Observables model (see Figure 2) and followed these guidelines:
Mapping is performed from LOINC to SNOMED CT
In general, we mapped from LOINC axis to SNOMED CT attribute as such:
LOINC Component → Component attribute in SNOMED CT for quality observables (or Process output attribute in process observables such as excretions)
LOINC Components containing divisors → Component + Relative to attributes in SNOMED CT
LOINC Components containing challenges → Component + Precondition attributes in SNOMED CT
LOINC Components containing adjustments → Component + Technique attributes in SNOMED CT
Sometimes a new SNOMED CT concept containing a combination of techniques was needed
LOINC Property → Property attribute in SNOMED CT
LOINC Scale → Scale attribute in SNOMED CT
LOINC System → Direct site + Inheres In in SNOMED CT
Direct site is the equivalent of system in LOINC. Used for all specimen types except XXX.
Inheres in applies to all specimen types except “specimen” and XXX and Body fluid
Direct site and Inheres in
The Direct site is the direct object of the observation action; the site or specimen where the observation takes place. This may be different from the value of Inheres in, since the property being observed may be inferred from a specimen or from a remote site. The intended object of the observation is the entity in which the observed property inheres; or the independent continuant
which is ideally intended to be observed.Example:
Serum specimen being used to determine body
plasma sodium concentration. The concentration inheres in the plasma, but is being measured in a serum specimen.
LOINC Time
LOINC Part Pt → Time aspect attribute = Single point in time in SNOMED CT
LOINC X hrs = Process duration attribute in SNOMED CT
Exception: Where LOINC System = urine AND Time = 24 hrs AND Property is not one of MRat, SRat, VRat, and NRat, the Term is mapped as such:
Specimen = Change map from Urine → 24 hour urine sample
Time = Change map from 24hrs → Single point in time
Inheres in is not affected
LOINC Method → Technique attribute in SNOMED CT
An expression only needs to include the attributes necessary to specify the LOINC Term. It does not need to use every attribute in the Observables model.
We mapped from one LOINC Part to one SNOMED CT concept where possible. In some cases a one to one map was not possible:
LOINC Part mapped to more than one SNOMED CT concept
LOINC System Parts are mapped using two attribute-value pairs in SNOMED CT: Direct site and Inheres in
Example: LOINC Part “Ser/Plas” is mapped to SNOMED CT Direct site=Acellular blood (serum or plasma) specimen and Inheres in=Plasma
LOINC Parts for cells (e.g. Basophils) are often mapped to two concepts in SNOMED CT: an individual X cell concept and a population of X cells in portion of fluid concept. The property type and scale of the associated LOINC Term will determine which map is appropriate for that LOINC Term.
Some LOINC Component Parts (generally substances) are mapped using the Component and/or Process output attribute in SNOMED CT depending on the time aspect and property of a LOINC Term. When the Property type is MRat, SRat, VRat, and NRat, and Time = 24 hrs, then the Process output attribute carries the SNOMED CT concept equivalent to the LOINC Component. Otherwise, the Component attribute carries the SNOMED CT concept equivalent to the LOINC Component. A LOINC Term will generally only include a value for Component OR for Process Output, but not both. The Part map may include a value for Component and Process Output.
Example: Creatinine is used as a value of the Component attribute in LOINC Term Creatinine/Calcium [Mass Ratio] in Urine. Creatinine is used as a value of the Process output attribute in LOINC Term Creatinine [Mass/volume] in 24 hour Urine.
LOINC Divisor Parts are mapped to two attribute-value pairs in SNOMED CT: Relative to and Units
LOINC Part 100 Leukocytes is mapped to SNOMED CT Relative to=Population of all leukocytes in portion of fluid and Units=Percentage
LOINC Part is not mapped to an equivalent SNOMED CT concept
LOINC Part that is not universal and reproducible is mapped to a more general concept in SNOMED CT.
Example, the LOINC Part “Leukocyte other” is mapped to “Leukocyte (cell)” and “Population of leukocytes in portion of fluid” in SNOMED CT because the meaning of “Leukocyte other” cannot be specified.
LOINC Part mapped to a different attribute in SNOMED CT concept
Example: The LOINC Component Part “Color” is mapped to the Property attribute with a value of “Color” in SNOMED CT
Two LOINC Parts are combined to map to two SNOMED CT concepts
LOINC Component Part Crystals.unidentified and LOINC Method Microscopy.light map to SNOMED CT Component=Crystal and Technique=Detecting by light microscopy without classifying
Our goal is to create maps that are exact matches between LOINC Parts and SNOMED CT concepts. Where this is not possible, the map is given a designation other than “Exact match.”
Example, the LOINC Part “Leukocyte other” is mapped to “Leukocyte (cell)” and “Population of leukocytes in portion of fluid” with a correlation of “SNOMED CT Broader.”
Our goal is to create SNOMED CT expressions that are exact matches to LOINC Terms and mark these as fully defined. Where this is not possible, the map is marked as primitive and/or a designation other than “Exact match” is utilized.
Example, the LOINC Term “Leukocytes other [#/volume] in Body fluid” is mapped to an expression that has Component=Population of leukocytes in portion of fluid along with other attribute-value pairs. The map is given a correlation of “LOINC narrower” and a designation of “Primitive.”
Additional information is designated for each map:
content origin (LOINC or SNOMED CT or both)
correlation (exact, narrower, broader)
attribute (where a Part is used in an expression)
IHTSDO refset identifier
IHTSDO module identifier
effective time of map
map status for active vs inactive
unique identifier of map row (GUID)
Some SNOMED CT Concepts included in the file do not specifically map to a LOINC Part or Terms, e.g. grouping concepts, concepts used in the Observables modeling, some technique concepts.
Active, discouraged and trial LOINC Terms are included in the mapping as some implementers are using these LOINC Terms. Deprecated LOINC Terms and Parts are not included in the mapping.
Some naming conventions in SNOMED CT concepts are not consistent
Example: "Immunoglobulin G antibody to Yersinia" vs "Immunoglobulin A antibody to Yersinia species"
7 Quality Assurance
The files associated with this Alpha release were reviewed by a number of individuals including Terminologists at IHTSDO, Regenstrief Institute, Kaiser Permanente, University of Nebraska, Linköping University and Mapping Specialists from the IHTSDO Mapping Service Team. Quality assurance reviews were performed both manually and with some automated processes. Feedback received from reviewers (internal and external) on the previous Alpha releases were considered and changes were implemented in this release where applicable. There are several known issues that are currently under review. Changes will be implemented when a resolution becomes available. Known issues include:
Proper representation of LOINC Terms using “total,” e.g. Total cholesterol. In this Alpha release, expressions for these Terms are marked as primitive rather than fully defined.
8 Classifying Expressions with SNOMED CT
If reviewers are familiar with classifying in ontologies and would like to classify the expressions with all or a portion of SNOMED CT, send us an email at LOINC-SNOMEDProject@ihtsdo.org with a subject line of “Alpha release.”
9 Next Steps
Next steps in the project include:
Evaluate feedback received on this Alpha Release
Prepare Beta release
Finish the map of LOINC Parts to SNOMED CT concepts. Additional SNOMED CT concepts will need to be created to finish the map.
Use the above map to create more expressions for LOINC Terms.
Resolve and/or note content and modeling known and upcoming issues.
Implement the SNOMED CT Observables model to define existing pre-coordinated SNOMED CT concepts
10 References
“Guidelines for using SNOMED CT and LOINC together - Phase 2 Draft:” http://snomed.org/snomedloinc
Alpha release files of LOINC - SNOMED CT Cooperation Project, including additional file formats (OWL, Excel) are available at: https://mlds.ihtsdotools.org/#/ihtsdoReleases/ihtsdoRelease/50041
COOPERATION AGREEMENT dated July 2013 Between The International Health Terminology Standards Development Organisation (IHTSDO) and The Regenstrief Institute, Incorporated (RII): http://www.ihtsdo.org/about-ihtsdo/partnerships/loinc
Draft SNOMED CT Observables Model described in a PowerPoint presentation titled “Observables model in the context of the concept model:” https://snomed.atlassian.net/wiki/x/_RLXBw
Note that viewing this presentation requires being a member of Observable and Investigation Model Project on Confluence. If you are not yet a user of this project on Confluence, please request addition through the site.
Observables and investigation procedures redesign Inception/Elaboration document: https://snomed.atlassian.net/wiki/x/thrXBw
Note that viewing this presentation requires being a member of Observable and Investigation Model Project on Confluence. If you are not yet a user of this project on Confluence, please request addition through the site.
Information about Expressions can be found in the “SNOMED CT Technical Implementation Guide:” http://ihtsdo.org/fileadmin/user_upload/doc/
The International Health Terminology Standards Organization (IHTSDO): http://www.ihtsdo.org/
IHTSDO Confluence: https://confluence.ihtsdotools.org/
Logical Identifiers Names and Codes (LOINC): http://loinc.org/
Area to submit feedback on the LOINC - SNOMED CT Alpha release: https://jira.ihtsdotools.org/projects/LOINC