How to use IotJsonPathContentTemplate mappings
This article describes how to use IoTJsonPathContentTemplate mappings with the MedTech service device mappings.
IotJsonPathContentTemplate
The IotJsonPathContentTemplate is similar to the JsonPathContentTemplate except the DeviceIdExpression and TimestampExpression aren't required.
The assumption, when using this template, is the device messages being evaluated were sent using the Azure IoT Hub Device SDKs or Export Data (legacy) feature of Azure IoT Central.
When you're using these SDKs, the device identity and the timestamp of the message are known.
Important
Make sure that you're using a device identifier from Azure Iot Hub or Azure IoT Central that is registered as an identifier for a device resource on the destination Fast Healthcare Interoperability Resource (FHIR®) service.
If you're using Azure IoT Hub Device SDKs, you can still use the JsonPathContentTemplate, assuming that you're using custom properties in the message body for the device identity or measurement timestamp.
Note
When using IotJsonPathContentTemplate, the TypeMatchExpression should resolve to the entire message as a JToken. For more information, see the following examples:
Examples
With each of these examples, you're provided with:
- A valid device message.
- An example of what the device message will look like after being received and processed by the IoT hub.
- Conforming and valid MedTech service device mappings for normalizing the device message after IoT hub processing.
- An example of what the MedTech service device message will look like after normalization.
Important
To avoid device spoofing in device-to-cloud messages, Azure IoT Hub enriches all messages with additional properties. To learn more about these properties, see Anti-spoofing properties.
Tip
Visual Studio Code with the Azure IoT Hub extension is a recommended method for sending IoT device messages to your IoT Hub for testing and troubleshooting.
Heart rate
A valid device message to send to your IoT hub.
{“heartRate” : “78”}
An example of what the device message will look like after being received and processed by the IoT hub.
Note
The IoT Hub enriches the device message before sending it to the MedTech service device event hub with all properties starting with iothub. For example: iothub-creation-time-utc.
patientIdExpression is only required for MedTech services in the Create mode, however, if Lookup is being used, a Device resource with a matching Device Identifier must exist in the FHIR service. These examples assume your MedTech service is in a Create mode. For more information on the Create and Lookup Destination properties, see Configure Destination properties.
{
"Body": {
"heartRate": "78"
},
"Properties": {
"iothub-creation-time-utc" : "2021-02-01T22:46:01.8750000Z"
},
"SystemProperties": {
"iothub-connection-device-id" : "device123"
}
}
Conforming and valid MedTech service device mappings for normalizing device message data after IoT Hub processing.
{
"templateType": "CollectionContent",
"template": [
{
"templateType": "IotJsonPathContentTemplate",
"template": {
"typeName": "heartRate",
"typeMatchExpression": "$..[?(@Body.heartRate)]",
"patientIdExpression": "$.SystemProperties.iothub-connection-device-id",
"values": [
{
"required": "true",
"valueExpression": "$.Body.heartRate",
"valueName": "hr"
}
]
}
}
]
}
An example of what the MedTech service device message will look like after the normalization process.
{
"type": "heartRate",
"occurrenceTimeUtc": "2021-02-01T22:46:01.875Z",
"deviceId": "device123",
"properties": [
{
"name": "hr",
"value": "78"
}
]
}
Blood pressure
A valid IoT device message to send to your IoT hub.
{
"systolic": "123",
"diastolic": "87"
}
An example of what the device message will look like after being received and processed by the IoT hub.
Note
The IoT hyub enriches the device message before sending it to the MedTech service device event hub with all properties starting with iothub. For example: iothub-creation-time-utc.
patientIdExpression is only required for MedTech services in the Create mode, however, if Lookup is being used, a Device resource with a matching Device Identifier must exist in the FHIR service. These examples assume your MedTech service is in a Create mode. For more information on the Create and Lookup Destination properties, see Configure Destination properties.
{
"Body": {
"systolic": "123",
"diastolic" : "87"
},
"Properties": {
"iothub-creation-time-utc" : "2021-02-01T22:46:01.8750000Z"
},
"SystemProperties": {
"iothub-connection-device-id" : "device123"
}
}
Conforming and valid MedTech service device mappings for normalizing the device message after IoT hub processing.
{
"templateType": "CollectionContent",
"template": [
{
"templateType": "IotJsonPathContentTemplate",
"template": {
"typeName": "bloodpressure",
"typeMatchExpression": "$..[?(@Body.systolic && @Body.diastolic)]",
"patientIdExpression": "$.SystemProperties.iothub-connection-device-id",
"values": [
{
"required": "true",
"valueExpression": "$.Body.systolic",
"valueName": "systolic"
},
{
"required": "true",
"valueExpression": "$.Body.diastolic",
"valueName": "diastolic"
}
]
}
}
]
}
An example of what the MedTech service device message will look like after the normalization process.
{
"type": "bloodpressure",
"occurrenceTimeUtc": "2021-02-01T22:46:01.875Z",
"deviceId": "device123",
"properties": [
{
"name": "systolic",
"value": "123"
},
{
"name": "diastolic",
"value": "87"
}
]
}
Tip
The IotJsonPathContentTemplate device mapping examples provided in this article may be combined into a single MedTech service device mappings as shown.
Additionally, the IotJasonPathContentTemplate can also be combined with with other template types such as JsonPathContentTemplate mappings to further expand your MedTech service device mapping.
Combined heart rate and blood pressure MedTech service device mappings example.
{
"templateType": "CollectionContent",
"template": [
{
"templateType": "IotJsonPathContentTemplate",
"template": {
"typeName": "heartRate",
"typeMatchExpression": "$..[?(@Body.heartRate)]",
"patientIdExpression": "$.SystemProperties.iothub-connection-device-id",
"values": [
{
"required": "true",
"valueExpression": "$.Body.heartRate",
"valueName": "hr"
}
]
}
},
{
"templateType": "IotJsonPathContentTemplate",
"template": {
"typeName": "bloodpressure",
"typeMatchExpression": "$..[?(@Body.systolic && @Body.diastolic)]",
"patientIdExpression": "$.SystemProperties.iothub-connection-device-id",
"values": [
{
"required": "true",
"valueExpression": "$.Body.systolic",
"valueName": "systolic"
},
{
"required": "true",
"valueExpression": "$.Body.diastolic",
"valueName": "diastolic"
}
]
}
}
]
}
Tip
See the MedTech service article Troubleshoot MedTech service errors for assistance fixing MedTech service errors.
Next steps
In this article, you learned how to use IotJsonPathContentTemplate mappings with the MedTech service device mappings.
To learn how to configure the MedTech service FHIR destination mappings, see
FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
Feedback
Submit and view feedback for