About Partners Facilities HeartCode BLS Consultation and Training Jobs Scenarios for Sale Policies and Procedures

Clinical Simulation Center Scenario Development

I. Purpose: To produce, test and validate objective clinical scenarios that are based on standards of care/practice. The scenarios will progress according to student intervention or lack of intervention and will be run objectively by each CSC simulation educator.

II. Definitions:

Actions: Manikin responses

Events: Student interventions or student performance expectations

Frames: Section of flowchart that includes simulated manikin (patient) actions

Trends: Physiological changes in manikin actions over time

Handlers: Events customized to initiate an “Action” (vocal, trend, comment, physiological change…)

II. Scenario Development Expectations:

1. To develop objective scenarios driven by student events.

2. Student event(s) or time constraint will progress frames.

3. Trends will be used whenever possible to simulate changes in physiological changes in the manikin.

4. Scenarios will develop and change overtime during testing and validation process.

II. Procedure:

New Scenario Development Process TEAM Approach:

1. Each team member will be assigned roles in scenario development:

Researcher

Programmer

Documentation Developer

Admission Ticket Developer

Debrief Template Developer

Pre/post Encounter Developer

Review Question Developer

2. Complete “Scenario Planning Worksheet”. This can be done as a team or done by an individual and shared with the team for feedback and revisions prior to programming.

3. Researcher – reviews literature for best practice regarding scenario topic and provides input during feedback session listed above

4. Programmer – programs scenario in appropriate simulator software using pre-recorded vocals, standardized event menu, handlers and trends in a student driven format.

5. Documentation Developer – develops chart/EHR forms

6. Admission Ticket Developer – completes student admission ticket template

7. Debrief Template Developer – completes debriefing template

8. Pre/post Encounter Developer – develops pre/post encounter questions and after approval gives questions to Administrative Specialist to enter into simulation management system.

9. Review Question Developer – chooses standardized exam questions that correlate with simulation case

10. Team reviews and revises simulation case documents

11. Team participates in running scenario to test trends, cueing, etc., regarding flow of scenario and student interventions.

12. Programmer will make revisions in program as needed based on team feedback

13. Place scenario and supporting documentation in “Final Sim” folder on the CSC Share.

Scenario Revision and Validation Process:

1. During academic year simulation educators will note possible scenario revisions/improvements during student education sessions.

a. If a critical change is needed prior to the end of the semester, the team will vote on when the change should be implemented and determine assignments for changes and deadlines for making those changes.

NOTE: Critical need for change means that student education is compromised without making such change.

b. The update will be made and program or documents will be placed on CSC share drive in appropriate folder. With notification via mail to team describing changes.

c. All other revisions will wait until annual scenario review process.

2. Every May simulation educators will meet as a team to review scenarios for best practice and revise as needed.

a. Role assignments will be made to each team member

b. Scenario program will be run using different student interventions at different times. The following scenario items will be reviewed:

  • Cueing
  • Trends
  • Student interventions
  • Vocals
  • Other

c. Each portion of the scenario will be reviewed as a team and changes made by individual assigned to that role.

d. Old version if necessary will be moved to archived scenario folder.

e. All changes will be saved to the CSC share drive.