v3.0

post

/ec-ors-svc/rest/v3.0/studies/{studyId}/{mode}/visits/subjectvisit

Randomize a subject and/or dispense kits during a randomization or dispensation visit. Rights: OrsVisitManagementPost.

Request

Path Parameters
Supported Media Types
Request Body - application/json ()
Root Schema : Visit Request
Type: object
Title: Visit Request
Request containing subject visit details.
Show Source
Nested Schema : AuthUserListDtoV1
Type: array
Show Source
Nested Schema : DCS Subject
Type: object
Title: DCS Subject
Subject properties indicating completion capability and the locked study version
Show Source
Nested Schema : Kit Types for Dose Hold
Type: array
Title: Kit Types for Dose Hold
List of kit types configured for dose hold.
Show Source
Nested Schema : Kit Types for Resume Dispensation
Type: array
Title: Kit Types for Resume Dispensation
List of kit types for which to resume dispensation.
Show Source
Nested Schema : Reusable Kits
Type: array
Title: Reusable Kits
Unique Items Required: true
IDs of kits that can be reused in the visit.
Show Source
Nested Schema : Visits
Type: array
Title: Visits
Visit status details.
Show Source
Nested Schema : Parameter
Type: object
Contains details about parameters of the form
Show Source
Nested Schema : Dose Hold Request
Type: object
Title: Dose Hold Request
Request containing dose hold settings.
Show Source
Nested Schema : VisitsStatusDto9
Type: object
Visit status details including associated study version
Show Source
  • Study version with which the visit status is associated
    Example: 3.0.0.1
  • Minimum Length: 0
    Maximum Length: 2048
    Additional comment for the visit status
    Example: All data verified
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: ABCDEF1234567890ABCDEF1234567890
  • Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.
    Example: 1
  • Event type corresponding to the visit. The acceptable values are: Visit_Not_Started, Visit_Started, Visit_Complete, Visit_Skipped, Visit_Skip_Undone, Visit_Date_Changed, Visit_Inserted, Visit_Show, Visit_Hide, VisitDateEntered and VisitDateCleared.
    Example: Visit_Not_Started
  • Frozen status of the record can have values NOT_APPLICABLE, FROZEN, UNFREEZE.
    Example: FROZEN
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the record
    Example: 1BC29B36F5D64B1B95F4BDBBCEA481BE
  • Minimum Length: 0
    Maximum Length: 255
    Reason associated with the visit status
    Example: Subject completed the visit successfully
  • Number of repeating form instances for the visit.
    Example: 2
  • Scheduled window end date for the visit
    Example: 2025-10-16T14:30:31.892Z
  • Scheduled window start date for the visit
    Example: 2025-10-16T14:30:31.892Z
  • Signed status for workflow, the acceptable values are: NEVER_SIGNED, SIGNED, UNSIGNED, NEVER_SIGNED.
    Example: SIGNED
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.
    Example: ABCDEF1234567890ABCDEF1234567890
  • Minimum Length: 0
    Maximum Length: 100
    String representing the version of the study configuration or protocol. Helps track changes in form or study design.
    Example: 3.0.0.1
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example: ABCDEF1234567890ABCDEF1234567890
  • Verified status for review workflow,the acceptable values are: NEVER_VEIFIED, VERIFIED, UNVERIFIED, NOT_APPLICABLE.
    Example: VERIFIED
  • Start timestamp of the version record
    Example: 2025-10-16T14:30:31.892Z
  • Visit start date timestamp
    Example: 2025-10-16T14:30:31.892Z
  • Status of the visit. The Value of the status can be NEW, COMPLETE, COMPLETE_ERR, INPROGRESS, INCOMPLETE, INCOMPLETE_ERR, SKIPPED, UNDO_SKIP and NOT_STARTED.
    Example: COMPLETE
  • Type of visit as per the visit type enumeration. The acceptable values are: SCREENING, RANDOMIZATION, DISPENSATION, NON_DISPENSATION, OPTIONAL, OPTIONAL_DISPENSATION, WITHDRAW, SCREENDISP, SCREENRAND, SUBJECT_COMPLETE, UNSCHEDULED, UNSCHEDULED_DISPENSATION, ADVERSE_EVENT, SCREENFAILURE, RESCREENING and RESCREENDISP.
    Example: SCREENING
Back to Top

Response

Supported Media Types

200 Response

Successful operation
Body ()
Root Schema : VisitResult
Type: object
Title: VisitResult
Visit result.
Show Source
Nested Schema : Kits
Type: array
Title: Kits
Contains information for the kit dispensation.
Show Source
Nested Schema : DispensationKit v13.0
Type: object
Title: DispensationKit v13.0
Contains information for the kit dispensation.
Show Source

400 Response

Invalid visit timestamp. Or you must associate the randomization design with a visit before you can create/upload a randomization list for it Or the next step in this visit isn???t allowed for subject because the study version at your site isn???t compatible with the subject Or subject can't be re-randomized before randomization. Or this operation is not allowed in the current subject status
Body ()
Root Schema : ORSResponse
Type: object
Common response object.
Show Source
Nested Schema : ErrorResponseData
Type: object
Show Source
Nested Schema : result
Type: object
Result Object
Nested Schema : details
Type: object

404 Response

Invalid study ID or version OR Rand List not found OR Design not found
Body ()
Root Schema : ORSResponse
Type: object
Common response object.
Show Source
Nested Schema : ErrorResponseData
Type: object
Show Source
Nested Schema : result
Type: object
Result Object
Nested Schema : details
Type: object

500 Response

Unsupported visit. Or subject already completed the visit. Or subject is randomized in error Or invalid treatment found for the subject. Or visit out of order. Or this operation is not allowed in the current subject status Or visit is outside visit window. Or visit is outside visit window and at least one kit is configured not to dispense outside visit window Or not enough inventory.
Body ()
Root Schema : ORSResponse
Type: object
Common response object.
Show Source
Nested Schema : ErrorResponseData
Type: object
Show Source
Nested Schema : result
Type: object
Result Object
Nested Schema : details
Type: object
Back to Top