Difference: OrderlySimulation (5 vs. 6)

Revision 62010-11-26 - NickSimmons

Line: 1 to 1
 
META TOPICPARENT name="WebHome" 
<-- 
    
 
  • 
 
      

    •  Set ALLOWTOPICVIEW = TWikiAdminGroup,Main.NickSimmons,Main.MichaelOSullivan,Main.CameronWalker,Main.AndrewPeterson,Main.TimDenison,Main.TimWinstone

      •  
    •  Set ALLOWTOPICCHANGE = TWikiAdminGroup,Main.NickSimmons,Main.MichaelOSullivan,Main.CameronWalker

     

 
-->
Changed:
<
<		Nick's research blog
>
>		ADHB Orderly Simulation Project
 
Changed:
<
<		15/11/10-Read through G.O.A.L user guide and Chapter 1 of the report.
>
>		Objectives:
 
Changed:
<
<		-Read up on C++ to refresh my knowledge
>
>		-Use historical data out of the INFRA transit booking system to develop a simulation of in-patient transit between Radilogy and other departments with the assistance of orderlies.
 
Changed:
<
<		-Attempted to compile GOAL in Windows XP
>
>		-Once the simulation has been developed and validated, use it to explore different scheduling scenarios.
 
Changed:
<
<		-Read up on Boost 1.33.1 and the building of it using bjam.exe
>
>		Expected outcomes:
 
Changed:
<
<		-Attempted to build Boost but discovered compatibility issues with Visual Studio 2008
>
>		Summary of ADHB Meeting 25/11/10
 
Changed:
<
<		-Decided to work on compiling GOAL in 64 bit Linux instead of Windows
>
>		-Ethics approval required as particular patients may be identified from the data
 
Changed:
<
<		-Had issues with the make files, the first issue being resolved by using the 'clean' command
>
>		-Radiology Sites-Level 5 (main site), Level 2 (Emergency), Level 9 (Maternity)
 
Changed:
<
<		-Read up on make files in order to be able to potentially write a make file for the boost library, as well as edit the makefiles for the other libraries and test goal executable.
>
>		-Focussed on inpatients, those already admitted. These patients are moved to/from radiology. This could be from any ward/theater/critical care.
 
Changed:
<
<		-- TWikiAdminGroup - 14 Nov 2010
>
>		-Two orderly teams. We are focussing on the non-maternity team.

-Transfers are scheduled using an online booking system by the MRT imagers.

-Bookings may not be communicated correctly, but we will assume they are for the purposes of this project

-The booking system is known as INFRA

-The time taken for the radiography procedures is relatively reliable, the main variability is in the set-up times for different patients, which depends on the condition of the patient.

-Approximately 2/3 of patients can be taken by orderlies on their own, and around 1/4 or more require the presence of a transit nurse due to the condition of the patient.

-Specific nurses are assigned to be transit nurses for a particular shift. The ratio of transit nurses to orderlies is around 1:4.

-The target is for a patient to reach their destination within 15 minutes of the scheduled time.

-As a measure of the arrival time, we use the time the orderly calls the dispatcher to report the job completed-assume that this is the arrival time, no delay from orderly.

-Dispatcher will schedule MRIs in preference to X-rays

-Return+transit jobs are handled by the same scheduler

-Need to do return jobs-if too many people are left waiting then beds fill up and people cannot be transferred into Radiology.

-Possible thing to explore with simulation: what happens if the orderly stays with the patient throughout the radiology procedure

-First step in simulation-use historical data.

 
META TOPICMOVED by="BaseUserMapping_333" date="1290674958" from="NDSG.SimulatingOrderlies" to="NDSG.OrderlySimulation"
View topic | History: r14 < r13 < r12 < r11 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback