v1.0

get

/ec-dataintegration-svc/rest/v1.0/studies/{studyId}/{mode}/lock/subjects

Retrieves latest lock status for all subjects under a study.

Request

Path Parameters
Query Parameters
  • Minimum Value: 0
    number of records
    Default Value: 5000
    Example:
    5000
  • Minimum Value: 0
    starting offset
    Example:
    0
  • asc or desc
    Default Value: DESC
    Example:
    DESC
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example:
    E3E70682E5F7473E8D39BB0D7B1A3B52

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 : LockedStatusDTO
Type: object
Show Source
  • Action taken on the visit start date value.Acceptable values are LOCKED, UNLOCKED, NEVER_LOCKED.
    Example: LOCKED
  • Minimum Length: 0
    Maximum Length: 2048
    Additional comment or note about the action.
    Example: Locked by monitor for review
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: D4E5F6A1B2C347839ABCDEF012345678
  • 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: ABCDEF12ABCDEF12ABCDEF12ABCDEF12
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the record.
    Example: 1BC29B36F5D64B1B95F4BDBBCEA481BE
  • 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
  • Unique Item identifier (UUID, 32-character uppercase hexadecimal string) from the study Designer, associated to a form.
    Example: 0F1E2D3C4B5A69788796A5B4C3D2E1F0
  • Object version number used for concurrency control.
    Example: 1
  • Operation type on the record, can have values CREATED, MODIFIED or REMOVED
    Example: MODIFIED
  • 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
  • Minimum Length: 0
    Maximum Length: 255
    Reason provided for the lock or action.
    Example: Site audit lock
  • 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
  • Internal repeat sequence number for item or visit repeats.
    Example: 0
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.
    Example: 938D23FA6B7241CCA41BD627E5DB60DA
  • Software version number used when the record was generated.
    Example: 300
  • 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: A1B2C3D4E5F647839ABCDEF012345678
  • Unique Identifier (UUID, 32-character uppercase hexadecimal string) of the user
    Example: 225B79C982104415886DE02BC73C1E1E
  • 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
  • Action to be taken for the visit. The value may be SCREEN_ENABLE, SCREEN_DISABLE, RANDOMIZE_ENABLE, RANDOMIZE_DISABLE, DISPENSE_ENABLE, DISPENSE_DISABLE, COMPLETE_STUDY_ENABLE and COMPLETE_STUDY_DISABLE.
    Example: COMPLETE_STUDY_DISABLE
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