Cross-Version Extension for Device.udiCarrier.carrierAIDC in R5

Context of Use

This extension may be used in the following contexts:

Name	Flags	Card.	Type	Description & Constraints
Extension		0..1	Extension	UDI Machine Readable Barcode String
extension		..0
value[x]		1..
url				"http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.udiCarrier.carrierAIDC"
Documentation for this format

{
  "resourceType" : "StructureDefinition",
  "id" : "xv-r5-dev.udi.carrierAIDC",
  "url" : "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.udiCarrier.carrierAIDC",
  "name" : "XVerExtensionDevice.udiCarrier.carrierAIDCR5",
  "title" : "Cross-Version Extension for Device.udiCarrier.carrierAIDC in R5",
  "status" : "active",
  "experimental" : false,
  "publisher" : "Health Level Seven International (Orders and Observations)",
  "contact" : [{
    "telecom" : [{
      "system" : "url",
      "value" : "http://hl7.org/fhir"
    }]
  },
  {
    "telecom" : [{
      "system" : "url",
      "value" : "http://www.hl7.org/Special/committees/orders/index.cfm"
    }]
  }],
  "description" : "Cross-Version Extension for Device.udiCarrier.carrierAIDC. Valid in versions null\r\n\r\nThis is a valid cross-version extension because it has a parent that can be an extension in at least one version",
  "jurisdiction" : [{
    "coding" : [{
      "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
      "code" : "001"
    }]
  }],
  "fhirVersion" : "5.0.0",
  "kind" : "complex-type",
  "abstract" : false,
  "type" : "Extension",
  "baseDefinition" : "http://hl7.org/fhir/StructureDefinition/Extension",
  "derivation" : "constraint",
  "differential" : {
    "element" : [{
      "path" : "Extension",
      "short" : "UDI Machine Readable Barcode String",
      "definition" : "The full UDI carrier of the Automatic Identification and Data Capture (AIDC) technology representation of the barcode string as printed on the packaging of the device - e.g., a barcode or RFID.   Because of limitations on character sets in XML and the need to round-trip JSON data through XML, AIDC Formats *SHALL* be base64 encoded.",
      "comment" : "The AIDC form of UDIs should be scanned or otherwise used for the identification of the device whenever possible to minimize errors in records resulting from manual transcriptions. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.",
      "alias" : ["Automatic Identification and Data Capture"],
      "min" : 0,
      "max" : "1",
      "isModifier" : false,
      "mapping" : [{
        "identity" : "rim",
        "map" : "Role.id.extension"
      },
      {
        "identity" : "udi",
        "map" : "A unique device identifier (UDI) on a device label a form that uses automatic identification and data capture (AIDC) technology."
      }]
    },
    {
      "path" : "Extension.extension",
      "max" : "0"
    },
    {
      "path" : "Extension.value[x]",
      "min" : 1
    },
    {
      "path" : "Extension.url",
      "fixedUri" : "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.udiCarrier.carrierAIDC"
    }]
  }
}