{
  "description": "Data Element for Reference.identifier",
  "_filename": "StructureDefinition-de-Reference.identifier.json",
  "package_name": "hl7.fhir.r4b.elements",
  "date": "2022-05-28T12:47:40+10:00",
  "derivation": "specialization",
  "meta": {
    "lastUpdated": "2022-05-28T12:47:40.239+10:00"
  },
  "publisher": "HL7 FHIR Standard",
  "fhirVersion": "4.3.0",
  "purpose": "Data Elements are defined for each element to assist in questionnaire construction etc",
  "name": "Reference.identifier",
  "mapping": [ {
    "uri": "http://hl7.org/v3",
    "name": "RIM Mapping",
    "identity": "rim"
  } ],
  "abstract": false,
  "type": "Reference.identifier",
  "experimental": "true",
  "resourceType": "StructureDefinition",
  "title": "Reference.identifier",
  "package_version": "4.3.0",
  "snapshot": {
    "element": [ {
      "path": "Reference.identifier",
      "min": 0,
      "definition": "An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.",
      "isModifier": false,
      "short": "Logical reference, when literal reference is not known",
      "mapping": [ {
        "map": ".identifier",
        "identity": "rim"
      } ],
      "type": [ {
        "code": "Identifier"
      } ],
      "max": "1",
      "id": "Reference.identifier",
      "comment": "When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. \n\nWhen both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference\n\nApplications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.\n\nReference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference.  For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport).  One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).",
      "base": {
        "max": "1",
        "min": 0,
        "path": "Reference.identifier"
      },
      "isSummary": true
    } ]
  },
  "status": "draft",
  "id": "d32b3ab1-93e7-44c0-93b1-b033480650af",
  "kind": "logical",
  "url": "http://hl7.org/fhir/StructureDefinition/de-Reference.identifier",
  "version": "4.3.0",
  "contact": [ {
    "telecom": [ {
      "value": "http://hl7.org/fhir",
      "system": "url"
    } ]
  } ],
  "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Element"
}