Why GitHub for integration code

Integration logic often lives only inside the integration engine (TIE) and in the heads of one or two people. When they leave, or a change goes wrong at 2am, the Trust has no reliable record of what changed, why, or how to roll back.

What a repository gives you

• A full history — every change to a channel, route or transform is recorded with who made it, when, and why.
• Documentation next to the code — README files, diagrams and mappings live with the integration they describe, so they stay current.
• Safe change — changes are reviewed before they reach live systems, and any version can be restored.
• Clinical safety evidence — reviews and history support your DCB0129/DCB0160 hazard logs and change control.
• Less key-person risk — new team members, suppliers and auditors can understand the estate.

Why GitHub

GitHub is the most widely used platform, many NHS organisations already use it, and it includes code review, automation (Actions), issue tracking and security scanning in one place. Private repositories keep Trust code visible only to people you invite.