[Deprecated]: V2.0

post

/ec-dc-svc/rest/v2.0/studies/{studyId}/{mode}/studyVersion/{studyVersion}/signSubject/subject/{subjectId}/code/{code}/orgId/{orgId}

Deprecated: Signs a subject and all completed visits in the subject. Repeating sections supported. Use V4 in addition to V3 it utilizes signDTO subject signature.

Request

Path Parameters
Query Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Subjects sign success
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : SignVerifyFreezeDTOv30
Type: object
Extends v20 by adding form section identifier and repeat form number for repeating forms.
Show Source
  • Minimum Length: 0
    Maximum Length: 2048
    Additional comments if provided
    Example: Data discrepancy observed and clarified
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: AF77C6450BE94DE293C9630142E0AFAD
  • 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: 0C50E26E482246B2BB9646C739E97CAA
  • Freeze status can be of FROZEN, UNFROZEN, NEVER_FROZEN
    Example: FROZEN
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) for the Sign/Verify/Freeze record in UUID format
    Example: 1BC29B36F5D64B1B95F4BDBBCEA481BE
  • Unique Item identifier (UUID, 32-character uppercase hexadecimal string) from the study Designer, associated to a form.
    Example: 33CAF3CB1DF64DF5A353A337CBE6B50A
  • Object version number
    Example: 1
  • Operation type on the record, can have values CREATED, MODIFIED or REMOVED
    Example: CREATED
  • Minimum Length: 0
    Maximum Length: 255
    reason to make this change
    Example: Other
  • Represents the ordinal number assigned to a repeated instance of a data collection form. It uniquely identifies each occurrence of a repeating form for a subject when multiple instances of the form.
    Example: 0
  • Indicates the order of occurrence for a repeating form instance, used to distinguish between multiple repetitions of the same form.
    Example: 1
  • Signed status can be of SIGNED, UNSIGNED, NEVER_SIGNED, PARTIAL_SIGNED
    Example: 2C3F40649C654D0F995A7FDBBCEA4FAB
  • Software version number
    Example: 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: C39E34A9152148E0BB831239BAA3E502
  • Unique Identifier (UUID, 32-character uppercase hexadecimal string) of the user
    Example: 2C3F40649C654D0F995A7FDBBCEA4FAB
  • Verify status can be UNVERIFIED, VERIFIED, NEVER_VERIFIED, VERIFY_REQUIRED
    Example: VERIFIED
  • The end date until which the data is applicable or valid.
    Example: 2023-01-02T17:30:00Z
  • The timestamp marking the beginning of the validity period for this record version within the system.
    Example: 2023-01-01T09:00:00Z

400 Response

Bad request.
Body ()
Root Schema : DcsResponse
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