V2.0

put

/ec-dc-svc/rest/v2.0/studies/{studyId}/{mode}/dataelements/subject/{subjectId}/event/{eventId}/form/{formId}/formassociations

Updates form associations, if any, for a given form, event and subject. Deletes all associations for the data element if request is empty. The response contains additional fields like associatedFormSectionId, associatedRepeatFormNumber and srcRepeatFormNumber.

Request

Path Parameters
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example:
    7FCBB303F8D24A3FB7DABCACF7600629
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical form.
    Example:
    6FCBB303F8D24A3FB7DABCACF7600629
  • Mode of the study, accepts: test, active, or training.
    Example:
    active
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.
    Example:
    9FCBB303F8D24A3FB7DABCACF7600629
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example:
    8FCBB303F8D24A3FB7DABCACF7600629
Query Parameters
  • Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.
    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:
    2
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Payload to update form associations for a given form context
Show Source
Nested Schema : formsAssociations
Type: array
List of form association updates to apply
Show Source
Nested Schema : FormsAssociationsDto2
Type: object
Associations between source and associated form sections including repeat numbers
Show Source
  • 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
  • ID (UUID, 32-character uppercase hexadecimal string) of the form section.
    Example: 0123456789ABCDEF0123456789ABCDEF
  • 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
  • String representing the version of the study configuration or protocol. Helps track changes in form or study design.
    Example: 1.0.0.0
  • Comment
    Example: Updated association details
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the record
    Example: 0123456789ABCDEF0123456789ABCDEF
  • Object version number used for concurrency control.
    Example: 1
  • Reason
    Example: Data association update
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.
    Example: 0123456789ABCDEF0123456789ABCDEF
  • 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
  • ID (UUID, 32-character uppercase hexadecimal string) of the form section.
    Example: 0123456789ABCDEF0123456789ABCDEF
  • Unique Item identifier (UUID, 32-character uppercase hexadecimal string) from the study Designer, associated to a form.
    Example: 0123456789ABCDEF0123456789ABCDEF
  • 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
  • String representing the version of the study configuration or protocol. Helps track changes in form or study design.
    Example: 1.0.0.1
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example: 0123456789ABCDEF0123456789ABCDEF
  • The timestamp marking the beginning of the validity period for this record version within the system.
    Example: 2024-12-01T10:15:30Z
Examples

Back to Top

Response

Supported Media Types

200 Response

Success
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : FormAssociationsUpdateRespDto2
Type: object
Form associations update response (v2)
Show Source
Nested Schema : formsAssociations
Type: array
List of form associations
Show Source
Nested Schema : FormsAssociationsDto2
Type: object
Associations between source and associated form sections including repeat numbers
Show Source
  • 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
  • ID (UUID, 32-character uppercase hexadecimal string) of the form section.
    Example: 0123456789ABCDEF0123456789ABCDEF
  • 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
  • String representing the version of the study configuration or protocol. Helps track changes in form or study design.
    Example: 1.0.0.0
  • Comment
    Example: Updated association details
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the record
    Example: 0123456789ABCDEF0123456789ABCDEF
  • Object version number used for concurrency control.
    Example: 1
  • Reason
    Example: Data association update
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.
    Example: 0123456789ABCDEF0123456789ABCDEF
  • 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
  • ID (UUID, 32-character uppercase hexadecimal string) of the form section.
    Example: 0123456789ABCDEF0123456789ABCDEF
  • Unique Item identifier (UUID, 32-character uppercase hexadecimal string) from the study Designer, associated to a form.
    Example: 0123456789ABCDEF0123456789ABCDEF
  • 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
  • String representing the version of the study configuration or protocol. Helps track changes in form or study design.
    Example: 1.0.0.1
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example: 0123456789ABCDEF0123456789ABCDEF
  • The timestamp marking the beginning of the validity period for this record version within the system.
    Example: 2024-12-01T10:15:30Z
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