Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
The deprecation of the MedTech service was initiated 3 May 2025. If using a MedTech service is no longer a priority, deprovision your instance, which can be found here. Support for active instances in the following regions will end 3 May 2028: West US2, UK South, West Europe, East US, Australia East, East US 2, Central India, North Europe. The Open Source version of the MedTech service can be found here.
The MedTech service scenario-based samples provide conforming and valid device and FHIR® destination mappings and test device messages. These samples can be used to help with the authoring and troubleshooting of your own MedTech service mappings.
Sample resources
Each MedTech service scenario-based sample contains the following resources:
- Device mapping
- FHIR destination mapping
- README
- Test device message(s)
Tip
You can use the MedTech service Mapping debugger for assistance creating, updating, and troubleshooting the MedTech service device and FHIR destination mappings. The Mapping debugger enables you to easily view and make inline adjustments in real-time, without ever having to leave the Azure portal. The Mapping debugger can also be used for uploading test device messages to see how they'll look after being processed into normalized messages and transformed into FHIR Observations.
CalculatedContent
IotJsonPathContent
Single device message into multiple resources
Next steps
Overview of the MedTech service device data processing stages
Choose a deployment method for the MedTech service
Overview of the MedTech service device mapping
Overview of the MedTech service FHIR destination mapping
Note
FHIR® is a registered trademark of HL7 and is used with the permission of HL7.