HL7 Terminology (THO)
6.1.0 - Continuous Process Integration (ci build) International flag

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

: Sex Parameter For Clinical Use - XML Representation

Active as of 2024-11-19

Raw xml | Download


<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="sex-parameter-for-clinical-use"/>
  <meta>
    <profile
             value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem sex-parameter-for-clinical-use</b></p><a name="sex-parameter-for-clinical-use"> </a><a name="hcsex-parameter-for-clinical-use"> </a><a name="sex-parameter-for-clinical-use-en-US"> </a><p><b>Properties</b></p><p><b>This code system defines the following properties for its concepts</b></p><table class="grid"><tr><td><b>Name</b></td><td><b>Code</b></td><td><b>URI</b></td><td><b>Type</b></td><td><b>Description</b></td></tr><tr><td>usage-note</td><td>usage-note</td><td>http://terminology.hl7.org/CodeSystem/sex-parameter-for-clinical-use/property/usage-note</td><td>string</td><td>Usage notes for the concept.</td></tr></table><p><b>Concepts</b></p><p>This case-sensitive code system <code>http://terminology.hl7.org/CodeSystem/sex-parameter-for-clinical-use</code> 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">female-typical<a name="sex-parameter-for-clinical-use-female-typical"> </a></td><td>Apply female-typical setting or reference range</td><td>Available data indicates that diagnostics, analytics, and treatments should consider best practices associated with female reference populations.</td></tr><tr><td style="white-space:nowrap">male-typical<a name="sex-parameter-for-clinical-use-male-typical"> </a></td><td>Apply male-typical setting or reference range</td><td>Available data indicates that diagnostics, analytics, and treatments should consider best practices associated with male reference populations.</td></tr><tr><td style="white-space:nowrap">specified<a name="sex-parameter-for-clinical-use-specified"> </a></td><td>Apply specified setting or reference range</td><td>Available data indicates that diagnostics, analytics, and treatment best practices may be undefined or not aligned with sex-derived reference populations. Additional information may be available in the form of comments and/or observations. The terms &quot;Other&quot; or &quot;Complex&quot; may be considered synonyms of &quot;Specified&quot;.</td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="pa"/>
  </extension>
  <url
       value="http://terminology.hl7.org/CodeSystem/sex-parameter-for-clinical-use"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.4.642.4.2038"/>
  </identifier>
  <version value="2.0.0"/>
  <name value="SexParameterForClinicalUseCS"/>
  <title value="Sex Parameter For Clinical Use"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2024-11-19T17:21:55+00:00"/>
  <publisher value="Health Level Seven International"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://hl7.org"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="hq@HL7.org"/>
    </telecom>
  </contact>
  <description
               value="A summary parameter that provides guidance on how a receiver should apply settings or reference ranges that are derived from observable information such as an organ inventory, recent hormone lab tests, genetic testing, menstrual status, obstetric history, etc.."/>
  <copyright
             value="This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html"/>
  <caseSensitive value="true"/>
  <content value="complete"/>
  <property>
    <code value="usage-note"/>
    <uri
         value="http://terminology.hl7.org/CodeSystem/sex-parameter-for-clinical-use/property/usage-note"/>
    <description value="Usage notes for the concept."/>
    <type value="string"/>
  </property>
  <concept>
    <code value="female-typical"/>
    <display value="Apply female-typical setting or reference range"/>
    <definition
                value="Available data indicates that diagnostics, analytics, and treatments should consider best practices associated with female reference populations."/>
  </concept>
  <concept>
    <code value="male-typical"/>
    <display value="Apply male-typical setting or reference range"/>
    <definition
                value="Available data indicates that diagnostics, analytics, and treatments should consider best practices associated with male reference populations."/>
  </concept>
  <concept>
    <code value="specified"/>
    <display value="Apply specified setting or reference range"/>
    <definition
                value="Available data indicates that diagnostics, analytics, and treatment best practices may be undefined or not aligned with sex-derived reference populations. Additional information may be available in the form of comments and/or observations. The terms &quot;Other&quot; or &quot;Complex&quot; may be considered synonyms of &quot;Specified&quot;."/>
    <property>
      <code value="usage-note"/>
      <valueString
                   value="Individuals or systems providing care should either use default behavior that is safe for both male and female populations, individually review treatment options with the patient, or carefully inspect comments and relevant observations before proceeding with treatment. Systems that are unable to review additional information may manage a SPECIFIED and an UNKNOWN value in the same way."/>
    </property>
  </concept>
</CodeSystem>