V2.0

get

/ec-dc-svc/rest/v2.0/studies/{studyId}/{mode}/dataelements/{dataelementId}/{opeartionType}/childItems

Retrieves all the child items, forms and visits required to be cleared in order to modify a given data element.

Request

Path Parameters
Query Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Success
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : ChildItemDto2
Type: object
Extended child item metadata with event instance number
Show Source
  • Indicates if the item belongs to a branch visit
    Example: false
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: 0123456789ABCDEF0123456789ABCDEF
  • Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.
    Example: 1
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical form.
    Example: 0123456789ABCDEF0123456789ABCDEF
  • Whether the item belongs to a future visit instance
    Example: false
  • Whether the item is hidden by rule or configuration
    Example: false
  • Whether the item is read-only
    Example: false
  • Unique Item identifier (UUID, 32-character uppercase hexadecimal string) from the study Designer, associated to a form.
    Example: 0123456789ABCDEF0123456789ABCDEF
  • Display title of the child item
    Example: Height
  • Type/category of the child item (e.g., Question, Section)
    Example: Question
  • Title of the visit containing this item
    Example: Screening
Examples

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