V2.0

get

/ec-dc-svc/rest/v2.0/studies/{studyId}/{mode}/dataelements/formassociations/history/sourceForm/{sourceFormId}

Retrieves the audit history for a form association. The api response has additional fields like userId, versionStart, versionEnd, objectVersionNumber and softwareVersionNumber.

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 : FormsAssociationsHistoryDto2
Type: object
Extends FormsAssociationsHistoryDto with version end timestamp, software version number and section linkage details for source and associated forms including repeat form numbers.
Show Source
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: 93CC828113AC439181071CB44D2C6FE5
  • 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: AA11BB22CC33DD44EE55FF6677889900
  • ID (UUID, 32-character uppercase hexadecimal string) of the form section.
    Example: C6E0C7D5A1F3428C8B8B6A77C5E9D4AB
  • 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: 3.0.0.2
  • Comment
    Example: Linked forms across events
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) of the association record
    Example: 1BC29B36F5D64B1B95F4BDBBCEA481BE
  • Object version number used for concurrency control.
    Example: 14
  • Operation type on the record, can have values CREATED, MODIFIED or REMOVED
    Example: CREATED
  • Reason
    Example: Association created
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.
    Example: ABCDEF1234567890ABCDEF1234567890
  • Software version number
    Example: 14
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: ADF5A7800A954FA5B831E7B6B9CA39A9
  • 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: 40DB4EF4847849CCB24EFCCB71CDA436
  • ID (UUID, 32-character uppercase hexadecimal string) of the form section.
    Example: B6E0C7D5A1F3428C8B8B6A77C5E9D4AA
  • Unique Item identifier (UUID, 32-character uppercase hexadecimal string) from the study Designer, associated to a form.
    Example: DEADBEEFDEADBEEFDEADBEEFDEADBEEF
  • 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: 3.0.0.1
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example: ABCDEF1234567890ABCDEF1234567890
  • User identifier (UUID) who created or modified the association
    Example: 9F8E7D6C5B4A3A2B1C0D9E8F7A6B5C4D
  • The end date until which the data is applicable or valid.
    Example: 2023-01-01T10:00:00Z
  • The timestamp marking the beginning of the validity period for this record version within the system.
    Example: 2023-01-01T09:00:00Z
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