Skip to main content

Screening – Updated

Added validations in the Screening Receptor when a batch is created and results are sent back from the provider to check:

  • That all the entities being returned for the batch search results to the receptor belong to the batch.
  • That the match.providerId returned for the batch search results to the receptor exists in the list of the batch providers.

Also, added fields to the Screening Command API in order to support implementation of Alias Screening. For all the endpoints, entityAliases can be sent as null or an empty list if not using Alias Screening.

Affected Endpoints​

  • POST /api/batch
    • Added entityAliases to CreateBatchEntityDto (within CreateBatchDto).
  • POST /api/entity
    • Added entityAliases to CreateEntityDto.
    • Added entityAliases to EntityCreatedDto (response).
  • PUT /api/entity/{entityId}
    • Added entityAliases to UpdateEntityDto.
  • POST /screeningreceptor/api/receptor
    • Validations explained above