Publication standard
Editorial and health-content policy
These are prospective publication standards for content released or restored after August 31, 2026. They do not claim that earlier content met this gate.
01
Editorial policy
Public content must separate verified facts from plans, examples, and unresolved claims. Code presence alone does not establish that a feature is active, approved, or commercially available.
A content owner must record material claims, their sources, required approvals, and the exact language approved for publication. Unsupported claims stay unpublished or noindex until the record is complete.
02
Health Content Review Policy
Health, medical, scientific, numerical, testing, interpretation, or behavioral guidance requires claim-level evidence review. A named qualified reviewer must review the exact version when the subject requires clinical expertise, and the reviewer’s credentials and scope must be recorded.
A review credit appears only after that person completes the review. CoreSignal does not use placeholder authors, reviewers, credentials, or dates.
03
Evidence and Source Standards
Material health claims should use primary sources where available. References must support the wording and population described on the page; a citation is not approval for a broader or more certain claim.
Publication records distinguish source publication dates, material review dates, and material modification dates. Build or deployment time is not a content date.
04
Corrections Policy
A material correction must preserve a dated description of what changed and why. A correction that changes clinical meaning, product truth, legal meaning, or evidence scope returns the page to the relevant review gate before republication.
Readers may report a possible error through the contact route. Do not send medical records, lab reports, passwords, one-time codes, or urgent health information by email.
05
Product-Claim Review Policy
A product claim needs evidence for the current approved public product—not only a source file, test fixture, prototype, internal document, or planned integration. Commercial, legal, privacy, security, clinical, AI, and integration claims also need their named owner’s approval when applicable.
Pricing, subscription, trial, refund, regulated-status, vendor-contract, clinical-authority, and outcome claims remain unpublished unless direct authority is recorded.
