V1.0
post
/ec-dc-svc/rest/v1.0/studies/{studyId}/{mode}/codingstatus
Retrieve data elements to be coded based on 'codeType' parameter and list of source IDs.
Request
Path Parameters
-
mode(required): string
Mode of the study, accepts: test, active, or training.Example:
test -
studyId(required): string
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.Example:
3F2504E04F8911D39A0C0305E82C3301
Query Parameters
-
codeType: string
Type of coded questions to be fetched. Allowed values: NeedsCodingOrDeleted, NeedsCoding.Example:
NeedsCodingOrDeleted
Supported Media Types
- application/json
Root Schema : schema
Type:
objectRequest object for retrieving coded data using a set of source IDs.
Show Source
-
sourceIds: array
sourceIds
A list of upper-case hexadecimal UUID strings identifying source objects for coding.
Nested Schema : sourceIds
Type:
arrayA list of upper-case hexadecimal UUID strings identifying source objects for coding.
Show Source
-
Array of:
string
A list of upper-case hexadecimal UUID strings identifying source objects for coding.Example:
["123E4567E89B12D3A456426655440000","123E4567E89B12D3A45642665544AAAA"]
Example:
[
"123E4567E89B12D3A456426655440000",
"123E4567E89B12D3A45642665544AAAA"
]Examples
Back to Top
Response
Supported Media Types
- application/json
200 Response
Coded question data for the requested sources.
Root Schema : schema
Type:
Show Source
array-
Array of:
object CodedDataDTO
Title:
CodedDataDTORepresents coded data details for a verbatim term including identifiers for study, subject, visit, form, item and associated metadata.
Nested Schema : CodedDataDTO
Type:
objectTitle:
CodedDataDTORepresents coded data details for a verbatim term including identifiers for study, subject, visit, form, item and associated metadata.
Show Source
-
context: string
Additional context information for the coded value.Example:
{} -
dataElementId: string
Unique identifier (UUID, 32-character uppercase hexadecimal string) of the underlying data element.Example:
318148C517104168B7F7AA90EA888DDA -
eventName(required): string
Display name of the study event.Example:
Visit 1 -
eventRefName(required): string
Reference name of the study event as defined in the study design.Example:
VISIT_1 -
formId(required): string
Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical form.Example:
2A5E92F1C2D54DDA9F1C0A9E7B3C2D1A -
formName(required): string
Display name of the form.Example:
Adverse Events -
formRefName(required): string
Reference name of the form as defined in the study design.Example:
AE_FORM -
Id(required): string
Unique identifier (UUID, 32-character uppercase hexadecimal string) for the coded data record.Example:
1BC29B36F5D64B1B95F4BDBBCEA481BE -
itemId(required): string
Unique Item identifier (UUID, 32-character uppercase hexadecimal string) from the study Designer, associated to a form.Example:
D4E5F6A1B2C347839ABCDEF012345678 -
itemName(required): string
Display name of the data item.Example:
Adverse Event Term -
itemRefName(required): string
Reference name of the data item as defined in the study design.Example:
AE_TERM -
siteId(required): string
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.Example:
938D23FA6B7241CCA41BD627E5DB60DA -
siteMnemonic(required): string
Mnemonic code of the site.Example:
SITE001 -
siteName(required): string
Name of the clinical site.Example:
Main Site -
studyVersion(required): string
String representing the version of the study configuration or protocol. Helps track changes in form or study design.Example:
1.0.0.3 -
subjectId(required): string
Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.Example:
A1B2C3D4E5F647839ABCDEF012345678 -
subjectInitials(required): string
Subject initials as captured in study.Example:
JD -
subjectNumber(required): string
Subject number assigned within the study.Example:
SUBJ-0001 -
value(required): string
Verbatim or coded value captured for the item.Example:
Headache -
verstionStart: string
(date-time)
Record version start timestamp.Example:
2023-01-01T09:00:00Z -
visitId(required): string
Unique identifier (UUID, 32-character uppercase hexadecimal string) of the visitExample:
699EF3745FC545589F186D2198F3C65E
Examples
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