import { ElementDefinition_Slicing_Discriminator } from './ElementDefinition_Slicing_Discriminator.js';
import { Extension } from './Extension.js';
import { FhirPrimitive } from './FhirPrimitive.js';
export interface ElementDefinition_Slicing {
    /**
     * @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[];
    /**
     * @backbone Nested BackboneElement: discriminator [0..*]
     */
    discriminator?: ElementDefinition_Slicing_Discriminator[];
    /**
     * @description A human-readable text description of how the slicing works. If there is no discriminator, this is required to be present to provide whatever information is possible about how the slices can be differentiated.
     * @comment If it's really not possible to differentiate them, the design should be re-evaluated to make the content usable.
     * @short Text description of how slicing works (or not)
     */
    description?: FhirPrimitive<string>;
    /**
     * @description If the matching elements have to occur in the same order as defined in the profile.
     * @comment Order should only be required when it is a pressing concern for presentation. Profile authors should consider making the order a feature of the rules about the narrative, not the rules about the data - requiring ordered data makes the profile much less re-usable.
     * @short If elements must be in same order as slices
     */
    ordered?: FhirPrimitive<boolean>;
    /**
     * @description Whether additional slices are allowed or not. When the slices are ordered, profile authors can also say that additional slices are only allowed at the end.
     * @comment Allowing additional elements makes for a much for flexible template - it's open for use in wider contexts, but also means that the content of the resource is not closed, and applications have to decide how to handle content not described by the profile.
     * @short closed | open | openAtEnd
     */
    rules: FhirPrimitive<string>;
}
//# sourceMappingURL=ElementDefinition_Slicing.d.ts.map