[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
Query Parameters
  • If the call is from Digital Gateway / Digital Gateway Builder, isDgCall set to true, Cleardynamics won't be supported.
Supported Media Types
Request Body - */* ()
Root Schema : schema
Type: object
Request to clear data elements for a subject at visit/form/item scope
Show Source
  • Minimum Length: 0
    Maximum Length: 2048
    Comment
    Example: Incorrect entry; clearing to re-enter
  • Minimum Length: 0
    Maximum Length: 255
    Reason
    Example: Data correction
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example: ABCDEF1234567890ABCDEF1234567890
  • visits
    List of visit-level clear requests containing event, instance number and forms to clear
Nested Schema : visits
Type: array
List of visit-level clear requests containing event, instance number and forms to clear
Show Source
Nested Schema : CoreClearVisitRequestDto
Type: object
Visit-level clear request that includes visit identifiers and the list of forms/items to clear
Show Source
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: CBCDEF1234567890ABCDEF1234567890
  • Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.
    Example: 1
  • forms
    List of form-level clear requests to process in this visit
  • String representing the version of the study configuration or protocol. Helps track changes in form or study design.
    Example: 1.0.0.0
  • Identifier of the Visit Start Date data element (UUID, 32-character uppercase hexadecimal string)
    Example: DBCDEF1234567890ABCDEF1234567890
Nested Schema : forms
Type: array
List of form-level clear requests to process in this visit
Show Source
Nested Schema : CoreClearFormsRequestDto
Type: object
Form-level clear request that identifies the form, repeats and optionally a specific item or section to clear
Show Source
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical form.
    Example: 40DB4EF4847849CCB24EFCCB71CDA436
  • ID (UUID, 32-character uppercase hexadecimal string) of the form section.
    Example: 50DB4EF4847849CCB24EFCCB71CDA436
  • 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
  • Unique Item identifier (UUID, 32-character uppercase hexadecimal string) from the study Designer, associated to a form.
    Example: DEADBEEFDEADBEEFDEADBEEFDEADBEEF
  • 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
  • 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
  • Indicates the order of occurrence for a repeating form instance, used to distinguish between multiple repetitions of the same form.
    Example: 1
Back to Top

Response

Supported Media Types

200 Response

Success
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : DataElementDto
Type: object
Base data element details including identity, study and subject context, values and metadata
Show Source

400 Response

Bad request.
Body ()
Root Schema : DcsResponse
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