Release 4

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4

Codesystem-secondary-finding.xml

Vocabulary Work GroupMaturity Level: N/AStandards Status: Informative

Raw XML (canonical form + also see XML Format Specification)

Definition for Code System ObservationCategoryCodes

<?xml version="1.0" encoding="UTF-8"?>

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="secondary-finding"/> 
  <meta> 
    <lastUpdated value="2019-11-01T09:29:23.356+11:00"/> 
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2> Observation Category Codes</h2> 
      <div> 
        <p> Codes to denote a guideline or policy statement.when a genetic test result is being shared
           as a secondary finding.</p> 

      </div> 
      <p> This code system http://hl7.org/fhir/secondary-finding defines the following codes:</p> 
      <table class="codes">
        <tr> 
          <td style="white-space:nowrap">
            <b> Code</b> 
          </td> 
          <td> 
            <b> Display</b> 
          </td> 
          <td> 
            <b> Definition</b> 
          </td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">acmg-version1
            <a name="secondary-finding-acmg-version1"> </a> 
          </td> 
          <td> ACMG Version 1</td> 
          <td> First release (2013): ACMG Recommendations for Reporting of Incidental Findings in Clinical
             Exome and Genome Sequencing.  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3727274/</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">acmg-version2
            <a name="secondary-finding-acmg-version2"> </a> 
          </td> 
          <td> ACMG Version 2</td> 
          <td> Second release (2016): Recommendations for reporting of secondary findings in clinical
             exome and genome sequencing, 2016 update (ACMG SF v2.0): a policy statement of the American
             College of Medical Genetics and Genomics. https://www.ncbi.nlm.nih.gov/pubmed/27854360</td> 
        </tr> 
      </table> 
    </div> 
  </text> 
  <url value="http://hl7.org/fhir/secondary-finding"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.4.1286"/> 
  </identifier> 
  <version value="4.0.1"/> 
  <name value="ObservationCategoryCodes"/> 
  <title value="Observation Category Codes"/> 
  <status value="draft"/> 
  <experimental value="false"/> 
  <publisher value="FHIR Project team"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org/fhir"/> 
    </telecom> 
  </contact> 
  <description value="Codes to denote a guideline or policy statement.when a genetic test result is being shared
   as a secondary finding."/> 
  <caseSensitive value="true"/> 
  <valueSet value="http://hl7.org/fhir/ValueSet/secondary-finding"/> 
  <content value="complete"/> 
  <concept> 
    <code value="acmg-version1"/> 
    <display value="ACMG Version 1"/> 
    <definition value="First release (2013): ACMG Recommendations for Reporting of Incidental Findings in Clinical
     Exome and Genome Sequencing.  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3727274/"/> 
  </concept> 
  <concept> 
    <code value="acmg-version2"/> 
    <display value="ACMG Version 2"/> 
    <definition value="Second release (2016): Recommendations for reporting of secondary findings in clinical
     exome and genome sequencing, 2016 update (ACMG SF v2.0): a policy statement of the American
     College of Medical Genetics and Genomics. https://www.ncbi.nlm.nih.gov/pubmed/27854360"/> 
  </concept> 
</CodeSystem> 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.