Create a device to receive clinical data from an eSource
post
/api/studies/{studyId}/subjects/{subjectId}/devices
Creates a virtual device to collect / receive clinical data from a datasource. Devices are assiged to a subject in the study.
Request
Path Parameters
-
studyId: string
Study identifier.
-
subjectId: string
Subject ID.
Supported Media Types
- application/json
Subject attributes.
Root Schema : schema
Type:
Show Source
object
-
esourceName(optional):
string
Optional field. Use to identify source cloud incase of cloud-to-cloud (c2c) data integrations. Leave this field empty for device-to-cloud (d2c) data transfer scenario.
-
srcDeviceName(optional):
string
Optional field. Device or eSource name.
-
surrogateSubjId(optional):
string
Optional field. Surrogate subject identifier for the orginal subject. If this field is empty or not included in the request, mHealth Cloud uses subject number (srcSubjId attribute of Subject entity) as the value.
-
targetSubjIdMap:
array targetSubjIdMap
Subject ID in each target application.
Nested Schema : TargetSubj
Type:
Show Source
object
-
subjId:
string
subject ID in the target application.
-
type:
string
Target type. Possible values are INFORM, DMW, or DEFAULT. Use DEFAULT type if the same subject Id is to be used across all targets. If DEFAULT and a specific target type exist in a map, the specific target type gets higher precedence over the DEFAULT type.
Response
Supported Media Types
- application/json
200 Response
Successful operation.
Root Schema : device
Type:
Show Source
object
-
esourceName(optional):
string
Representation of the eSource name. Used when a device message gets into the mHealth platform through a cloud-to-cloud (c2c) connector. Leave this field empty for device-to-cloud (d2c) connector.
-
id:
string(uuid)
Device instance identifier.
-
iotDeviceId:
string(uuid)
DeviceId created for the virtual device in the underlying IoT Cloud.
-
srcDeviceName(optional):
string
An arbitrary name set by the caller application when the device instance was created.
-
studyId:
string
mHealth study identifier.
-
subjectId:
string(uuid)
Subject identifier in the mHealth Connector Cloud. Generated when a subject is registered in an mHealth study.
-
surrogateSubjId:
string
Surrogate subject identifier. This could be automatically generated by the mHealth Connector Cloud or set by the customer's subject management system. Device data payload must use this value as KEY_UID field.
-
targetSubjIdMap:
array targetSubjIdMap
Subject ID in each target application.
Nested Schema : TargetSubj
Type:
Show Source
object
-
subjId:
string
subject ID in the target application.
-
type:
string
Target type. Possible values are INFORM, DMW, or DEFAULT. Use DEFAULT type if the same subject Id is to be used across all targets. If DEFAULT and a specific target type exist in a map, the specific target type gets higher precedence over the DEFAULT type.
400 Response
Invalid payload.
404 Response
Invalid studyId or subjectId.