V1.0

get

/ec-dataaction-svc/rest/v1.0/studies/{studyId}/{mode}/dataelements/sdv

API allows you to retrieve a list of items (data fields) within a clinical study that require Source Data Verification (SDV) for a specified subject, event, and study version. SDV is a critical process that ensures data accuracy by cross-checking entries against original source documents.

Request

Path Parameters
Query Parameters
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example:
    7978B7DD0A0A4CA899C485990994300C
  • String representing the version of the study configuration or protocol. Helps track changes in form or study design.
    Example:
    2.0.0.38
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example:
    AF77C6450BE94DE293C9630142E0AFAD

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Success
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : SdvItemSelectionResponse
Type: object
DTO representing selected SDV items for subject/event/form context.
Show Source
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical form.
    Example: AF77C6450BE94DE293C9630142E0AFAD
  • Unique Item identifier (UUID, 32-character uppercase hexadecimal string) from the study Designer, associated to a form.
    Example: 33CAF3CB1DF64DF5A353A337CBE6B50A
  • Nature of SDV selection for the item result may containg OPTIONAL_CRITICAL, IRRELEVANT, OLD,OBLIGATORY, OPTIONAL, IRRELEVANT_OLD.
    Example: OPTIONAL_CRITICAL
Examples

400 Response

Bad request.
Body ()
Root Schema : RestResponse
Type: object
Show Source
Nested Schema : ErrorResponseData
Type: object
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
  • details
    Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
  • Application or business-specific error code representing the error type.
    Example: REPT_401
  • Human-readable error message describing the failure or issue.
    Example: Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type: object
Nested Schema : details
Type: object
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
Example:
User role is missing required permission REPORTING_VIEW. Field: userId
Back to Top