Skip to end of metadata
Go to start of metadata

Sharing athlete demographic profile

  • An athlete demographic profile is composed of the 4 tabs (demographic, sport/discipline, activities and security). It does not include TUEs, Whereabouts, etc.
  • By default, every organization which has access (explicit or implicit) on an athlete has access to the demographic profile of the athlete.
  • An organization can share access to the demographic profile of any athlete for which they are the custodian organization.

Sharing indicator

  • When a user is able to access certain record types in ADAMS because their organization has been granted a SHARE, an indicator is displayed in the page similar to the one shown here:


 

Accessibility of shared athlete profile

  • Quick search does not retrieve shared athletes; however, athlete advanced search and athlete report will retrieve them. They contain two new criteria and a display column to facilitate it.
  • Criteria:
    • Shared by (Multi Organization picker)
    • Accessible using sharing (Boolean picker)
  • Column
    • Shared by (List of organizations sharing this athlete with the current organization)

Use Case Examples:

Case No. 1: CCES shares in Read-only their athlete profiles with FITA.

  • CCES is custodian of A1. FITA has explicit access on A1.
  • Does not change anything.
  • FITA keeps access on A1 and can set up their RTPs accordingly.
  • CCES is custodian of A1. FITA has automatic access to A1.
  • Does not change anything.
  • FITA keeps access on A1 and can set up their RTPs accordingly.
  • CCES is custodian of A1. FITA has no access to A1.
  • This gives READ access to A1 demographic profile to FITA (per the sharing).
  • CCES is custodian of A1. FITA has an explicit deny of access on A1.
  • FITA does not get access to the athlete profile.
  • CCES has explicit or automatic access on A1.
  • This does not change anything for FITA on A1.CCES has no access on A1.

Case No. 2: CCES shares in WRITE their athlete profiles with FITA.

  • CCES is custodian of A1.
  • FITA will get write access on the profile of A1 and will have the same write capabilities that CCES has on it.
  • CCES has explicit or automatic access on A1.
  • This does not change anything for FITA on A1.
  • CCES has no access on A1.
  • This does not change anything for FITA on A1.


Athlete Medical Tree

  • When an athlete profile is shared, a medical tree is displayed with the following items:
    • The tree permits to access every element of the athlete file which is accessible to the current user.
    • It also permits the creation of new elements in the athlete profile. If the current user has a share on the athlete profile, it may create the following record types:
      • DCF - as any (N)ADO can create a DCF on every athlete
      • TEST - as any (N)ADO can create a TEST on every athlete

Registered Testing Pool Configuration

  • Currently an organization which has access to an athlete demographic profile through a share cannot add that athlete to any of its RTPs.

Whereabouts WRITE sharing
It is not possible to configure a share in READ-only mode as this does not provide any additional capability than the current accessibility rules.
An athlete whereabouts are composed of:

  • the monthly calendars, with the entries including the ones coming from any team(s) the athlete belongs to
  • the Whereabouts descriptors
  • optional attachment(s)
  • notes and activities.

By default, every organization which has access (explicit or implicit) on an athlete has READ access on the whereabouts of that athlete.

By default, only the custodian organization of an athlete has WRITE access on his whereabouts. (This is in addition to the athlete himself and his agent.)
An organization can only share the Whereabouts of athletes for which it is the custodian.

A target organization NEEDS to have access to the athlete to get WRITE access from a share by the custodian.

  • For example: IPC is the custodian of athlete "A1." IPC grants access to Whereabouts to UK Sport. If UK sport has no access to "A1," it will not get access to the Whereabouts of "A1."

Write access means:

  • create/update/delete entries
  • create/edit/delete descriptor
  • create/edit/delete attachments
  • create activities
  • reject team entries in the calendar
  • submit a month of whereabouts

Write access does not grant any access to the teams of the source organization.

The following cases illustrate this definition:

  • CCES shares, in WRITE mode, athletes' whereabouts with FITA.
  • CCES is custodian of A1, FITA has access (auto or explicit) to A1.
  • FITA can write the whereabouts of A1 and has the same rights than CCES on them:
  • Create/update/delete and present and future whereabouts entries of A1create/update/delete any whereabouts descriptor of A1.create/update/delete attachment on A1 like CCEScreate/update/delete activities on A1 like CCES
  • However, FITA has no access on the team whereabouts of CCES.The target organization will be able to view/reject the team whereabouts entries from the athlete whereabouts calendar, but that's all.
  • CCES is custodian of A1, FITA has no access on A1, BUT CCES has also shared in write his athlete demographic profile
  • Currently, there is no cumulative effect between partial sharing rights
  • CCES is custodian of A1, FITA has no access on A1.
  • FITA has no access at all on A1's whereabouts.


Mission Order sharing

  • Currently Creator and TA have write access to a Mission Order, except the lead DCO and Participants, which can only be set by the SCA.
  • When an organization shares its Mission Orders, it only shares the ones the organization has created. Being TA/SCA/RMA is not enough to make a Mission Order created by another organization accessible through sharing.
    • When a target organization has WRITE access to a MO because of a sharing, it gets the same writing capabilities of the source organization except for creation of a Doping Control Form on the TEST from the complete status, which is not allowed.

Sharing indicator
When an organization accesses, in READ or WRITE, a shared Mission Order, ADAMS will indicate it on the page, because the source organization may not be the TA/SCA/RMA (perhaps it is only the creator).

Mission Order's TESTS accessibility
The tests contained on a shared Mission Order are also accessible by the target organization, as long as the source organization is the TA of the MO.If the MO is accessible in WRITE, so are the tests, and the target organization has the same writing capabilities as the source organization, except that the target organization cannot create the DCF on the TEST accessible that way.
If the creator of the Mission Order is no longer the TA of the MO, the target organization has no access to the details of the tests of the MO.

  • However, the target can add new TESTs to the MO and these ones are still accessible, because the target organization is the creator of these new tests.

Athlete Selection on Shared Mission Orders:
If a target organization with WRITE access to a MO creates tests in the MO, the athlete selection will have the following rules:

Adding from Selection List
The proposed selection lists will be those of the target organization

Test pool selection criteria
Advanced search and random search can be filtered on the RTP participation of the athlete. In that case, the RTP used will be the one of the target organization.

Rank factor for random search.
The athlete ranking (risk) factor used will be that of the target organization.
 

Set the lead DCO and Participant
Given a shared Mission Order, if the source organization is also the SCA of the MO, the target organization can set the Lead DCO and participants of the MO; however, the pool of available DCOs and participants will come from the source organization. The target organization will not be allowed to assign any of its own DCOs and participants.
Note that sharing Mission Orders implies that the list of DCOs and participants will also be shared!

Finding a Shared Mission Order
When a user of the target organization makes a quick search in the Mission Order management page, only the Mission Orders his organization is related to will be selected. Mission orders accessible by partial sharing will not be accessible through this mechanism. It will be necessary to use the Mission Order report to retrieve these ones.The MO report will work by default on every accessible MO, including the ones shared by any source organizations.

New criteria and display columns support the shared mission order.

TEST sharing
When an organization shares its tests, it only shares the ones the organization has created. Being TA/SCA/RMA is not enough to make a TEST accessible to other organizations through sharing.
When a target organization has WRITE access on a TEST because of a sharing, it gets the same writing capabilities as the source organization except:

  • Creation of a DCF on the TEST from the complete status, which is not allowed.

Sharing indicator
When an organization accesses, in READ or WRITE, a shared TEST, ADAMS will indicate it on the page, because the source organization may not be the TA/SCA/RMA. For example, it may just be its creator.

Finding a shared TEST

  • If the target organization has access to the athlete medical tree, the tests will appear in it; otherwise the organization will have to rely on notification and the TEST report.
  • The TEST report will work by default on every accessible TEST, including the one shared by any source organizations. New criteria and display columns support shared tests.

Set the Lead DCO and Participant

  • Given a shared TEST, if the source organization is also the SCA of the TEST, the target organization can set the Lead DCO and participants of the MO; however, the pool of available DCOs and participants will come from the source organization. The target organization will not be allowed to assign any of its own DCOs and participants.

Sharing TESTs implies that the list of DCOs and participants will also be shared!

Test's DCF accessibility
The DCF of a TEST which is accessible through sharing is not accessible by the target organization because of this share. But it could be accessible according to other rules (DCF sharing or DCF's RMA for instance). The target organization will not see that there is a DCF linked to this TEST if it has no access to the DCF.

Sharing DCFs

  • When an organization shares its DCFs, it only shares the ones the organization has created. Being TA/SCA/RMA is not enough to make a DCF accessible to other organizations through sharing.
  • When a target organization has WRITE access to a DCF because of a sharing, it gets the same writing capabilities as the source organization, except that it may not confirm lab result matching

Finding a shared DCF
If the target organization has access to the athlete medical tree, the DCFs will appear in it, otherwise the organization will have to rely on notification and DCF report.The DCF report will work by default on every accessible DCF, including the ones shared by any source organizations.New criteria and display columns support the shared DCF.

Sharing indicator
When an organization access, in READ or WRITE, a shared DCF, ADAMS will indicate it on the page, because the source organization may not be the TA/SCA/RMA. It may just be its creator, for example.

DCF's TEST accessibility
The TEST of a DCF is not accessible to organizations which only have access to the DCF through a share.

Matched lab result accessibility
The matched lab result(s) of a DCF are not accessible to organizations which only have access to the DCF through a share.The target organization will not be informed that there are any matched lab results.

  • No labels