Cts2/EntryDescription.xml

Logical Model EntryDescription

<StructureDefinition xmlns="http://hl7.org/fhir">
  <id value="EntryDescription"/>
  <url value="{http://www.omg.org/spec/CTS2/1.1/Core}EntryDescription"/>
  <name value="EntryDescription"/>
  <display value="CTS2.EntryDescription"/>
  <status value="draft"/>
  <publisher value="Generated by Xsd-to-FHIR"/>
  <contact>
    <name value="Visit the Github repository for more information"/>
    <telecom>
      <system value="other"/>
      <value value="https://github.com/cts2/CTS2-to-FHIR"/>
    </telecom>
  </contact>
  <date value="2016-02-08T19:11:02-07:00"/>
  <description value="EntryDescription is a subclass of OpaqueData. The purpose behind this is that there are
   certain textual fields that some CTS2 service implementations may want constrain. As an
   example,      Designation text is of type \\ EntryDescription, but implementations may
   want to restrict the OpaqueData     value attribute to a simple string rather than xs:anyType.
   When OpaqueData appears directly as a model element, implementations must be able to support
   the full OpaqueData model. EntryDescription,     however, may be constrained by implementations
   or specialized PSMs."/>
  <fhirVersion value="1.4.0"/>
  <kind value="logical"/>
  <abstract value="false"/>
  <baseDefinition value="{http://www.omg.org/spec/CTS2/1.1/Core}OpaqueData"/>
  <snapshot>
    <element>
      <path value="EntryDescription"/>
      <short value="EntryDescription"/>
      <definition value="EntryDescription is a subclass of OpaqueData. The purpose behind this is that there are
       certain textual fields that some CTS2 service implementations may want constrain. As an
       example,      Designation text is of type \\ EntryDescription, but implementations may
       want to restrict the OpaqueData     value attribute to a simple string rather than xs:anyType.
       When OpaqueData appears directly as a model element, implementations must be able to support
       the full OpaqueData model. EntryDescription,     however, may be constrained by implementations
       or specialized PSMs."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="{http://www.omg.org/spec/CTS2/1.1/Core}OpaqueData"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="OpaqueData"/>
      </type>
    </element>
  </snapshot>
</StructureDefinition>