Profile Comparison between http://hl7.org/fhir/StructureDefinition/preferredTerminologyServer vs http://hl7.org/fhir/StructureDefinition/preferredTerminologyServer

Left:Preferred Terminology Server (http://hl7.org/fhir/StructureDefinition/preferredTerminologyServer)
Right:Preferred Terminology Server (http://hl7.org/fhir/StructureDefinition/preferredTerminologyServer)

Messages

Metadata

NameValueComments
abstractfalse
    baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Extension
      copyright
        descriptionIndicates the terminology server(s) that are known to be capable of returning and potentially expanding the value set(s) associated with the resource or a particular portion of the resource (depending on where the extension appears). If a full URL is not provided AND the requested query is a terminology operation (e.g. $lookup or $expand) the client SHOULD execute the operation against (one of) the preferredTerminologyServer(s) rather than the local repository. Systems SHOULD evaluate value sets using terminology servers as follows: First, try any terminology servers declared on the element in question. If there are more then one, try them in the order they appear. Then try any servers that appear on ancestor elements in order of closest ancestor up to any on the resource root If there are no declared servers or none of the ones listed provide a useful response, the form filler may then try any of the typical servers it would normally use. A 'useful response' means a response that provides a valid (though potentially empty) expansion. Clients MAY wish to log/report errors returned by terminology servers.
          experimental
            fhirVersion5.0.0
              jurisdiction
                jurisdiction / jurisdiction[0]http://unstats.un.org/unsd/methods/m49/m49.htm#001
                  kindcomplex-type
                    namePreferredTerminologyServer
                      publisherHL7 International / FHIR Infrastructure
                        purposeNot all terminology servers will necessarily have access to the codes. If a questionnaire points to value sets, the rendering engine needs to know where to get a current expansion.
                          statusactive
                            titlePreferred Terminology Server
                              typeExtension
                                urlhttp://hl7.org/fhir/StructureDefinition/preferredTerminologyServer

                                  Structure

                                  NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                                  Extension 0..*ExtensionPreferred terminology server
                                  0..*ExtensionPreferred terminology server
                                    Extension.id 0..1idUnique id for inter-element referencing0..1idUnique id for inter-element referencing
                                      Extension.Slices for extension 0..0Extension
                                      Slice: Unordered, Open by value:url

                                      Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them
                                      0..0Extension
                                      Slice: Unordered, Open by value:url

                                      Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them
                                        Extension.url 1..1uri"http://hl7.org/fhir/StructureDefinition/preferredTerminologyServer"1..1uri"http://hl7.org/fhir/StructureDefinition/preferredTerminologyServer"
                                          Extension.value[x] 0..1urlValue of extension0..1urlValue of extension

                                            doco Documentation for this format