z-logo
Premium
Enantioseparation of aromatic amino acids and amino acid esters by capillary electrophoresis with crown ether and prediction of enantiomer migration orders by a three‐dimensional quantitative structure‐property relationship/comparative field analysis model
Author(s) -
Park HyunJu,
Choi Youngmie,
Lee Wonjae,
Kim KyoungRae
Publication year - 2004
Publication title -
electrophoresis
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.666
H-Index - 158
eISSN - 1522-2683
pISSN - 0173-0835
DOI - 10.1002/elps.200405963
Subject(s) - enantiomer , chemistry , amino acid , capillary electrophoresis , quantitative structure–activity relationship , steric effects , crown ether , stereochemistry , chromatography , organic chemistry , ion , biochemistry
The complete enantioseparations of eight aromatic amino acids and four alkyl esters of 2‐phenylglycine were achieved by chiral capillary electrophoresis employing 20 m M Tris‐citric acid background electrolyte (pH 2.50) containing 5.0 m M of (+)‐18‐crown‐6‐tetracarboxylic acid. The relative migration times (RMTs) to that of 6‐aminonicotinic acid were characteristic of each enantiomer with good within‐day precisions (% relative standard deviation (RSD) ≤ 2.0). Quantitative structure‐property relationship (QSPR) modeling based on comparative molecular field analysis (CoMFA) was performed to investigate the correlation between the molecular field descriptor values of each enantiomer studied as analyte and its RMT. The resulting CoMFA model allowed reliable prediction for the RMT values ( q 2 = 0.406, r 2 = 0.996), thus being expected to become a valuable tool to predict enantiomer migration orders (EMOs) of amino acids and amines whose pure enantiomers are unavailable. The CoMFA steric fields supported the well‐established chiral recognition mechanism based on molecular interaction between chiral selector (+)‐18‐crown‐6‐tetracarboxylic acid and amino acid enantiomers.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here