V1.0

post

/ec-dataaction-svc/rest/v1.0/studies/{studyId}/{mode}/subject/{subjectId}/validate/multiplevisits

Provides the summary for the multiple visits and returns the actions of visit and visitStartDate.

Request

Path Parameters
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Request DTO with a list of VisitsDTO objects for validating visit start dates across multiple visits.
Show Source
Nested Schema : visits
Type: array
The list of visit objects to validate.
Show Source
Nested Schema : VisitsDTO1
Type: object
Takes eventId and eventInstanceNum to uniquely reference a visit instance
Show Source
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: D27DB9E0AFE349D7980683CF55A33883
  • Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.
    Example: 1
Examples

Back to Top

Response

Supported Media Types

200 Response

Visit start dates validated, results for each visit returned as array.
Body ()
Root Schema : VisitStartDateValidationDto
Type: object
Includes subjectId, eventId, eventInstanceNum, and boolean results indicating whether the visit and the visit start date are locked
Show Source
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: B1ABA3F2E29F4EE193AB6A5DEEC1B5CA
  • Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.
    Example: 5
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example: A1B2C3D4E5F60718293A4BCCFA7EE829
  • Whether the visit is locked.
    Example: false
  • Whether the visit start date is locked.
    Example: true
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