e-ISSN 2395-3950, p-ISSN 2395-440X
Severity: 8192
Message: Return type of CI_Session_files_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 132
Backtrace:
File: /home1/irpmsom/public_html/application/controllers/Home.php
Line: 9
Function: library
File: /home1/irpmsom/public_html/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 294
Backtrace:
File: /home1/irpmsom/public_html/application/controllers/Home.php
Line: 9
Function: library
File: /home1/irpmsom/public_html/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 168
Backtrace:
File: /home1/irpmsom/public_html/application/controllers/Home.php
Line: 9
Function: library
File: /home1/irpmsom/public_html/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 237
Backtrace:
File: /home1/irpmsom/public_html/application/controllers/Home.php
Line: 9
Function: library
File: /home1/irpmsom/public_html/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 317
Backtrace:
File: /home1/irpmsom/public_html/application/controllers/Home.php
Line: 9
Function: library
File: /home1/irpmsom/public_html/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 358
Backtrace:
File: /home1/irpmsom/public_html/application/controllers/Home.php
Line: 9
Function: library
File: /home1/irpmsom/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 282
Backtrace:
File: /home1/irpmsom/public_html/application/controllers/Home.php
Line: 9
Function: library
File: /home1/irpmsom/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 294
Backtrace:
File: /home1/irpmsom/public_html/application/controllers/Home.php
Line: 9
Function: library
File: /home1/irpmsom/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 304
Backtrace:
File: /home1/irpmsom/public_html/application/controllers/Home.php
Line: 9
Function: library
File: /home1/irpmsom/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 314
Backtrace:
File: /home1/irpmsom/public_html/application/controllers/Home.php
Line: 9
Function: library
File: /home1/irpmsom/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 315
Backtrace:
File: /home1/irpmsom/public_html/application/controllers/Home.php
Line: 9
Function: library
File: /home1/irpmsom/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 316
Backtrace:
File: /home1/irpmsom/public_html/application/controllers/Home.php
Line: 9
Function: library
File: /home1/irpmsom/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 317
Backtrace:
File: /home1/irpmsom/public_html/application/controllers/Home.php
Line: 9
Function: library
File: /home1/irpmsom/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 375
Backtrace:
File: /home1/irpmsom/public_html/application/controllers/Home.php
Line: 9
Function: library
File: /home1/irpmsom/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 110
Backtrace:
File: /home1/irpmsom/public_html/application/controllers/Home.php
Line: 9
Function: library
File: /home1/irpmsom/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_start(): Session cannot be started after headers have already been sent
Filename: Session/Session.php
Line Number: 143
Backtrace:
File: /home1/irpmsom/public_html/application/controllers/Home.php
Line: 9
Function: library
File: /home1/irpmsom/public_html/index.php
Line: 315
Function: require_once
e-ISSN 2395-3950, p-ISSN 2395-440X
This to certify that International Research and Publications in Medical Sciences (IRPMS) editorial team has considered to present the best paper award to the corresponding author Kristine Joy G. Boholst, Noli A. Cabildo, David Vi for publishing his outstanding research paper in IRPMS, Volume-3, Issue-4, Oct-Dec entitled as 1. FACTORS FOR TUBERCULOSIS TREATMENT RELAPSE AMONG PATIENTS PREVIOUSLY TAKING CATEGORY 1 STANDARD TUBERCULOSIS TREATMENT REGIMEN IN SELECTED MUNICIPALITIES OF ILOCOS SUR.
editor@ irpms.com, irpmseditor@gmail.com +91 9427222776
Dr. Sutapa Basu IRPMS, 2015; 1(1): 30-34
ABSTRACT
Hanging is one of the most common method opted for committing suicide in India. The presence of ligature mark and its characteristics like its position, direction and appearance over the neck are the most significant criteria to deal with in cases of asphyxial deaths, either due to hanging or strangulation. Various authors have reported controversies regarding the cause of death in the cases of hanging and strangulation. It has been reported in literature that determined person may commit suicide by cutting his throat first and finally hang himself to produce the death while on the contrary; it is rare to observe it in cases of homicide, where an accuse will first cut the throat of the victim and then he will strangulate him. One such rare case was brought to us for the autopsy examination with an alleged history of hanging in which the ligature mark and cut throat injury both were present over the neck. The police presumed that the injuries were sustained due to slipping of ligature during suspension, while after autopsy it was concluded a homicidal cut throat followed by ligature strangulation. This case represents a rare and unexpected presence of two different mechanisms of homicide in one.
Key words: Asphyxia, Cut throat, Homicide and Strangulation
HOW TO CITE THIS ARTICLE:
PubMed Style
Basu S. A Cut Throat Associated With Ligature Strangulation in Victim of Murder. Int Res Pub Med Sci, 2015; 1(1): 30-34.
Vancouver/ICMJE Style
Basu S. A Cut Throat Associated With Ligature Strangulation in Victim of Murder. Int Res Pub Med Sci 2015; 1(1): 30-34.
Web Style
Basu S. A Cut Throat Associated With Ligature Strangulation in Victim of Murder. http://irpms.com/home/article_abstract/19 [Access: Jan 10, 2015].
AMA (American Medical Association) Style
Basu S. A Cut Throat Associated With Ligature Strangulation in Victim of Murder. Int Res Pub Med Sci, 2015; 1(1): 30-34.
Harvard Style
Basu S. (2015) A Cut Throat Associated With Ligature Strangulation in Victim of Murder. Int Res Pub Med Sci 1(1): 30-34.
Designed By - Innctech Solutions