V1.0

post

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

API locks all data records associated with a specific event for a given subject, identified by subject ID and event ID. This endpoint is used to restrict changes to the event-level data for the specified subject,

Request

Path Parameters
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
DTO used to specify the parameters for locking visit elements for a subject/event/site.
Show Source
  • elements
    List of data elements to lock.
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: BEEFAABBCCDDEEDDFF00112233445566
  • Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.
    Example: 1
  • Start date for the locked visit.
    Example: 2023-01-01T09:00:00Z
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.
    Example: BEEFAABBCCDDEEDDFF00112233445566
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.
    Example: ABD123EFC6784123BBAA1122CCDDEE44
  • 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: ABD123EFC6784123BBAA1122CCDDEE44
Nested Schema : elements
Type: array
List of data elements to lock.
Show Source
Nested Schema : DataElementRequestDTO
Type: object
DTO specifying a data elements (form, form section, item, or repeat) to be locked or unlocked in a visit.
Show Source
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical form.
    Example: AABBCCDDEEFF00112233445566778899
  • ID (UUID, 32-character uppercase hexadecimal string) of the form section.
    Example: BB112233445566778899AABBCCDDEEFF
  • 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: EEFF00112233445566778899AABBCCDD
  • 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
Examples

Back to Top

Response

Supported Media Types

202 Response

Accepted - No response body is returned for this operation.

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