Secondary Uses Service
CDS Data Sender Registration Form (SR1)
Please return the completed form to bt.sus.helpdesk@bt.com and ask for a call to be
raised.
1. Organisation Details
Organisation Name
(the User)
Organisation
(NACS) Code
EDI Address
Please include variants used for different data flows. Where
a different NACS code is used then please use an additional
form.
DTS ID
(Not necessary for XML
submission)
Organisation Details
Address
Postcode
Date Completed
V1.0 (02/02/07)
Page 1 of 4
SUS CDS Data Sender Registration Form
SR1
2. Contacts for Message Rejection
We will contact the person named below when an interchange fails to be processed by the
SUS Service. During the first phase, this contact will be by e-mail. Please duplicate this
section as necessary if additional contacts are required.
Prime Contact
First Name
Surname
Address
(if different from above)
Postcode
Telephone
E-mail Address
Other Contact 1
First Name
Surname
Address
(if different from above)
Postcode
Telephone
E-mail Address
V1.0 (02/02/07)
Page 2 of 4
SUS CDS Data Sender Registration Form
SR1
3. Notes for Completion
All organisation need to be registered to send data to SUS. If you were registered to send
data to NWCS/Clearnet then you are already registered to send data to SUS.
Please note that this form is in addition to the form necessary to register for PbR managed
service extracts.
You should complete this form if:

You have not sent data before.

You wish to send from a new CDS Interchange Sender Identity (EDIFACT/EDI address).

You wish to change your registered organisation code (e.g. you are a new organisation
using an old CDS Interchange Sender Identity but would like all interchanges to appear
on your tracker under the new organisation code).

You wish to change the contact details for e-mail notification of interchange failure.
Guidance on the XML migration of the CDS data flow is available from:
http://www.connectingforhealth.nhs.uk/sus/reference/sus_cds_xml.pdf
Details required
Organisation Name
Note
The name of the NHS organisation wishing to use
SUS/PbR.
This will be replaced in SUS/PbR with the name
recorded on the Spine Directory Service (SDS) and is
used here to help confirm the code is correct.
Organisation Code
The organisation code that owns the interchange data
sent to SUS. If an organisation sends on behalf of
more than one other organisation this will be covered
separately. Please enter the 3 character NACS/OCS
code. SUS will only distinguish the 4th/5th characters for
non-NHS Providers.
EDI Address
The EDI address to be used in the data flow.
The EDI address is a 15 character string, the first 10
digits identifies the subscriber organisation. The last 5
digits are used to identify different sites within the
organisation. See “The CDS Interchange Sender
Identity” guidance below.
DTS ID (required for EDIFACT
flows only)
The DTS ID for sender and recipient which can be
obtained from NHS net
http://nww.connectingforhealth.nhs.uk/nhais/dts
(note that we recommend that you re-use an existing
address if there is one for your organisation)
3.1 The CDS Interchange Sender Identity
Both EDIFACT and XML flows require a CDS INTERCHANGE SENDER IDENTITY, which is
described in the NHS Data Dictionary at:
http://www.connectingforhealth.nhs.uk/datadictionary/data_dictionary/data_field_notes/c/cds/c
ds_interchange_sender_identity_de.asp?shownav=1
V1.0 (02/02/07)
Page 3 of 4
SUS CDS Data Sender Registration Form
SR1
This comprises a 10 character EDIFACT address and a local 5 character tail that you can
select for yourself. You apply for the 10 character identifier at:
http://www.connectingforhealth.nhs.uk/addressing/registrations/edi-registration
The code is used to manage physical interchange senders, particularly to ensure that
interchanges are processed in sequence, flow blocking following error is also managed at this
level. Most senders use the same 5 character suffix for all data (e.g. 00001.) A few use a
different suffix for different dataset types (APC, OP etc) or for different PAS systems. There
are risks associated with this practice; you should make sure that you fully understand the
update protocols before taking this route.
3.2 SUS Helpdesk
If you have a query about using SUS, you can get help and information via the SUS
Helpdesk: Telephone: 0845 600 2558, E-mail: bt.sus.helpdesk@bt.com
V1.0 (02/02/07)
Page 4 of 4