An exclusive report by JTBC's 'Newsroom' on November 4 disclosed that the autopsy report on Shin Hae Chul the other day did not cover everything, revealing that the 0.3 cm perforation the forensics rep publicized yesterday through an official briefing was not the only one. The exclusive report confirmed there was actually another perforation that was 2 cm large!
This second perforation was revealed to have been about 3 cm away from the one reported through the news on November 3. The National Forensic Service revealed that the perforation was created by the Asan Hospital during first aid to get rid of the contamination within the pericardium and was sewn up as normal after the emergency care.
The National Forensic Service revealed that the 2 cm perforation purposely created by Asan Hospital had nothing to do directly with Shin Hae Chul's death and explained the reason this was not disclosed during the briefing was because it had nothing to do with the cause of death.
SEE ALSO: Autopsy results show Shin Hae Chul's cause of death to be blood poisoning
Currently, the forensics team is investigating the exact cause of the 0.3 cm perforation, but thinks it is highly possible that it came about during the surgical procedure done by Sky Hospital, which puts weight on the possibility of malpractice.
Meanwhile, Asan Hospital and Sky Hospital are portraying conflicting opinions by pointing fingers at the other for possible medical malpractice. Sky Hospital is claiming they did not touch his heart at all during their procedure, whereas Asan Hospital said that when Shin Hae Chul arrived at the hospital in an unconscious state, his pericardium had already been filled with contaminants and the perforation had already been there.
In addition, it was revealed that another woman, similarly to Shin Hae Chul, had received stomach band surgery at Sky Hospital, where a perforation was discovered during the removal process and after which she passed away within four months. Currently, her family is suing Sky Hospital for malpractice.
Log in to comment