Skip to main content

Screening – Updated

Update BatchExternalIds to use their own model (BatchExternalId instead of ExternalId), as it does not make sense for a BatchExternalId to have EntityAliasId since BatchExternalId is specifically related to the batch, not any of its entities. This should not affect any clients as Alias Screening has not been enabled yet.

Affected Endpoints​

  • POST /screeningreceptor/api/receptor (ScreenResponseDto, OngoingScreeningGetResultsResponseDto)
  • POST /{anyScreeningAdapter}/api/resolvematches (ResolveMatchesRequestDto)
  • GET /screeningquery/api/batch/{id}, GET /screeningquery/api/batch/journey/{journeyId}, GET /screeningquery/api/batch/journey/{journeyId}/process/{processId} (BatchDto)