Kordeus.SURGERY: Difference between revisions

From Kordeus Wiki
Jump to navigation Jump to search
← Older edit
VisualWikitext
Stefanseiler (talk | contribs)
Bureaucrats, dev-team, developer, Interface administrators, iroc-team, Suppressors, Administrators, yousee-team
1,381 edits
No edit summary
Stefanseiler (talk | contribs)
Bureaucrats, dev-team, developer, Interface administrators, iroc-team, Suppressors, Administrators, yousee-team
1,381 edits
 
(8 intermediate revisions by the same user not shown)
Line 11: Line 11:
* integrated with Kordeus.CORE agenda
* integrated with Kordeus.CORE agenda


=== Main building blocks ===
=== Main process flow ===


* Step 1: [[Surgery procedure request]] - In a [[Kordeus.CORE]] documentation form a doctor sets a procedure to be planned with a patient. The [[Surgery Procedure Automation Engine (SPAE)]] immediately schedules preliminary appointments and blocks capacities according to the doctors requirements and available capacities. Eventually the main surgery appointment is already visible to the doctor during the procedure request
*Step 2: [[Dev:Surgery patient planning|Surgery patient planning]] - In this process, a surgery planning officer reviews and changes (together with the patient) the automatically assigned appointments. The planning officer may change, create hand out documents and performs all actions required during surgery planing. Once the appointments are confirmed, invitations are automatically created and invitations sent by the [[Surgery Procedure Automation Engine (SPAE)]]
*Step 3: [[Dev:Surgery doctor approval|Surgery doctor approval]] - Before the day of surgery, the surgery planning officer locks the surgery day and digitally requests the doctor to approve his surgeries.
*Step 4: [[Dev:Surgery documentation|Surgery documentation]] - In this step the surgery is documented. Once the surgery is closed, the surgeon signs and automatically a doctoral letter is created, which the surgeon has to review and approve. Once the letter is approved, the sugery planning officer can send the doctoral letter out to the patient and the referring doctor.
=== Main dependencies ===
* [[Surgery Capacity Planning Administration App|Surgery theater capacity planning]] - Allows to define when and where surgery may be performed at all
* [[Surgery Capacity Planning Administration App|Surgery theater capacity planning]] - Allows to define when and where surgery may be performed at all
* [[Surgery Planning Template Administration App|Surgery templates]] - They allow to define the surgery planning flow, the surgery requirements and related actions.
* [[Surgery Planning Template Administration App|Surgery templates]] - They allow to define the surgery planning flow, the surgery requirements and related actions.
=== Main process flow ===
* Step 1: [[Surgery procedure request]] - In a [[Kordeus.CORE]] documentation form a doctor sets a procedure to be planned with a patient.
*Step 2: [[Dev:Surgery automatic assignment|Surgery automatic assignment]] - The [[Surgery Procedure Automation Engine (SPAE)]] immediately schedules preliminary appointments and blocks capacities according to the doctors requirements and available capacities. Eventually the main surgery appointment is already visible to the doctor during the procedure request
*Step 3: [[Surgery patient planning]] - In this process, a surgery planning officer reviews and changes (together with the patient) the automatically assigned appointments. Once the appointments are confirmed, invitations are automatically created and invitations sent by the [[Surgery Procedure Automation Engine (SPAE)]]
*Step 4: [[Dev:Surgery doctor planning|Surgery doctor planning]] - Before the day of surgery, the surgery planning officer locks the surgery day and digitally requests the doctor to approve his surgeries.
== Step 4: Surgeon approval app ==
In this app, a doctor logs on and sees a list of days with planned surgeries. Each day with surgeries should show the overall medical approval status.
Once the surgeon clicks on a day, he sees the list of scheduled surgeries with his participation. The surgeon can click on each of them and sees:
* patient, gender, birthday, surgery type, surgery location, surgeon, medical ok, financial ok, paperwork ok
* relevant medical information for review on this patient (see surgery planning template administration)
* planned products, ... .
* Doctor may: OK, Request change. If change: enter text.
== Step 5: Surgery app ==
This app shows the list of surgeries planned for the current day. The user can pick one surgery and see the medical parameters. In this app he can document the surgery:
# pick actions from predefined actions
# pick products from predefined products
# add non-std. products and non-std. actions
After surgery is finished, the doctor needs to sign the protocoll.


== Related apps ==
== Related apps ==

Latest revision as of 11:21, 10 August 2024

Kordeus.SURGERY is a product, which extends Kordeus.CORE. It unifies, integrates and automates work fragments along the process chain from surgery planning to surgery aftercare into one tool.

Benefits

There are may benefits for the using clincs/practises. Most important are:

  • massive time saving potential for surgery planning
  • increased patient security with approval workflows before surgery
  • automation of prepayment and billing processes
  • surgery document management, including creation and digital signage of documents
  • surgery theater and capacity planning
  • integrated with Kordeus.CORE agenda

Main process flow

  • Step 1: Surgery procedure request - In a Kordeus.CORE documentation form a doctor sets a procedure to be planned with a patient. The Surgery Procedure Automation Engine (SPAE) immediately schedules preliminary appointments and blocks capacities according to the doctors requirements and available capacities. Eventually the main surgery appointment is already visible to the doctor during the procedure request
  • Step 2: Surgery patient planning - In this process, a surgery planning officer reviews and changes (together with the patient) the automatically assigned appointments. The planning officer may change, create hand out documents and performs all actions required during surgery planing. Once the appointments are confirmed, invitations are automatically created and invitations sent by the Surgery Procedure Automation Engine (SPAE)
  • Step 3: Surgery doctor approval - Before the day of surgery, the surgery planning officer locks the surgery day and digitally requests the doctor to approve his surgeries.
  • Step 4: Surgery documentation - In this step the surgery is documented. Once the surgery is closed, the surgeon signs and automatically a doctoral letter is created, which the surgeon has to review and approve. Once the letter is approved, the sugery planning officer can send the doctoral letter out to the patient and the referring doctor.

Main dependencies

Related apps

Related articles

Retrieved from "https://wiki.kordeus.com/index.php?title=Kordeus.SURGERY&oldid=1398"