Teriparatide
ATLPD0000096
Product-level evidence profile for identity, peptide link, PK exposure, clinical context, safety context, label material, and reproducible data access.
Formulation context: Injection, solution
- ADMETatlas IDATLPD0000096
- Peptide-link statusLinked peptide identity
- Linked peptides1
- Routesubcutaneous
- PK summaries14
- Trial references33
- Label references1
Product evidence profile
Product identity, peptide link, PK exposure evidence, safety context, clinical and label context, interpretation boundaries, and reproducibility exits available for this product.
What is this product, which peptide does it map to, and what is its structure?
What is the drug used for and how does it act?
Are there curated exposure / PK summaries?
What safety, postmarketing, and immune-recognition signals surround the product?
What trial and product-label context is attached to this product?
How is the evidence scoped, traced, cited, and reopened?
One. Molecular identity & structure
What the product is: its names and identifiers, the reviewed peptide identity it maps to, and that peptide's chemical / 3D structure.
Identity
Teriparatide
ATLPD0000096This product identity anchors product-level label, trial, postmarketing, and PK context. Route, form, and holder fields are shown when they are normalized from product or label references, not inferred from the product name.
- Product name
- Teriparatide
- ADMETatlas product ID
- ATLPD0000096
- Aliases / marketed names
- FORTEOBONSITY
- Sponsor / label holder
- Eli Lilly and Company
- Route
- subcutaneous
- Dosage form / class
- Injection, solution
These anchors support product-level lookup and context attachment. They are identity evidence, not ADMET endpoint measurements.
- H05AA02 · teriparatide
ATC classification © WHO Collaborating Centre for Drug Statistics Methodology; used unmodified for non-commercial research.
Linked peptide identity
Product-level label, safety, trial, and PK context may be read beside the linked peptide identity. Endpoint truth still remains controlled by endpoint-specific evidence and compatibility rules.
The public link view emphasizes sequence, identity role, reference support, and interpretation boundary rather than non-public peptide identifiers.
- Identity role
- Reference identity
- Sequence
- SVSEIQLMHNLGKHLNSMERVEWLRKKLQDVHNF
- Residue length
- 34 residues
- Reference support
- 2 supporting references
Multiple linked identities can reflect reviewed source-sequence differences, variant entries, or precursor-like entries. Use the reference identity as the main product-context link.
Link reference trace2 references
| Linked identity | Reference | Link review |
|---|---|---|
| Reference identity | Not linked | Linked peptide identity |
| Reference identity | Not linked | Linked peptide identity |
The link supports product-context interpretation beside a peptide identity. It is not a measured endpoint, and it does not promote label, safety, or trial context into peptide-level endpoint truth by itself.
Structure shown for the reviewed peptide identity linked to this product (ATLPC0009758). Experimental / model 3D coordinate references; use the reference selector to compare.
A 2D graph describes connectivity, not conformation; a 3D reference describes one coordinate model, not the full ensemble.
Open linked peptide · ATLPC0009758Two. Pharmacology: indication & mechanism
What the drug is used for and how it acts — curated therapeutic indications and mechanism of action for the linked molecule.
Indication & mechanism of action
Three. Pharmacokinetics & exposure
Curated exposure / PK summaries — absorption, half-life, clearance, volume of distribution — with cited measurements.
Pharmacokinetics & exposure
Source-backed exposure properties with measurement trace
Human label-derived PK is separated from supporting literature and nonclinical contexts, so users can distinguish product-label exposure statements from broader source-backed observations.
Label-sourced human exposure properties are shown first because they usually carry the most direct product-context interpretation.
Literature, database, or nonclinical observations remain visible as supporting evidence instead of being blended with human label summaries.
Sparse PK summaries do not average across species, units, route, dose, matrix, population, or source context. The cited measurements remain the reproducibility layer for interpreting each summary.
Four. Safety & immunogenicity
Regulatory safety warnings, postmarketing and nonclinical safety context, and immune-recognition context. These describe available signals, not incidence rates or causality.
Safety & immunogenicity
Five. Clinical & regulatory evidence
Clinical-trial context and structured product-label references attached by product identity.
Clinical & regulatory evidence
Six. Provenance, scope & access
How to read, trace, cite, and reopen this profile: evidence scope, reference lineage, and reproducible data access.
Evidence scope
Evidence roles stay separate before interpretation
Endpoint summaries, product-context lanes, identity links, and source references answer different questions. This boundary keeps the page useful without converting context into stronger claims than the current review layer supports.
Use module 3 when comparing PK summaries or cited measurements.
Use module 4 for label, trial, safety, immune, and nonclinical context.
Linked peptide identity
Comparable measurement layer
Endpoint-level interpretation when context fields match.
Pooled product parameters across mismatched species, units, route, dose, matrix, population, or source context.
Clinical, label, safety, immune, and nonclinical context
Reading the product's evidence surroundings and source-backed context lanes.
Incidence rates, causality claims, product safety ranking, or normalized ADMET endpoint values.
Product-to-peptide interpretation gate
Whether product context can be read beside a reviewed peptide identity.
Automatic transfer of every product-level signal to peptide-level endpoint evidence.
Reproducibility and source trace
Checking where labels, trials, safety reports, identity links, and curated measurements came from.
A substitute for normalized evidence, context grouping, or endpoint review.
Original-source reading path
Reading the source reference in its native regulatory, registry, literature, or source context.
Bypassing ADMETatlas curation status, interpretation boundaries, or endpoint-promotion policy.
Reference lineage
Source families are separated by scientific role
Label, trial, safety, immune, identity-link, and PK evidence enter the product profile through different review paths. This module keeps their roles visible so users can trace evidence without over-reading context counts.
active reference families
link reference traces
PK plus context entries
current product profile
Regulatory product-label context
Label sections, label-derived PK statements, safety wording, route, formulation, and immunogenicity context when extracted.
Label material supports product context. It becomes endpoint evidence only through the reviewed PK or endpoint extraction path.
Human study-registration context
Trial identity, phase/status, intervention matching, and availability of results context around the product.
Trial registry entries are study context unless endpoint-compatible results are extracted and reviewed separately.
Safety surveillance context
Signal-aware reading of reported adverse-event context around marketed products.
Report counts do not establish causality, incidence, or comparative product safety.
Assay and nonclinical support context
Immune-recognition assays, nonclinical safety context, and neighboring signals that help interpret the product profile.
These entries are not clinical incidence or endpoint truth unless a review policy promotes a specific endpoint.
Product-peptide identity support
Reviewed product-to-peptide linkage and context propagation decisions.
Link references support identity interpretation, not measured ADMET endpoint values.
Endpoint measurement trace
Rechecking source values, units, route, dose, matrix, population, and source context for PK summaries.
PK entries remain context-bound measurements and should not be pooled across incompatible contexts.
Link references and selected label entries carry direct source links. Product-context entries may instead carry source labels and curated summaries in the structured profile. Both are provenance, but only direct reference fields should be displayed as citation links.
This profile also retains 30 regulatory evidence entries and 0 immunogenicity-context entries in the structured product profile.
Data access & citation
The structured profile access reopens the same product view used by this page, including identity, peptide link, PK evidence trace, context lanes, and reference lineage for the current public release.
public product profile
identity link scope
cited measurement trace
product-context entries
label plus link traces
Use the product profile access for product-specific reproducibility. Use full-release downloads for catalog-scale analysis, with the current source policy and data dictionary.
Current product
Machine-readable profile for identity, peptide link, PK evidence summaries, context signals, and reference lineage.
Uses the public ATL product ID in the URL. Non-public product identifiers remain outside the navigation label.
The request returns the structured product profile used by this page. It is the current product-specific reproducibility path while product-only tabular exports remain a release follow-up.
curl -sS 'https://admetatlas.scbdd.com/products/ATLPD0000096' \
-H 'accept: application/json' \
-H 'X-Visibility: public_release'Use this module to reproduce the current product profile and locate full-release exports. Cross-product comparison still depends on compatible endpoint, species, route, dose, matrix, population, source, identity-link, and review context.