Admission

This part of the iSHARE Scheme is considered normative and is therefore compliant with RFC 2119.


This admission process describes the steps that all parties MUST take to be admitted to the iSHARE network. For Certified Parties, additional steps are required and are described below. The process is the responsibility of, and facilitated by, the Scheme Administrator. 

Admission of prospective ISHARE participant includes:

  • potential Adhering Party wants to start fulfilling one or more adhering role(s) in the network.
  • A potential Certified Party wants to start fulfilling one or more certified roles(s) in the network.
  • An already Adhering and/or Certified Party wants to expand its current role(s) by one or more role(s) in the network.

Note: prospective iSHARE participants can start testing at any moment in time before initiating the admission process.

Goal

The goal of the admission process is to let prospective iSHARE participants join iSHARE in a simple and controlled way. A controlled admission process is important to warrant trust in the iSHARE Scheme. It provides assurance that all parties signing an accession agreement fulfil the scheme's accession criteria. 

Admission criteria

To be admitted to the iSHARE network as a full participant, prospective iSHARE participants need to comply with several criteria*:

  • Provide a signed iSHARE accession agreement;
  • Provide a valid EORI number (or other nationally recognised chamber of commerce number which can be verified);
  • Provide a PKIOverheid Certificate or Qualified Electronic Seal (see PKI) that will be used for iSHARE;
  • Provide a successful test report of iSHARE certification tool.

* For operational reasons, additional admission criteria MAY apply.

Responsibilities

Several parties have responsibilities and tasks in the admission process:

  • The Scheme Administrator is responsible for facilitation of the process while safeguarding the integrity of the iSHARE Scheme;
  • The prospective iSHARE participant is responsible for implementing the guidelines set out in iSHARE, and for showing compliance with the relevant admission criteria. 

Sequence

  1. A representative of the prospective iSHARE participant registers with a Scheme Administratorr and provides the Scheme Administrator with:
    1. Primary contact details: name, role, e-mail.
    2. Description of how they will be using iSHARE
    3. A valid EORI number (or other nationally recognised chamber of commerce number which can be verified);
  2. The Scheme Administrator checks whether there are potential impediments that could block the completion of the admission process for the prospective iSHARE participant:
    1. E.g. previous exclusions from the iSHARE Scheme in the recent past;
  3. The Scheme Administrator will facilitate testing and certification of the prospective iSHARE participant.
    1. The Scheme Administrator may provide testing material and documentation on the Scheme test environment: certificates, keys, SDKs, etc.;
    2. For prospective Certified Parties this will include role-specific non-technical requirements.
  4. The prospective iSHARE participant formally requests admission to the iSHARE network to the Scheme Administrator by providing:
    1. An iSHARE accession agreement signed by an authorized representative of the prospective iSHARE participant;
    2. The technical certificate that will be used for iSHARE;
    3. Acceptable proof that the prospective participant’s technical implementation adheres to iSHARE specifications;
    4. For a prospective Certified Party: The level of assurance for which the prospective Certified Party wants to be certified, accompanied by a filled in Assessment Framework (and related evidence) to prove that the operational processes of the prospective Certified Party comply with the indicated level of assurance. 
      1. If desired, a standard NDA can be signed before providing the Assessment Framework and related evidence. Please request a signed NDA at info@ishareworks.org. 
    5. For prospective Certified Parties additional verification may be required.
  5. The Scheme Administrator verifies the acceptance of the prospective participant's admission request and its conformance with the admission criteria;
    1. For prospective Adhering Parties the Scheme Administrator has 5 working days to verify the acceptance of the prospective participant’s admission request and its conformance with the admission criteria;
    2. For prospective Certified Parties the Scheme Administrator has 30 days to verify the acceptance of the prospective participant's admission request and its conformance with the admission criteria, but aims to respond and soon as possible;
  6. A legal representative of the Scheme Administrator (or Scheme Owner) signs the participant’s iSHARE accession agreement, and communicates the verified acceptance to the new participant;
  7. The Scheme Administrator records the participant’s status within the scheme in the iSHARE participant registry.

Levels of participation

In order to lower initial barriers for participation, a prospective participant may join the iSHARE scheme without meeting all criteria. A possible situation could occur where a party wishes to join iSHARE as a participant, but is not able to meet all technical requirements for data exchange. Instead, the participant will delegate this to an intermediary party (for example, a data hub) that will provide technical data exchange services.

Identity verification level

  • Verified according to publicly available trusted resources

The identity of the party can be verified (eg. EORI, or other internationally verifiable source)

  • Verified by Scheme Administrator

Although this option is not generally recommended, this denotes that the participant is explicitly trusted by the Scheme Administrator that recorded the participants admission.

Legal adherence

  • Legal adherence

The Participant has signed an Accession Agreement AND Terms of Use

  • No legal adherence

The Particpant is trusted by the Scheme Administrator. Note that this indication MAY limit the available options for data sharing for this participant within the iSHARE scheme due to a lower level of legal assurance.

Technical compliance

  • Full technical compliance

Technical compliance was verified by providing a successful test report of iSHARE certification tool.

  • No technical compliance

Technical Compliance has not been verified. Note that this indication WILL limit the available options for data sharing for this participant within the iSHARE scheme, because the participant MUST use another (compliant) participant to handle exchanges on his behalf.