REST API for Clinical One Cloud Service

~~[Deprecated]: v6.0~~

get

/ec-query-svc/rest/v6.0/studies/{studyId}/{mode}/openQueryDetails

Deprecated: Use latest version instead. Compared to v5.0, this v6.0 endpoint keeps open-query detail filtering behavior while aligning response metadata with the v6 contract. This benefits users by preserving open-query triage compatibility across upgrades.

Request

Path Parameters

mode(required): string

Study mode. Allowed values: test (testing sandbox), training (training environment), and active (production).
studyId(required): string(uuid)

Clinical One study identifier formatted as a 32 to 36 character GUID.

There's no request body for this operation.

Response

Supported Media Types

application/json

200 Response

Successful operation.

Root Schema : schema

Type: array

Show Source

Array of: object QueryDetailsDTOV6Resp

{
    "type":"array",
    "items":{
        "$ref":"#/components/schemas/QueryDetailsDTOV6Resp"
    }
}

Nested Schema : QueryDetailsDTOV6Resp

Type: object

Show Source

comments: array comments
eventInstanceNumber: integer (int32)
formId: string (uuid)
formInstanceNumber: integer (int32)
formName: string
id: string (uuid)
itemId: string (uuid)
itemName: string
queryModAllowedByUser: boolean
ruleId: string (uuid)
studyRoles: array studyRoles
studyVersion: string
subjectId: string (uuid)
subjectName: string
userCanCloseQuery: boolean
visitId: string (uuid)
visitName: string

{
    "type":"object",
    "properties":{
        "id":{
            "type":"string",
            "format":"uuid"
        },
        "subjectName":{
            "type":"string"
        },
        "visitName":{
            "type":"string"
        },
        "formName":{
            "type":"string"
        },
        "formId":{
            "type":"string",
            "format":"uuid"
        },
        "subjectId":{
            "type":"string",
            "format":"uuid"
        },
        "visitId":{
            "type":"string",
            "format":"uuid"
        },
        "ruleId":{
            "type":"string",
            "format":"uuid"
        },
        "studyVersion":{
            "type":"string"
        },
        "itemId":{
            "type":"string",
            "format":"uuid"
        },
        "itemName":{
            "type":"string"
        },
        "comments":{
            "type":"array",
            "items":{
                "$ref":"#/components/schemas/CommentDetailsDTO"
            }
        },
        "eventInstanceNumber":{
            "type":"integer",
            "format":"int32"
        },
        "formInstanceNumber":{
            "type":"integer",
            "format":"int32"
        },
        "studyRoles":{
            "type":"array",
            "items":{
                "$ref":"#/components/schemas/QueryStudyRoleDTOv6"
            }
        },
        "queryModAllowedByUser":{
            "type":"boolean"
        },
        "userCanCloseQuery":{
            "type":"boolean"
        }
    }
}

Nested Schema : comments

Type: array

Show Source

Array of: object CommentDetailsDTO

A list of comments associated with the query

{
    "type":"array",
    "items":{
        "$ref":"#/components/schemas/CommentDetailsDTO"
    }
}

Nested Schema : studyRoles

Type: array

Show Source

Array of: object QueryStudyRoleDTOv6

{
    "type":"array",
    "items":{
        "$ref":"#/components/schemas/QueryStudyRoleDTOv6"
    }
}

Nested Schema : CommentDetailsDTO

Type: object

A list of comments associated with the query

Show Source

queryComment: string

Comment text recorded for the query state transition.

Example: Query remains open pending site response.
state: string

Allowed Values: [ "Candidate", "Opened", "Answered", "Closed", "Deleted" ]

Query state for the comment entry. Candidate = query created but not yet opened; Opened = action required; Answered = awaiting review; Closed = resolved; Deleted = removed from workflow.

Example: Opened
userInfo: object DisplayUserDto

User details including name, username, and email address.
value: string

Optional value associated with the comment.

Example: Visit data validated.
versionStart: string (date-time)

Timestamp when the comment became effective.

Example: 2024-03-14T09:15:30Z

{
    "type":"object",
    "properties":{
        "state":{
            "type":"string",
            "description":"Query state for the comment entry. Candidate = query created but not yet opened; Opened = action required; Answered = awaiting review; Closed = resolved; Deleted = removed from workflow.",
            "example":"Opened",
            "enum":[
                "Candidate",
                "Opened",
                "Answered",
                "Closed",
                "Deleted"
            ]
        },
        "queryComment":{
            "type":"string",
            "description":"Comment text recorded for the query state transition.",
            "example":"Query remains open pending site response."
        },
        "versionStart":{
            "type":"string",
            "description":"Timestamp when the comment became effective.",
            "format":"date-time",
            "example":"2024-03-14T09:15:30Z"
        },
        "value":{
            "type":"string",
            "description":"Optional value associated with the comment.",
            "example":"Visit data validated."
        },
        "userInfo":{
            "$ref":"#/components/schemas/DisplayUserDto"
        }
    },
    "description":"A list of comments associated with the query"
}

Nested Schema : DisplayUserDto

Type: object

User details including name, username, and email address.

Show Source

emailAddress: string

User's email address.

Example: alice.brown@email.com
firstName: string

User's first name.

Example: Alice
id: string

Unique identifier for the user.

Example: 1BC29B36F5D64B1B95F4BDBBCEA481BE
lastName: string

User's last name.

Example: Brown
userName: string

User's login name.

Example: alicebrown

{
    "type":"object",
    "properties":{
        "id":{
            "type":"string",
            "description":"Unique identifier for the user.",
            "example":"1BC29B36F5D64B1B95F4BDBBCEA481BE"
        },
        "firstName":{
            "type":"string",
            "description":"User's first name.",
            "example":"Alice"
        },
        "lastName":{
            "type":"string",
            "description":"User's last name.",
            "example":"Brown"
        },
        "userName":{
            "type":"string",
            "description":"User's login name.",
            "example":"alicebrown"
        },
        "emailAddress":{
            "type":"string",
            "description":"User's email address.",
            "example":"alice.brown@email.com"
        }
    },
    "description":"User details including name, username, and email address."
}

Nested Schema : QueryStudyRoleDTOv6

Type: object

Show Source

studyRoleId: string (uuid)

Study role of the user performing the query operation
studyRoleName: string

Study role name of the user performing the query operation

Example: CRA

{
    "type":"object",
    "properties":{
        "studyRoleId":{
            "type":"string",
            "description":"Study role of the user performing the query operation",
            "format":"uuid"
        },
        "studyRoleName":{
            "type":"string",
            "description":"Study role name of the user performing the query operation",
            "example":"CRA"
        }
    }
}

Examples

400 Response

Request validation failed due to missing, invalid, or inconsistent request data.

Root Schema : Response DTO

Type: object

Base envelope returned by Query APIs. Use the status field to determine whether result or errorData is populated.

Show Source

errorData: object Error details DTO

Standard structure used to describe errors returned by Query APIs.
result: object result

Result payload returned when status equals success.
status: string

Read Only: true

Allowed Values: [ "success", "failed" ]

Overall execution status. Value is success when result is populated and failed when errorData is returned.

Example: success
version: string

Read Only: true

Semantic version of the response envelope.

Example: 1

{
    "type":"object",
    "properties":{
        "status":{
            "type":"string",
            "description":"Overall execution status. Value is success when result is populated and failed when errorData is returned.",
            "readOnly":true,
            "example":"success",
            "enum":[
                "success",
                "failed"
            ]
        },
        "result":{
            "type":"object",
            "description":"Result payload returned when status equals success.",
            "example":{
                "opened":3,
                "answered":1,
                "closed":2
            }
        },
        "errorData":{
            "$ref":"#/components/schemas/Error details DTO"
        },
        "version":{
            "type":"string",
            "description":"Semantic version of the response envelope.",
            "readOnly":true,
            "example":"1"
        }
    },
    "description":"Base envelope returned by Query APIs. Use the status field to determine whether result or errorData is populated.",
    "example":"{\\n  \\\"status\\\": \\\"success\\\",\\n  \\\"result\\\": {\\n    \\\"id\\\": \\\"AE33A9096BF548BBB29A96E399E9FBBB\\\",\\n    \\\"state\\\": \\\"Answered\\\"\\n  },\\n  \\\"errorData\\\": null,\\n  \\\"version\\\": \\\"1\\\"\\n}"
}

Example:

{\n  \"status\": \"success\",\n  \"result\": {\n    \"id\": \"AE33A9096BF548BBB29A96E399E9FBBB\",\n    \"state\": \"Answered\"\n  },\n  \"errorData\": null,\n  \"version\": \"1\"\n}

Nested Schema : Error details DTO

Type: object

Standard structure used to describe errors returned by Query APIs.

Show Source

details: object QueryRestErrorDetail

Read Only: true

Context object returned when additional error metadata is available.
errorCode: string

Read Only: true

Machine-readable error code that identifies the failure.

Example: QRY-5000
errorMessage: string

Read Only: true

Human-readable explanation describing why the request failed.

Example: Unexpected server error.

{
    "type":"object",
    "properties":{
        "errorCode":{
            "type":"string",
            "description":"Machine-readable error code that identifies the failure.",
            "readOnly":true,
            "example":"QRY-5000"
        },
        "errorMessage":{
            "type":"string",
            "description":"Human-readable explanation describing why the request failed.",
            "readOnly":true,
            "example":"Unexpected server error."
        },
        "details":{
            "$ref":"#/components/schemas/QueryRestErrorDetail"
        }
    },
    "description":"Standard structure used to describe errors returned by Query APIs.",
    "example":{
        "errorCode":"QRY-5000",
        "errorMessage":"Unexpected server error.",
        "details":{
            "requestId":"3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a",
            "supportCode":"QRY-5000",
            "hint":"Retry request after verifying the study mode."
        }
    }
}

Example:

{
    "errorCode":"QRY-5000",
    "errorMessage":"Unexpected server error.",
    "details":{
        "requestId":"3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a",
        "supportCode":"QRY-5000",
        "hint":"Retry request after verifying the study mode."
    }
}

Nested Schema : result

Type: object

Result payload returned when status equals success.

Example:

{
    "opened":3,
    "answered":1,
    "closed":2
}

Nested Schema : QueryRestErrorDetail

Type: object

Read Only: true

Context object returned when additional error metadata is available.

Show Source

hint: string

Client-facing guidance that clarifies how to resolve or retry the request.

Example: Retry request after verifying the study mode.
requestId: string

Unique identifier that can be supplied to Oracle Support when troubleshooting.

Example: 3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a
supportCode: string

Support or incident code associated with the error source.

Example: QRY-5000

{
    "type":"object",
    "properties":{
        "requestId":{
            "type":"string",
            "description":"Unique identifier that can be supplied to Oracle Support when troubleshooting.",
            "example":"3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a"
        },
        "supportCode":{
            "type":"string",
            "description":"Support or incident code associated with the error source.",
            "example":"QRY-5000"
        },
        "hint":{
            "type":"string",
            "description":"Client-facing guidance that clarifies how to resolve or retry the request.",
            "example":"Retry request after verifying the study mode."
        }
    },
    "description":"Context object returned when additional error metadata is available.",
    "readOnly":true,
    "example":{
        "requestId":"3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a",
        "supportCode":"QRY-5000",
        "hint":"Retry request"
    }
}

Example:

{
    "requestId":"3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a",
    "supportCode":"QRY-5000",
    "hint":"Retry request"
}

Examples

404 Response

The query could not be found.

Root Schema : Response DTO

Type: object

Base envelope returned by Query APIs. Use the status field to determine whether result or errorData is populated.

Show Source

errorData: object Error details DTO

Standard structure used to describe errors returned by Query APIs.
result: object result

Result payload returned when status equals success.
status: string

Read Only: true

Allowed Values: [ "success", "failed" ]

Overall execution status. Value is success when result is populated and failed when errorData is returned.

Example: success
version: string

Read Only: true

Semantic version of the response envelope.

Example: 1

{
    "type":"object",
    "properties":{
        "status":{
            "type":"string",
            "description":"Overall execution status. Value is success when result is populated and failed when errorData is returned.",
            "readOnly":true,
            "example":"success",
            "enum":[
                "success",
                "failed"
            ]
        },
        "result":{
            "type":"object",
            "description":"Result payload returned when status equals success.",
            "example":{
                "opened":3,
                "answered":1,
                "closed":2
            }
        },
        "errorData":{
            "$ref":"#/components/schemas/Error details DTO"
        },
        "version":{
            "type":"string",
            "description":"Semantic version of the response envelope.",
            "readOnly":true,
            "example":"1"
        }
    },
    "description":"Base envelope returned by Query APIs. Use the status field to determine whether result or errorData is populated.",
    "example":"{\\n  \\\"status\\\": \\\"success\\\",\\n  \\\"result\\\": {\\n    \\\"id\\\": \\\"AE33A9096BF548BBB29A96E399E9FBBB\\\",\\n    \\\"state\\\": \\\"Answered\\\"\\n  },\\n  \\\"errorData\\\": null,\\n  \\\"version\\\": \\\"1\\\"\\n}"
}

Example:

{\n  \"status\": \"success\",\n  \"result\": {\n    \"id\": \"AE33A9096BF548BBB29A96E399E9FBBB\",\n    \"state\": \"Answered\"\n  },\n  \"errorData\": null,\n  \"version\": \"1\"\n}

Nested Schema : Error details DTO

Type: object

Standard structure used to describe errors returned by Query APIs.

Show Source

details: object QueryRestErrorDetail

Read Only: true

Context object returned when additional error metadata is available.
errorCode: string

Read Only: true

Machine-readable error code that identifies the failure.

Example: QRY-5000
errorMessage: string

Read Only: true

Human-readable explanation describing why the request failed.

Example: Unexpected server error.

{
    "type":"object",
    "properties":{
        "errorCode":{
            "type":"string",
            "description":"Machine-readable error code that identifies the failure.",
            "readOnly":true,
            "example":"QRY-5000"
        },
        "errorMessage":{
            "type":"string",
            "description":"Human-readable explanation describing why the request failed.",
            "readOnly":true,
            "example":"Unexpected server error."
        },
        "details":{
            "$ref":"#/components/schemas/QueryRestErrorDetail"
        }
    },
    "description":"Standard structure used to describe errors returned by Query APIs.",
    "example":{
        "errorCode":"QRY-5000",
        "errorMessage":"Unexpected server error.",
        "details":{
            "requestId":"3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a",
            "supportCode":"QRY-5000",
            "hint":"Retry request after verifying the study mode."
        }
    }
}

Example:

{
    "errorCode":"QRY-5000",
    "errorMessage":"Unexpected server error.",
    "details":{
        "requestId":"3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a",
        "supportCode":"QRY-5000",
        "hint":"Retry request after verifying the study mode."
    }
}

Nested Schema : result

Type: object

Result payload returned when status equals success.

Example:

{
    "opened":3,
    "answered":1,
    "closed":2
}

Nested Schema : QueryRestErrorDetail

Type: object

Read Only: true

Context object returned when additional error metadata is available.

Show Source

hint: string

Client-facing guidance that clarifies how to resolve or retry the request.

Example: Retry request after verifying the study mode.
requestId: string

Unique identifier that can be supplied to Oracle Support when troubleshooting.

Example: 3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a
supportCode: string

Support or incident code associated with the error source.

Example: QRY-5000

{
    "type":"object",
    "properties":{
        "requestId":{
            "type":"string",
            "description":"Unique identifier that can be supplied to Oracle Support when troubleshooting.",
            "example":"3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a"
        },
        "supportCode":{
            "type":"string",
            "description":"Support or incident code associated with the error source.",
            "example":"QRY-5000"
        },
        "hint":{
            "type":"string",
            "description":"Client-facing guidance that clarifies how to resolve or retry the request.",
            "example":"Retry request after verifying the study mode."
        }
    },
    "description":"Context object returned when additional error metadata is available.",
    "readOnly":true,
    "example":{
        "requestId":"3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a",
        "supportCode":"QRY-5000",
        "hint":"Retry request"
    }
}

Example:

{
    "requestId":"3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a",
    "supportCode":"QRY-5000",
    "hint":"Retry request"
}

Examples