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
-
mode(required): string
Mode of the study, accepts: test, active, or training.Example:
test -
studyId(required): string(uuid)
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.Example:
B1D8B2BA9DD84F0BAEF700387265AC8A -
subjectId(required): string(uuid)
Unique subject identifier representing the patient/participant enrolled in the study.Example:
FE647AE28C394F3BA1C9701045D1C4F8
Supported Media Types
- application/json
Root Schema : schema
Type:
objectRequest DTO with a list of VisitsDTO objects for validating visit start dates across multiple visits.
Show Source
-
visits(required): array
visits
The list of visit objects to validate.
Nested Schema : visits
Type:
arrayThe list of visit objects to validate.
Show Source
-
Array of:
object VisitsDTO1
Takes eventId and eventInstanceNum to uniquely reference a visit instance
Nested Schema : VisitsDTO1
Type:
objectTakes eventId and eventInstanceNum to uniquely reference a visit instance
Show Source
-
eventId: string
(UUID)
Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.Example:
D27DB9E0AFE349D7980683CF55A33883 -
eventInstanceNum: integer
(int64)
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
- application/json
200 Response
Visit start dates validated, results for each visit returned as array.
Root Schema : VisitStartDateValidationDto
Type:
objectIncludes subjectId, eventId, eventInstanceNum, and boolean results indicating whether the visit and the visit start date are locked
Show Source
-
eventId: string
(UUID)
Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.Example:
B1ABA3F2E29F4EE193AB6A5DEEC1B5CA -
eventInstanceNum: integer
(int32)
Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.Example:
5 -
subjectId: string
(UUID)
Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.Example:
A1B2C3D4E5F60718293A4BCCFA7EE829 -
visitLocked: boolean
Whether the visit is locked.Example:
false -
visitStartDateLocked: boolean
Whether the visit start date is locked.Example:
true
Examples
400 Response
Bad request.
Root Schema : RestResponse
Type:
Show Source
object-
errorData: object
ErrorResponseData
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
-
result: object
result
-
status: string
-
version: integer
(int32)
Nested Schema : ErrorResponseData
Type:
objectStructure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
-
details: object
details
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
-
errorCode: string
Application or business-specific error code representing the error type.Example:
REPT_401 -
errorMessage: string
Human-readable error message describing the failure or issue.Example:
Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type:
objectNested Schema : details
Type:
objectDetailed 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