v1.0

get

/ec-dataintegration-svc/rest/v1.0/studies/{studyId}/{mode}/signeligibility/history

Retrieves the flat history of eligibility.

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 : SignEligibilityDTO
Type: object
Eligibility history record capturing audit metadata, target objects and status within a specific study version.
Show Source
  • Free-form comment providing additional context
    Example: Eligibility approved by investigator
  • Signature configuration identifier (UUID, 32-character uppercase hexadecimal string).
    Example: 2A5E92F1C2D54DDA9F1C0A9E7B3C2D1A
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: 2A5E92F1C2D54DDA9F1C0A9E7B3C2D1A
  • 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: 2A5E92F1C2D54DDA9F1C0A9E7B3C2D1A
  • ID (UUID, 32-character uppercase hexadecimal string) of the form section.
    Example: 2A5E92F1C2D54DDA9F1C0A9E7B3C2D1A
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) of the eligibility history record
    Example: 2A5E92F1C2D54DDA9F1C0A9E7B3C2D1A
  • 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: 0
  • Object version number used for concurrency control.
    Example: 1
  • Operation type on the record, can have values CREATED, MODIFIED or REMOVED
    Example: CREATED
  • 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: 0
  • Reason for eligibility determination
    Example: All inclusion and no exclusion criteria met
  • 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: 0
  • Indicates the order of occurrence for a repeating form instance, used to distinguish between multiple repetitions of the same form.
    Example: 0
  • Entity on which signature is required Example - SUBJECT/FORM/CASEBOOK)
    Example: SUBJECT
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.
    Example: 2A5E92F1C2D54DDA9F1C0A9E7B3C2D1A
  • Software version number used when the record was generated.
    Example: 1
  • Date from which subject becomes eligible
    Example: 2023-01-01T09:00:00Z
  • Eligibility status.Values can be SIGNED,UNSIGNED or NEVER_SIGNED.
    Example: NEVER_SIGNED
  • String representing the version of the study configuration or protocol. Helps track changes in form or study design.
    Example: 1.0.0.3
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example: 2A5E92F1C2D54DDA9F1C0A9E7B3C2D1A
  • Unique Identifier (UUID, 32-character uppercase hexadecimal string) of the user
    Example: 2A5E92F1C2D54DDA9F1C0A9E7B3C2D1A
  • The end date until which the data is applicable or valid.
    Example: 2023-01-02T09: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 : RestResponse
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