|
|
| Line 1: |
Line 1: |
| if multiple doctors are primary resources on this day, each doctor has to approve the surgeries in which they are the primary resource. | | if multiple doctors are primary resources on this day, each doctor has to approve the surgeries in which they are the primary resource. |
|
| |
| In this app, the surgery planning officer has two views:
| |
| *list view - shows all planned surgery sorted by date and their status (patient, birthday, surgery type, surgery location, surgeon ok [OK/Rejected], surgeon comments, medical ok, financial ok, paperwork ok)
| |
| *schedule view - the user sees the upcoming surgery days in a calendar overview and sees on the date (by background color) if all prework is done and the surgery is good to go. When selecting a date, he will see like in the list view a table of surgeries planned on that date in the day plan (similar to surgery assignment and planning)
| |
| From here:
| |
| *the planning officer can summon for each planned surgery the "surgery data update documentation form" in Kordeus.CORE (see surgery planning template administration), where he can update medical data if the doctor has changes. (NOTE: This form only works for one surgery, so if both eyes are undergoing surgery, this is two independent surgeries and changes!)
| |
| *the planning officer can print a day plan as pdf or automatically send it to the doctors doing the surgeries. This automatically triggers a approval request with the doctors for surgeries, which have not received the medical ok from the surgeon
| |
| Please note: On any change of the medical data or product, the medical approval is revoked (if already provided)
| |
|
| |
|
| == Related articles == | | == Related articles == |
|
| |
|
| * [[Kordeus.SURGERY]] | | * [[Kordeus.SURGERY]] |
if multiple doctors are primary resources on this day, each doctor has to approve the surgeries in which they are the primary resource.
Related articles