Make product decisions traceable
Connect the catalog number to its intended use, market status, IFU revision, handling instructions, and service route so procurement does not have to infer across disconnected records.
Documentation is part of the device experience
Boston Scientific Work Is Read at the Point of Care and in the Audit Room
Clarity before claims
Where a specification depends on SKU, indication, market, or configuration, state the boundary and route the reader to the controlled source rather than generalizing.
Working principles
Six disciplines behind a usable record
Patient context
Start with intended use, users, environment, and foreseeable misuse.
QMS discipline
Connect the quality system regulation (QSR), design history file (DHF), device master record (DMR), revisions, approvals, distribution, and retirement.
Clinical co-design
Translate workflow constraints into setup and training requirements.
Regulatory precision
Separate cleared, approved, registered, and not-applicable states.
Service closure
Record device identity, work performed, tests, and release status.
Feedback loop
Route complaints, adverse event reporting (MDR), and post-market surveillance (PMS) trend signals into review.
Cross-functional work
One record, multiple readers
A precise handoff matters
Choose a Contact RouteBring a product question to the right discipline
Clinical, regulatory, service, and procurement requests follow different evidence paths.