Search loading...


Explore and Make use of Nationally Defined Messaging APIs



Details of how requirements are presented in the GP Connect specification


Where specific mandated requirements exist in the GP Connect Messaging specification, they are presented in the following format:

ID Requirement description

The Requirement ID provides a unique requirement identifier within this specification, as is constructed according to the following format:


The second section, {C|SD|ST|SU} provides a capability identifier where SD refers to Send Document, ST refers to Send Task, SU refers to Send Update. Requirements which apply to all capabilities are indicated by C (common)

The keywords ‘MUST’ and ‘MUST NOT’ on this site are to be interpreted as described in RFC 2119.

Tags: design

All content is available under the Open Government Licence v3.0, except where otherwise stated