import { Extension } from './Extension.js';
import { FhirPrimitive } from './FhirPrimitive.js';
import { Resource } from './Resource.js';
export interface Bundle_Entry_Response {
    /**
     * @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 status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.
     * @short Status response code (text optional)
     */
    status: FhirPrimitive<string>;
    /**
     * @description The location header created by processing this operation, populated if the operation returns a location.
     * @short The location (if the operation returns a location)
     */
    location?: FhirPrimitive<string>;
    /**
     * @description The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http.html#versioning) and [Managing Resource Contention](http.html#concurrency)).
     * @comment Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.
     * @short The Etag for the resource (if relevant)
     */
    etag?: FhirPrimitive<string>;
    /**
     * @description The datetime that the resource was modified on the server.
     * @comment This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.
     * @short Server's date time modified
     */
    lastModified?: FhirPrimitive<string>;
    /**
     * @description An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction.
     * @comment For a POSTPUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
  
  This outcome is not used for error responses in batchtransaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.
     * @short OperationOutcome with hints and warnings (for batchtransaction)
     */
    outcome?: Resource;
}
//# sourceMappingURL=Bundle_Entry_Response.d.ts.map