V1.0

post

/ec-dataaction-svc/rest/v1.0/studies/{studyId}/{mode}/subjects/bulkaction

This API will return count of subjects/visits processed for lock/Unlock. For visit lock/unlock, subjectId will be added to subjectIds list and visits be to locked are added to visitIds parameter

Request

Path Parameters
Query Parameters
  • Action needs to be performed in bulk. Example: SUBJECTS_LOCK - Locks selected subjects to stop any modification, SUBJECTS_UNLOCK - Unlocks selected subjects to redo modifications, VISITS_LOCK - Locks selected visits of a subject to stop any modification, VISITS_UNLOCK - Locks selected visits of a subject to stop any modification,
    Example:
    SUBJECTS_LOCK
Supported Media Types
Request Body - application/json ()
Root Schema : BulkActionDTO
Type: object
Title: BulkActionDTO
Information for bulk action
Show Source
Nested Schema : SubjectsVisitScheduleRequestV3
Type: object
DTO for specifying filter and sorting options when scheduling visits for multiple subjects (bulk operations).
Show Source
Nested Schema : subjectIds
Type: array
List of Subject Ids. For visit lock/unlock in UUID format
Show Source
Example:
[
    "6AF54DB79B764662B685D68C52AB0B84",
    "6AF54DB79B764662B685D68C52AB0B84"
]
Nested Schema : visitIds
Type: array
List of visits mandatory for visit lock/unlock in UUID format
Show Source
Nested Schema : containsSearchKeywords
Type: array
Keywords for contains match in subject search which will be applied on subject number
Show Source
  • Keywords for contains match in subject search which will be applied on subject number
    Example: ["100","SMI"]
Example:
[
    "100",
    "SMI"
]
Nested Schema : dmViewReviewStatus
Type: array
Review status for data management view.The acceptable values are: noopenqueries, openqueries, verified, signed, locked, allvisitscomplete, readytosign, allvisitscomplete, readytoverify.
Show Source
  • Review status for data management view.The acceptable values are: noopenqueries, openqueries, verified, signed, locked, allvisitscomplete, readytosign, allvisitscomplete, readytoverify.
    Example: ["readytoverify"]
Example:
[
    "readytoverify"
]
Nested Schema : exactSearchKeywords
Type: array
Keywords for exact match in subject search which will be applied on subject number
Show Source
  • Keywords for exact match in subject search which will be applied on subject number
    Example: ["1001","SMITH"]
Example:
[
    "1001",
    "SMITH"
]
Nested Schema : sites
Type: array
List of site identifiers to scope the search
Show Source
Example:
[
    "D3C9A4B5E6F78123456789ABCDEF1234",
    "E1F2A3B4C5D6E7F89012ABCDEF345678"
]
Nested Schema : subjectStates
Type: array
States of subjects to filter by Active, New, Screening_Initiated, Enrolled, Complete, Withdrawn, ehrLinked, ehrNotLinked, Screen_Failed, Auto_Screen_Failed
Show Source
  • States of subjects to filter by Active, New, Screening_Initiated, Enrolled, Complete, Withdrawn, ehrLinked, ehrNotLinked, Screen_Failed, Auto_Screen_Failed
    Example: ["Auto_Screen_Failed"]
Example:
[
    "Auto_Screen_Failed"
]
Nested Schema : VisitsDTO1
Type: object
Takes eventId and eventInstanceNum to uniquely reference a visit instance
Show Source
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: D27DB9E0AFE349D7980683CF55A33883
  • Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.
    Example: 1
Examples

Back to Top

Response

Supported Media Types

200 Response

Success - integer body lists number of subjects/visits affected by bulk action.
Examples

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