V1.0

post

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

API is used to lock list of subjects, visits, forms, and items within a clinical study.

Request

Path Parameters
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
DTO representing a subject and the list of events (visits/forms/items) to be locked.
Show Source
  • events
    List of visit/form/item objects for the subject in UUID format.
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example: F5F6EA48B9D04C6F8C657CFA5A20EC53
Nested Schema : events
Type: array
List of visit/form/item objects for the subject in UUID format.
Show Source
Nested Schema : VisitFormsItemsDTO
Type: object
DTO for event (visit) details including forms and items to be locked.
Show Source
  • elements
    List of data element DTOs indicating forms/items under the visit.
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: BCAF12ED87549BA59F7A43AB6A77C1E2
  • Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.
    Example: 1
  • String representing the version of the study configuration or protocol. Helps track changes in form or study design.
    Example: 2.0.0.38
Nested Schema : elements
Type: array
List of data element DTOs indicating forms/items under the visit.
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

200 Response

Success
Body ()
Root Schema : SubjectVisitsItemsResponseDTO
Type: object
Response DTO for bulk lock operation, includes processed and failed objects
Show Source
Nested Schema : exceptions
Type: array
Exceptions or error messages for failed objects.
Show Source
  • Exceptions or error messages for failed objects.
    Example: ["Event not found for subject 18DFFBDF2523489AAF3DE9D6CA60B7F2"]
Example:
[
    "Event not found for subject 18DFFBDF2523489AAF3DE9D6CA60B7F2"
]
Nested Schema : failedObjects
Type: array
List of subject/visit/form/item objects which failed to process.
Show Source
Nested Schema : processedObjects
Type: array
List of successfully processed subject/visit/form/item objects.
Show Source
Nested Schema : schema
Type: object
DTO representing a subject and the list of events (visits/forms/items) to be locked.
Show Source
  • events
    List of visit/form/item objects for the subject in UUID format.
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example: F5F6EA48B9D04C6F8C657CFA5A20EC53
Nested Schema : events
Type: array
List of visit/form/item objects for the subject in UUID format.
Show Source
Nested Schema : VisitFormsItemsDTO
Type: object
DTO for event (visit) details including forms and items to be locked.
Show Source
  • elements
    List of data element DTOs indicating forms/items under the visit.
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: BCAF12ED87549BA59F7A43AB6A77C1E2
  • Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.
    Example: 1
  • String representing the version of the study configuration or protocol. Helps track changes in form or study design.
    Example: 2.0.0.38
Nested Schema : elements
Type: array
List of data element DTOs indicating forms/items under the visit.
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

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