%3CLINGO-SUB%20id%3D%22lingo-sub-1451935%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20the%20COVID-19%20%E2%80%9CBack%20to%20Work%E2%80%9D%20template%20in%20Microsoft%20Healthcare%20Bot%20with%20Azure%20API%20for%20FHIR%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1451935%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F30664%22%20target%3D%22_blank%22%3E%40Amit%20Puri%3C%2FA%3E%26nbsp%3B%2C%20I%20had%20the%20same%20message%20and%20validated%20this%3A%26nbsp%3B%3CSPAN%3ERequired%20Access%20Token%20URL%20is%20in%20the%20form%20of%3A%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%2F%253Ctenantid%253E%2Foauth2%2Fv2.0%2Ftoken%25C2%25A0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flogin.microsoftonline.com%2F%3CTENANTID%3E%2Foauth2%2Fv2.0%2Ftoken%3C%2FTENANTID%3E%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20had%20entered%20only%20up%20to%20tenantid%2C%20but%20was%20lacking%20%2Foauth%2Fv2.0%2Ftoken...%20after%20that%2C%20worked%20like%20a%20charm%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1452703%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20the%20COVID-19%20%E2%80%9CBack%20to%20Work%E2%80%9D%20template%20in%20Microsoft%20Healthcare%20Bot%20with%20Azure%20API%20for%20FHIR%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1452703%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F8231%22%20target%3D%22_blank%22%3E%40Ignacio%20Rauda%20Salazar%3C%2FA%3E%3C%2FP%3E%3CP%3ENope%20-%20it%20didn't%20help%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222020-06-10.png%22%20style%3D%22width%3A%20440px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F197791i325C706C5F90B7AC%2Fimage-dimensions%2F440x416%3Fv%3D1.0%22%20width%3D%22440%22%20height%3D%22416%22%20title%3D%222020-06-10.png%22%20alt%3D%22Screenshot%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EScreenshot%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1455379%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20the%20COVID-19%20%E2%80%9CBack%20to%20Work%E2%80%9D%20template%20in%20Microsoft%20Healthcare%20Bot%20with%20Azure%20API%20for%20FHIR%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1455379%22%20slang%3D%22en-US%22%3E%3CP%3ESome%20things%20to%20check%20on%20setting%20up%20Authentication%3C%2FP%3E%0A%3CP%3E1)%20Ensure%20that%20RBAC%20is%20setup%20and%20that%20the%20registered%20application%20has%20the%20FHIR%20Data%20Contributor%20role.%20T%3CSPAN%3Ehis%20article%20may%20help%3A%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fhealthcare-apis%2Fconfigure-azure-rbac%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fhealthcare-apis%2Fconfigure-azure-rbac%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E2)%20Under%20Integrations%20-%20Authentication%20Provider%20-%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20%26nbsp%3B%20Access%20Token%20URL%20should%20be%3A%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%2F%253ctenantID%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flogin.microsoftonline.com%2F%26lt%3B%3C%2FA%3Enumerical-tenantID%26gt%3B%2Foauth2%2Fv2.0%2Ftoken%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20%26nbsp%3B%20Scope%20should%20be%3A%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2F%26lt%3Byourservername%26gt%3B.azurehealthcareapis.com%2F.default%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2F%3CYOURSERVERNAME%3E.azurehealthcareapis.com%2F.default%3C%2FYOURSERVERNAME%3E%3C%2FA%3E%26nbsp%3B%20(make%20sure%20the%20%22.%22%20is%20there)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E3)%20Under%20Data%20Connections%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20%26nbsp%3B%20Base%20URL%20should%20be%3A%26nbsp%3B%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2F%26lt%3Byourservername%26gt%3B.azurehealthcareapis.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2F%3CYOURSERVERNAME%3E.azurehealthcareapis.com%3C%2FYOURSERVERNAME%3E%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFinally%20-%20remember%20to%20check%20your%20configuration%20with%20Postman%20(read%20more%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fhealthcare-apis%2Faccess-fhir-postman-tutorial%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fhealthcare-apis%2Faccess-fhir-postman-tutorial%3C%2FA%3E)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHope%20this%20helps%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1456458%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20the%20COVID-19%20%E2%80%9CBack%20to%20Work%E2%80%9D%20template%20in%20Microsoft%20Healthcare%20Bot%20with%20Azure%20API%20for%20FHIR%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1456458%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F173674%22%20target%3D%22_blank%22%3E%40Dale%20Emel%3C%2FA%3E%26nbsp%3BAll%203%20items%20-%20looks%20good%2C%20but%20from%20Postman%2C%20it%20looks%20like%20steps%20are%20outdated%20for%20OAuth2.0%2C%20let%20me%20figure%20it%20out.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1439390%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20the%20COVID-19%20%E2%80%9CBack%20to%20Work%E2%80%9D%20template%20in%20Microsoft%20Healthcare%20Bot%20with%20Azure%20API%20for%20FHIR%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1439390%22%20slang%3D%22en-US%22%3E%3CP%3EHey%2C%20I%20am%20getting%20error%20message-Error%20in%20connection%20to%20FHIR%20storage%26nbsp%3B%3CSPAN%3EI%20have%20followed%20the%20article%20strictly%20and%20configured%20Data%20connection%20and%20authentication.%20Is%20something%20missing%20on%20your%20article.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1566160%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20the%20COVID-19%20%E2%80%9CBack%20to%20Work%E2%80%9D%20template%20in%20Microsoft%20Healthcare%20Bot%20with%20Azure%20API%20for%20FHIR%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1566160%22%20slang%3D%22en-US%22%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F173674%22%20target%3D%22_blank%22%3E%40Dale%20Emel%3C%2FA%3E%3CP%3EAfter%20I%20followed%20the%20instructions%20the%20app%20is%20able%20to%20run.%20However%2C%20I%20expected%20the%20app%20to%20ask%20to%20log%20in%20before%2C%20but%20it%20does%20not%20work%20that%20way.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1425833%22%20slang%3D%22en-US%22%3ECOVID-19%20Back%20to%20Work%20template%20in%20Microsoft%20Healthcare%20Bot%20with%20Azure%20API%20for%20FHIR%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1425833%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22lia-align-left%22%3E%3CEM%3E%3CFONT%20color%3D%22%23FF0000%22%3E%3CU%3EUpdate%3C%2FU%3E%3C%2FFONT%3E%3C%2FEM%3E%3CEM%3E%3CFONT%20color%3D%22%23FF0000%22%3E%3A%20This%20blog%20was%20last%20edited%20on%208%2F4%2F2020.%20This%20blog%20outlines%20using%20Healthcare%20Bot%20for%20Back%20to%20Work%20use%20case%20with%20FHIR%20backend.%3C%2FFONT%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CH2%20class%3D%22lia-align-center%22%20id%3D%22toc-hId--1328575145%22%20id%3D%22toc-hId--1328575147%22%20id%3D%22toc-hId--1328575147%22%20id%3D%22toc-hId--1328575147%22%20id%3D%22toc-hId--1328575147%22%20id%3D%22toc-hId--1328575147%22%3E%26nbsp%3B%3C%2FH2%3E%0A%3CH2%20class%3D%22lia-align-center%22%20id%3D%22toc-hId-1158937688%22%20id%3D%22toc-hId-1158937686%22%20id%3D%22toc-hId-1158937686%22%20id%3D%22toc-hId-1158937686%22%20id%3D%22toc-hId-1158937686%22%20id%3D%22toc-hId-1158937686%22%3E%3CSTRONG%3E%3CU%3EWhat%20is%20the%20COVID-19%20Back%20to%20Work%20Solution%20Template%3F%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20countries%20worldwide%20seek%20to%20re-open%20their%20economies%20by%20relaxing%20%E2%80%9Cstay-at-home%E2%80%9D%20orders%2C%20many%20employers%20are%20considering%20how%20to%20prepare%20their%20facilities%20and%20employees%20for%20the%20return%20to%20the%20physical%20workplace.%20To%20do%20this%20in%20a%20more%20safe%20manner%2C%20it%20is%20critical%20to%20monitor%20employees%20for%20common%20COVID-19%20symptoms%20and%20provide%20a%20simple%20way%20for%20affected%20employees%20to%20physically%20return%20to%20the%20workplace%20once%20they%20are%20cleared%20to%20do%20so.%20Microsoft%20teams%20have%20developed%20a%20special%20solution%20template%20to%20enable%20employers%20worldwide%20to%20easily%20create%20deploy%20Microsoft%20technologies%20to%20scale%20and%20automate%20those%20critical%20steps%20for%20return%20to%20the%20workplace.%20We%20call%20it%20the%20%E2%80%9CBack%20to%20Work%E2%80%9D%20solution%20template%20and%20below%20you%20will%20find%20detailed%20instructions%20on%20how%20to%20use%20this%20to%20empower%20a%20safer%20return%20to%20the%20workplace%20for%20your%20organization.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOur%20COVID-19%20%22Back%20To%20Work%22%20template%20is%20built%20on%20Microsoft%20Healthcare%20Bot%20service%20and%20the%20Microsoft%20Azure%20API%20for%20FHIR.%26nbsp%3BSome%20key%20elements%20include%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSTRONG%3ESymptom%20tracking%20for%20essential%20workers%20who%20have%20been%20exposed%20to%20COVID%20(physicians%2C%20nurses%2C%20ancillary%20staff%2C%20volunteers)%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EIn%20accordance%20with%20CDC%20guidelines*%26nbsp%3B%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EOrganizational%20configurable%20documentation%20of%20information%20such%20as%20symptoms%2C%20occupational%20exposure%20type%2C%E2%80%AFand%20testing%20status%20%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EAllows%20systems%20to%20determine%20when%20employees%20will%20be%20safe%20to%20return%20to%20patient%20care%20activities%20or%20work%20or%20campus%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3ESupported%20by%20Microsoft%E2%80%99s%20industry%20leading%20compliance%2C%20privacy%2C%20and%20security%20portfolio%20(-ERR%3AREF-NOT-FOUND-link)%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20class%3D%22lia-align-center%22%20id%3D%22toc-hId--648516775%22%20id%3D%22toc-hId--648516777%22%20id%3D%22toc-hId--648516777%22%20id%3D%22toc-hId--648516777%22%20id%3D%22toc-hId--648516777%22%20id%3D%22toc-hId--648516777%22%3E%3CSTRONG%3E%3CU%3ECOVID-19%20Back%20to%20Work%20Template%20with%20data%20persistence%20in%20Azure%20API%20for%20FHIR%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20will%20take%20you%20step-by-step%20through%20the%20following%2C%20so%20that%20you%20can%20use%20the%20%E2%80%9CBack%20to%20Work%E2%80%9D%20template%20with%20FHIR%20persistence%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3ESetup%20Azure%20API%20for%20FHIR%3C%2FLI%3E%0A%3CLI%3EImport%20Back%20to%20Work%20template%3C%2FLI%3E%0A%3CLI%3EHealthcare%20Bot%20Authentication%20and%20Data%20Connection%3C%2FLI%3E%0A%3CLI%3ECreate%20Web%20Chat%20Channel%20and%20embed%20in%20a%20website%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20class%3D%22lia-align-center%22%20id%3D%22toc-hId-42044699%22%20id%3D%22toc-hId-42044697%22%20id%3D%22toc-hId-42044697%22%20id%3D%22toc-hId-42044697%22%20id%3D%22toc-hId-42044697%22%20id%3D%22toc-hId-42044697%22%3E%3CSTRONG%3E%3CU%3ESetup%20Azure%20API%20for%20FHIR%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EPrerequisite%3A%20If%20you%20don't%20have%20an%20Azure%20subscription%2C%20create%20a%20-ERR%3AREF-NOT-FOUND-free%20account%20before%20you%20begin.%3C%2FP%3E%0A%3CP%3EThe%20COVID-19%20Back%20to%20Work%20template%20uses%20FHIR%20persistence.%20To%20ensure%20appropriate%20configuration%2C%20you%20need%203%20steps%3A%3C%2FP%3E%0A%3CP%3E1.%26nbsp%3BDeploy%20FHIR%20Server%3C%2FP%3E%0A%3CP%3E2.%26nbsp%3BRegister%20a%20Service%20Client%20application%20in%20Azure%20AD%3C%2FP%3E%0A%3CP%3E3.%20Configure%20Azure%20RBAC%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH4%20class%3D%22lia-align-left%22%20id%3D%22toc-hId-732606173%22%20id%3D%22toc-hId-732606171%22%20id%3D%22toc-hId-732606171%22%20id%3D%22toc-hId-732606171%22%20id%3D%22toc-hId-732606171%22%20id%3D%22toc-hId-732606171%22%3E%3CU%3E%3CSTRONG%3EStep%201%3A%20Deploy%20FHIR%20Server%3C%2FSTRONG%3E%3C%2FU%3E%3C%2FH4%3E%0A%3CP%3ELogin%20to%20-ERR%3AREF-NOT-FOUND-Azure%20portal.%20Click%20%2BCreate%20a%20resource.%20Search%20for%20%3CSTRONG%3EAzure%20API%20for%20FHIR%3C%2FSTRONG%3E%20and%20click%20%3CEM%3ECreate%3C%2FEM%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22pic1.png%22%20style%3D%22width%3A%20624px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F199116i2145D076B53B212E%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22pic1.png%22%20alt%3D%22pic1.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EEnter%20details%20in%20%3CSTRONG%3EBasics%3C%2FSTRONG%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22pic2.png%22%20style%3D%22width%3A%20624px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F199117i26A38F2D90E5EDC9%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22pic2.png%22%20alt%3D%22pic2.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EEnter%20Resource%20Group%3C%2FP%3E%0A%3CP%3EAccount%20Name%20(FHIR%20Server%20name%20%E2%80%93%20must%20be%20unique)%3C%2FP%3E%0A%3CP%3ESelect%20Region%3C%2FP%3E%0A%3CP%3ESelect%20FHIR%20Version%20%3D%20R4%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3EClick%20Next%3A%26nbsp%3B%20Additional%20settings%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EAdditional%20settings%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22pic3.png%22%20style%3D%22width%3A%20624px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F199118i8D01CF192B60A60F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22pic3.png%22%20alt%3D%22pic3.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3ENotes%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSTRONG%3ECopy%3C%2FSTRONG%3E%20Authority%3A%26nbsp%3B%20-ERR%3AREF-NOT-FOUND-%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flogin.microsoftonline.com%2F%3C%2FA%3E%3CTENANTID%3E%26gt%3B%20where%20Tenant%20ID%20%3D%20deployment%20tenant%3C%2FTENANTID%3E%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3ECopy%3C%2FSTRONG%3E%20Audience%3A%26nbsp%3B%20https%3A%2F%2F%3CYOUR-FHIR-API-NAME%3E.azurehealthcareapis.com%20where%20%E2%80%9Cyour-fhir-api-name%20is%20the%20name%20of%20the%20Server%20you%20specified%20in%20Basics%3C%2FYOUR-FHIR-API-NAME%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAzure%20API%20for%20FHIR%20uses%20-ERR%3AREF-NOT-FOUND-Azure%20Cosmos%20DB%20as%20backend%20database%20with%20a%20default%20setting%20of%20400%20RU%2Fs.%20You%20can%20change%20Provisioned%20throughput%20(RU%2Fs)%20to%20a%20higher%20number.%20More%20details%20on%20Request%20Units%20(RU)%20can%20be%20found%20%5B%23%24dp84%5D%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fcosmos-db%2Frequest-units%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20margin-bottom%3A%20.0001pt%3B%20background%3A%20white%3B%22%3E%3CI%3E%3CSPAN%20style%3D%22font-family%3A%20'Helvetica'%2Csans-serif%3B%20color%3A%20%23333333%3B%22%3EClick%20Review%20%2B%20Create%3C%2FSPAN%3E%3C%2FI%3E%3CSPAN%20style%3D%22font-family%3A%20'Helvetica'%2Csans-serif%3B%20color%3A%20%23333333%3B%22%3E%20to%20create%20your%20API%20for%20FHIR%20deployment%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CU%3E%3CSTRONG%3EStep%202%3A%20Register%20a%20Service%20Client%20application%20in%20Azure%20AD%3C%2FSTRONG%3E%3C%2FU%3E%3C%2FP%3E%0A%3CP%3EIn%20-ERR%3AREF-NOT-FOUND-Azure%20portal%2C%20on%20the%20left%20navigation%20panel%20(if%20not%20visible%2C%20click%20on%20the%20hamburger%20symbol%20on%20left)%2C%20click%20%3CSTRONG%3EAzure%20Active%20Directory%20-%26gt%3B%20App%20registrations%20-%26gt%3B%20%2BNew%20registration%3C%2FSTRONG%3E.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22pic4.png%22%20style%3D%22width%3A%20624px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F199119i7C369B466A833FD0%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22pic4.png%22%20alt%3D%22pic4.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20margin-bottom%3A%20.0001pt%3B%20background%3A%20white%3B%22%3E%3CSPAN%20style%3D%22font-family%3A%20'Helvetica'%2Csans-serif%3B%20color%3A%20%23333333%3B%22%3EEnter%20a%20user%20friendly%20name%20(something%20like%20service-client-%3CYOURFHIRAPINAME%3E).%20Leave%20the%20default%20supported%20account%20types.%3C%2FYOURFHIRAPINAME%3E%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%2C%20sans-serif%3B%22%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20margin-bottom%3A%20.0001pt%3B%20background%3A%20white%3B%22%3E%3CSPAN%20style%3D%22font-family%3A%20'Helvetica'%2Csans-serif%3B%20color%3A%20%23333333%3B%22%3EClick%26nbsp%3B%3CSTRONG%3E%3CI%3E%3CSPAN%20style%3D%22font-family%3A%20'Helvetica'%2Csans-serif%3B%22%3ERegister%3C%2FSPAN%3E%3C%2FI%3E%3C%2FSTRONG%3E.%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-family%3A%20'Helvetica'%2Csans-serif%3B%20color%3A%20%23333333%3B%22%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20margin-bottom%3A%20.0001pt%3B%20background%3A%20white%3B%22%3E%3CSPAN%20style%3D%22font-family%3A%20'Helvetica'%2Csans-serif%3B%20color%3A%20%23333333%3B%22%3EOnce%20created%20the%20Portal%20will%20take%20you%20to%20the%20new%20Application%20Registration.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20margin-bottom%3A%20.0001pt%3B%20background%3A%20white%3B%22%3E%3CSPAN%20style%3D%22font-family%3A%20'Helvetica'%2Csans-serif%3B%20color%3A%20%23333333%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22pic5.png%22%20style%3D%22width%3A%20624px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F199120i3414E9A6BCB8B1C4%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22pic5.png%22%20alt%3D%22pic5.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3ERead%20more%20about%20Public%20%26amp%3B%20Confidential%20Client%20applications%20here%20(-ERR%3AREF-NOT-FOUND-link)%3C%2FP%3E%0A%3CP%3ECopy%20the%26nbsp%3B%3CSTRONG%3EApplication%20(client)%20ID%26nbsp%3B%3C%2FSTRONG%3Eand%20save%20it%20for%20later%20use%20as%3CSTRONG%3E%26nbsp%3B%E2%80%9CClient%20ID%E2%80%9D.%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20the%20same%20service%20client%20application%20blade%2C%20under%20Manage%2C%20click%20on%26nbsp%3B%3CSTRONG%3ECertificates%20and%20secrets%3C%2FSTRONG%3E.%20Click%20on%26nbsp%3B%3CSTRONG%3E%2B%20New%20client%20secret%3C%2FSTRONG%3E.%20Enter%20a%20description%20and%20expiry%20period%20for%20the%20key%20and%20click%26nbsp%3B%3CSTRONG%3EAdd%3C%2FSTRONG%3E.%20Copy%20the%20generated%20secret%20and%20save%20it%20for%20later%20use%20as%20%E2%80%9C%3CSTRONG%3EClient%20Secret%3C%2FSTRONG%3E%E2%80%9D.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22pic6.png%22%20style%3D%22width%3A%20624px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F199123iE614A835FA417211%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22pic6.png%22%20alt%3D%22pic6.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CU%3E%3CSTRONG%3EStep%203%3A%20Configure%20Azure%20RBAC%3C%2FSTRONG%3E%3C%2FU%3E%3C%2FP%3E%0A%3CP%3EGo%20to%20the%20Azure%20API%20for%20FHIR%20created%20in%20Step%201.%20In%20left%20pane%2C%20click%20on%20%3CSTRONG%3EAccess%20control%20(IAM)%3C%2FSTRONG%3E%20and%20%3CSTRONG%3E%2B%20Add%20%3C%2FSTRONG%3E-%26gt%3B%20Add%20role%20assignment.%20Choose%20(1)%20Role%3A%20FHIR%20Data%20Contributor%20(2)%20Assign%20access%20to%3A%20Azure%20AD%20user%2C%20group%2C%20or%20service%20principal%20(3)%20Select%20service-client-%3CYOURFHIRAPINAME%3E.%20Click%20on%20Save.%3C%2FYOURFHIRAPINAME%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22pic7.png%22%20style%3D%22width%3A%20624px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F199125iA091E10BC459E83E%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22pic7.png%22%20alt%3D%22pic7.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20class%3D%22lia-align-center%22%20id%3D%22toc-hId-722103069%22%20id%3D%22toc-hId-722103067%22%20id%3D%22toc-hId-722103067%22%20id%3D%22toc-hId-722103067%22%20id%3D%22toc-hId-722103067%22%20id%3D%22toc-hId-722103067%22%3E%26nbsp%3B%3C%2FH3%3E%0A%3CH3%20class%3D%22lia-align-center%22%20id%3D%22toc-hId--1085351394%22%20id%3D%22toc-hId--1085351396%22%20id%3D%22toc-hId--1085351396%22%20id%3D%22toc-hId--1085351396%22%20id%3D%22toc-hId--1085351396%22%20id%3D%22toc-hId--1085351396%22%3E%3CSTRONG%3E%3CU%3EConfigure%20Healthcare%20Bot%20and%20Import%20Back%20to%20Work%20template%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E1.%20Go%20to%20Azure%20Marketplace%20and%20-ERR%3AREF-NOT-FOUND-Try%20out%20Microsoft%20Healthcare%20Bot%20instance%20for%20free.%3C%2FP%3E%0A%3CP%3E2.%20Sign%20into%20the%20Azure%20portal%20with%20your%20Azure%20credentials%20and%20select%20Create.%3C%2FP%3E%0A%3CP%3E3.%20In%20the%20Microsoft%20Healthcare%20Bot%20blade%2C%20provide%20the%20necessary%20details%20and%20click%20Subscribe.%20You%20can%20start%20with%20the%20W1%20%E2%80%93%20Free%20plan%20and%20update%20Plan%20later.%3C%2FP%3E%0A%3CP%3E4.%20On%20successful%20deployment%2C%20Go%20To%20Resource%20and%20click%20Configure%20Account.%20Verify%20details%20and%20click%20Create.%3C%2FP%3E%0A%3CP%3E5.%20You%20will%20be%20redirected%20to%20Healthcare%20Bot%20Service%20admin%20portal.%3C%2FP%3E%0A%3CP%3E6.%20Navigate%20to%20Scenarios%20-%26gt%3B%20Manage.%20At%20the%20top%20bar%2C%20you%20will%20find%20option%20to%20%3CEM%3E%3CSTRONG%3EImport%20%3C%2FSTRONG%3E%3C%2FEM%3Escenario.%20The%20Back%20to%20Work%20scenarios%20for%20FHIR%20will%20be%20available%20soon%20in%20the%20GitHub%20folder%20for%20FHIR%20persistence%20**COMING%20SOON**%3C%2FP%3E%0A%3CP%3E7.%26nbsp%3BNavigate%20to%20Language%20-%26gt%3B%20Localization.%26nbsp%3BAt%20the%20top%20bar%2C%20you%20will%20find%20option%20to%20%3CEM%3E%3CSTRONG%3EImport%20%3C%2FSTRONG%3E%3C%2FEM%3Ecustom%20strings.%20The%20Back%20to%20Work%20custom%20strings%20will%20be%20available%20soon%20in%20the%20GitHub%20folder%20for%20FHIR%20persistence%20**COMING%20SOON**%3C%2FP%3E%0A%3CP%3E8.%20In%20Scenarios%20-%26gt%3B%20Manage%2C%20the%20two%20new%20scenarios%20added%20are%3A%3C%2FP%3E%0A%3CP%3E-%20COVID19%20Back%20To%20Work%20Core%3A%20Logical%20workflow%20for%20(a)%20Registration%2Flogin%2C%20(b)%20Daily%20screening%20of%20exposure%2C%20symptoms%20and%20lab%20test%3C%2FP%3E%0A%3CP%3E-%20COVID19%20Back%20To%20Work%20CRUD%3A%20For%20backend%20Create%2C%20Read%2C%20Edit%2C%20Delete%20operations%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22scenarioMgmt.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F195271iC328AAE19B48A1D2%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22scenarioMgmt.png%22%20alt%3D%22scenarioMgmt.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E9.%20Click%20on%26nbsp%3BCOVID19%20Back%20To%20Work%20Core%20scenario%20to%20run%20and%20test%20or%20make%20necessary%20modification%20to%20UI.%3C%2FP%3E%0A%3CH3%20class%3D%22lia-align-center%22%20id%3D%22toc-hId-1402161439%22%20id%3D%22toc-hId-1402161437%22%20id%3D%22toc-hId-1402161437%22%20id%3D%22toc-hId-1402161437%22%20id%3D%22toc-hId-1402161437%22%20id%3D%22toc-hId-1402161437%22%3E%26nbsp%3B%3C%2FH3%3E%0A%3CH3%20class%3D%22lia-align-center%22%20id%3D%22toc-hId--405293024%22%20id%3D%22toc-hId--405293026%22%20id%3D%22toc-hId--405293026%22%20id%3D%22toc-hId--405293026%22%20id%3D%22toc-hId--405293026%22%20id%3D%22toc-hId--405293026%22%3E%3CSTRONG%3E%3CU%3EHealthcare%20Bot%20Authentication%20and%20Data%20Connection%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E1.%20Add%20Authentication%20Provider%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EGo%20to%20Integration%20-%26gt%3B%20Authentication%20-%26gt%3B%20click%20%2BNew.%26nbsp%3BIn%20the%20%22New%20Authentication%20provider%22%20dialog%20box%2C%20enter%20the%20following%20details%20-%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EName%3A%26nbsp%3BFHIR%20Back%20To%20Work%20Auth%3C%2FLI%3E%0A%3CLI%3EAuthentication%20method%3A%20OAuth%202.0%3A%20Server-to-server%3C%2FLI%3E%0A%3CLI%3EAdd%20accurate%20values%20of%3COL%3E%0A%3CLI%3EClient%20ID%20(copied%20from%20Application%20Registration)%3C%2FLI%3E%0A%3CLI%3EClient%20Secret%20(copied%20from%20Application%20Registration)%3C%2FLI%3E%0A%3CLI%3EAccess%20Token%20URL%26nbsp%3B%3CUL%20class%3D%22lia-list-style-type-circle%22%3E%0A%3CLI%3E-ERR%3AREF-NOT-FOUND-%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flogin.microsoftonline.com%2F%3C%2FA%3E%3CTENANTID%3E-numerical%26gt%3B%2Foauth2%2Fv2.0%2Ftoken%3C%2FTENANTID%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3CLI%3EScope%20according%20to%20your%20Azure%20API%20for%20FHIR%3CUL%20class%3D%22lia-list-style-type-circle%22%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2F%26lt%3Byourservername%26gt%3B.azurehealthcareapis.com%2F.default%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2F%3CYOURSERVERNAME%3E.azurehealthcareapis.com%2F.default%3C%2FYOURSERVERNAME%3E%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3ENote%20the%20%E2%80%9C.%E2%80%9D%20In%20front%20of%20default%20(%2F.default)%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CUL%3E%0A%3CLI%3EClick%20Create%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22EditAuthProvider.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F195275i3E37BAF1A8C9D8D0%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22EditAuthProvider.png%22%20alt%3D%22EditAuthProvider.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E2.%20Add%20Data%20connections%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EGo%20to%20Integration%20-%26gt%3B%20Data%20Connections%20%26gt%3B%20click%20%2BAdd.%26nbsp%3BIn%20the%20%22New%20Data%20connection%22%20dialog%20box%2C%20enter%20the%20following%20details%20-%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EName%3A%20FHIR%20Back%20To%20Work%3C%2FLI%3E%0A%3CLI%3EEnable%20FHIR%20Support%3C%2FLI%3E%0A%3CLI%3EAdd%20Base%20URL%20to%20point%20to%20your%20Azure%20API%20for%20FHIR%20URL%20%26nbsp%3B%3C%2FLI%3E%0A%3CUL%20class%3D%22lia-list-style-type-circle%22%3E%0A%3CLI%3E%3CSPAN%3Ehttps%3A%2F%2F%3CYOURNAME%3E.azurehealthcareapis.com%3C%2FYOURNAME%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CLI%3EAuthentication%20Provider%3A%20FHIR%20Back%20To%20Work%20Auth%20(Server%202%20Server)%3C%2FLI%3E%0A%3CLI%3EClick%20Update%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22EditDataConn.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F195277iCE98062A435B1AE1%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22EditDataConn.png%22%20alt%3D%22EditDataConn.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20are%20ready%20to%20use%20the%20Back%20to%20Work%20template!%3C%2FP%3E%0A%3CP%3EThis%20template%20can%20be%20used%20with%20any%20of%20the%20channels%20available%20by%20default%20including%20%E2%80%93%20Web%20Chat%2FDirectLine%2C%20Microsoft%20Teams%2C%20Twilio%2C%20Facebook%20and%20Telegram.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20class%3D%22lia-align-center%22%20id%3D%22toc-hId-2082219809%22%20id%3D%22toc-hId-2082219807%22%20id%3D%22toc-hId-2082219807%22%20id%3D%22toc-hId-2082219807%22%20id%3D%22toc-hId-2082219807%22%20id%3D%22toc-hId-2082219807%22%3E%3CSTRONG%3E%3CU%3ECreating%20Web%20Chat%20Channel%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3E1.%20In%20Healthcare%20Bot%20admin%20portal%2C%20navigate%20to%20Integration%20-%26gt%3B%20Secrets.%20Copy%20values%20of%20APP_SECRET%20and%20WEBCHAT_SECRET%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22secrets.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F195289i5B117C8F68017444%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22secrets.png%22%20alt%3D%22secrets.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E2.%20To%20deploy%20Web%20Chat%20channel%2C%20go%20to%20-ERR%3AREF-NOT-FOUND-GitHub%20repository.%20Click%20%E2%80%9CDeploy%20to%20Azure%E2%80%9D.%3C%2FP%3E%0A%3CP%3E3.%20Fill%20in%20required%20details%20and%20click%20Next.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22deploytoazure.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F195290i460F605794097A4F%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22deploytoazure.png%22%20alt%3D%22deploytoazure.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E4.%20Go%20back%20to%20Azure%20portal%20and%20navigate%20to%20the%20chosen%20Resource%20Group%20in%20previous%20step.%26nbsp%3BClick%20on%20the%20App%20Service%20(fhirbacktowork%20in%20this%20example).%20On%20the%20left%20pane%2C%20look%20for%20Development%20Tools%20-%26gt%3B%20App%20Service%20Editor%20(Preview).%20Click%20Go.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E5.%20In%20the%20App%20Service%20Editor%20screen%2C%20Click%20on%20Explore%20-%26gt%3B%20WWWRoot%20-%26gt%3B%20public%2Findex.js%20file.%20Scroll%20down%20to%20line%20107%2C%20remove%20the%20comment%20symbols%20%2F*%20and%20*%2F%20from%20lines%20108%20and%20116.%20Change%20trigger%20in%20line%20110%20to%20trigger%3A%20%E2%80%9Ccovid19_backToWork_core%E2%80%9D%2C%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22appserviceeditor.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F195292i3AC98ABD25C4332F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22appserviceeditor.png%22%20alt%3D%22appserviceeditor.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E6.%20Once%20that%E2%80%99s%20done%2C%20you%20are%20ready%20to%20run%20the%20Back%20to%20Work%20template.%20Click%20%E2%80%9CRun%E2%80%9D%20in%20App%20Service%20Editor%20or%20copy%20the%20Azure%20App%20Service%20URL%20in%20a%20new%20browser%20window%20and%20you%20will%20get%20this%20Azure%20website.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22webchat.png%22%20style%3D%22width%3A%20262px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F195293i2746F2D407BCB78B%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22webchat.png%22%20alt%3D%22webchat.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20reading%20and%20let%20us%20know%20how%20we%20can%20help!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EMicrosoft%20Health%20Engineering%20Team%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Bert_LinkedIn.jpg%22%20style%3D%22width%3A%20200px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F195294i9066C9DCCB8151D3%2Fimage-size%2Fsmall%3Fv%3D1.0%26amp%3Bpx%3D200%22%20title%3D%22Bert_LinkedIn.jpg%22%20alt%3D%22Bert_LinkedIn.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E-ERR%3AREF-NOT-FOUND-Bert%20Hoorne%2C%20Microsoft%26nbsp%3BHealthcare%20Industry%20Technology%20Strategist%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Nikita_LinkedIn.jfif%22%20style%3D%22width%3A%20200px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F180770i08B1EB22654DCABD%2Fimage-size%2Fsmall%3Fv%3D1.0%26amp%3Bpx%3D200%22%20title%3D%22Nikita_LinkedIn.jfif%22%20alt%3D%22Nikita_LinkedIn.jfif%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E-ERR%3AREF-NOT-FOUND-Nikita%20Pitliya%2C%20Microsoft%20Senior%20Solutions%20Architect%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Srini_LinkedIn.jpg%22%20style%3D%22width%3A%20200px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F191100iDA92746C7B6B494E%2Fimage-size%2Fsmall%3Fv%3D1.0%26amp%3Bpx%3D200%22%20title%3D%22Srini_LinkedIn.jpg%22%20alt%3D%22Srini_LinkedIn.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E-ERR%3AREF-NOT-FOUND-Srini%20Surendranath%2C%26nbsp%3BWW%20Customer%20Lead%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1425833%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%223steps.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F198497i82F8536F6B27D158%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%223steps.png%22%20alt%3D%223steps.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EMicrosoft's%20COVID-19%20%22Back%20To%20Work%22%20template%20is%20built%20on%20Healthcare%20Bot%20service%20and%20the%20Azure%20API%20for%20FHIR%20service.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1425833%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ehealthcare%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELife%20Sciences%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EModern%20workplace%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1566276%22%20slang%3D%22en-US%22%3ERe%3A%20COVID-19%20Back%20to%20Work%20template%20in%20Microsoft%20Healthcare%20Bot%20with%20Azure%20API%20for%20FHIR%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1566276%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F715933%22%20target%3D%22_blank%22%3E%40Noel_Ramirez%3C%2FA%3E%26nbsp%3B-%20The%20latest%20Back-to-Work%20template%20in%20Healthcare%20Bot%20service%20is%20a%20simpler%20version%20without%20login%2Fauthentication%20and%20without%20FHIR%20connections%2C%20hence%20you%20do%20not%20see%20the%20login%20form.%20We%20updated%20this%20blog%20today%20to%20reflect%20the%20recent%20changes.%20To%20answer%20your%20question%20on%20FHIR%2C%20the%20Azure%20API%20for%20FHIR%20is%20supported%20by%20Cosmos%20DB%20as%20its%20managed%20backend.%20Please%20find%20more%20info%20here%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fhealthcare-apis%2Foverview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fhealthcare-apis%2Foverview%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1566175%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20the%20COVID-19%20%E2%80%9CBack%20to%20Work%E2%80%9D%20template%20in%20Microsoft%20Healthcare%20Bot%20with%20Azure%20API%20for%20FHIR%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1566175%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F173674%22%20target%3D%22_blank%22%3E%40Dale%20Emel%3C%2FA%3E%3C%2FP%3E%3CP%3EI%20am%20new%20to%20FHIR%2C%20how%20could%20I%20read%20the%20data%20enter%20into%20the%20bot%3F%20Is%20this%20a%20Cosmo%20database%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1567322%22%20slang%3D%22en-US%22%3ERe%3A%20COVID-19%20Back%20to%20Work%20template%20in%20Microsoft%20Healthcare%20Bot%20with%20Azure%20API%20for%20FHIR%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1567322%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20there%20a%20COVID-19%20Back%20to%20Work%20Template%20with%20data%20persistence%20in%20Azure%20SQL%20Server%20database%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1569058%22%20slang%3D%22en-US%22%3ERe%3A%20COVID-19%20Back%20to%20Work%20template%20in%20Microsoft%20Healthcare%20Bot%20with%20Azure%20API%20for%20FHIR%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1569058%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F715933%22%20target%3D%22_blank%22%3E%40Noel_Ramirez%3C%2FA%3E%26nbsp%3B-%20Yes%20there%20is%2C%20please%20refer%20the%20following%20links%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fazure-ai%2Fcovid-19-back-to-work-solution-template-using-microsoft%2Fba-p%2F1460240%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fazure-ai%2Fcovid-19-back-to-work-solution-template-using-microsoft%2Fba-p%2F1460240%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcovid19-BackToWork%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcovid19-BackToWork%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Update: This blog was last edited on 8/4/2020. This blog outlines using Healthcare Bot for Back to Work use case with FHIR backend.

 

What is the COVID-19 Back to Work Solution Template?

 

As countries worldwide seek to re-open their economies by relaxing “stay-at-home” orders, many employers are considering how to prepare their facilities and employees for the return to the physical workplace. To do this in a more safe manner, it is critical to monitor employees for common COVID-19 symptoms and provide a simple way for affected employees to physically return to the workplace once they are cleared to do so. Microsoft teams have developed a special solution template to enable employers worldwide to easily create deploy Microsoft technologies to scale and automate those critical steps for return to the workplace. We call it the “Back to Work” solution template and below you will find detailed instructions on how to use this to empower a safer return to the workplace for your organization.

 

Our COVID-19 "Back To Work" template is built on Microsoft Healthcare Bot service and the Microsoft Azure API for FHIR. Some key elements include:

  • Symptom tracking for essential workers who have been exposed to COVID (physicians, nurses, ancillary staff, volunteers)
  • In accordance with CDC guidelines* 
  • Organizational configurable documentation of information such as symptoms, occupational exposure type, and testing status
  • Allows systems to determine when employees will be safe to return to patient care activities or work or campus
  • Supported by Microsoft’s industry leading compliance, privacy, and security portfolio (link)

 

COVID-19 Back to Work Template with data persistence in Azure API for FHIR

 

We will take you step-by-step through the following, so that you can use the “Back to Work” template with FHIR persistence:

  1. Setup Azure API for FHIR
  2. Import Back to Work template
  3. Healthcare Bot Authentication and Data Connection
  4. Create Web Chat Channel and embed in a website

 

Setup Azure API for FHIR

Prerequisite: If you don't have an Azure subscription, create a free account before you begin.

The COVID-19 Back to Work template uses FHIR persistence. To ensure appropriate configuration, you need 3 steps:

1. Deploy FHIR Server

2. Register a Service Client application in Azure AD

3. Configure Azure RBAC

 

Step 1: Deploy FHIR Server

​Login to Azure portal. Click +Create a resource. Search for Azure API for FHIR and click Create.

 

pic1.png

Enter details in Basics 

pic2.png

Enter Resource Group

Account Name (FHIR Server name – must be unique)

Select Region

Select FHIR Version = R4

 

Click Next:  Additional settings

 

Additional settings

pic3.png

Notes:

  • Copy Authority:  https://login.microsoftonline.com/<tenantid> where Tenant ID = deployment tenant
  • Copy Audience:  https://<your-fhir-api-name>.azurehealthcareapis.com where “your-fhir-api-name is the name of the Server you specified in Basics

 

Azure API for FHIR uses Azure Cosmos DB as backend database with a default setting of 400 RU/s. You can change Provisioned throughput (RU/s) to a higher number. More details on Request Units (RU) can be found here.

 

Click Review + Create to create your API for FHIR deployment

 

Step 2: Register a Service Client application in Azure AD

In Azure portal, on the left navigation panel (if not visible, click on the hamburger symbol on left), click Azure Active Directory -> App registrations -> +New registration.

pic4.png

Enter a user friendly name (something like service-client-<yourfhirapiname>). Leave the default supported account types. 

Click Register. 

Once created the Portal will take you to the new Application Registration.

pic5.png

Read more about Public & Confidential Client applications here (link)

Copy the Application (client) ID and save it for later use as “Client ID”.

 

In the same service client application blade, under Manage, click on Certificates and secrets. Click on + New client secret. Enter a description and expiry period for the key and click Add. Copy the generated secret and save it for later use as “Client Secret”.

 

pic6.png

 

Step 3: Configure Azure RBAC

Go to the Azure API for FHIR created in Step 1. In left pane, click on Access control (IAM) and + Add -> Add role assignment. Choose (1) Role: FHIR Data Contributor (2) Assign access to: Azure AD user, group, or service principal (3) Select service-client-<yourfhirapiname>. Click on Save.

 

pic7.png

 

 

Configure Healthcare Bot and Import Back to Work template

 

1. Go to Azure Marketplace and Try out Microsoft Healthcare Bot instance for free.

2. Sign into the Azure portal with your Azure credentials and select Create.

3. In the Microsoft Healthcare Bot blade, provide the necessary details and click Subscribe. You can start with the W1 – Free plan and update Plan later.

4. On successful deployment, Go To Resource and click Configure Account. Verify details and click Create.

5. You will be redirected to Healthcare Bot Service admin portal.

6. Navigate to Scenarios -> Manage. At the top bar, you will find option to Import scenario. The Back to Work scenarios for FHIR will be available soon in the GitHub folder for FHIR persistence **COMING SOON**

7. Navigate to Language -> Localization. At the top bar, you will find option to Import custom strings. The Back to Work custom strings will be available soon in the GitHub folder for FHIR persistence **COMING SOON**

8. In Scenarios -> Manage, the two new scenarios added are:

- COVID19 Back To Work Core: Logical workflow for (a) Registration/login, (b) Daily screening of exposure, symptoms and lab test

- COVID19 Back To Work CRUD: For backend Create, Read, Edit, Delete operations

 

scenarioMgmt.png

9. Click on COVID19 Back To Work Core scenario to run and test or make necessary modification to UI.

 

Healthcare Bot Authentication and Data Connection

 

1. Add Authentication Provider

Go to Integration -> Authentication -> click +New. In the "New Authentication provider" dialog box,​ enter the following details - 

  • Click Create

EditAuthProvider.png

 

2. Add Data connections​

Go to Integration -> Data Connections > click +Add. In the "New Data connection" dialog box,​ enter the following details - 

  • Name: FHIR Back To Work
  • Enable FHIR Support ​
  • Add Base URL to point to your Azure API for FHIR URL​ 
    • https://<yourname>.azurehealthcareapis.com
  • Authentication Provider: FHIR Back To Work Auth (Server 2 Server)​
  • Click Update​

EditDataConn.png

 

You are ready to use the Back to Work template!

This template can be used with any of the channels available by default including – Web Chat/DirectLine, Microsoft Teams, Twilio, Facebook and Telegram. 

 

Creating Web Chat Channel

1. In Healthcare Bot admin portal, navigate to Integration -> Secrets. Copy values of APP_SECRET and WEBCHAT_SECRET

secrets.png

 

2. To deploy Web Chat channel, go to GitHub repository. Click “Deploy to Azure”.

3. Fill in required details and click Next.

deploytoazure.png

 

4. Go back to Azure portal and navigate to the chosen Resource Group in previous step. Click on the App Service (fhirbacktowork in this example). On the left pane, look for Development Tools -> App Service Editor (Preview). Click Go.

 

5. In the App Service Editor screen, Click on Explore -> WWWRoot -> public/index.js file. Scroll down to line 107, remove the comment symbols /* and */ from lines 108 and 116. Change trigger in line 110 to trigger: “covid19_backToWork_core”,

appserviceeditor.png

 

6. Once that’s done, you are ready to run the Back to Work template. Click “Run” in App Service Editor or copy the Azure App Service URL in a new browser window and you will get this Azure website.

webchat.png

 

Thanks for reading and let us know how we can help!

 

Microsoft Health Engineering Team

 

Bert_LinkedIn.jpg

Bert Hoorne, Microsoft Healthcare Industry Technology Strategist

 

Nikita_LinkedIn.jfif

Nikita Pitliya, Microsoft Senior Solutions Architect

 

Srini_LinkedIn.jpg

Srini Surendranath, WW Customer Lead

 

10 Comments
New Contributor

Hey, I am getting error message-Error in connection to FHIR storage I have followed the article strictly and configured Data connection and authentication. Is something missing on your article.

@Amit Puri , I had the same message and validated this: Required Access Token URL is in the form of: https://login.microsoftonline.com/<tenantid>/oauth2/v2.0/token 

 

I had entered only up to tenantid, but was lacking /oauth/v2.0/token... after that, worked like a charm

New Contributor
 

@Ignacio Rauda Salazar

Nope - it didn't help

ScreenshotScreenshot

Microsoft

Some things to check on setting up Authentication

1) Ensure that RBAC is setup and that the registered application has the FHIR Data Contributor role. This article may help:  https://docs.microsoft.com/en-us/azure/healthcare-apis/configure-azure-rbac

 

2) Under Integrations - Authentication Provider -

    Access Token URL should be:  https://login.microsoftonline.com/<numerical-tenantID>/oauth2/v2.0/token

    Scope should be:  https://<yourservername>.azurehealthcareapis.com/.default  (make sure the "." is there)

  

3) Under Data Connections 

    Base URL should be: https://<yourservername>.azurehealthcareapis.com

 

Finally - remember to check your configuration with Postman (read more here: https://docs.microsoft.com/en-us/azure/healthcare-apis/access-fhir-postman-tutorial)

 

Hope this helps

  

New Contributor

@Dale Emel All 3 items - looks good, but from Postman, it looks like steps are outdated for OAuth2.0, let me figure it out.

Visitor
Hi @Dale Emel

After I followed the instructions the app is able to run. However, I expected the app to ask to log in before, but it does not work that way.

Visitor

Hello @Dale Emel

I am new to FHIR, how could I read the data enter into the bot? Is this a Cosmo database?

Microsoft

Hi @Noel_Ramirez - The latest Back-to-Work template in Healthcare Bot service is a simpler version without login/authentication and without FHIR connections, hence you do not see the login form. We updated this blog today to reflect the recent changes. To answer your question on FHIR, the Azure API for FHIR is supported by Cosmos DB as its managed backend. Please find more info here - https://docs.microsoft.com/en-us/azure/healthcare-apis/overview

Visitor

Is there a COVID-19 Back to Work Template with data persistence in Azure SQL Server database?