Private repositories for a Trust

1. Create a GitHub organisation for the Trust

Use an organisation, not a personal account, so the Trust owns the code. Name it clearly, for exampleexample-nhs-trust-integration. Make at least two people owners.

2. Require two-factor authentication

In organisation settings, turn on "Require two-factor authentication" for all members.

3. Create teams

• integration-maintainers — can approve and merge changes.
• integration-developers — can create branches and pull requests.
• readers — suppliers or auditors with read-only access.

4. Create private repositories

One repository per integration domain works well, for example:

tie-pathology-orders      LIMS orders and results
tie-radiology             RIS / PACS orders and reports
tie-adt                   patient administration feeds
tie-medicines             ePMA and pharmacy interfaces
tie-shared                shared code templates, lookups, utilities

Always set the visibility to Private. Never commit passwords, certificates or patient data — use a secrets manager.

5. Suggested repository layout

README.md            what it does, who owns it, how to deploy
docs/                diagrams, mappings, test plans
channels/            TIE exports (one file per channel or route)
transforms/          scripts and mapping code
tests/               sample synthetic messages and expected output
CODEOWNERS           who must review changes