V1.0

post

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

API unlocks all data records associated with a specific event for a given subject, identified by subject ID and event ID. This endpoint is used to remove event-level locks, enabling updates and modifications for the specified event in the subjects visit or activity schedule within a clinical trial.

Request

Path Parameters
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example:
    E835FACE12345678A1B2C3D4E5F60789
  • Mode of the study, accepts: test, active, or training.
    Example:
    test
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.
    Example:
    C439E2B3212345678FAB1123FD342871
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example:
    18DFFBDF2523489AAF3DE9D6CA60B7F2
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
DTO representing unlock operation for elements/subjects/visits.
Show Source
  • Additional comments about the unlock operation.
    Example: Unlocked due to query resolution
  • elements
    List of Elements to unlock
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: 0112233445566778899AABBCCDDEEFF0
  • Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.
    Example: 2
  • Visit start date for the unlock operation.
    Example: 2023-12-01T12:00:00Z
  • Reason information for why the unlock operation is being performed.
    Example: Other
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.
    Example: DDEEFF112233445566778899AABBCC00
  • 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: CCBBAA99887766554433221100FFEEDD
Nested Schema : elements
Type: array
List of Elements to unlock
Show Source
Nested Schema : UnlockElements
Type: object
DTO describing a single data element to unlock, such as form, form section, item, or repeat.
Show Source
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical form.
    Example: ABCDEFAB1234567890ABCDEFAB123456
  • ID (UUID, 32-character uppercase hexadecimal string) of the form section.
    Example: 7890ABCDEFAB1234DEFABC1234567890
  • 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: EFAB1234ABCDEF907890ABCDEFAB1234
  • 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

Success- empty response body - standard for HTTP 202

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