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

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="R5-v3-ActClassSupply-for-R4B"/>
  <text>
    <status value="generated"/><div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ValueSet R5-v3-ActClassSupply-for-R4B</b></p><a name="R5-v3-ActClassSupply-for-R4B"> </a><a name="hcR5-v3-ActClassSupply-for-R4B"> </a><p>This value set expansion contains 2 concepts.</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>System</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style="white-space:nowrap"><a name="R5-v3-ActClassSupply-for-R4B-http://terminology.hl7.org/CodeSystem/v3-ActClass-SPLY"> </a>  <a href="http://terminology.hl7.org/6.5.0/CodeSystem-v3-ActClass.html#v3-ActClass-SPLY">SPLY</a></td><td>http://terminology.hl7.org/CodeSystem/v3-ActClass</td><td>supply</td><td><div><p>Supply orders and deliveries are simple Acts that focus on the delivered product. The product is associated with the Supply Act via Participation.typeCode=&quot;product&quot;. With general Supply Acts, the precise identification of the Material (manufacturer, serial numbers, etc.) is important. Most of the detailed information about the Supply should be represented using the Material class. If delivery needs to be scheduled, tracked, and billed separately, one can associate a Transportation Act with the Supply Act. Pharmacy dispense services are represented as Supply Acts, associated with a SubstanceAdministration Act. The SubstanceAdministration class represents the administration of medication, while dispensing is supply.</p>
</div></td></tr><tr><td style="white-space:nowrap"><a name="R5-v3-ActClassSupply-for-R4B-http://terminology.hl7.org/CodeSystem/v3-ActClass-DIET"> </a>  <a href="http://terminology.hl7.org/6.5.0/CodeSystem-v3-ActClass.html#v3-ActClass-DIET">DIET</a></td><td>http://terminology.hl7.org/CodeSystem/v3-ActClass</td><td>diet</td><td><div><p>Diet services are supply services, with some aspects resembling Medication services: the detail of the diet is given as a description of the Material associated via Participation.typeCode=&quot;product&quot;. Medically relevant diet types may be communicated in the Diet.code attribute using domain ActDietCode, however, the detail of the food supplied and the various combinations of dishes should be communicated as Material instances.</p>
<p><strong>Deprecation Note</strong></p>
<p><strong>Class:</strong> Use either the Supply class (if dealing with what should be given to the patient) or SubstanceAdministration class (if dealing with what the patient should consume)</p>
<p><strong>energyQuantity:</strong> This quantity can be conveyed by using a Content relationship with a quantity attribute expressing the calories</p>
<p>**carbohydrateQuantity:**This quantity can be conveyed using a Content relationship to an Entity with a code of carbohydrate and a quantity attribute on the content relationship.</p>
</div></td></tr></table></div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="fhir"/>
  </extension>
  <extension url="http://hl7.org/fhir/StructureDefinition/package-source">
    <extension url="packageId">
      <valueId value="hl7.fhir.uv.xver-r5.r4b"/>
    </extension>
    <extension url="version">
      <valueString value="0.0.1-snapshot-2"/>
    </extension>
  </extension>
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="0">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical value="http://hl7.org/fhir/5.0/ImplementationGuide/hl7.fhir.uv.xver-r5.r4b"/>
      </extension>
    </valueInteger>
  </extension>
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical value="http://hl7.org/fhir/5.0/ImplementationGuide/hl7.fhir.uv.xver-r5.r4b"/>
      </extension>
    </valueCode>
  </extension>
  <url value="http://hl7.org/fhir/5.0/ValueSet/R5-v3-ActClassSupply-for-R4B"/>
  <version value="0.0.1-snapshot-2"/>
  <name value="R5_v3_ActClassSupply_for_R4B"/>
  <title value="Cross-version VS for R5.ActClassSupply for use in FHIR R4B"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2025-09-01T22:37:04.457452+10:00"/>
  <publisher value="FHIR Infrastructure"/>
  <contact>
    <name value="FHIR Infrastructure"/>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/fiwg"/>
    </telecom>
  </contact>
  <description value="This cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-ActClassSupply|2.0.0 for use in FHIR R4B. Concepts not present here have direct `equivalent` mappings crossing all versions from R5 to R4B."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
  <compose>
    <include>
      <system value="http://terminology.hl7.org/CodeSystem/v3-ActClass"/>
      <version value="3.1.1"/>
      <concept>
        <code value="SPLY"/>
        <display value="supply"/>
      </concept>
      <concept>
        <code value="DIET"/>
        <display value="diet"/>
      </concept>
    </include>
  </compose>
  <expansion>
    <timestamp value="2025-09-01T22:37:04.457452+10:00"/>
    <contains>
      <system value="http://terminology.hl7.org/CodeSystem/v3-ActClass"/>
      <version value="3.1.1"/>
      <code value="SPLY"/>
      <display value="supply"/>
    </contains>
    <contains>
      <system value="http://terminology.hl7.org/CodeSystem/v3-ActClass"/>
      <version value="3.1.1"/>
      <code value="DIET"/>
      <display value="diet"/>
    </contains>
  </expansion>
</ValueSet>