Trust and transparency

Editorial, sources and corrections policy

This policy explains how technical procurement content is prepared, reviewed, updated, corrected, and kept separate from commercial influence.

Last reviewed: July 10, 2026

Vendor-neutral requirements

Content begins with clinical need, site readiness, maintainability, evidence, and lifecycle value rather than manufacturer marketing.

Traceable source hierarchy

Current regulations, standards, and device claims should be checked against official regulators, standards bodies, WHO guidance, and current manufacturer documentation.

Cautious technical wording

Model-specific values and regulatory claims are not presented as universal. Uncertainty is stated and local professional verification is required.

Commercial separation

Advertising, directory placement, consulting, and sponsorship must not determine technical conclusions or suppress material procurement risks.

Content development and review

Equipment pages are structured around intended use, workflow, technical requirements, utilities, accessories, interoperability, safety, acceptance, maintenance, service, training, warranty, and total cost where those topics are relevant. Reusable templates support consistency, but device-family details should be reviewed individually before procurement use.

Published content is educational and does not replace the review of qualified biomedical engineers, clinical users, facilities, information technology, infection prevention, radiation safety, legal counsel, or local regulators.

Source and citation standard

Priority sources are official regulators and government publications, WHO and recognized public-health bodies, standards organizations, peer-reviewed literature, and current manufacturer technical documentation. A standard number, certification, performance value, or compatibility claim should not be inferred when the source does not support it.

Updates and review dates

Material updates should record a review date. Pages involving regulation, cybersecurity, software, standards, or changing product capabilities require more frequent verification than stable engineering principles. A date indicates review activity, not a guarantee that every external requirement remains current.

Corrections

Readers may report factual errors, outdated references, ambiguous clauses, unsafe wording, attribution concerns, or commercial conflicts. Correction requests should identify the page, disputed text, reason, and supporting source. Substantive corrections should be made promptly and transparently; disagreements that require specialist review should be marked for manual assessment.

AI-assisted drafting

Automation may support outlines, consistency checks, and draft procurement wording. It must not be treated as an authority for technical specifications, standards, regulatory status, clinical claims, or model compatibility. Human professional review remains required before operational use.

Submit a correction

Include the page URL and an authoritative source where possible.

Contact the editorial desk