V1.0

put

/ec-dataaction-svc/rest/v1.0/studies/{studyId}/{mode}/unfreeze/vsd

Unfreezes a visit start date. This endpoint is used to revert a previously frozen visit start date to a state that allows further data entry or edits.

Request

Path Parameters
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Superclass for unfreeze requests, contains the reason for unfreezing.
Show Source
  • A short comment explaining for the unfreeze action when Other is selected in reasonForChange
    Example: comment
  • 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
  • A short description explaining the reason for the unfreeze action. Accepted values are Change for encoding, Incorrect Subject, Investigator Correction, Transcription Error, Other.
    Example: Other
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example: AF77C6450BE94DE293C9630142E0AFAD
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