V1.0

post

/ec-dataaction-svc/rest/v1.0/studies/{studyId}/{mode}/subjects/{subjectId}/multipleitems/locks

Retrieves lock records/status details for multiple specified items of a subject in bulk. It returns a list describing each items lock state.

Request

Path Parameters
  • Mode of the study, accepts: test, active, or training.
    Example:
    test
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.
    Example:
    3F2504E04F8911D39A0C0305E82C3301
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example:
    C456939817234691AFAE1684FD097F45
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Request payload for batch lock/unlock operations on subject visits/items.
Show Source
Nested Schema : visitItems
Type: array
List of ItemsLockRequest objects for each subject/visit/item to lock.
Show Source
Nested Schema : ItemsLockRequest
Type: object
Request element for locking/unlocking a specific item within a subject's visit.
Show Source
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: 680F2514D67889ABCDEF112233ABCDEF
  • 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: CA12B34DEA56B789C1789EFEDEE10988
  • 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: 12ABCD3421345678BACE1122CCFEDD11
  • 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: 2
Examples

Back to Top

Response

Supported Media Types

200 Response

Success
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : DataActionsDTO
Type: object
DTO representing details of a data action and locking operations.
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 comments about the action.
    Example: Lock applied due to protocol deviation
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: A1B23C45D67E89F123456789ABCDEF12
  • 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: C9F84A1D5C7E42A8B9F56321A4B8D721
  • ID (UUID, 32-character uppercase hexadecimal string) of the form section.
    Example: 8877665544332211AABBCCDDEEFF0011
  • Unique identifier for a data action given in UUID, 32-character uppercase hexadecimal string format.
    Example: A1B23C45D67E89F123456789ABCDEF12
  • 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: ABCDEFABCDEF1234567890ABCDEF1234
  • Object version number
    Example: 2
  • 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: 1
  • Minimum Length: 0
    Maximum Length: 255
    Reason for the data action.
    Example: Other
  • Form repeat number if applicable.
    Example: 1
  • Indicates the order of occurrence for a repeating form instance, used to distinguish between multiple repetitions of the same form.
    Example: 2
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.
    Example: B1B8327AFAA6412287106192AB5984EF
  • Software version number
    Example: 3
  • String representing the version of the study configuration or protocol. Helps track changes in form or study design.
    Example: 2.0.0.38
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example: 3EFD49D47C96428C9AAE2FDDE2A32D23
  • Unique Identifier (UUID, 32-character uppercase hexadecimal string) of the user
    Example: E1F2D3C4B5A697887766554433221100
  • The end date until which the data is applicable or valid.
    Example: 2023-12-31T23:59:59Z
  • The timestamp marking the beginning of the validity period for this record version within the system.
    Example: 2023-01-01T00:00:00Z
  • Action performed on visit start date LOCKED, UNLOCKED, NEVER_LOCKED.
    Example: UNLOCKED
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