ASP.NET MVC Razor, Azure CI/CD for Medical Web Project
Budget: $250 – $750 USD
ASP.NET MVC Razor, Azure CI/CD specialist to develop one of the project Phases on the website: http://priorauthspace.com
ALL HTML/CSS/JS IS PROVIDED (out of scope)
(A more detailed requirements document will be provided when a decision to collaborate is made).
Our project is called: “Prior Authorization Space”. O This project is related to USA medicine, and more specifically to the Prior Authorization Process. The Prior Authorization process is a series of steps that a healthcare provider and insurance company take to determine if a patient's requested treatment is covered by their health insurance plan.
We already have some database with codes, service names and requirements for Prior Authorization.
The goal of the web-site is to provide doctors with an easy-to-use form so they can quickly receive a response about the need for pre-authorization with a specific insurer using various search fields and attract as many users as possible to the site.
So far our project consists of 5 Phases.
In Phase 1 of the project, the website and the main Authorization page were created (with REST API). The design of Phase 2 is also ready.
The requirements for Phase 2 are described below.
Requirements (for Phase 2):
In Phase 2 of the project, needs to implement the following components:
1. User Access- ability to identify the users for future purpose
- Magic link
- Social login
2. REST API
Current Structure:
The site consists of two projects: Web App (ASP.NET Core/Razor) and REST API (ASP.NET Web API). The first project acts as a user frontend and is responsible for all user interactions, the second is a pure API that implements all basic operations.
The web application must accept POST requests for all data operations, such as submitting a form, and internally access the API to retrieve data, etc.
Given that the default API security is based on Bearer authentication, the Web App must receive and cache one token (test or production) in memory for the user support (at) priorauthspace.com. The sequence diagram below depicts the desired interactions.
3. Knowledge base:
Knowlwdge base is a set of content pages cross-linked together. The navigation implementation should be in the form of Breadcrumbs to enhance user
experience and improve SEO by showing the path from the home page to the current Page.
4. Misc updates
There are 4 items that have been carried over into Phase 2:
- Save Button: When you click on Save-it should be possible to save the page in pdf format
- Entering a non-existent Insurer: In case user does not select from drop down but instead types and this value is not in the list, the following error message should be displayed: “This insurer is not currently supported, please let us know and we will add it soon”.
- Add another Procedure Code capability: Limit the output of fields to 10
5. CI/ CD Pipeline in Azure
Utilize CI/CD pipelines with Azure DevOps Services for code integration and deployment.
6. QA automation
This includes writing test scripts, managing test data, and continuously updating test cases as new features are developed.
7. Logging
Set up full detailed logs of all API calls and major user operations using standard logger with tab separated table
ALL HTML/CSS/JS IS PROVIDED (out of scope)
(A more detailed requirements document will be provided when a decision to collaborate is made).
Our project is called: “Prior Authorization Space”. O This project is related to USA medicine, and more specifically to the Prior Authorization Process. The Prior Authorization process is a series of steps that a healthcare provider and insurance company take to determine if a patient's requested treatment is covered by their health insurance plan.
We already have some database with codes, service names and requirements for Prior Authorization.
The goal of the web-site is to provide doctors with an easy-to-use form so they can quickly receive a response about the need for pre-authorization with a specific insurer using various search fields and attract as many users as possible to the site.
So far our project consists of 5 Phases.
In Phase 1 of the project, the website and the main Authorization page were created (with REST API). The design of Phase 2 is also ready.
The requirements for Phase 2 are described below.
Requirements (for Phase 2):
In Phase 2 of the project, needs to implement the following components:
1. User Access- ability to identify the users for future purpose
- Magic link
- Social login
2. REST API
Current Structure:
The site consists of two projects: Web App (ASP.NET Core/Razor) and REST API (ASP.NET Web API). The first project acts as a user frontend and is responsible for all user interactions, the second is a pure API that implements all basic operations.
The web application must accept POST requests for all data operations, such as submitting a form, and internally access the API to retrieve data, etc.
Given that the default API security is based on Bearer authentication, the Web App must receive and cache one token (test or production) in memory for the user support (at) priorauthspace.com. The sequence diagram below depicts the desired interactions.
3. Knowledge base:
Knowlwdge base is a set of content pages cross-linked together. The navigation implementation should be in the form of Breadcrumbs to enhance user
experience and improve SEO by showing the path from the home page to the current Page.
4. Misc updates
There are 4 items that have been carried over into Phase 2:
- Save Button: When you click on Save-it should be possible to save the page in pdf format
- Entering a non-existent Insurer: In case user does not select from drop down but instead types and this value is not in the list, the following error message should be displayed: “This insurer is not currently supported, please let us know and we will add it soon”.
- Add another Procedure Code capability: Limit the output of fields to 10
5. CI/ CD Pipeline in Azure
Utilize CI/CD pipelines with Azure DevOps Services for code integration and deployment.
6. QA automation
This includes writing test scripts, managing test data, and continuously updating test cases as new features are developed.
7. Logging
Set up full detailed logs of all API calls and major user operations using standard logger with tab separated table