Getting it

The mechanics, in full.

The framework costs nothing and always will. Access is an invitation to the private repository rather than a download link, so I know who is implementing and can help them. This page is the detail: what the form asks, what the licence covers, and the two things you need in place before you deploy. The invitation itself, and why the cohort exists, is on Get involved.

What access is

A repo invitation, not a zip file.

The code lives in a private GitHub repository. Approved implementers are invited into it, which means you get the full history, tagged releases, an issue tracker to report what broke, and a route to send changes back if you want to. You are not receiving a snapshot that goes stale the week after you get it.

  • CostNothing, now or later. No paid tier, no seat count, no support contract
  • AccessAn invitation to the private repository, after a short conversation
  • LicencePolyForm Internal Use 1.0.0 — deploy and modify it inside your own organisation at no cost; reselling or hosting it for others needs a separate agreement (the detail)
  • Your dataNever leaves your environment. You host it and control what enters it
  • Not open sourceSource-available. The licence withholds the right to resell, and the distinction is set out in full here

What the form asks

Five questions, two minutes.

Nothing is a trick question and nothing is sold on. Here is every field and why it is there.

Who
Your name and an email address I can reply to. That is the whole of it — no phone number.
What
Which of these you are: student · university or research group · clinician or care provider · hospital or health service IT · government health department · medical software vendor · terminology or standards body · independent developer · something else. It sets how technical my reply should be.
Where
Country, and your organisation if you are acting for one. SNOMED CT licensing and health data rules are national, so where you are changes what applies to you.
When
Whether you are reading with interest, evaluating in the next few months, or trying to start now. It decides who I get back to first.
Why
What you would do with it — the records you would point it at, the problem you are trying to solve, the part you think is missing. This is the field I actually read twice.
Then
I reply personally, and if it is a fit, you get the repo invitation. There is no drip campaign, no newsletter, and your details go to no one else.
Open the form Just a quick question?

Before you deploy

Two things that are yours, not mine.

A SNOMED CT licence. The framework ships no terminology content. SNOMED CT is licensed nationally — free at the point of use in member countries including Australia, the UK and the US, and licensed directly elsewhere. You import your own release under your own affiliate licence.

Your clinical and privacy governance. You host it, implement it into your own infrastructure and control what flows into it, so patient data never reaches me — and validation, ethics approval, privacy assessment and regulatory conformance sit with the organisation running it. I can tell you how the pipeline behaves. I cannot sign off your deployment.