/**
 * compliesWithProfile — derived StructureDefinition compliance check.
 *
 * When an SD carries the `structuredefinition-compliesWithProfile` extension,
 * it claims that every constraint of the named parent profile is at least as
 * strictly carried by this derived profile. Java enforces this with one
 * `business-rule` error per detected non-compliance:
 *
 *   "This profile does not comply with claimed profile '<url>' because:
 *    The min value of '0' on the path Patient.name does not comply with the
 *    value '1' from the claimed profile"
 *
 * Records emits the same diagnostics for the conformance fixture set:
 * cardinality (loosened min, widened max, max=0 forcing effective min=0),
 * missing constraints, weakened binding strength, ValueSet inequality
 * for required/extensible bindings (cw-binding-superset, conservative
 * URL-equality heuristic — full expansion intersection is upstream
 * follow-up), slicing rule and presence mismatches, and CodeableConcept
 * pattern/fixed conflicts. The snapshot generator-driven cw-slice-adds
 * remains pending.
 */
import type { ValidationIssue } from '../types';
import type { StructureDefinitionLoader } from '../core/structure-definition-loader';
export declare class CompliesWithValidator {
    private sdLoader;
    constructor(sdLoader: StructureDefinitionLoader);
    validate(sd: any, fhirVersion?: 'R4' | 'R5' | 'R6'): Promise<ValidationIssue[]>;
    private loadClaimedProfile;
}
//# sourceMappingURL=complies-with-validator.d.ts.map