10.46243/jst.2020.v5.i5.pp85-89 registered
Co-Processed Excipients- A Review
Resolves to https://www.jst.org.in/index.php/pub/article/view/300
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2020.v5.i5.pp85-89
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 181957119c051a96…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
Co-Processed Excipients- A Review (PrincipalTitle)
Published 2020-10-11
Part of Journal of Science & Technology · ISSN 2456-5660 · issue Volume 5 · pages 85–89
Agents
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2020.v5.i5.pp85-89
Abstract
Here is no single-component excipient satisfies all the essential execution to permit a active pharmaceutical component to be formulated into a selected dosage form. Co-processed excipient has received substantially more consideration in the definition improvement of different dosage form, uncommonly for tablet preparation by direct compression strategy. The main aim of this review is to talk about the rise of co-processed excipients as a present and future pattern of excipient innovation in pharmaceutical manufacturing. Co-processed excipients is a novel idea of consolidating at least two excipients designed to physical mixing without significant chemical change. These co-processed excipients have high functionalize compared to individual excipients such as better compressibility, flow property. All the developed excipients are enlisted for their beneficial and multifunctional characteristics. Further it gives opportunity for use of single multifunctional excipient rather than multiple excipients.
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jst.2020.v5.i5.pp85-89 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Co-Processed Excipients- A Review (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | publisher: Longman Publishers published: 2020-10-11 part of: Journal of Science & Technology · ISSN 2456-5660 · no. Volume 5 · pp. 85–89 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2020-09-24 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
Recommended for a journal article and not in this record: its author(s), editor(s) or corporate author · the volume number.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 68 fields set · sha256 9444110397ca… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
