Get blinding group by ID

get

/ec-ors-svc/rest/v2.0/studies/{studyId}/{mode}/blindinggroups/{blindingGroupId}

Retrieves blinding group in a study by blinding group ID.
Required sponsor roles are: clinical supply manager and site manager.
Rights: SupplySettingRightsPost

Request

Path Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Successful operation
Body ()
Root Schema : BlindingGroupResponse.BlindingGroup v2.0
Type: object
Title: BlindingGroupResponse.BlindingGroup v2.0
Object containing blinding group details.
Show Source
Nested Schema : kitTypes
Type: array
Show Source
Nested Schema : BlindingGroupResponse.KitTypeSummary v2.0
Type: object
Title: BlindingGroupResponse.KitTypeSummary v2.0
Object for kit type summary details.
Show Source
  • Kit type description.
    Example: Non dosing kit
  • Allowed Values: [ "CloudtoCloud", "DevicetoCloud", "NoConnection" ]
    Device Connection Type
    Example: NoConnection
  • Allowed Values: [ "ActivityWatch", "BloodPressureMonitor", "WeightScale", "ECGReader", "Spirometer", "MobileApp", "SmartPillBottle", "PulseOximeter", "WearablePatch", "Other", "GlucoseMonitor" ]
    Device Type
    Example: GlucoseMonitor
  • ID of the kit type.
    Example: kitA
  • Kit type name.
    Example: Kit A
  • Allowed Values: [ "BLISTERPACK", "BOTTLE", "DEVICE", "SYRINGE", "OINTMENT", "VIAL", "INHALER", "INFUSION", "BOX", "OTHER" ]
    Package Type
    Example: BOTTLE
  • Allowed Values: [ 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 ]
    Unique ID corresponding to each package type value (1 for BLISTERPACK, 2 for BOTTLE, 3 for DEVICE, 4 for SYRINGE, 5 for OINTMENT, 6 for VIAL, 7 for INHALER, 8 for INFUSION, 9 for BOX, 10 for OTHER).
    Example: 5
  • ID of the kit type.
    Example: D313327EF13845169A8ADADDA435431E

404 Response

Invalid study. OR Blinding Group not found.
Body ()
Root Schema : ORSResponse
Type: object
Common response object.
Show Source
Nested Schema : ErrorResponseData
Type: object
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
  • details
    Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
  • Application or business-specific error code representing the error type.
    Example: REPT_401
  • Human-readable error message describing the failure or issue.
    Example: Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type: object
Result Object
Nested Schema : details
Type: object
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
Example:
User role is missing required permission REPORTING_VIEW. Field: userId

500 Response

Internal server error
Body ()
Root Schema : ORSResponse
Type: object
Common response object.
Show Source
Nested Schema : ErrorResponseData
Type: object
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
  • details
    Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
  • Application or business-specific error code representing the error type.
    Example: REPT_401
  • Human-readable error message describing the failure or issue.
    Example: Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type: object
Result Object
Nested Schema : details
Type: object
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
Example:
User role is missing required permission REPORTING_VIEW. Field: userId
Back to Top