Who Owns the Innovation? Gordon Gould’s Laser Patent and the Legal Foundations of a Health-Tech Company

The founder paid the developer. The prototype works. The pitch deck says the company owns the technology. None of those facts, standing alone, establishes who owns the patent rights, source code, training materials, or underlying data – or whether the product may legally be marketed for its proposed clinical use.

A health-tech company’s assets rarely fit inside one neat definition of ‘intellectual property.’ Patent inventorship, assignments, copyright in contractor-created work, trade-secret protections, access to clinical data, FDA status, and sales relationships may all be governed by different rules. An investor’s diligence request can expose a gap that never appeared in the product demonstration.

The story of Gordon Gould is a sharp illustration. A laser-related patent, U.S. Patent No. 4,704,583, issued on November 3, 1987, during a much longer struggle over laser inventions and patent rights. Gould’s history is not the story of a single patent creating the entire laser industry. It is a reminder that the commercial promise of a technical breakthrough and the legal ability to control it are separate matters. ^[1]^[2]

Patent ownership is a documentation issue from day one

Federal patent law treats patents as personal property and provides that patents and patent applications can be assigned through a written instrument. Section 261 of Title 35 is a fundamental starting point. The USPTO’s Manual of Patent Examining Procedure distinguishes assignments, which convey ownership interests, from licenses, which provide rights of use within defined limits. These distinctions affect the right to exclude competitors, license territories, enforce claims, and make representations to investors or counterparties. ^[3]^[4]

For a health-tech business, every inventor and development entity must be identified. That includes a founder working before incorporation, a university laboratory, a consulting engineer, or a clinical advisor who contributes to an inventive concept. Counsel should examine employment agreements, invention-assignment provisions, consulting contracts, collaboration agreements, funding arrangements, and any retained rights. A cap table is not an IP ownership chart. Owning stock in the company is different from conveying an invention to the company.

Agreements should also distinguish existing background technology from new project inventions. A developer may bring previously written code or know-how to a project. The company may need a perpetual, transferable license to that background material without pretending to acquire all the contractor’s unrelated intellectual property. On the other hand, new deliverables and project-specific inventions may need to be assigned to the company upon creation, with cooperation obligations for future filings. What is appropriate depends on the deal and applicable law.

“Work made for hire” does not solve every problem

The phrase “work made for hire” is often pasted into consulting contracts as a supposedly universal solution. Under federal copyright law, however, the statutory definition applies to works prepared by employees within the scope of employment and to certain specifically enumerated commissioned categories when the parties make a signed written agreement. The Copyright Office explains these limitations. Most important, copyright’s work-made-for-hire concept is not a substitute for a patent assignment. ^[5]

A medical device developer may create drawings, software, an algorithm, prototypes, testing protocols, and marketing materials. Different rights may attach to each deliverable. The contract should explicitly cover copyright assignment where necessary, rights in improvements and derivative works, patent assignment and filing cooperation, moral-rights waivers where legally appropriate, trade-secret protection, open-source software obligations, and permitted reuse of generic know-how. Broad language without an actual inventory of deliverables invites disputes about what the company purchased.

Healthcare companies should also consider data rights. Access to de-identified or patient-derived datasets can be limited by HIPAA, contracts, research approvals, consent, and other laws. Saying in a development agreement that the company “owns all data” does not supersede those restrictions. The ability to train, commercialize, or share an analytic model using data requires its own rights analysis.

Trade secrets need operational protection, not just an NDA

Not every valuable innovation should or can be protected through a patent. A pricing algorithm, source code architecture, manufacturing process, proprietary distribution list, or clinical workflow may derive commercial value from remaining secret. The federal Defend Trade Secrets Act permits a civil action in specified circumstances involving trade secrets connected to interstate or foreign commerce. But an organization must be able to demonstrate that information was protected by reasonable measures and that it qualifies as a trade secret. ^[6]

A confidentiality provision is a start, not a complete program. Limit access to information by role, label sensitive files, control third-party repositories, implement offboarding procedures, and maintain records showing who accessed what. For remote teams and 1099 contractors, offboarding should include return or deletion of materials, revocation of credentials, transfer of work product, and confirmation that company-controlled systems retain the authoritative versions.

There is also an important distinction between protecting genuine trade secrets and attempting to prevent ordinary professional mobility. Overbroad restrictions can be difficult to enforce and can harm recruiting or business relationships. The appropriate mechanism depends on the state and on whether the legitimate concern is confidentiality, customer solicitation, ownership, or competition.

Regulatory authorization is a separate asset and constraint

A health-tech startup cannot stop at intellectual property. A patent is not FDA authorization, and a regulatory clearance or approval does not by itself establish patent ownership. The business should evaluate whether its product is a medical device, a drug, a biologic, an HCT/P, a clinical service, or a combination of regulated activities. Classification controls what evidence, manufacturing systems, claims, labeling, and postmarket duties may apply.

For device companies, the FDA’s revised Quality Management System Regulation became effective February 2, 2026. The regulation applies to finished device manufacturers covered by its terms and incorporates ISO 13485:2016 into the updated Part 820 framework. A product-development agreement should assign responsibility for design records, supplier management, document retention, complaint escalation, and assistance during inspections as appropriate to each party’s role. A short contractor form may be insufficient for critical design or quality-system work. ^[7]

Commercialization agreements should also control promotional claims. FDA guidance explains that a seller or distributor may create labeling obligations when it intends a device for uses beyond those intended by the original supplier. An exclusive territory provision should therefore never be read as authorization to invent additional clinical indications or Medicare reimbursement claims. ^[8]

The 1099 sales model can threaten an otherwise sound invention

Even where ownership and FDA status are well documented, a commercial arrangement may create federal healthcare fraud-and-abuse exposure. Suppose a medical device or wound-care product company hires independent contractors whose compensation depends on placements or orders at Medicare-billing clinics. The commercial case for commissions is obvious, but the federal Anti-Kickback Statute analysis cannot be reduced to a label such as “marketing services.”

The personal-services and management-contract safe harbor at 42 C.F.R. 1001.952(d) includes requirements concerning a signed written contract, a term of at least one year, services specified in the agreement, compensation methodology set in advance, fair market value, and restrictions on taking account of the volume or value of federal program business. Whether a particular arrangement is protected requires careful attention to the facts and to the safe harbor’s full text. Falling outside a safe harbor does not automatically mean an arrangement violates the statute, but it eliminates a common basis for regulatory certainty. ^[9]

The company should specify the representative’s authority, approved statements, pricing approval, use of samples, financial arrangements with clinicians, expense reimbursement, data access, and escalation obligations. Where physicians also advise the company, serve as inventors, or hold ownership interests, counsel should evaluate the roles separately. Compensation for bona fide product-development services is not the same thing as a payment to induce ordering, and a contract should make the distinction demonstrable.

An outside-general-counsel checklist for an innovation company

A company preparing to hire its first sales team or enter a new market should map its assets and dependencies before promising exclusivity. Begin with a chain-of-title schedule of patents, applications, software, trade secrets, trademarks, data rights, regulatory submissions, and third-party licenses. Note which rights are owned outright, licensed, jointly developed, or unresolved. Then review all founders’ agreements, developer contracts, advisory engagements, and key supplier documents against that schedule.

Next, create a product-classification and claims matrix. Identify the regulatory category for each offering, permitted intended use, approval or clearance status if relevant, ownership of labeling, and the individual responsible for product changes. Link every sales presentation and website claim to an approved source. Then review the money: commissions, consulting fees, royalties, reseller margins, reimbursement representations, and any transfers of value to clinicians or their affiliates.

Finally, negotiate the exit before the relationship begins. If a founder departs, a contractor is terminated, or a distributor fails, the company must still control credentials, source files, technical records, customer communications, and regulatory correspondence. The agreement should allocate transition assistance, confidential information, and continuing cooperation in reasonable detail. Good contracts make separation manageable rather than merely declaring that the company may terminate on thirty days’ notice.

Make ownership provable before diligence begins

Signed assignments, clear contractor terms, documented invention provenance, protected trade secrets, and an accurate regulatory strategy are more than tidy paperwork. They allow a company to explain to an investor, clinical partner, distributor, or acquirer why its rights and commercial claims are defensible.

Gould’s history shows the friction that can arise when invention and legal control travel on different timelines. Before hiring the next developer or granting the next distribution right, identify the assets the company depends on and confirm that the necessary ownership, licenses, permissions, and records follow the work.

Authorities and Further Reading

General information only; not legal advice. Legal rules and payer policies should be verified for the specific facts and date of service.