Skip to content
GearDock

Documentation

Introduction

What GearDock does, who it is for, and what it deliberately does not do.

Last updated

GearDock turns incomplete medical product data and source documents into complete, source-backed product content that a person has reviewed and approved before it leaves the system.

Who It Is For

GearDock is built for organizations that sell medical equipment, whether new, refurbished, demo, or reconditioned, and that keep catalogs large enough that writing content by hand never finishes.

  • Medical equipment sellers with catalogs held in spreadsheets and partial records.
  • Refurbished and demo dealers who need unit condition kept separate from device facts.
  • Catalog and eCommerce teams responsible for attribute completeness and publishing.
  • Compliance and review teams accountable for what a published claim rests on.

What It Does

You provide product data, usually a spreadsheet with manufacturers, model numbers, and prices, plus whatever source documents you hold. GearDock identifies the products, organizes the evidence, reports what is missing, drafts the catalog content, routes it through human review, and prepares released content for export.

What It Deliberately Does Not Do

  • It does not approve its own drafts. Review is a human decision with no automatic path around it.
  • It does not publish live listings on its own. Export produces drafts and packages, and release state is re-checked at export time.
  • It does not fill a gap that no evidence supports. Unsupported attributes stay visible as gaps.
  • It does not provide regulatory, legal, or clinical approval of any kind.
  • It is not a system for patient data. Protected health information must not be uploaded.

Traceability Is Not a Correctness Guarantee

GearDock records what a statement was based on. A manufacturer document can still contain an error, and an extraction can misread a dense table. What traceability provides is the ability to find such errors and correct every affected product at once.

Something here unclear or out of date? Tell us Documentation gaps are worth more to us than feature requests.