Assign the randomization design to a visit

Make a POST request to assign the randomization design to the study.

Note:

  • To run these Oracle Clinical One Platform API calls, you need to include an authentication token. For instructions on how to generate your authentication token, see Get a token for authentication and Use the token to make an API request.
  • For every API call make sure you construct the URL using the correct server URL and path parameters values.
For the following API calls, you need the studyID and version, as well as the visitId. These values are retrieved as part of a prerequisite, see Get study information and Get visit information.

Assign the Randomization Design to the Randomization Visit

Given a randomizationId and visitId , run the following cURL call to assign the Randomization Design previously created to the Randomization visit:

curl -X PUT "https://tenant.clinicalone.oraclecloud.com/ec-designer-svc/rest/v1.0/studies/{studyId}/versions/{version}/design/visits/{visitId}/randomizations/{randomizationId}"

For more details on this API, like its parameters and response objects, see Assign randomization design to visit.

Update existing randomization design

Step 1: Create request payload file

In this JSON file the ID refers to the previously created randomization ID from the last step. Include the visit ID of the visit you want the randomization to take place.

Given a Randomization Design id and visitId , create the following JSON called AssignRandomization.json.

Note:

Make sure you replace the id and visitId with the correct values.
{
    "id": "9280AFE88EF047AB8AC574DA0FB0C762",
    "visits": [
    {
        "visitId": "DE920371BDC14FC09E494EB97D908D3A",
        "visitName": "Screening"
    }]
}

Step 2: Assign the Randomization Design to the Screening Visit

Run the following cURL call to assign the Randomization Design previously created to the Screening visit:

curl -X PUT "https://tenant.clinicalone.oraclecloud.com/ec-designer-svc/rest/v5.0/studies/{studyId}/versions/{version}/randomizations/{randomId}" -d "@AssignRandomization.json"

For more information on how to build the payload and other parameters, see Update existing randomization design.

Tip:

There may be different ways to perform these tasks according to the protocol requirements. Browse for these and other related APIs under the Tasks section of this guide. If you see any deprecated endpoint, look for its newest version.