HL7 Terminology (THO)
3.1.13 - Continuous Process Integration (ci build) World

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This is not an authorized publication; it is the continuous build for version 3.1.13). This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

: RadLex radiology lexicon - XML Representation

Active as of 2022-03-31

Raw xml | Download



<NamingSystem xmlns="http://hl7.org/fhir">
  <id value="RadLex"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><h3>Summary</h3><table class="grid"><tr><td>Defining URL</td><td>http://terminology.hl7.org/NamingSystem/RadLex</td></tr><tr><td>Name</td><td>RadLex</td></tr><tr><td>Status</td><td>active</td></tr><tr><td>Definition</td><td><div><p>RadLex is a comprehensive set of radiology terms for use in radiology reporting, decision support, data mining, data registries, education and research.</p>
<p>RadLex Playbook is a project of the Radiological Society of North America (RSNA), and constitutes a portion of the RadLex ontology. Playbook aims to provide a standard system for naming radiology procedures, based on the elements which define an imaging exam such as modality and body part. By providing standard names and codes for radiologic studies, Playbook is intended to facilitate a variety of operational and quality improvement efforts, including workflow optimization, chargemaster management, radiation dose tracking, enterprise integration and image exchange.</p>
<p>As of RadLex Playbook version 2.5, a four-year project to harmonize RadLex Playbook with the radiology portion of the LOINC standard has been concluded, leading to the LOINC-RSNA Radiology Playbook which is jointly managed by the Regenstrief Institute (publisher of LOINC) and RSNA. This harmonized Playbook defines a new information model for describing imaging procedures, and identifies correspondences between RadLex Playbook codes and LOINC codes. (See https://loinc.org/download/loinc-users-guide and http://pubs.rsna.org/doi/pdf/10.1148/rg.2017160188 for details.) Note that RadLex Playbook codes start with &quot;RPID&quot; followed by a numerical value. LOINC codes consist of a numerical code, followed by a hyphen and a single additional digit (called the check digit). Note that in the future, new codes will be created in the LOINC format only, not the RPID format. New adopters are encouraged to use LOINC-format codes.</p>
<p>LOINC-format codes may be accessed at http://search.loinc.org. New code requests may be submitted to the joint Regenstrief-RSNA governance committee at https://loinc.org/submissions/.</p>
<p>From the RSNA website:</p>
<p>&quot;We (RSNA) recognize the benefits that come from radiologists using common language to communicate diagnostic results. For this reason, RSNA produced RadLex®, a comprehensive set of radiology terms for use in radiology reporting, decision support, data mining, data registries, education and research.</p>
<p>RadLex provides the foundation for vital data resources used in radiology:</p>
<ul>
<li>The LOINC/RSNA Radiology Playbook (http://playbook.radlex.org/playbook/SearchRadlexAction)</li>
<li>RadElement Common Data Elements (http://www.radelement.org/)</li>
<li>RadReport Radiology Reporting Templates (http://radreport.org/)</li>
</ul>
<p>The development of RadLex has been supported by the National Institute of Biomedical Imaging and Bioengineering (NIBIB) and the cancer Biomedical Informatics Grid (caBIG) project.;&quot;</p>
</div></td></tr><tr><td>Publisher</td><td>RSNA (Radiological Society of North America)</td></tr></table><h3>Identifiers</h3><table class="grid"><tr><td><b>Type</b></td><td><b>Value</b></td><td><b>Preferred</b></td><td><b>Period</b></td><td><b>Comment</b></td></tr><tr><td>OID</td><td>2.16.840.1.113883.6.256</td><td>true</td><td></td><td/></tr><tr><td>URI</td><td>http://radlex.org</td><td>true</td><td>2019-05-05 --&gt; (ongoing)</td><td>This is the URL as specified by the terminology owner, and is considered authoritative.</td></tr></table></div>
  </text>
  <extension url="http://hl7.org/fhir/tools/StructureDefinition/extension-title">
    <valueString value="RadLex radiology lexicon"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/5.0/StructureDefinition/extension-NamingSystem.url">
    <valueUri value="http://terminology.hl7.org/NamingSystem/RadLex"/>
  </extension>
  <extension
             url="http://terminology.hl7.org/StructureDefinition/ext-namingsystem-version">
    <valueString value="1.0.1"/>
  </extension>
  <name value="RadLex"/>
  <status value="active"/>
  <kind value="codesystem"/>
  <date value="2022-03-31T00:00:00-00:00"/>
  <publisher value="RSNA (Radiological Society of North America)"/>
  <contact>
    <name
          value="RSNA (Radiological Society of North America); 820 Jorie Blvd., Suite 200, Oak Brook, IL 60523-2251 USA"/>
    <telecom>
      <system value="email"/>
      <value value="informatics@rsna.org"/>
    </telecom>
    <telecom>
      <system value="url"/>
      <value value="https://www.rsna.org/"/>
    </telecom>
    <telecom>
      <system value="phone"/>
      <value value="1-800-381-6660"/>
    </telecom>
  </contact>
  <responsible value="RSNA (Radiological Society of North America)"/>
  <description
               value="RadLex is a comprehensive set of radiology terms for use in radiology reporting, decision support, data mining, data registries, education and research.

RadLex Playbook is a project of the Radiological Society of North America (RSNA), and constitutes a portion of the RadLex ontology. Playbook aims to provide a standard system for naming radiology procedures, based on the elements which define an imaging exam such as modality and body part. By providing standard names and codes for radiologic studies, Playbook is intended to facilitate a variety of operational and quality improvement efforts, including workflow optimization, chargemaster management, radiation dose tracking, enterprise integration and image exchange.

As of RadLex Playbook version 2.5, a four-year project to harmonize RadLex Playbook with the radiology portion of the LOINC standard has been concluded, leading to the LOINC-RSNA Radiology Playbook which is jointly managed by the Regenstrief Institute (publisher of LOINC) and RSNA. This harmonized Playbook defines a new information model for describing imaging procedures, and identifies correspondences between RadLex Playbook codes and LOINC codes. (See https://loinc.org/download/loinc-users-guide and http://pubs.rsna.org/doi/pdf/10.1148/rg.2017160188 for details.) Note that RadLex Playbook codes start with &quot;RPID&quot; followed by a numerical value. LOINC codes consist of a numerical code, followed by a hyphen and a single additional digit (called the check digit). Note that in the future, new codes will be created in the LOINC format only, not the RPID format. New adopters are encouraged to use LOINC-format codes.

LOINC-format codes may be accessed at http://search.loinc.org. New code requests may be submitted to the joint Regenstrief-RSNA governance committee at https://loinc.org/submissions/. 

From the RSNA website:

&quot;We (RSNA) recognize the benefits that come from radiologists using common language to communicate diagnostic results. For this reason, RSNA produced RadLex®, a comprehensive set of radiology terms for use in radiology reporting, decision support, data mining, data registries, education and research.

RadLex provides the foundation for vital data resources used in radiology:

 *  The LOINC/RSNA Radiology Playbook (http://playbook.radlex.org/playbook/SearchRadlexAction) 
 *  RadElement Common Data Elements (http://www.radelement.org/) 
 *  RadReport Radiology Reporting Templates (http://radreport.org/) 

The development of RadLex has been supported by the National Institute of Biomedical Imaging and Bioengineering (NIBIB) and the cancer Biomedical Informatics Grid (caBIG) project.;&quot;"/>
  <uniqueId>
    <type value="oid"/>
    <value value="2.16.840.1.113883.6.256"/>
    <preferred value="true"/>
  </uniqueId>
  <uniqueId>
    <type value="uri"/>
    <value value="http://radlex.org"/>
    <preferred value="true"/>
    <comment
             value="This is the URL as specified by the terminology owner, and is considered authoritative."/>
    <period>
      <start value="2019-05-05"/>
    </period>
  </uniqueId>
</NamingSystem>