[Deprecated]:V2.0
put
/ec-dc-svc/rest/v2.0/studies/{studyId}/{mode}/dataelements/clear/{scope}
Clears the scope of data elements by study ID and mode. Return dynamic child which got cleared.
Request
Path Parameters
-
scope(required): string
Scope of the dataElement. Scope can be - ITEM or VSD .
Query Parameters
-
isDgCall: boolean
If the call is from Digital Gateway / Digital Gateway Builder, isDgCall set to true, Cleardynamics won't be supported.
Supported Media Types
- */*
Root Schema : schema
Type:
objectRequest to clear data elements for a subject at visit/form/item scope
Show Source
-
comment: string
Minimum Length:
0Maximum Length:2048CommentExample:Incorrect entry; clearing to re-enter -
reason: string
Minimum Length:
0Maximum Length:255ReasonExample:Data correction -
subjectId: string
Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.Example:
ABCDEF1234567890ABCDEF1234567890 -
visits: array
visits
List of visit-level clear requests containing event, instance number and forms to clear
Nested Schema : visits
Type:
arrayList of visit-level clear requests containing event, instance number and forms to clear
Show Source
-
Array of:
object CoreClearVisitRequestDto
Visit-level clear request that includes visit identifiers and the list of forms/items to clear
Nested Schema : CoreClearVisitRequestDto
Type:
objectVisit-level clear request that includes visit identifiers and the list of forms/items to clear
Show Source
-
eventId: string
Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.Example:
CBCDEF1234567890ABCDEF1234567890 -
eventInstanceNumber: integer
Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.Example:
1 -
forms: array
forms
List of form-level clear requests to process in this visit
-
studyVersion: string
String representing the version of the study configuration or protocol. Helps track changes in form or study design.Example:
1.0.0.0 -
visitStartDateId: string
Identifier of the Visit Start Date data element (UUID, 32-character uppercase hexadecimal string)Example:
DBCDEF1234567890ABCDEF1234567890
Nested Schema : forms
Type:
arrayList of form-level clear requests to process in this visit
Show Source
-
Array of:
object CoreClearFormsRequestDto
Form-level clear request that identifies the form, repeats and optionally a specific item or section to clear
Nested Schema : CoreClearFormsRequestDto
Type:
objectForm-level clear request that identifies the form, repeats and optionally a specific item or section to clear
Show Source
-
formId: string
Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical form.Example:
40DB4EF4847849CCB24EFCCB71CDA436 -
formSectionId: string
ID (UUID, 32-character uppercase hexadecimal string) of the form section.Example:
50DB4EF4847849CCB24EFCCB71CDA436 -
innerRepeat: integer
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
Unique Item identifier (UUID, 32-character uppercase hexadecimal string) from the study Designer, associated to a form.Example:
DEADBEEFDEADBEEFDEADBEEFDEADBEEF -
outerRepeat: integer
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
Represents the ordinal number assigned to a repeated instance of a data collection form. It uniquely identifies each occurrence of a repeating form for a subject when multiple instances of the form.Example:
1 -
repeatSequenceNumber: integer
Indicates the order of occurrence for a repeating form instance, used to distinguish between multiple repetitions of the same form.Example:
1
Response
Supported Media Types
- application/json
200 Response
Success
Root Schema : schema
Type:
Show Source
array-
Array of:
object DataElementDto
Base data element details including identity, study and subject context, values and metadata
Nested Schema : DataElementDto
Type:
objectBase data element details including identity, study and subject context, values and metadata
Show Source
-
comment: string
Minimum Length:
0Maximum Length:2048Comment for the data element changeExample:Captured by device -
dateTimeValueUTC: string
(date-time)
Date-time value in UTCExample:
2025-10-16T14:30:31.892Z -
dayValue: integer
(int32)
Day part of dateExample:
16 -
eventId: string
(UUID)
Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.Example:
ADF5A7800A954FA5B831E7B6B9CA39A9 -
floatValue: number
(decimal)
Numeric decimal valueExample:
12.34 -
formId: string
(UUID)
Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical form.Example:
40DB4EF4847849CCB24EFCCB71CDA436 -
formSectionId: string
(UUID)
ID (UUID, 32-character uppercase hexadecimal string) of the form section.Example:
B6E0C7D5A1F3428C8B8B6A77C5E9D4AA -
hourValue: integer
(int32)
Hour part of timeExample:
14 -
id: string
(UUID)
Unique identifier(UUID, 32-character uppercase hexadecimal string) of the data elementExample:
1BC29B36F5D64B1B95F4BDBBCEA481BE -
itemId: string
(UUID)
Unique Item identifier (UUID, 32-character uppercase hexadecimal string) from the study Designer, associated to a form.Example:
DEADBEEFDEADBEEFDEADBEEFDEADBEEF -
measureUnit: string
Minimum Length:
0Maximum Length:64Measurement unitExample:mg/dL -
minuteValue: integer
(int32)
Minute part of timeExample:
30 -
monthValue: integer
(int32)
Month part of dateExample:
10 -
normalizedUnitId: string
Identifier of normalized unitExample:
A78AD8C31CD843CD8B847C06C0420FF5 -
normalizedValue: string
Minimum Length:
0Maximum Length:100Normalized value if applicableExample:120 -
numValue: integer
(int32)
Numeric integer valueExample:
120 -
originatorId: string
(UUID)
An identifier representing the system, or user that initiated the transaction (UUID, 32-character uppercase hexadecimal string).Example:
FEDCBA9876543210FEDCBA9876543210 -
reason: string
Minimum Length:
0Maximum Length:255Reason associated with the data element changeExample:Initial entry -
repeatSequenceNumber: integer
(int32)
Indicates the order of occurrence for a repeating form instance, used to distinguish between multiple repetitions of the same form.Example:
1 -
secondValue: integer
(int32)
Second part of timeExample:
31 -
siteId: string
(UUID)
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.Example:
ABCDEF1234567890ABCDEF1234567890 -
studyId: string
(UUID)
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.Example:
ABCDEF1234567890ABCDEF1234567890 -
studyName: string
Minimum Length:
0Maximum Length:100Study nameExample:STUDY-ABC -
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:3.0.0.1 -
subjectId: string
(UUID)
Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.Example:
10F75668189F422F9A461A315D211111 -
transactionEnd: string
(date-time)
The date and time at which the transaction processing completed.Example:
2025-10-16T14:30:31.892Z -
transactionStart: string
(date-time)
The date and time at which the transaction processing began.Example:
2025-10-16T14:30:31.892Z -
validationFailure: string
Minimum Length:
0Maximum Length:32767Validation failure details if anyExample:Incorrect values not allowed -
validationStatus: string
Minimum Length:
0Maximum Length:25Validation status of the data element. The validation status can be null or SUCCESS.Example:SUCCESS -
value: string
Minimum Length:
0Maximum Length:4000Raw value captured for the itemExample:120 -
variableId: string
(UUID)
Variable identifier (UUID, 32-character uppercase hexadecimal string) in uppercase hex format.Example:
0123456789ABCDEF0123456789ABCDEF -
vendorCode: string
Minimum Length:
0Maximum Length:100Vendor code if providedExample:VENDOR1 -
versionStart: string
(date-time)
The timestamp marking the beginning of the validity period for this record version within the system.Example:
2025-10-16T14:30:31.892Z -
yearValue: integer
(int32)
Year part of dateExample:
2025
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