Cross-Version Extension for CapabilityStatement.rest.resource.supportedProfile in R4

Context of Use

This extension may be used in the following contexts:

• element CapabilityStatement.rest.resource (For version R3)
• extension http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.rest.resource
• element Conformance.rest.resource (For version R2)
• extension http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.rest.resource

Name	Flags	Card.	Type	Description & Constraints
Extension		0..*	Extension	Profiles for use cases supported
extension		..0
value[x]		1..	canonical(StructureDefinition)
url				"http://hl7.org/fhir/4.0/StructureDefinition/extension-CapabilityStatement.rest.resource.supportedProfile"
Documentation for this format

{
  "resourceType" : "StructureDefinition",
  "id" : "xv-r4-cpb.res.res.supportedProfile",
  "url" : "http://hl7.org/fhir/4.0/StructureDefinition/extension-CapabilityStatement.rest.resource.supportedProfile",
  "name" : "XVerExtensionCapabilityStatement.rest.resource.supportedProfileR4",
  "title" : "Cross-Version Extension for CapabilityStatement.rest.resource.supportedProfile in R4",
  "status" : "active",
  "experimental" : false,
  "publisher" : "Health Level Seven International (FHIR Infrastructure)",
  "contact" : [{
    "telecom" : [{
      "system" : "url",
      "value" : "http://hl7.org/fhir"
    }]
  },
  {
    "telecom" : [{
      "system" : "url",
      "value" : "http://www.hl7.org/Special/committees/fiwg/index.cfm"
    }]
  }],
  "description" : "Cross-Version Extension for CapabilityStatement.rest.resource.supportedProfile. Valid in versions R2, R3\r\n\r\nThis is a valid cross-version extension because the cardinality changed",
  "jurisdiction" : [{
    "coding" : [{
      "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
      "code" : "001"
    }]
  }],
  "fhirVersion" : "5.0.0",
  "kind" : "complex-type",
  "abstract" : false,
  "context" : [{
    "extension" : [{
      "extension" : [{
        "url" : "startFhirVersion",
        "valueCode" : "3.0"
      },
      {
        "url" : "endFhirVersion",
        "valueCode" : "3.0"
      }],
      "url" : "http://hl7.org/fhir/StructureDefinition/version-specific-use"
    }],
    "type" : "element",
    "expression" : "CapabilityStatement.rest.resource"
  },
  {
    "type" : "extension",
    "expression" : "http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.rest.resource"
  },
  {
    "extension" : [{
      "extension" : [{
        "url" : "startFhirVersion",
        "valueCode" : "1.0"
      },
      {
        "url" : "endFhirVersion",
        "valueCode" : "1.0"
      }],
      "url" : "http://hl7.org/fhir/StructureDefinition/version-specific-use"
    }],
    "type" : "element",
    "expression" : "Conformance.rest.resource"
  },
  {
    "type" : "extension",
    "expression" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.rest.resource"
  }],
  "type" : "Extension",
  "baseDefinition" : "http://hl7.org/fhir/StructureDefinition/Extension",
  "derivation" : "constraint",
  "differential" : {
    "element" : [{
      "path" : "Extension",
      "short" : "Profiles for use cases supported",
      "definition" : "A list of profiles that represent different use cases supported by the system. For a server, \"supported by the system\" means the system hosts/produces a set of resources that are conformant to a particular profile, and allows clients that use its services to search using this profile and to find appropriate data. For a client, it means the system will search by this profile and process data according to the guidance implicit in the profile. See further discussion in [Using Profiles](profiling.html#profile-uses).",
      "comment" : "Supported profiles are different than the profile that applies to a particular resource in .rest.resource.profile. The resource profile is a general statement of what features of the resource are supported overall by the system - the sum total of the facilities it supports. A supported profile is a deeper statement about the functionality of the data and services provided by the server (or used by the client). A typical case is a laboratory system that produces a set of different reports - this is the list of types of data that it publishes. A key aspect of declaring profiles here is the question of how the client converts knowledge that the server publishes this data into working with the data; the client can inspect individual resources to determine whether they conform to a particular profile, but how does it find the ones that do? It does so by searching using the _profile parameter, so any resources listed here must be valid values for the _profile resource (using the identifier in the target profile).",
      "min" : 0,
      "max" : "*",
      "isModifier" : false
    },
    {
      "path" : "Extension.extension",
      "max" : "0"
    },
    {
      "path" : "Extension.value[x]",
      "min" : 1,
      "type" : [{
        "code" : "canonical",
        "targetProfile" : ["http://hl7.org/fhir/StructureDefinition/StructureDefinition"]
      }]
    },
    {
      "path" : "Extension.url",
      "fixedUri" : "http://hl7.org/fhir/4.0/StructureDefinition/extension-CapabilityStatement.rest.resource.supportedProfile"
    }]
  }
}