MedTech service and Microsoft Teams notifications
In this article, learn about using the MedTech service and Microsoft Teams for notifications.
The MedTech service and Teams notifications reference architecture
When combining the MedTech service, the FHIR® service, and Teams, you can enable multiple care solutions.
The diagram is a MedTech service to Teams notifications conceptual architecture for enabling the MedTech service, the FHIR service, and the Teams Patient App.
You can even embed Power BI Dashboards inside the Microsoft Teams client. For more information on embedding Power BI in Microsoft Team, see Embed Power BI content in Microsoft Teams.
The MedTech service for can ingest IoT data from most IoT devices or gateways regardless of location, data center, or cloud.
We do encourage the use of Azure IoT services to assist with device/gateway connectivity.
For some solutions, Azure IoT Central can be used in place of Azure IoT Hub.
Azure IoT Edge can be used in with IoT Hub to create an on-premises end point for devices and/or in-device connectivity.
Next steps
Understand the MedTech service device data processing stages
Choose a deployment method for the MedTech service
Note
FHIR® is a registered trademark of HL7 and is used with the permission of HL7.
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for