[Deprecated]: V4.0
post
/ec-dc-svc/rest/v4.0/studies/{studyId}/{mode}/subjects/randomizeordispense
Randomizes, dispenses or activates a subject, based on visit type, and completes the visit status. ORS dispensation or randomization is called.
Request
Path Parameters
-
mode(required): string
Mode of the study. Accepts test, active, or training.
-
studyId(required): string
ID of the study where a subject is being randomized or dispensed.
Supported Media Types
- application/json
Root Schema : Visit Request
Type:
objectTitle:
Visit RequestRequest containing subject visit details.
Show Source
-
AuthUserListDtoV1: array
AuthUserListDtoV1
-
blind_rand_number_enabled: string
Title:
Blind Rand Number EnabledCheck if rand number needs to be blindedExample:true -
dcssubjects: object
DCS Subject
Title:
DCS SubjectSubject properties indicating completion capability and the locked study version -
forcedRandLimitReached: boolean
Title:
forcedRandLimitReachedCheck if forced limit is reachedExample:true -
instanceNumber: number
(BigDecimal)
Title:
Instance NumberMinimum Value:1Visit instance number.Example:2 -
isVisitWithinWindow: boolean
Title:
Visit Within WindowIndicates whether the visit occurs within the configured window.Example:true -
kitTypesForDoseHold: array
Kit Types for Dose Hold
Title:
Kit Types for Dose HoldList of kit types configured for dose hold. -
kitTypesForResumeDispensation: array
Kit Types for Resume Dispensation
Title:
Kit Types for Resume DispensationList of kit types for which to resume dispensation. -
notify_dispensation_failure_only: string
Title:
Notify Dispensation Failure OnlySend notification only for dispensation failures.Example:true -
notify_randomization_failure_only: string
Title:
Notify Randomization Failure OnlySend notification only for randomization failures.Example:true -
notifyDispensationFailureOnly: string
-
notifyRandomizationFailureOnly: string
-
resumePartialDispensation: boolean
Title:
Resume Partial DispensationIndicates whether to resume partial dispensation in the visit.Example:false -
reusableKits: array
Reusable Kits
Title:
Reusable KitsUnique Items Required:trueIDs of kits that can be reused in the visit. -
siteId(required): string
(uuid)
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical 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.5 -
subjectId(required): string
Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.Example:
B1B8327AFAA6412287106192AB5984EF -
titrationOption: string
Title:
Titration OptionAllowed Values:[ "up", "down", "maintain" ]Pattern:up|down|maintainTitration options to dispense kits. For example: up/down/maintain.Example:up -
userConfirmationTaken: boolean
Title:
User Confirmation TakenUser confirmation for titration.Example:true -
visitId(required): string
(uuid)
Unique identifier (UUID, 32-character uppercase hexadecimal string) of the visit
-
visits: array
Visits
Title:
VisitsVisit status details. -
visitTimestamp: string
Pattern:
(\d){4}-(\d){2}-(\d){2} (\d){2}:(\d){2}:(\d){2}Visit date and timeExample:2018-11-23 08:43:01
Nested Schema : AuthUserListDtoV1
Type:
Show Source
array-
Array of:
object Parameter
Contains details about parameters of the form
Nested Schema : DCS Subject
Type:
objectTitle:
DCS SubjectSubject properties indicating completion capability and the locked study version
Show Source
-
canBeCompleted: boolean
Indicates if the subject has met conditions to be completedExample:
true -
comment: string
Minimum Length:
0Maximum Length:2048Comment for latest subject updateExample:Initial enrollment -
description: string
Minimum Length:
0Maximum Length:500Free text description for the subjectExample:Screened subject -
dob: string
(date-time)
Date of birth
-
enrollmentFailure: string
Minimum Length:
0Maximum Length:255Reason for enrollment failure, if anyExample:Consent withdrawn -
enrollmentOverride: string
Minimum Length:
0Maximum Length:255If subject enrollment is overridden.Example:Subject Enrollment Overridden -
eventType: string
Event Type for Subject, can have value New, Screened, Randomized, Withdrawn, Undo_Withdrawn, Randomization_Replaced, Transferred, Screen_Failed, Undo_Randomization.Example:
Screened -
freezedStatus: string
Frozen status of the record can have values NOT_APPLICABLE, FROZEN, UNFREEZE.Example:
FROZEN -
fromStudyId: string
Origin study identifier (UUID, 32-character uppercase hexadecimal string) from which the subject was transferredExample:
5D5F9311C591424F852B99FD902E98A4 -
gender: string
Minimum Length:
0Maximum Length:10Gender valueExample:[{"value":"1","label":"male"}] -
hasLockData: boolean
Indicates whether lock related data exists for the subjectExample:
false -
id: string
Unique identifier (UUID, 32-character uppercase hexadecimal string) of the subjectExample:
1BC29B36F5D64B1B95F4BDBBCEA481BE -
informedConsentDate: string
(date-time)
Informed consent dateExample:
2025-09-25T09:00:00Z -
lastSigned: string
(date-time)
Timestamp when the subject was last signedExample:
2025-10-16T14:30:31.892Z -
lockedDateTime: string
(date-time)
Timestamp when the subject was lockedExample:
2025-10-16T14:30:31.892Z -
lockedInStudyVersion: string
Study version in which the subject is lockedExample:
3.0.0.4 -
lockedStatus: string
Lock status of the subject,applicable values are LOCKED, UNLOCKEDExample:
UNLOCKED -
mhealthSubjectId: string
Unique Identifier (UUID, 32-character uppercase hexadecimal string) of the subject in mHealth system.Example:
1BC29B36F5D64B1B95F4BDBBCEA481BE -
objectVersionNumber: number
Object version numberExample:
14 -
operationType: string
Operation type on the record, can have values CREATED, MODIFIED or REMOVEDExample:
MODIFIED -
previousSubjectNumber: string
Previous subject number if renumbered or transferredExample:
SUBJECT-0001-OLD -
reason: string
Minimum Length:
0Maximum Length:255Reason for latest subject updateExample:Protocol break happened -
screenFailureDate: string
(date-time)
Date when the subject was marked as screen failureExample:
2025-10-16T14:30:31.892Z -
screeningDate: string
(date-time)
Screening date if applicableExample:
2025-10-01T10:00:00Z -
screeningFailure: string
Minimum Length:
0Maximum Length:255Reason for screening failure, if anyExample:Inclusion criteria not met -
signedStatus: string
Signed status for workflow, the acceptable values are: NEVER_SIGNED, SIGNED, UNSIGNED, NEVER_SIGNED.Example:
SIGNED -
siteId: string
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.Example:
ABCDEF1234567890ABCDEF1234567890 -
softwareVersionNumber: number
Software version number associated with the eventExample:
14 -
sourceTimeStamp: string
(date-time)
Source system timestamp for the subject payloadExample:
2025-10-16T14:30:31.892Z -
state(required): string
Minimum Length:
0Maximum Length:100Lifecycle state of the subject.The state can be New, Active, Screening_Initiated, Screen_Failed, Withdrawn, Auto_Screen_Failed, Complete or Enrolled.Example:Active -
stateDate: string
(date-time)
Timestamp when the subject transitioned to current stateExample:
2025-10-16T14:30:31.892Z -
studyId: string
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.Example:
ABCDEF1234567890ABCDEF1234567890 -
studyVersion(required): string
String representing the version of the study configuration or protocol. Helps track changes in form or study design.Example:
3.0.0.1 -
subjectNumber(required): string
Minimum Length:
0Maximum Length:500Unique subject Number representing the patient/participant enrolled in the study.Example:SUBJ-0001 -
subjectSiteSerialNumber: string
Site-level serial number assigned to the subjectExample:
SITE-0001-001 -
subjectStudySerialNumber: string
Study-level serial number assigned to the subjectExample:
STUDY-0001-001 -
subjectTransferId: string
Unique Identifier(UUID, 32-character uppercase hexadecimal string) of a subject transfer if applicableExample:
1BC29B36F5D64B1B95F4BDBBCEA481BE -
subjNumSiteOrgId: string
Subject number site organization identifier (UUID, 32-character uppercase hexadecimal string)Example:
5D5F9311C591424F852B99FD902E98A4 -
verifiedStatus: string
Verified status for review workflow,the acceptable values are: NEVER_VEIFIED, VERIFIED, UNVERIFIED, NOT_APPLICABLE.Example:
VERIFIED -
versionEnd: string
(date-time)
End timestamp of the subject version recordExample:
2025-10-16T14:30:31.892Z -
versionStart: string
(date-time)
The timestamp marking the beginning of the validity period for this record version within the system.Example:
2025-10-16T14:30:31.892Z
Nested Schema : Kit Types for Dose Hold
Type:
arrayTitle:
Kit Types for Dose HoldList of kit types configured for dose hold.
Show Source
-
Array of:
object Dose Hold Request
Title:
Dose Hold RequestRequest containing dose hold settings.
Nested Schema : Kit Types for Resume Dispensation
Type:
arrayTitle:
Kit Types for Resume DispensationList of kit types for which to resume dispensation.
Show Source
-
Array of:
object Dose Hold Request
Title:
Dose Hold RequestRequest containing dose hold settings.
Nested Schema : Reusable Kits
Type:
arrayTitle:
Reusable KitsUnique Items Required:
trueIDs of kits that can be reused in the visit.
Show Source
Nested Schema : Visits
Type:
arrayTitle:
VisitsVisit status details.
Show Source
-
Array of:
object VisitsStatusDto9
Visit status details including associated study version
Nested Schema : Parameter
Type:
objectContains details about parameters of the form
Show Source
-
formId: string
(uuid)
Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical form.
-
itemId: string
(uuid)
Unique Item identifier (UUID, 32-character uppercase hexadecimal string) from the study Designer, associated to a form.
-
value: string
(uuid)
Value of the item
Nested Schema : Dose Hold Request
Type:
objectTitle:
Dose Hold RequestRequest containing dose hold settings.
Show Source
-
deviceType: string
Title:
Device TypeDevice type.Example:Spirometer -
isTitration: boolean
Title:
TitrationIndicates whether the current medication is a titration.Example:true -
isUnblindedPharmacist: boolean
Title:
Treatment Assignment VisibilityIndicates whether treatment assignment information may be visible to study personnel. It should not be visible to study personnel and must be accessible only to an unblinded pharmacist.Example:true -
kitTypeSrcId: string
(uuid)
Title:
Kit Type Source IDKit type ID. -
trialSupplyType: string
Title:
Trial Supply TypeType of the trial supply.Example:BOTTLE
Nested Schema : VisitsStatusDto9
Type:
objectVisit status details including associated study version
Show Source
-
associatedStudyVersion: string
Study version with which the visit status is associatedExample:
3.0.0.1 -
comment: string
Minimum Length:
0Maximum Length:2048Additional comment for the visit statusExample:All data verified -
eventId: string
Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.Example:
ABCDEF1234567890ABCDEF1234567890 -
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:
1 -
eventType: string
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 -
freezedStatus: string
Frozen status of the record can have values NOT_APPLICABLE, FROZEN, UNFREEZE.Example:
FROZEN -
id: string
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the recordExample:
1BC29B36F5D64B1B95F4BDBBCEA481BE -
reason: string
Minimum Length:
0Maximum Length:255Reason associated with the visit statusExample:Subject completed the visit successfully -
repeatingFormCount: number
Number of repeating form instances for the visit.Example:
2 -
scheduledWindowEndDate: string
(date-time)
Scheduled window end date for the visitExample:
2025-10-16T14:30:31.892Z -
scheduledWindowStartDate: string
(date-time)
Scheduled window start date for the visitExample:
2025-10-16T14:30:31.892Z -
signedStatus: string
Signed status for workflow, the acceptable values are: NEVER_SIGNED, SIGNED, UNSIGNED, NEVER_SIGNED.Example:
SIGNED -
siteId: string
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.Example:
ABCDEF1234567890ABCDEF1234567890 -
studyVersion(required): string
Minimum Length:
0Maximum Length:100String representing the version of the study configuration or protocol. Helps track changes in form or study design.Example:3.0.0.1 -
subjectId: string
Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.Example:
ABCDEF1234567890ABCDEF1234567890 -
verifiedStatus: string
Verified status for review workflow,the acceptable values are: NEVER_VEIFIED, VERIFIED, UNVERIFIED, NOT_APPLICABLE.Example:
VERIFIED -
versionStart: string
Start timestamp of the version recordExample:
2025-10-16T14:30:31.892Z -
visitStartDate: string
(date-time)
Visit start date timestampExample:
2025-10-16T14:30:31.892Z -
visitStatus: string
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 -
visitType: string
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
Response
Supported Media Types
- application/json
200 Response
Success
Root Schema : VisitResult v15.0
Type:
objectTitle:
VisitResult v15.0Visit result.
Show Source
-
countOfKitTypesOnDoseHold: integer
(int32)
Title:
Count Of Kit Types On Dose HoldNumber of kit types on dose hold.Example:1 -
kits: array
kits
-
needsToVisitPharmacist: boolean
Title:
Needs To Visit PharmacistIndicates whether the subject needs to visit an unblinded pharmacist for kit dispensation.Example:true -
pendingKitQuantity: integer
(int32)
Title:
Pending Kit QuantityNumber of kits pending dispensation.Example:1 -
randomNumber: string
Title:
Random NumberRandom number.Example:10 -
treatmentTitle: string
Title:
Treatment TitleTreatment title.Example:A -
visitTimestamp: string
(date-time)
Title:
Visit TimestampVisit timestamp.
Nested Schema : kits
Type:
Show Source
array-
Array of:
object DispensationKit v12.0
Title:
DispensationKit v12.0Contains information for the kit dispensation.
Nested Schema : DispensationKit v12.0
Type:
objectTitle:
DispensationKit v12.0Contains information for the kit dispensation.
Show Source
-
barcode: string
Barcode.Example:
1000 -
conserved: boolean
Title:
ConservedConserved for dispensation.Example:true -
consumeAcrossDoses: boolean
Title:
Consume Across DosesIndicates whether consumption across doses is allowed.Example:true -
deviceConnection: string
Title:
Device Connection TypeAllowed Values:[ "CloudtoCloud", "DevicetoCloud", "NoConnection" ]Device connection type.Example:DevicetoCloud -
deviceType: string
Title:
Device TypeAllowed Values:[ "ActivityWatch", "BloodPressureMonitor", "WeightScale", "ECGReader", "Spirometer", "MobileApp", "SmartPillBottle", "PulseOximeter", "WearablePatch", "Other", "GlucoseMonitor" ]Device type.Example:ActivityWatch -
dispensationConfirmed: boolean
Indicates whether dispensation is confirmed.Example:
true -
dose: number
(double)
Title:
DoseDose.Example:5 -
dosingUnblinded: boolean
Title:
Dosing UnblindedIndicates whether dosing is unblinded.Example:true -
frequency: string
Title:
FrequencyAllowed Values:[ "Once", "QD", "BID", "TID", "QID", "Q3", "Q4", "Q8", "Q12", "Q24", "Bedtime", "With meals", "With meals and at bedtime" ]Dosing frequency.Example:BID -
groupingNumber: integer
(int32)
Title:
Grouping NumberGrouping number for a kit.Example:1 -
id: number
(Integer)
Title:
Dispensation Kit IDUnique identifier of the dispensation kit.Example:2 -
inventoryId: string
Title:
Inventory IDInventory ID.Example:D313327EF13845169A8ADADDA435431E -
kitDescription: string
Title:
Kit DescriptionKit description.Example:Kit A -
kitNumberUTF: string
Title:
Kit Number UTFKit number with UTF-8 support.Example:A-1 -
locallySourced: boolean
Title:
Locally SourcedIndicates whether the kit is locally sourced.Example:true -
lotId: string
Title:
Lot IDLot ID.Example:D313327EF13845169A8ADADDA435431E -
lotNumber: string
Title:
Lot NumberLot number.Example:LOT20240605A -
measurement: string
Title:
MeasurementDose Measurement.Example:ml -
quantity: number
(BigDecimal)
Title:
QuantityKit quantity.Example:5 -
titrationKitLabel: string
Title:
Blinded Titration LabelBlinded titration label.Example:High dose -
titrationOption: string
Title:
Titration OptionAllowed Values:[ "up", "down", "maintain" ]Titration options to dispense kits. For example: up/down/maintain.Example:up -
trialSupplyType: string
Title:
Trial Supply TypeType of the trial supply.Example:BOTTLE
400 Response
Bad request.
Nested Schema : result
Type:
objectNested Schema : details
Type:
object500 Response
Internal server error.
Nested Schema : result
Type:
objectNested Schema : details
Type:
object