import { Extension } from './Extension.js';
import { FhirPrimitive } from './FhirPrimitive.js';
export interface Device_UdiCarrier {
    /**
     * @description Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
     * @short Unique id for inter-element referencing
     */
    id?: string;
    /**
     * @description May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
     * @comment There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions.  The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
     * @short Additional content defined by implementations
     */
    extension?: Extension[];
    /**
     * @description May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained andor the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
  
  Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
     * @comment There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions.  The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
     * @short Extensions that cannot be ignored even if unrecognized
     */
    modifierExtension?: Extension[];
    /**
     * @description The device identifier (DI) is a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device.
     * @short Mandatory fixed portion of UDI
     */
    deviceIdentifier: FhirPrimitive<string>;
    /**
     * @description Organization that is charged with issuing UDIs for devices. For example, the US FDA issuers include:
  1) GS1: http:hl7.orgfhirNamingSystemgs1-di,
  2) HIBCC: http:hl7.orgfhirNamingSystemhibcc-diI,
  3) ICCBBA for blood containers: http:hl7.orgfhirNamingSystemiccbba-blood-di,
  4) ICCBA for other devices: http:hl7.orgfhirNamingSystemiccbba-other-di # Informationsstelle für Arzneispezialitäten (IFA GmbH) (EU only): http:hl7.orgfhirNamingSystemifa-gmbh-di.
     * @short UDI Issuing Organization
     */
    issuer: FhirPrimitive<string>;
    /**
     * @description The identity of the authoritative source for UDI generation within a jurisdiction. All UDIs are globally unique within a single namespace with the appropriate repository uri as the system. For example, UDIs of devices managed in the U.S. by the FDA, the value is http:hl7.orgfhirNamingSystemus-fda-udi or in the European Union by the European Commission http:hl7.orgfhirNamingSystemeu-ec-udi.
     * @short Regional UDI authority
     */
    jurisdiction?: FhirPrimitive<string>;
    /**
     * @description 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.
     * @short UDI Machine Readable Barcode String
     */
    carrierAIDC?: FhirPrimitive<string>;
    /**
     * @description The full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device.
     * @comment If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.
     * @short UDI Human Readable Barcode String
     */
    carrierHRF?: FhirPrimitive<string>;
    /**
     * @description A coded entry to indicate how the data was entered.
     * @short barcode | rfid | manual | card | self-reported | electronic-transmission | unknown
     */
    entryType?: FhirPrimitive<string>;
}
//# sourceMappingURL=Device_UdiCarrier.d.ts.map