<StructureDefinition xmlns="http://hl7.org/fhir">
  <id value="CodeableConcept-ca-ps" />
  <url value="http://fhir.infoway-inforoute.ca/io/psca/StructureDefinition/CodeableConcept-ca-ps" />
  <version value="2.2.0" />
  <name value="CodeableConceptPSCA" />
  <title value="Codeable Concept (PS-CA)" />
  <status value="draft" />
  <experimental value="false" />
  <date value="2022-02-25T01:23:00-08:00" />
  <description value="This profile represents the constraints applied to the CodeableConcept data type by the PS-CA project to use the [PS-CA Coding](http://fhir.infoway-inforoute.ca/io/psca/StructureDefinition/Coding-ca-ps) data type profile and removes the overarching expectation that all patient summary creators must demonstrate they can support codings for conformance." />
  <copyright value="Copyright © 2024+ Canada Health Infoway. All rights reserved. [Terms of Use and License Agreements](https://ic.infoway-inforoute.ca/en/about/tou). [Privacy Policy](https://www.infoway-inforoute.ca/en/legal/privacy-policy)." />
  <fhirVersion value="4.0.1" />
  <kind value="complex-type" />
  <abstract value="false" />
  <type value="CodeableConcept" />
  <baseDefinition value="http://hl7.org/fhir/StructureDefinition/CodeableConcept" />
  <derivation value="constraint" />
  <differential>
    <element id="CodeableConcept">
      <path value="CodeableConcept" />
      <comment value="For all CodeableConcepts, at least one of coding or text must be present. If coding contains only a display value (no code) then CodeableConcept must include text." />
    </element>
    <element id="CodeableConcept.coding">
      <path value="CodeableConcept.coding" />
      <comment value="While the IPS-UV specification considers this a Must Support element, some systems will not have the ability to support codings for every codeableConcept, further feedback is required on whether these systems are still expected to be able to demonstrate they can construct this element when developing the patient summary instance.&#xD;&#xA;&#xD;&#xA;Implementers that support codings should still send the codings for codeable concepts if they are available and receivers should not produce failures or rejections if codings are included in the patient summary in the first release (a base tenet of FHIR).&#xD;&#xA;&#xD;&#xA;Additionally vendors should expect that some jurisdictions may further constrain support of this element within the context of their own jurisdictional content" />
      <type>
        <code value="Coding" />
        <profile value="http://fhir.infoway-inforoute.ca/io/psca/StructureDefinition/Coding-ca-ps" />
      </type>
    </element>
    <element id="CodeableConcept.text">
      <extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-translatable">
        <valueBoolean value="true" />
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/obligation">
        <extension url="code">
          <valueCode value="SHALL:able-to-populate" />
        </extension>
        <extension url="actor">
          <valueCanonical value="http://hl7.org/fhir/io/psca/ActorDefinition/Producer" />
        </extension>
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/obligation">
        <extension url="code">
          <valueCode value="SHALL:no-error" />
        </extension>
        <extension url="actor">
          <valueCanonical value="http://hl7.org/fhir/io/psca/ActorDefinition/Consumer" />
        </extension>
      </extension>
      <path value="CodeableConcept.text" />
      <mustSupport value="true" />
    </element>
  </differential>
</StructureDefinition>