MedTech service and Microsoft Teams notifications

Note

Fast Healthcare Interoperability Resources (FHIR®) is an open healthcare specification.

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.

Screenshot of the MedTech service and 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.

Screenshot of the MedTech service and IoT Hub.

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.

Screenshot of the MedTech service and IoT Edge.

Next steps

In this article, you've learned about the MedTech service and Teams notifications integration.

For an overview of the MedTech service, see

To learn about the MedTech service device message data transformation, see

To learn about methods for deploying the MedTech service, see

FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.