Release 5 Preview #1

This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). 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 R3 R2

Valueset-focal-subject.xml

Vocabulary Work GroupMaturity Level: N/AStandards Status: Informative

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

Definition for Value SetFocal Subject Codes

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

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="focal-subject"/> 
  <meta> 
    <lastUpdated value="2019-12-31T21:03:40.621+11:00"/> 
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2> Focal Subject Codes</h2> 
      <div> 
        <p> Example value set composed from SNOMED CT and HL7 V3 codes for observation targets such
           as donor, fetus or spouse. As use cases are discovered, more values may be added.</p> 

      </div> 
      <p> 
        <b> Copyright Statement:</b>  This resource includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright
         of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers
         of these specifications must have the appropriate SNOMED CT Affiliate license - for more
         information contact http://www.snomed.org/snomed-ct/get-snomed-ct or info@snomed.org
      </p> 
      <p> This value set includes codes from the following code systems:</p> 
      <ul> 
        <li> Include these codes as defined in 
          <a href="http://www.snomed.org/">
            <code> http://snomed.info/sct</code> 
          </a> 
          <table class="none">
            <tr> 
              <td style="white-space:nowrap">
                <b> Code</b> 
              </td> 
              <td> 
                <b> Display</b> 
              </td> 
            </tr> 
            <tr> 
              <td> 
                <a href="http://browser.ihtsdotools.org/?perspective=full&amp;conceptId1=83418008">83418008</a> 
              </td> 
              <td> Fetus</td> 
              <td/>  
            </tr> 
          </table> 
        </li> 
        <li> Include these codes as defined in 
          <a href="v3/ParticipationType/cs.html">
            <code> http://terminology.hl7.org/CodeSystem/v3-ParticipationType</code> 
          </a> 
          <table class="none">
            <tr> 
              <td style="white-space:nowrap">
                <b> Code</b> 
              </td> 
              <td> 
                <b> Display</b> 
              </td> 
            </tr> 
            <tr> 
              <td> 
                <a href="v3/ParticipationType/cs.html#v3-ParticipationType-DON">DON</a> 
              </td> 
              <td> donor</td> 
              <td> In some organ transplantation services and rarely in transfusion services a donor will
                 be a target participant in the service.  However, in most cases transplantation is decomposed
                 in three services: explantation, transport, and implantation.  The identity of the donor
                 (recipient) is often irrelevant for the explantation (implantation) service.</td> 
            </tr> 
          </table> 
        </li> 
        <li> Include these codes as defined in 
          <a href="v3/RoleCode/cs.html">
            <code> http://terminology.hl7.org/CodeSystem/v3-RoleCode</code> 
          </a> 
          <table class="none">
            <tr> 
              <td style="white-space:nowrap">
                <b> Code</b> 
              </td> 
              <td> 
                <b> Display</b> 
              </td> 
            </tr> 
            <tr> 
              <td> 
                <a href="v3/RoleCode/cs.html#v3-RoleCode-SPS">SPS</a> 
              </td> 
              <td> spouse</td> 
              <td> The player of the role is a marriage partner of the scoping person.</td> 
            </tr> 
          </table> 
        </li> 
      </ul> 
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="oo"/> 
  </extension> 
  <url value="http://hl7.org/fhir/ValueSet/focal-subject"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.3.954"/> 
  </identifier> 
  <version value="4.2.0"/> 
  <name value="FocalSubjectCodes"/> 
  <title value="Focal Subject Codes"/> 
  <status value="draft"/> 
  <experimental value="false"/> 
  <date value="2019-12-31T21:03:40+11:00"/> 
  <publisher value="HL7 International - Orders and Observations WG"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org/fhir"/> 
    </telecom> 
  </contact> 
  <description value="Example value set composed from SNOMED CT and HL7 V3 codes for observation targets such
   as donor, fetus or spouse. As use cases are discovered, more values may be added."/> 
  <copyright value="This resource includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright
   of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers
   of these specifications must have the appropriate SNOMED CT Affiliate license - for more
   information contact http://www.snomed.org/snomed-ct/get-snomed-ct or info@snomed.org"/> 
  <compose> 
    <include> 
      <system value="http://snomed.info/sct"/> 
      <concept> 
        <code value="83418008"/> 
        <display value="Fetus"/> 
      </concept> 
    </include> 
    <include> 
      <system value="http://terminology.hl7.org/CodeSystem/v3-ParticipationType"/> 
      <concept> 
        <code value="DON"/> 
        <display value="donor"/> 
      </concept> 
    </include> 
    <include> 
      <system value="http://terminology.hl7.org/CodeSystem/v3-RoleCode"/> 
      <concept> 
        <code value="SPS"/> 
        <display value="spouse"/> 
      </concept> 
    </include> 
  </compose> 
</ValueSet> 

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.