V1.0

post

/ec-dc-svc/rest/v1/studies/{studyId}/{mode}/visitstatus/migratevisit

Persists migrated visit data.

Request

Path Parameters
  • Indicates the operational mode of the study. Accepted values: active, test, or training.
    Example:
    test
  • Unique identifier of the study. Uses UUID in a 32-character uppercase hexadecimal string format.
    Example:
    1BC29B36F5D64B1B95F4BDBBCEA481BE
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Request payload to migrate visit data for a subject and event. Contains identifiers and timestamps.
Show Source
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) of the clinical event. A clinical event can be, for example: Screening, Randomization, Visit 1, etc. Uses UUID in a 32-character uppercase hexadecimal string format.
    Example: 53915DD9B758466AB2226CBCC4466B7E
  • Numeric value representing the instance number of the event. Used for repeated or unscheduled visits (e.g., 1, 2, 3). It is null for scheduled events.
    Example: 1
  • Unique identifier of the site. Uses UUID in a 32-character uppercase hexadecimal string format.
    Example: 8F2B7E6C5D4A3B2C1D0E9F8A7B6C5D4E
  • Source system timestamp in ISO 8601 UTC
    Example: 2023-01-01T09:00:00Z
  • String representing the version of the study. Helps track changes in form or study design.
    Example: 3.0.0.1
  • Unique identifier of the subject. Used to represent a participant enrolled in a study. Uses UUID in a 32-character uppercase hexadecimal string format.
    Example: 1BC29B36F5D64B1B95F4BDBBCEA481BE
  • Visit start date-time in ISO 8601 UTC
    Example: 2023-01-01T09:00:00Z
  • 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
Examples

Back to Top

Response

Supported Media Types

200 Response

Success
Body ()
Root Schema : VisitDataMigrationDtoV1
Type: object
Visit data migration payload/response containing identity, versioning, visit status and timing fields.
Show Source
  • Minimum Length: 0
    Maximum Length: 2048
    Comment
    Example: All data verified
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) of the clinical event. A clinical event can be, for example: Screening, Randomization, Visit 1, etc. Uses UUID in a 32-character uppercase hexadecimal string format.
    Example: 53915DD9B758466AB2226CBCC4466B7E
  • Numeric value representing the instance number of the event. Used for repeated or unscheduled visits (e.g., 1, 2, 3). 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
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the record
    Example: A1B2C3D4E5F6471890ABCDEF12345678
  • Audit trail field that represents the version number of the data.
    Example: 14
  • Minimum Length: 0
    Maximum Length: 255
    Reason
    Example: Subject completed the visit successfully
  • Unique identifier of the site. Uses UUID in a 32-character uppercase hexadecimal string format.
    Example: 8F2B7E6C5D4A3B2C1D0E9F8A7B6C5D4E
  • Source timestamp when the record was generated in the source system
    Example: 2023-01-01T09:00:00Z
  • Minimum Length: 0
    Maximum Length: 100
    String representing the version of the study. Helps track changes in form or study design.
    Example: 3.0.0.1
  • Unique identifier of the subject. Used to represent a participant enrolled in a study. Uses UUID in a 32-character uppercase hexadecimal string format.
    Example: 1BC29B36F5D64B1B95F4BDBBCEA481BE
  • Unique user identifier representing the clinicalone user who modified or interacted with the subject record. Uses UUID in a 32-character uppercase hexadecimal string format.
    Example: 9F8E7D6C5B4A3A2B1C0D9E8F7A6B5C4D
  • The timestamp marking the beginning of the validity period for this record version within the system.
    Example: 2023-01-01T09:00:00Z
  • Date of visit
    Example: 2023-01-01T09:00:00Z
  • 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
Examples

400 Response

Bad request.
Body ()
Root Schema : DcsResponse
Type: object
Show Source
Nested Schema : ErrorResponseData
Type: object
Show Source
Nested Schema : result
Type: object
Nested Schema : details
Type: object
Back to Top