PillRight US Source Policy
Last reviewed: June 12, 2026
Source-first rule
The U.S. version should show source-linked summaries and clear interpretation boundaries. It should not publish copied label pages, unsourced safety claims, or NDC-only approval assumptions.
Internal database boundary
- DailyMed, RxNorm, Drugs@FDA, and Orange Book are the internal database baseline for reviewed U.S. drug records.
- openFDA label and NDC data are identifier and retrieval helpers, not standalone medical or approval evidence.
- MedlinePlus is an outbound patient education link source only; licensed monographs, encyclopedia text, images, and third-party material should not be copied into the PillRight database.
Official sources and usage
DailyMed
U.S. National Library of Medicine
Primary source for Structured Product Labeling sections, label dates, warnings, indications, dosage, and patient medication guides.
Internal DB allowed
Store normalized SPL identifiers, dates, section labels, and source-linked summaries; avoid presenting copied label pages as PillRight-authored medical advice.
Open official sourceRxNorm
U.S. National Library of Medicine
Concept identity layer for ingredients, clinical drugs, brand names, and related RxCUI mappings.
Internal DB allowed
Use for concept identity and normalization; never treat RxNorm identity alone as approval, availability, or clinical suitability evidence.
Open official sourceDrugs@FDA
U.S. Food and Drug Administration
FDA approval and application context for approved prescription and over-the-counter drug products.
Internal DB allowed
Use application and product context as approval evidence; keep it separate from patient-facing dosage or treatment recommendations.
Open official sourceOrange Book
U.S. Food and Drug Administration
Therapeutic equivalence and application data for products listed in the FDA Orange Book.
Internal DB allowed
Use therapeutic-equivalence and application context; do not convert this into substitution advice for a specific patient.
Open official sourceopenFDA drug labeling
U.S. Food and Drug Administration
Search and retrieval layer for selected labeling fields. Used as a convenience API, not as the only source of truth.
Identifier only
Use as a search and harmonization layer with attribution; do not rely on openFDA alone for medical decisions or approval status.
Open official sourceopenFDA NDC directory
U.S. Food and Drug Administration
Listing and packaging context for NDC records. NDC listing is not treated as proof of FDA approval.
Identifier only
Store NDC listing and packaging pointers only; NDC listing must remain blocked from approval-evidence logic.
Open official sourceMedlinePlus
U.S. National Library of Medicine
Consumer-friendly patient education reference. Use as an outbound source link or context pointer, not as an internal copied content corpus.
Link only
Link to MedlinePlus pages instead of copying monographs, encyclopedia text, images, or third-party licensed material into the internal database.
Open official sourceImportant interpretation boundaries
- DailyMed labeling can include marketed products and label revisions, but page summaries must still cite the specific label used.
- RxNorm helps identify drug concepts, but it does not by itself decide product approval, availability, or clinical suitability.
- Drugs@FDA and Orange Book data should be used for approval and therapeutic-equivalence context when applicable.
- NDC listing and packaging records are not treated as proof that a product is FDA approved.
- Label summaries must tell users to confirm decisions with a clinician, pharmacist, official label, or emergency service when appropriate.