Who Owns the Source Code? 17 Questions to Ask a Healthcare Software Vendor
Leo Chelliah | 13 Nov 2026 Business & Operations Healthcare Technology

Who Owns the Source Code? 17 Questions to Ask a Healthcare Software Vendor

Founders often assume that if they paid for software, they own it. Clinic owners often assume that the patient data in a system they pay for is theirs to take away. Both assumptions can be wrong, and the time to find out is before you sign. This guide explains what “owning” healthcare software can mean, the arrangements you will be offered, and the questions that protect you. It is general information, not legal advice. Have a lawyer read any contract.

Four different things people mean by “ownership”

  1. The intellectual property. Who legally owns the code and may sell or license it.
  2. The source code itself. Whether you hold a copy you could hand to another developer.
  3. The data. Patient records, appointments, invoices.
  4. The accounts. The domain, hosting, payment gateway, messaging and store accounts the service runs on.

You can own any of these without the others. A founder who owns the IP on paper, but whose code sits in an agency’s repository on the agency’s servers, owns very little in practice.

The arrangements you will be offered

Arrangement Who owns the code What you get Watch for
SaaS subscription The vendor Use of the product while you pay Data export, price rises, what happens if the vendor closes
White-label licence The vendor The product under your brand The same, plus who owns your custom features
Source code licence The vendor, with a licence to you A copy of the code to run and modify Limits on resale, updates, number of deployments
Custom development with assignment You, once paid Everything written for you The vendor’s reusable components and third-party parts
Open source The project’s contributors Freedom to use and modify under the licence Licence duties when you distribute changes

None of these is wrong. A clinic rarely needs source code. A startup raising investment usually needs clear rights to what makes it different. Match the arrangement to what you are building.

Questions about the code

  1. Who owns the IP in work done for us, and when does it transfer? “On full payment” is normal. “Never” should be a deliberate choice, with a lower price.
  2. What existing code of yours is included, and on what licence? Most agencies start from their own base. You need a permanent licence to use it inside your product.
  3. Which third-party and open-source components are used? Ask for a list with licences. Some open-source licences place duties on you.
  4. Where is the repository, and do we have access now? Not “at the end of the project”. Now.
  5. Can another team build and deploy it from the repository alone? Ask for build instructions and documentation as deliverables.
  6. May we modify it, hire others to work on it, and sell the business with it?
  7. May you reuse what you built for us for our competitors? Often yes for general features. Negotiate exclusivity only for what is truly yours.

Questions about the data

  1. Do we own our data, in writing?
  2. Can we export all of it, in a usable format, at any time? Ask to see an export.
  3. What does export cost, and how long does it take?
  4. What happens to our data when the contract ends? How long is it kept, and how is it deleted?
  5. Where is it hosted, and who are your subprocessors?
  6. Will you sign a BAA or data processing agreement?

Questions about accounts and continuity

  1. In whose name are the domain, hosting, payment and messaging accounts? They should be in yours wherever possible. A payment account in the vendor’s name means your revenue passes through them.
  2. What if you stop trading or drop the product? For licensed software, ask about source code escrow, where a third party releases the code to you in defined events.
  3. What notice must you give of price changes?
  4. What help will you give if we leave? A paid handover period should be in the contract.

Warning signs

  • “You own everything” said in a meeting and absent from the contract.
  • No access to the repository during the project.
  • Hosting and store accounts in the agency’s name “for convenience”.
  • No list of third-party components.
  • Export available “on request” with no format, time or price.
  • A licence that ends your right to use custom features you paid for if you stop the subscription.

What is reasonable to expect

Be fair to vendors as well. A platform company cannot give every customer ownership of the product it sells to all of them. That would end its business and yours with it. Reasonable positions are:

  • the vendor owns the platform;
  • you own your data, your brand and your content;
  • custom features are either owned by you or licensed to you permanently, as agreed;
  • source code is available at a price for those who need it;
  • you can leave with your data.

How it works with Doccure

  • Data. Your data belongs to you.
  • Payments. Online patient payments run through your own Stripe account, so the money is yours from the start. Card data never touches Doccure servers. Payments are processed by PCI-compliant gateways.
  • Messaging. SMS and WhatsApp use your own provider account.
  • Source code. Enterprise offers custom scope, custom deployment, on-premise installation and source code.
  • Agreements. Doccure is HIPAA-ready and GDPR-ready. We sign a BAA.
  • Interfaces. Standards-based FHIR and HL7 interfaces for connecting to other systems.

Ask us the seventeen questions above. We would rather answer them before the contract than after.

Frequently asked questions

If I pay for custom software, do I own it automatically?

Not necessarily. In many countries the author owns the code unless the contract assigns it. Get the assignment in writing.

Do I need the source code?

A clinic usually does not. A funded startup, or an organisation that must host on its own servers, often does.

What is source code escrow?

An arrangement in which a neutral third party holds the code and releases it to you if defined events occur, such as the vendor ceasing to trade.

Who owns patient data in a SaaS system?

That is set by the contract and by data protection law. Insist on a clause that the data is yours and can be exported.

Can I get Doccure’s source code?

Yes, with Enterprise.

Ask us before you sign anything

See our custom development service and the Trust Center, or book a 30-minute call and bring the list.

Previous Post A HIPAA and GDPR Checklist for Founders Before You Write a Line of Code Next Post How to Build a Paediatric or Dental Finder Platform