Scope, prerequisites and deliverables

This document only describes the process to create a request in the Endpoint Registration Service for Service Registration (Party Key/ASID) and End Point certificates. 

This guide does not cover requests for new manufacturer products to be registered; this process will continue to be implemented via the Manufacturer Product Version (MPV) form.

1. A smartcard with the ‘Endpoint Administrator’ role at the relevant manufacturer organisation in the required environment. 
2. N3 connected PC with smartcard reader and GAC client configured to authenticate to Spine CIS.
3. Registry settings for the required environment, which can be obtained from the Assurance Support website if required.
4. Access to an up-to-date web browser as older browsers may not support use of the EPR application. for example, Microsoft Internet Explorer 7.
5. The IP Address(es) of the local MHS.
6. The Fully Qualified Domain Name (FQDN) of the local MHS.
7. The name and ODS code of the recipient organisation. In the Spine Integration, Spine Development and Spine Training environments this code should be allocated to the manufacturer by the Test Data Team.
8. The Product name and version number of the required product. 
9. The URL binding(s) required for the service(s).
10. For End Point Certificate Requests only: Certificate Signing Request (CSR) file with the common name (cn) set to the FQDN when creating the CSR.

1. Party Key and/or ASID
2. A zip file containing the certificate (the certificate can be extracted from the zip file when required).