Forum Widgets
Latest Discussions
Introducing the new look of the Health Bot management portal
In the next few weeks, a new version of the Health Bot management portal will be rolled out. The new version has an improved UI and enhanced accessibility. The transition will be seamless and does not require any action from your end. As always, we are happy to hear your feedback, please use the smiley icon at the top-right side of the frame to submit your feedback. What is new? New stylish look and feel: The scenario editor tool is now keyboard accessible: Users can smartly navigate the scenario flow, using the Arrows and Tab keys. All the actions applicable to the scenario steps are keyboard accessible as well. Adding and Deleting edges are also accessible using the Enter and Delete keys. Users can even move the steps around the canvas using the Shift+Arrows keys. Smooth navigation to and from the Scenario Editor tool: Open the Editor by clicking the “Edit steps” button: Navigate back to scenario management using the “Back arrow”: Using the navigation bar to the left, any page in the portal is one click away even from within the editor. Search & Filter: Every page containing a table or list includes also a Search & Filter component on the right-side of the page: And many more experience enhancements. Useful tips to boost your experience: To add a new element on the canvas to a specific location, use the mouse right-click and the Add menu will pop-up, each of the 3 categories will expand to the list of elements. To easily open a sub-scenario from within a parent scenario, click the “Open scenario” button from the actions menu, and the sub-scenario will be opened in a new tab. To select multiple elements and edges, press the Shift key and select the desired elements with your mouse. You can move them around and you can also delete them by using the Delete key. To restart the WebChat conversation, use the new Start-over button next to the language picker. Use your mouse roller to zoom the canvas in and out."Welcome Scenario" to enable automatic "call to action" in Healthcare Bot
Previously, only "Welcome messages" were supported in which markdown could be used to convey a welcome message on initial interaction with the Healthcare Bot. We got numerous requests from our customers to be able to trigger more elaborate uses cases where some "call to action" could be expressed and conversation could be started without "free text" utterances typed by the user. So, "Automatic Welcome scenario" was introduced. However, there is one major limitation to the "Welcome scenario": It does not support a multi-turn conversation. This means that you can't use any prompts that will ask the user for a value and use this value in the same scenario. It will simply return to the root of the conversation after the welcome scenario had run. The workaround for this: If you need to prompt the user for an action, is to show a statement with a Hero Card or an Adaptive Card that will display an option to click. Clicking the action button will "postBack" whatever value you have set in the card that will trigger another scenario that can be a multi-turn one. In the sample statement below, we show a "Hero Card" with two options. Selecting one of the options, will trigger another scenario which can be a multi-turn one. To assign a "Welcome Scenario", navigate to the "Configuration/Conversation" tab and scroll down to the "Automatic Welcome Scenario". Select the welcome scenario you just created from the dropdown. Note: Welcome scenario will override the "Automatic welcome message" if exists Now each time the user opens the Bot client, he will be prompted with the welcome scenario. Selecting one of the options will begin another scenario as defined in the Hero Card as shown belowNuance Mix NLU support added to Azure Health Bot
Now you can add Nuance Mix NLU service language model to Azure Health Bot just like you could add LUIS language model. Follow the steps to create your Mix application and language model, copy the client authentication details from Mix and paste it into the fields as shown below. You can test the setup by trying the utterance right inside the portal. Once it works, you can map each intent from Mix to an appropriate scenario. During runtime, utterances are evaluated against all other language models and the highest rated model is triggered with any associated entities that are passed to the scenario as "scenarioArgs" variable.
Unable to get API Outputs into Azure Healthcare Bot chat window - Dynamic Adaptive card
Hello Team, Currently, we are using Kyruus API with Azure healthcare Bot to get the Dynamics card value. We are able to get the data from API call. However, we are only getting single card value. e.g: We want to get atleast 10 to 15 cards in our Azure Healthcare chat window. However, when we try to use all locations information to be fetched then we get the error: Oops. Something went wrong and we need to start over. "Data is too large to be shown in the debugger" If we use one location value then we get only one Dynamics card value. Here is the screen shot: /providers/231470 FYI... What is Kyruus: Kyruus ProviderMatch is a Patient-Provider Matching & Scheduling System that helps health systems improve yield from their Patient Access programs, and generate high-quality, actionable patient encounters across their entire provider network. It provides referring physicians, schedulers, and referral coordinators with tools to find and connect patients with clinically appropriate, in-network, and available providers. The platform results in maximum provider productivity, reduction in misdirected referrals, and high patient and provider satisfaction. Introduction videos about what is Kyruss: https://www.youtube.com/watch?v=01cZgUhSZcw – Video length – 2:31 Mins https://www.youtube.com/watch?v=yHq4G89dBCk – Video length – 2:24 Mins Question: How do we get API data using Azure Healthcare Bot in Dynamics Cards? Regards, Anis
“Schedule appointment” and “Benefits Inquiry” scenarios no longer showing up in Health Bot Service
We have a team working with customers and making platform recommendations for AI elements that best align with the use cases they are seeking to enable. Not too long ago, the Microsoft Healthcare bot showed “Schedule appointment” and “Benefits Inquiry” as scenarios that were coming soon to the health bot service, but today they are no longer showing up in the same screen. These particular scenarios are required for what and we are seeking help in understanding why they are no longer there. Co Is there anyone here who can help us understand if these scenario templates are actually coming soon, and if so, when they may be available?Calling Power Automate flows from within Health Bot scenario
Health Bot can call any REST API endpoint from within the scenario. We can leverage this capability to access any Power Automate flow by using the Data Connection step. This opens an entire range of possibilities accessing Power Apps services, such as Dataverse and others. First define the flow that is triggered by "Request" as shown below. Once you save the flow, the "HTTP" post url is revelead. This the endpoint that also includes the access token to invoke this flow. We recommend to remove the access token from the URL and place in Health Bot's "Data Connections" configuration so it will be stored in a more secured manor. Author the flow according to your needs. For example, you can use the "Dataverse" connector to access dataverse data sources and tables. Return the data by using the "Response" step. In Health Bot scenario, use the "Data Connection" step and invoke the flow endpoint For more details see Calling Microsoft Flow from your application | Blog Power AutomateUsing Azure's Face API to detect faces from a locally uploaded image
Health bot supports uploading of files from local file systems. The files are temporarily stored on the Bot framework's infrastructure and access to them is only available to the holder of an exceedingly long URL. This can open various use cases, for example, having the patient upload some image of a medical condition via the bot, the bot can then use some cognitive service to detect the condition and answer the patient based on the uploaded image. In this example, we will use the Face API to detect faces in an image uploaded from the local file system. On the left you can see the scenario flow in which we first prompt for file upload, the canvas in response displays the prompt text and the "paper clip" icon is ready to be clicked and image can be selected from the file system (or Camera Roll on a mobile device). Prompt the user for an Image. Once the image is selected, we then proceed to call the Face API using the "Data Connection" step. We pass the URL of the uploaded image and calling the REST API for API Detection and use the subscription key I have copied from the Azure Cognitive Services resource I have created.Data connection using Server-to-server authentication
When calling a Data Source from the Data Connection step, usually authentication of some sort is required. Only limited use cases allow you to get away with anonymous access. Health Bot supports OAUTH2 server-to-server authentication out-of-the-box. When calling the actual resource with RESTful API, Health Bot first checks if there is already existing valid token in the global bot storage, if not, it obtains the new token using the "Authentication Provider" configuration, places it in the "Authorization" header and proceeds with the call. Upon success, stores the new token for consecutive calls for improved performance. Navigate to "Integrations/Authentication Providers". Click on the "New" button and fill out the required fields. Give it a unique name optional description, authentication methods should be "server-to-server" client id, client secret and the URL for obtaining the token. Note: The URL should use v2.0 endpoint that uses "scope" (not "resource" like in v1.0). It's recommended that you verify the settings by clicking the "verify settings" link. This will create the token and show it as decrypted JWT. Verify that all the claims in the JWT are correct. When calling the resource, in the Data Connection step. Click on the "Authentication Providers" dropdown and select the provider that you like. When running the step, it will take care of the authentication flow for you. There is no need to define "Authorization" Header since it will be added implicitly just before the call.ISSUE - Provisioning new instances of Healthcare Bot
Some customers are experiencing issues provisioning new instances of Healthcare Bot in both the EU and US regions. We have identified the root cause as the underlying Azure Bot Service. We are monitoring the issue and will update once it has been resolved. Existing instances of Healthcare Bot should not be affected. We apologise for any inconvenience.
