eng appeal

This commit is contained in:
2025-11-13 13:09:46 +05:00
parent 1963ab346f
commit 4febb93ec7
74 changed files with 330 additions and 1 deletions

View File

@@ -2,4 +2,5 @@
- [Работа с обращениями](./Работа с обращениями/)
- [Нецелевые запросы](./Нецелевые запросы/)
- [Настройка замещения](./Настройка замещения/)
- [Работа под замещением](./Работа под замещением.md)
- [Работа под замещением](./Работа под замещением.md)
- [User Guide](./User Guide/)

View File

@@ -0,0 +1,160 @@
Website for working on the Lexema portal - [https://lexema.zub.ru/](https://lexema.zub.ru/)
Login Start Page
![alt text](media/en1.png)
Initial Page
![alt text](media/en2.png)
## Stage 1 of Non-Targeted Request
To create a Non-Target Request, click the button in the tile menu __«Create non-target request»__
![alt text](media/en3.png)
![alt text](media/en4.png)
A form will open.
![alt text](media/en5.png)
Mandatory fields for filling will be highlighted in red when sending the request through the route.
![alt text](media/en6.png)
__Fill in the patients details:__
<br/>Full Name MRN and Full Name
<br/>Date of birth
<br/>Contact phone
<br/>Patient Category VMI, Cash payment, Not specified.
<br/>Short description of the request
<br/>![alt text](media/en7.png)
__Main Information:__
<br/>Urgency Yes, No, Unknown
<br/>Operators contact number operators internal number
<br/>Request Category select from the dropdown list
![alt text](media/en8.png)
To select «Subdivision», you need to click the «plus» button ![alt text](media/en9.png)
![alt text](media/en10.png)
From the dropdown list, select your direction: General Medicine or Dentistry.
Then click on the empty Responsible manager field and click «Insert».
![alt text](media/en11.png)
<br/>![alt text](media/image-48.png)
If desired, you can add comments.
![alt text](media/en15.png)
You can also add __attachments__.
![alt text](media/en16.png)
Once all fields in the request are filled, send the non-target request through the route __«Send Workflow»__.
![alt text](media/en17.png)
The route is built. Then click the **«Register»** button.
![alt text](media/en18_1-1.png)
Click «OK»
![alt text](media/en19.png)
The request will be visible in the sent items (Inbox) until it is processed
![alt text](media/en20.png)
Upon completion of a non-targeted request, a comment (response) will be received as follows:
A push notification to the email with the comment on the non-targeted request.
<br/>The token "Main Page" "Inbox".
![alt text](media/en31.png)
After receiving the response, the agent needs to go to the "Inbox" token, open the request, and in the upper left corner, click “Finish”.
![alt text](media/en30.jpg)
## Stage 2 of Non-Targeted Request
Requests received for processing are located on the main incoming requests screen.
![alt text](media/en1-1.png)
To complete the non-targeted request stage, you need to click the "Confirm Execution" button, fill in the mandatory field, and click "OK."
![alt text](media/en2-1.png)
<br/>![alt text](media/en3-1.png)
Comments about completing the stage will be displayed by clicking the "Route" button. ![alt text](media/en4-1.png)
<br/>![alt text](media/en5-1.png)
Without completing the stage, a comment can be added to the "Entering comments" table by clicking the "Add" button.
![alt text](media/en6-1.png)
## Registry of non-target requests
All non-target requests can be found in the «Appeal Journal» on the main form
![alt text](media/en21.png)
In the what to find field, select «Non-targeted requests data» and click
![alt text](media/en22.png)
![alt text](media/en23.png)
The selection by categories can be collapsed
![alt text](media/en24.png)
Colors in the selection
<br/>Red - Overdue
<br/>Yellow 2 hours before any stage is overdue or one of the stages is overdue
<br/>White in progress
<br/>Green closed
## Participants of the route by request categories
The route for a non-target request consists of three stages:
<br/>Stage 1: Initiator Start the route
<br/>Stage 2: Responsible persons Execute
<br/>Stage 3: Initiator Complete
For each category, Observers are assigned who have access to non-target requests. They also receive a notification about delays if the request processing deadline expires.
| | Direction | Category | Performers | Observers |
|---|---|---|---|---|
| 1 | General Medicine | Request to send documents (invoice, medical report, refund form) | Alaa Ali Rahal <br/> Shayma Mohamad | Anna Voskanyan <br/> Wesam Al Ashkar <br/> Mustafa Omer |
| 2 | Dentistry | Request to send documents (invoice, medical report, refund form) | Alaa Ali Rahal <br/>Shayma Mohamad | Anna Voskanyan <br/>Olga Voronets <br/>Mustafa Omer |
| 3 | General Medicine | Approval status | Imran Mohamed <br/>Priya Manoharan | Anna Voskanyan <br/>Mustafa Omer |
| 4 | General Medicine | Test results | Alaa Ali Rahal <br/>Shayma Mohamad | Anna Voskanyan <br/>Wesam Al Ashkar <br/>Mustafa Omer |
| 5 | General Medicine | Worsening condition | Wesam Al Ashkar <br/>Alaa Ali Rahal <br/>Shayma Mohamad | Anna Voskanyan <br/>Charalampos Harris Zourelidis <br/>Mustafa Omer |
| 6 | Dentistry | Worsening condition | Olga Voronets <br/>Alaa Ali Rahal | Anna Voskanyan <br/>Charalampos Harris Zourelidis <br/>Mustafa Omer |
| 7 | General Medicine | Explanation of prescribed tests/medications | Wesam Al Ashkar <br/>Alaa Ali Rahal | Anna Voskanyan <br/>Charalampos Harris Zourelidis <br/>Mustafa Omer |
| 8 | General Medicine | Approval status - no request (no appointment, medical record not filled) | Wesam Al Ashkar <br/>Imran Mohamed <br/>Priya Manoharan | Anna Voskanyan <br/>Mustafa Omer |
| 9 | Dentistry | Approval status - no request (no appointment, medical record not filled) | Olga Voronets <br/>Imran Mohamed <br/>Priya Manoharan | Anna Voskanyan <br/>Mustafa Omer |
| 10 | General Medicine <br/> Dentistry| File wont open, application not working | Ihsana K Mohammed | Anna Voskanyan <br/> Mustafa Omer |
| 11 | General Medicine | Results not received, although they were sent | Alaa Ali Rahal <br/>Shayma Mohamad | Anna Voskanyan<br/> Mustafa Omer |
| 12 | General Medicine | Want to contact the doctor (Questions after the visit) | Wesam Al Ashkar | Anna Voskanyan <br/>Mustafa Omer |
| 13 | General Medicine | Availability of medications for IV drip | Alaa Ali Rahal <br/>Shayma Mohamad | Anna Voskanyan <br/>Wesam Al Ashkar <br/>Mustafa Omer |
| 14 | General Medicine | MRI and CT Scan Details | Alaa Ali Rahal <br/>Shayma Mohamad | Anna Voskanyan <br/>Wesam Al Ashkar <br/>Mustafa Omer |
| 15 | General Medicine <br/> Dentistry | Send a payment receipt, send a link to the payment | Mustafa Omer <br/> Maryna Protsenko <br/> Narek Aleksanian <br/> Nataliia Loboda| Anna Voskanyan |
If you have any questions about working in Lexema, please contact us by clicking on "headphones"![alt text](media/en25.png)
![alt text](media/en27.png)

View File

@@ -0,0 +1,2 @@
- [Non target request](Non target request.md)
- [Working with the Appeal Card](Working with the Appeal Card.md)

View File

@@ -0,0 +1,166 @@
# Working with the Appeal Card
## Creating an Appeal Card
To create a patient appeal card, select the item in the tile menu “Create Appeal Card”.
A form will open<br/>
![alt text](media/a1.png)
In the opened window, you need to fill in the card fields; lets consider them by blocks:
1) __«Patient data», «Request text»__
<br/>![alt text](media/a2.png)
2) __"Main Information Block"__
<br/>![alt text](media/a3.png)
- _Category_
<br/>Select from the “Appeal Categories” dropdown list:
![alt text](media/a4.png)
- _Pre-Trial_
- _Subdivision, Responsible Manager_
<br/>![alt text](media/a5.png)
At the second stage, Responsible Managers become participants with the “Accept” action, as well as Branch Managers, via AND for multiple branches;
Responsible Managers are also participants in the “Execute” stage; You can specify multiple divisions and their responsibles if the appeal concerns several branches or departments, using the “Add” button.
To select a subdivision, click the “plus” to the right of “Responsibles”.</br>![alt text](media/a6.png)
Click “Add”, select the required subdivisions from the dropdown list, click the “Responsibles” field (it will auto-fill).
![alt text](media/a7.png)
In the “Responsible Manager” field, Chief Physicians of the branch are selected; if there is no such position, an employee with the position of Manager will be selected.
After that, click the “Insert” button.
![alt text](media/a8.png)
- _Direction_
<br/>Select the direction; Observers are selected depending on the chosen “Direction”.
![alt text](media/a9.png)
- _Reason for appeal_.
<br/>Selected from the dropdown list.
![alt text](media/a10.png)
- _Received from_<br/>
- _Appeal source_<br/>
- _Status_<br/>
- _Accepted by_<br/>
- _Payment type_<br/>
- _Counterparty_ insurance company, if known
![alt text](media/a11.png)
For the categories Quality of Treatment and Volume, the route also adds the Expert Physician stage (Conduct expert assessment). If the appeal is from an Insurance Company, the Initiator (accept) is added between Responsible Managers and the Expert Physician.
3) In the __“The timing of the analysis”__ block, fill in the “Review Start Date” field. When sending the card along the route, a warning will appear if the field remains empty.
![alt text](media/a12.png)
Planned review deadline is 5 working days, excluding the “Review Start Date”; “Deadline Extension” filled in by the Call Center employee at their stage, by the CC Manager at any stage. When changing the “Deadline Extension” field, the Planned review deadline also changes.
The “Planned review deadline” value is set as the deadline for the route stages by the responsible person.
“Deadline for insurance” 2 working days, excluding the Review Start Date.<br/>
The value is set as the deadline for the stages of reviewing appeals from insurance companies.<br/>
The response date is also filled in manually. The number of review days is calculated automatically in working days according to the production calendar.<br/>
4) Employees for whom the appeal is issued must be selected in the __“Employees”__ table:
In the “Employees selection” column, a dropdown list of employees from the management structure.<br/>
By entering part of the last name, you can filter the search:
![alt text](media/a13.png)<br/>
When selecting “Not defined”, the responsible person at the execute stage will need to add a new employee.
5) __“Decisions of Responsible Managers”__ Table
Using the “Load” button, the table is filled with rows for entering decisions and preventive measures for employees and categories
![alt text](media/a14.png)
Extra rows can be deleted. Deletion is also available at the “Correct” stage.<br/>
Rows in the “Decisions of Responsible Managers” table added by the initiator are not available for deletion by other route participants Responsible Managers.
![alt text](media/a15.png)
A Contact Center employee always has the option to withdraw the card using the button. ![alt text](media/a16.png)<br/>
To extend the review deadline at the request of route participants, it is necessary to fill in the field "Extension of the review deadline".<br/>
![alt text](media/a17.png)
## Role: Responsible Manager
### Description
Cards for review are located on the main screen in the "Inbox" tab.
![alt text](media/a18.png)
In the request card, the Appeal Text and review deadlines are indicated.
![alt text](media/a19.png)
By clicking on Attachments, you can add files related to the review.
![alt text](media/a20.png)
### Accept
At the "Accept" stage, you can add an employee to the card's route for review with the action "prepare"
To do this, click on the route.![alt text](media/a21.png)
Select the current stage and click Stage participant.
![alt text](media/a22.png)
A new stage will be added with an empty field for adding a participant.
![alt text](media/a23.png)
From the dropdown list, select the employee (this field is mandatory).
![alt text](media/a24.png)
Then click _"Prepare"_.
![alt text](media/a25.png)
You can add a comment when sending the card along the route.
![alt text](media/a26.png)
### Execute
When the card arrives for processing with the action "execute", it is necessary to fill in the table "Decision of the Responsible Manager".
![alt text](media/a27-1.png)
Mandatory fields are highlighted in red depending on Validity.
![alt text](media/a28.png)
The field "Who is guilty (Full Name)" is taken from the Employees table; you can add a new employee and then change it to the new one in the "Decision of the Responsible Manager".
![alt text](media/a29.png)<br/>
![alt text](media/a30.png)
If the employee "Not determined" is specified, it is necessary to fill in the "Employees" form and change the field "Who is guilty (Full Name)" in the "Decision of the Responsible Manager" table to the new participant.
If the review deadlines are approaching the end, you can click to send for revision, adding the corresponding comment with a request to extend the review deadline (excluding appeals from the insurance company).
![alt text](media/a31.png)<br/>
![alt text](media/a32.png)
Comments are displayed in the route.
![alt text](media/a33.png)

Binary file not shown.

After

Width:  |  Height:  |  Size: 71 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 55 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 82 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.5 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 73 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 67 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 68 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.5 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 88 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 56 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 59 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 53 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 54 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 61 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 61 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 36 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 44 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 44 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 69 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 24 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 863 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 71 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 100 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 48 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 42 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 44 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 46 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 87 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 69 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 66 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.9 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 90 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 726 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 97 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.9 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 71 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.3 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 82 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 31 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 78 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 48 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 58 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 20 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 818 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 78 KiB