import { Annotation } from './Annotation.js';
import { CodeableConcept } from './CodeableConcept.js';
import { CodeableReference } from './CodeableReference.js';
import { ContactPoint } from './ContactPoint.js';
import { Count } from './Count.js';
import { DeviceDefinition } from './DeviceDefinition.js';
import { Device_ConformsTo } from './Device_ConformsTo.js';
import { Device_Name } from './Device_Name.js';
import { Device_Property } from './Device_Property.js';
import { Device_UdiCarrier } from './Device_UdiCarrier.js';
import { Device_Version } from './Device_Version.js';
import { Duration } from './Duration.js';
import { Endpoint } from './Endpoint.js';
import { Extension } from './Extension.js';
import { FhirPrimitive } from './FhirPrimitive.js';
import { Identifier } from './Identifier.js';
import { Location } from './Location.js';
import { Meta } from './Meta.js';
import { Narrative } from './Narrative.js';
import { Organization } from './Organization.js';
import { Reference } from './Reference.js';
import { Resource } from './Resource.js';
export interface Device {
    /**
     * @description The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
     * @comment Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
     * @short Logical id of this artifact
     */
    id?: string;
    /**
     * @description The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
     * @short Metadata about the resource
     */
    meta?: Meta;
    /**
     * @description A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
     * @comment Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers andor specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
     * @short A set of rules under which this content was created
     */
    implicitRules?: FhirPrimitive<string>;
    /**
     * @description The base language in which the resource is written.
     * @comment Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies  to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
     * @short Language of the resource content
     */
    language?: FhirPrimitive<string>;
    /**
     * @description A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
     * @comment Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
     * @short Text summary of the resource, for human interpretation
     */
    text?: Narrative;
    /**
     * @description These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides contextmeaning.
     * @comment This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
     * @short Contained, inline Resources
     */
    contained?: Resource[];
    /**
     * @description May be used to represent additional information that is not part of the basic definition of the resource. 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 resource and that modifies the understanding of the element that contains it 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 is allowed to 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
     */
    modifierExtension?: Extension[];
    /**
     * @description Unique instance identifiers assigned to a device by manufacturers other organizations or owners.
     * @comment Certain attributes, like serial number and UDI Carrier (the HRF or AIDC barcode string) are not device instance identifiers as they are not consistently able to uniquely identify the instance of a device, thus are not appropriate to be used to value Device.identifier. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used. The identifier is typically valued if the serialNumber or lotNumber is not valued and represents a different type of identifier.  However, it is permissible to still include those identifiers in DeviceDefinition.identifier with the appropriate identifier.type.
     * @short Instance identifier
     */
    identifier?: Identifier[];
    /**
     * @description The name used to display by default when the device is referenced. Based on intent of use by the resource creator, this may reflect one of the names in Device.name, or may be another simple name.
     * @short The name used to display by default when the device is referenced
     */
    displayName?: FhirPrimitive<string>;
    /**
     * @description The reference to the definition for the device.
     * @short The reference to the definition for the device
     */
    definition?: CodeableReference<DeviceDefinition>;
    /**
     * @backbone Nested BackboneElement: udiCarrier [0..*]
     */
    udiCarrier?: Device_UdiCarrier[];
    /**
     * @description The Device record status. This is not the status of the device like availability.
     * @short active | inactive | entered-in-error
     */
    status?: FhirPrimitive<string>;
    /**
     * @description The availability of the device.
     * @short lost | damaged | destroyed | available
     */
    availabilityStatus?: CodeableConcept;
    /**
     * @description An identifier that supports traceability to the event during which material in this product from one or more biological entities was obtained or pooled.
     * @comment Necessary to support mandatory requirements for traceability from donorsource to recipient and vice versa, while also satisfying donor anonymity requirements. The element is defined consistently across BiologicallyDerivedProduct, NutritionProduct, and Device.  The identifier references an event that links to a single biological entity such as a blood donor, or to multiple biological entities (e.g. when the product is an embryo or a pooled platelet product).  A single biologicalSourceEvent identifier may appear on multiple products of many types derived from a single donation event or source extraction.  As an example, a single donation event may provide 2 kidneys and a liver for organ transplantation, 2 corneas for eye surgery, heart valves and arterial tissue for cardiovascular surgery, multiple skin grafts, tendons, multiple shaped bone grafts and a large number of bone puttypaste products; and each of them may be assigned to the same biological source event identifier.
     * @short An identifier that supports traceability to the event during which material in this product from one or more biological entities was obtained or pooled
     */
    biologicalSourceEvent?: Identifier;
    /**
     * @description A name of the manufacturer or entity legally responsible for the device.
     * @short Name of device manufacturer
     */
    manufacturer?: FhirPrimitive<string>;
    /**
     * @description The date and time when the device was manufactured.
     * @short Date when the device was made
     */
    manufactureDate?: FhirPrimitive<string>;
    /**
     * @description The date and time beyond which this device is no longer valid or should not be used (if applicable).
     * @short Date and time of expiry of this device (if applicable)
     */
    expirationDate?: FhirPrimitive<string>;
    /**
     * @description Lot number assigned by the manufacturer.
     * @short Lot number of manufacture
     */
    lotNumber?: FhirPrimitive<string>;
    /**
     * @description The serial number assigned by the organization when the device was manufactured.
     * @comment Alphanumeric Maximum 20. While a serial number is a type of identifier, in the context of devices for which a UDI is required, thus a serial number may be part of the production identifier, it is more informative to have the serial number as a dedicated attribute together with the other UDI production identifier.  When the device is not subject to including the UDI (e.g., its presence and exchange is not mandated by local regulatory requirements or specific use case at hand), thus the concept of production identifiers is not relevant as a set, it remains helpful for consistency to still use Device.serialNumber rather than using Device.identifier with an appropriate type.  Systems that do not realize an identifier is a serial number may place it in Device.identifier or if the identifier.system is known for the serial number, it may also be populated in the Device.identifier as a globally unique id_.
     * @short Serial number assigned by the manufacturer
     */
    serialNumber?: FhirPrimitive<string>;
    /**
     * @backbone Nested BackboneElement: name [0..*]
     */
    name?: Device_Name[];
    /**
     * @description The manufacturer's model number for the device.
     * @short The manufacturer's model number for the device
     */
    modelNumber?: FhirPrimitive<string>;
    /**
     * @description The part number or catalog number of the device.
     * @comment Alphanumeric Maximum 20.
     * @short The part number or catalog number of the device
     */
    partNumber?: FhirPrimitive<string>;
    /**
     * @description Devices may be associated with one or more categories.
     * @short Indicates a high-level grouping of the device
     */
    category?: CodeableConcept[];
    /**
     * @description The kind or type of device. A device instance may have more than one type - in which case those are the types that apply to the specific instance of the device.
     * @comment Multiple device types are use when a device is categorized in more than one context – for example, hybrid devices in which the device is both of type gateway and sensor.
     * @short The kind or type of device
     */
    type?: CodeableConcept[];
    /**
     * @backbone Nested BackboneElement: version [0..*]
     */
    version?: Device_Version[];
    /**
     * @backbone Nested BackboneElement: conformsTo [0..*]
     */
    conformsTo?: Device_ConformsTo[];
    /**
     * @backbone Nested BackboneElement: property [0..*]
     */
    property?: Device_Property[];
    /**
     * @description The designated condition for performing a task with the device.
     * @short The designated condition for performing a task
     */
    mode?: CodeableConcept;
    /**
     * @description The series of occurrences that repeats during the operation of the device.
     * @short The series of occurrences that repeats during the operation of the device
     */
    cycle?: Count;
    /**
     * @description A measurement of time during the device's operation (e.g., days, hours, mins, etc.).
     * @short A measurement of time during the device's operation (e.g., days, hours, mins, etc.)
     */
    duration?: Duration;
    /**
     * @description An organization that is responsible for the provision and ongoing maintenance of the device.
     * @short Organization responsible for device
     */
    owner?: Reference<Organization>;
    /**
     * @description Contact details for an organization or a particular human that is responsible for the device.
     * @comment used for troubleshooting etc.
     * @short Details for humanorganization for support
     */
    contact?: ContactPoint[];
    /**
     * @description The place where the device can be found.
     * @short Where the device is found
     */
    location?: Reference<Location>;
    /**
     * @description A network address on which the device may be contacted directly.
     * @comment If the device is running a FHIR server, the network address should  be the Base URL from which a conformance statement may be retrieved.
     * @short Network address to contact device
     */
    url?: FhirPrimitive<string>;
    /**
     * @description Technical endpoints providing access to services provided by the device defined at this resource.
     * @short Technical endpoints providing access to electronic services provided by the device
     */
    endpoint?: Reference<Endpoint>[];
    /**
     * @description The linked device acting as a communication controller, data collector, translator, or concentrator for the current device (e.g., mobile phone application that relays a blood pressure device's data).
     * @comment The Device.gateway may be used when the Device being referenced has a gateway andor to capture one or more gateways associated with the device. If the Gateway is included in the Observation resource, the Observation.gatewayDevice should be used instead.
     * @short Linked device acting as a communicationdata collector, translator or controller
     */
    gateway?: CodeableReference<Device>[];
    /**
     * @description Descriptive information, usage information or implantation information that is not captured in an existing element.
     * @short Device notes and comments
     */
    note?: Annotation[];
    /**
     * @description Provides additional safety characteristics about a medical device.  For example devices containing latex.
     * @short Safety Characteristics of Device
     */
    safety?: CodeableConcept[];
    /**
     * @description The higher level or encompassing device that this device is a logical part of.
     * @comment For example a vital signs monitor (parent) where three separate modules can be plugged into such as interchangeable blood pressure, oximeter, temperature modules.  These modules are represented as devices with the .parent valued to the vital signs monitor when plugged in.
     * @short The higher level or encompassing device that this device is a logical part of
     */
    parent?: Reference<Device>;
    /**
     * @const Auto-injected fixed value: Device
     */
    resourceType: "Device";
}
//# sourceMappingURL=Device.d.ts.map