[Deprecated]: V1.0
get
/ec-dc-svc/rest/v1.0/studies/{studyId}/{mode}/svf
Deprecated: Retrieves latest records for Sign, Verify and Freeze actions. API has been deprecated and moved to DIS (Data Integration Service), Path: /ec-dataintegration-svc/rest/v1.0/studies/{studyId}/{mode}/svf
Request
Path Parameters
-
mode(required): string
Mode of the study. Accepts test, active, or training.
-
studyId(required): string
ID of the study for which you want to get the list of subjects.
Query Parameters
-
limit: integer(int32)
Minimum Value:
0Number of records. -
offset: integer(int32)
Minimum Value:
0Starting offset. -
order: string
asc or desc
-
subjectId: string
Subject ID to fetch the record for.
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
200 Response
Success
Root Schema : schema
Type:
Show Source
array-
Array of:
object SignVerifyFreezeDTOv20
DTO representing signature and freeze information for a data element in a study.
Nested Schema : SignVerifyFreezeDTOv20
Type:
objectDTO representing signature and freeze information for a data element in a study.
Show Source
-
comment: string
Minimum Length:
0Maximum Length:2048Additional comments if providedExample:Data discrepancy observed and clarified -
eventId: string
Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.Example:
AF77C6450BE94DE293C9630142E0AFAD -
eventInstanceNum: integer
(int32)
Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.Example:
3 -
formId: string
Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical form.Example:
7978B7DD0A0A4CA899C485990994300C -
freeze: string
Freeze status can be of FROZEN, UNFROZEN, NEVER_FROZENExample:
FROZEN -
id: string
Unique identifier (UUID, 32-character uppercase hexadecimal string) for the Sign/Verify/Freeze record in UUID formatExample:
1BC29B36F5D64B1B95F4BDBBCEA481BE -
itemId: string
Unique Item identifier (UUID, 32-character uppercase hexadecimal string) from the study Designer, associated to a form.Example:
33CAF3CB1DF64DF5A353A337CBE6B50A -
objectVersionNumber: number
Object version numberExample:
1 -
operationType: string
Operation type on the record, can have values CREATED, MODIFIED or REMOVEDExample:
CREATED -
reason: string
Minimum Length:
0Maximum Length:255reason to make this changeExample:Other -
repeatSequenceNumber: integer
(int64)
Indicates the order of occurrence for a repeating form instance, used to distinguish between multiple repetitions of the same form.Example:
1 -
signed: string
Signed status can be of SIGNED, UNSIGNED, NEVER_SIGNED, PARTIAL_SIGNEDExample:
2C3F40649C654D0F995A7FDBBCEA4FAB -
softwareVersionNumber: number
Software version numberExample:
100 -
studyVersion: string
String representing the version of the study configuration or protocol. Helps track changes in form or study design.Example:
2.0.0.38 -
subjectId: string
Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.Example:
C39E34A9152148E0BB831239BAA3E502 -
userId: string
Unique Identifier (UUID, 32-character uppercase hexadecimal string) of the userExample:
2C3F40649C654D0F995A7FDBBCEA4FAB -
verify: string
Verify status can be UNVERIFIED, VERIFIED, NEVER_VERIFIED, VERIFY_REQUIREDExample:
VERIFIED -
versionEnd: string
(date-time)
The end date until which the data is applicable or valid.Example:
2023-01-02T17:30:00Z -
versionStart: string
(date-time)
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.
Root Schema : DcsResponse
Type:
Show Source
object-
errorData: object
ErrorResponseData
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
-
result: object
result
-
status: string
-
version: integer
(int32)
Nested Schema : ErrorResponseData
Type:
objectStructure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
-
details: object
details
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
-
errorCode: string
Application or business-specific error code representing the error type.Example:
REPT_401 -
errorMessage: string
Human-readable error message describing the failure or issue.Example:
Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type:
objectNested Schema : details
Type:
objectDetailed 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