Blagoveschensk, undefined

Grigory M Rutenburg

This inventor holds 1 USPTO granted patent. Top assignee: Other. Active years: 1988.

IDiyas Innovation Intelligence. (2026). Inventor Profile: Grigory M Rutenburg. Retrieved from https://idiyas.com/inventor/grigory-m-rutenburg

Data source: USPTO (United States Patent and Trademark Office) public patent records. Weekly synchronization. How IDiyas builds this profile

Calculating rank

% Patents Active = 100.0

Average Co-Inventor Count = 3.0

ph-index = 1

Forward Citations = 114(Granted Patents)


Company Filing History:

goldMedal1 out of 834,601 
Other
 patents

Years Active: 1988

Loading Chart...
1 patent (USPTO):Explore Patents

Title: Grigory M. Rutenburg and His Wound Retractor Invention.

Introduction

Grigory M. Rutenburg was an inventor associated with Blagoveshchensk, SU. His recorded patent concerns a wound retractor designed to hold an opening apart during a procedure.

Latest Patents

Rutenburg’s listed patent is titled “Wound retractor.” It describes a split tube made of two halves, with holders and a spreading mechanism that includes a retainer to lock the halves in position. One holder is a plate with an oblong opening, while the other is a strip that slides over the plate; each tube half is positioned along the edge of its holder’s opening. The record lists 1 patent for Rutenburg.

Career Highlights

The available information identifies Rutenburg’s invention but does not provide further details about his career or professional affiliations.

Collaborations

Yaroslav P. Kulik and Ivan I. Shmyrin are listed as Rutenburg’s coworkers. The available information does not specify their roles in developing the wound retractor.

Conclusion

Grigory M. Rutenburg’s recorded contribution is a patented wound retractor featuring adjustable, lockable tube halves intended to maintain an opening.

Profile summary based on public USPTO records.
Data Sources: USPTO Patent Grant XML, Patent Center, EPO & CIPO • Normalized by IDiyas Innovation Graph. Methodology & provenance architecturePlease report any incorrect information to [email protected]
Loading…