MétaCan
Menu
Back to cohort
Record W3103321439 · doi:10.3390/pharmaceutics12111095

Manufacturing Considerations for the Development of Lipid Nanoparticles Using Microfluidics

2020· article· en· W3103321439 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenuePharmaceutics · 2020
Typearticle
Languageen
FieldBiochemistry, Genetics and Molecular Biology
TopicRNA Interference and Gene Delivery
Canadian institutionsPrecision Nanosystems (Canada)
FundersEngineering and Physical Sciences Research CouncilCancer Research UK
KeywordsDispersityMicrofluidicsChemistryNanoparticleNanotechnologyBuffer (optical fiber)Payload (computing)Nucleic acidParticle sizeChromatographyMaterials scienceComputer scienceBiochemistryOrganic chemistry

Abstract

fetched live from OpenAlex

In the recent of years, the use of lipid nanoparticles (LNPs) for RNA delivery has gained considerable attention, with a large number in the clinical pipeline as vaccine candidates or to treat a wide range of diseases. Microfluidics offers considerable advantages for their manufacture due to its scalability, reproducibility and fast preparation. Thus, in this study, we have evaluated operating and formulation parameters to be considered when developing LNPs. Among them, the flow rate ratio (FRR) and the total flow rate (TFR) have been shown to significantly influence the physicochemical characteristics of the produced particles. In particular, increasing the TFR or increasing the FRR decreased the particle size. The amino lipid choice (cationic-DOTAP and DDAB; ionisable-MC3), buffer choice (citrate buffer pH 6 or TRIS pH 7.4) and type of nucleic acid payload (PolyA, ssDNA or mRNA) have also been shown to have an impact on the characteristics of these LNPs. LNPs were shown to have a high (>90%) loading in all cases and were below 100 nm with a low polydispersity index (≤0.25). The results within this paper could be used as a guide for the development and scalable manufacture of LNP systems using microfluidics.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.039
Threshold uncertainty score0.221

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.155
GPT teacher head0.351
Teacher spread0.196 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it