Technology & Operations
Medical 3D Printing 101 – From DiCOM to 3D Printed Model
Speakers: Mr Nigel Yap and Ms Catherine Chia
Date: 2 November 2017 (Thu) | Time: 1400 - 1530
| Location: Academia, Level 1, L1-S1
Workshop Level: Novice
Since its inception in 1976, Additive Manufacturing, otherwise known as 3D Printing, has brought about numerous benefits and solutions to many industries. In recent years, it is seen especially to have become more prominent as a tool in the area of Surgical Simulation and Medical Education.
This rapid emergence is expected to revolutionise how simulation labs and medical educators deliver medical education and service across all disciplines and surgical skill levels. The incorporation of 3D Printing enables Simulation Labs the ability to recreate life-like, patient specific pathology medical models that are taken from past patients’ CT/MRI Scans. In addition, these 3D Printed Models can also be made to emulate different tissues such as skin, muscle, fats and organs. These rubber-like materials aid junior doctors or medical students in identifying the essential tactile feedback that is needed during the learning of any surgical skillset.
Presently, 3D Printing has been applied to various medical disciplines in countries around the world. Simulation Labs and Medical Educators have actively employed this technology to aid and improve current simulation models and surgical practices as well as discover new methods and solutions, all in an effort to improve patients’ outcomes.
Learning Objectives:
-
Summarise and describe the entire process of 3D Printing in the medical industry, going from initial DiCOM file format to 3D Printed Medical Model.
Differentiate and evaluate the types of 3D printers available in the market for various applications of 3D printed medical model in Simulation Labs and Medical Education.
Develop and be able to recommend new surgical skills training modules into Simulation Labs and Medical Education modules with the integration of 3D printing technology.
*Information is correct at time of update.
<< Back to Programme