{width="1.3333333333333333in"
height="1.3333333333333333in"}
ICD-10 is the 10th revision of the International Statistical Classification of Diseases and Related Health Problems (ICD), a medical classification list by the World Health Organization (WHO). It contains codes for diseases, signs and symptoms, abnormal findings, complaints, social circumstances, and external causes of injury or diseases.
ICD2 is a simple, yet friendly bot that assists care providers with the lookup of ICD10 codes. This bot can be deployed and configured for several channels, including Facebook Messenger, Microsoft Teams, Slack, and other clients.
This is a Microsoft SQL Server database with a single table (ICD10Codes). Each row in the table contains an ICD10 code, and its associated text description. A full-text index on the table allows for ICD10 codes to be looked up using natural text search.
A bot built using the Microsoft Bot Framework, NodeJS, and TypeScript that handles user input for searching ICD10 codes.
{width="3.0in" height="1.7342946194225721in"}
Figure 1: ICD2-Bot in Action
-
An Azure Subscription that will host the ICD2 components.
-
Azure Module for PowerShell.
-
SQL Server Management Studio for deploying the ICDDB database to Azure.
-
(Optional) Visual Studio Code for local development.
-
(Optional) NGrok for local development and debugging.
ICD10 codes are stored in a SQL Server database. You must install and configure the database before using ICD2.
While you can use the database scripts located in the db folder to create the database manually, the easiest way to get the database up and running is to perform the following:
-
Download ICD2DB.bacpac to your local machine from here.
-
Upload the ICD2DB.bacpac file to Azure Blob Storage.
-
Import the ICD2DB.bacpac blob into Azure SQL Server.
-
Recommended: Using SQL Server Management Studio, create a SQL Login and add to the dbdatareader role for the database. Use this login when connecting to the database from the ICD2 bot. Do not use the admin password.
You will need your database name, login, and password for the next steps.
You can test the installation of the database by executing the following stored procedure from [SQL Server Management Studio:
EXEC [dbo].[SEARCH_CODES] @keywords = N'edema orbit'
If you get errors running the stored procedure, check the following:
-
Ensure that the SEARCH_CODES stored procedure has been created.
-
Ensure the current user has execute permissions to the SEARCH_CODES stored procedure. The user only needs read permissions for the ICD10Codes table.
-
Ensure that the ICD10Codes table has a FULL TEXT INDEX on all columns.
ICD2 is implemented as a NodeJS application running in Azure App Service. You must install ICD2 to App Service to run and use it.
First, Create a web app bot in Azure using the instructions located here.
-
Select a good bot name that is meaningful to you.
-
Make sure you specify a location near you.
-
Under Bot Template, ensure that SDK Version is set to SDK v.4 and SDK Language is set to Node JS. Choose Echo Bot, as we will deploy over this in later steps.
-
Remember the name of the bot you specified, as well as the resource group you selected. You will need them later during deployment.
Clone or download the *.zip for the bot source code. If choosing the *.zip download, extract the contents to a working directory.
Next, navigate to the working directory, and run the following command after logging into Azure PowerShell.
az bot publish --name "your-bot-name" --resource-group "your-resource-group" --code-dir <path to directory>
We'll need to install dependencies. From the Azure App Service Editor console, run the following command:
npm install --production
This command will take several minutes to run, and you will see several warnings during it's execution. Ignore them unless the command fails completely.
Configure the settings in the web app bot application settings by adding the following values:
-
DB_UID=nameofuser
-
DB_PWD=passwordofuser
-
DB_SERVER=yourserver.database.windows.net
-
DB_NAME=ICD2DB
{width="6.5in" height="2.717361111111111in"}
Figure 2: Configuring the ICD2 App Service instance in the Azure Portal.
[TBD]