V1.0

post

/ec-dataaction-svc/rest/v1.0/studies/{studyId}/{mode}/dataelements/freeze

Freezes one or more data elements for a study subject in a given study mode. This is typically used after data entry is complete to prevent further changes. The request payload must include subject and event information, as well as details of each data element to be frozen.

Request

Path Parameters
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Request for bulk unsign or unverify operations for a specific event/subject.
Show Source
  • Any extra comment for the unsign/unverify action.
    Example: The data required is missing.
  • elements
    List of core sign/verify target elements.
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: 7978B7DD0A0A4CA899C485990994300C
  • Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.
    Example: 3
  • Reason for the operation, if supplied.
    Example: Other
  • Minimum Length: 0
    Maximum Length: 100
    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: AF77C6450BE94DE293C9630142E0AFAD
Nested Schema : elements
Type: array
List of core sign/verify target elements.
Show Source
Nested Schema : CoreSignVerifyRequestDto
Type: object
DTO for a single data element to be signed/unverified as part of a bulk request.
Show Source
  • Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.
    Example: 3
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical form.
    Example: 7978B7DD0A0A4CA899C485990994300C
  • ID (UUID, 32-character uppercase hexadecimal string) of the form section.
    Example: 33CAF3CB1DF64DF5A353A337CBE6B50A
  • 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: 1
  • Unique Item identifier (UUID, 32-character uppercase hexadecimal string) from the study Designer, associated to a form.
    Example: 7978B7DD0A0A4CA899C485990994300C
  • 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
  • Form repeat number if applicable.
    Example: 0
  • Indicates the order of occurrence for a repeating form instance, used to distinguish between multiple repetitions of the same form.
    Example: 1
Examples

Back to Top

Response

Supported Media Types

200 Response

Success

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