International Simulation Data Registry (ISDR)
The International Simulation Data Registry (ISDR) collects and archives standardized data derived from simulation-based educational activities at various institutions throughout the World. Our purposes in this is threefold:
- Enhancement of the simulation community’s efficacy in translating proven educational methods into standard practice.
- Enhancement of the efficiency of simulation-based translational research.
- Provision of ongoing site-specific educational and quality benchmarking data to improve programmatic performance.
The registry currently involves 32 centers from around the world. Cases eligible for entry include:
- Pulseless Cardiac Arrest (Pulseless Ventricular Tachycardia, Ventricular Fibrillation, Pulseless Electrical Activity, Asystole)
- Malignant Hyperthermia
- Difficult Airway
A copy of our current Data Definitions Manual can be downloaded here. All cardiac arrest metrics are comparable (after conversion) with American Heart Association-Get With The Guidelines Registry data. A document describing this conversion process can be downloaded here.
NEWS: The International Simulation Data Registry is now an official partner of the International Network for Simulation-based Pediatric Innovation, Research, and Education (INSPIRE).
For more information on INSPIRE, please use the following link: https://inspiresim.com/
Instructions for access to the International Simulation Data Registry (ISDR) – please also see the FAQs at the end of the page below:
Please click on your username in the menu above. You will be directed to your log-in page, where you will have to enter your password. That will allow you to click the link to enter data in the Registry.
You may want to print the data sheet to fill out during the simulation (right click on document below to print):20160221-Simulation-Registry-Outcome-Worksheet-V3
Thank you for your participation!
Data pulls with the generated report are found in each center’s access page (if the center has contributed data).
Here is a sample report and a guide on how to interpret the report:
For any questions, please contact:
Matt Kurrek at email@example.com or (416) 399-7640 or
Aaron Calhoun at firstname.lastname@example.org
Note: This Pilot is a Quality Assurance Project. We acknowledge the support of the Research Committee from the Society of Simulation in Healthcare (SSH)
Q: What simulations count?
A: All simulations in which the first abnormal rhythm or condition is a pulseless state. Thus, pulseless ventricular tachycardia, pulseless electrical activity, asystole, and ventricular fibrillation all count for inclusion. Please note that this definition excludes cases where the pulseless rhythm is preceded by another dysrhythmia (such as a case where the patient has ventricular tachycardia with a pulse that, after a few minutes of therapy, transitions nevertheless to pulseless ventricular tachycardia) in which clinicians may, whether accidentally or not, begin CPR. This is to prevent “loading” the data with cases where CPR is already being performed when the pulseless state is entered. What we are looking at primarily is how well the team responds when abruptly confronted with a pulseless state.
Q: Which type of learners count?
A: All learners, whether student level, graduate medical level (i.e., residents), or practicing clinicians can be included. On the first page of the data entry form is a list of learners that explicitly includes students, and gives the option for “other” in case your population is outside those listed. We are not excluding any case based on level of learner.
Q: What do I do if I am missing data?
A: For each field where data could potentially be missing, entering the value 8888 will tell the system that this is a missing data point.
Q: What do I do if the team does not perform a listed action?
A: Here, there are two options that can be chosen, based on whether or not you, as facilitator, feel the team should have performed the action or not. If in your expert opinion an action should have been performed but was not (such as CPR for Vfib) the appropriate code to enter is 9999. This will not only record that the event did not happen, but that it should have per protocol. The alternative option is 0000 (not 0 alone), which indicates that an action was performed but not necessarily indicated. An example of this would be a case of ventricular fibrillation that resolves on the first defibrillation. In this case code dose epinephrine is not indicated, and so you would enter 0000 under time to Epi or vasopressin to indicate that it was not given, but this does not constitute a failure to treat.
Q: What do you mean by in-situ simulation and which in-situ simulations should be entered?
A: By in-situ simulations we mean those simulations that are conducted in actual clinical space and not at simulation centers. Many centers use in-situ simulation as their primary means of conducting cases (in an announced, pre-scheduled fashion), while some use in-situ as a means of conducting unannounced systems tests. We are interesting in collecting data from both types of simulation, so, at present, regardless of how you use in-situ simulation, please enter that data. We recognize that these are completely different simulation types and are currently working on adding a question to distinguish between them. If you wish to give us this information prior to that date, please enter it as a comment on the third page of the data entry form.