STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). 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: R4 R3

V3-ActClassSupply.xml

Raw XML (canonical form)

Supply orders and deliveries are simple Acts that focus on the delivered product. The product is associated with the Supply Act via Participation.typeCode="product". 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.

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="v3-ActClassSupply"/>
  <meta>
    <lastUpdated value="2016-03-31T08:01:25.570+11:00"/>
    <profile value="http://hl7.org/fhir/StructureDefinition/valueset-shareable-definition"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2>ActClassSupply</h2>
      <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>
      <p>This value set includes codes from the following code systems:</p>
      <ul>
        <li>Include codes from 
          <a href="../../v3/ActClass/cs.html">http://hl7.org/fhir/v3/ActClass</a> where concept  is-a  
          <a href="../../v3/ActClass/cs.html#SPLY">SPLY</a>
        </li>
      </ul>
    </div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid">
    <valueUri value="urn:oid:2.16.840.1.113883.1.11.11535"/>
  </extension>
  <url value="http://hl7.org/fhir/ValueSet/v3-ActClassSupply"/>
  <version value="2014-03-26"/>
  <name value="ActClassSupply"/>
  <status value="active"/>
  <experimental value="false"/>
  <publisher value="HL7 v3"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://www.hl7.org"/>
    </telecom>
  </contact>
  <description value=" 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."/>
  <compose>
    <include>
      <system value="http://hl7.org/fhir/v3/ActClass"/>
      <filter>
        <property value="concept"/>
        <op value="is-a"/>
        <value value="SPLY"/>
      </filter>
    </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.