V4.0
post
/ec-dc-svc/rest/v4.0/studies/{studyId}/{mode}/dataelements/verify
Verifies multiple data elements for a subject based on the data element ID..
Request
Path Parameters
-
mode(required): string
Mode of the study, accepts: test, active, or training.Example:
active -
studyId(required): string(UUID)
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.Example:
ABCDEF1234567890ABCDEF1234567890
Supported Media Types
- application/json
Root Schema : schema
Type:
objectRequest for bulk unsign or unverify operations for a specific event/subject.
Show Source
-
comment: string
Any extra comment for the unsign/unverify action.Example:
The data required is missing. -
elements: array
elements
List of core sign/verify target elements.
-
eventId: string
(UUID)
Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.Example:
7978B7DD0A0A4CA899C485990994300C -
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:
3 -
reason: string
Reason for the operation, if supplied.Example:
Other -
studyVersion(required): string
Minimum Length:
0Maximum Length:100String representing the version of the study configuration or protocol. Helps track changes in form or study design.Example:2.0.0.38 -
subjectId: string
(UUID)
Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.Example:
AF77C6450BE94DE293C9630142E0AFAD
Nested Schema : elements
Type:
arrayList of core sign/verify target elements.
Show Source
-
Array of:
object CoreSignVerifyRequestDto
DTO for a single data element to be signed/unverified as part of a bulk request.
Nested Schema : CoreSignVerifyRequestDto
Type:
objectDTO for a single data element to be signed/unverified as part of a bulk request.
Show Source
-
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:
3 -
formId: string
(UUID)
Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical form.Example:
7978B7DD0A0A4CA899C485990994300C -
formSectionId: string
(UUID)
ID (UUID, 32-character uppercase hexadecimal string) of the form section.Example:
33CAF3CB1DF64DF5A353A337CBE6B50A -
innerRepeat: integer
(int64)
Indicates the repeat sequence number of a nested or inner repeating form within an outer repeating structure. This value is used to distinguish multiple occurrences of the same inner form for a given outer repeat instance.Example:
1 -
itemId: string
(UUID)
Unique Item identifier (UUID, 32-character uppercase hexadecimal string) from the study Designer, associated to a form.Example:
7978B7DD0A0A4CA899C485990994300C -
outerRepeat: integer
(int64)
Indicates the repeat sequence number of the primary or outer repeating form. This value identifies each top-level occurrence of a repeating form and serves as the parent context for any nested inner repeats.Example:
1 -
repeatFormNumber: integer
(int64)
Form repeat number if applicable.Example:
0 -
repeatSequenceNumber: integer
(int64)
Indicates the order of occurrence for a repeating form instance, used to distinguish between multiple repetitions of the same form.Example:
1
Examples
Back to Top
Response
Supported Media Types
- application/json
200 Response
Success
400 Response
Bad request.
Root Schema : DcsResponse
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