Neuroscience & Neuroimaging Research Collection

Journal article

Fatal brain haemorrhage after MCA dissection: how aggressive should we treat?

Publication status:: Published

Actions

Email

Email this record

Send the bibliographic details of this record to your email address.

Your Email
Please enter the email address that the record information will be sent to.

-
Your message (optional)
Please add any additional information to be included within the email.
Share
Cite

Cite this record

APA Style

Kuker, W., Downer, J., & Cellerini, M. (2012). Fatal brain haemorrhage after MCA dissection: how aggressive should we treat? Neuroradiology, 54(6), 645–648.

MLA Style

Kuker, W, et al. “Fatal Brain Haemorrhage after MCA Dissection: How Aggressive Should We Treat?” Neuroradiology, vol. 54, no. 6, 2012, pp. 645–48.

Chicago Style

Kuker, W, J Downer, and M Cellerini. 2012. “Fatal Brain Haemorrhage after MCA Dissection: How Aggressive Should We Treat?” Neuroradiology 54 (6): 645–48.
Print

Access Document

Publisher copy:: 10.1007/s00234-011-0986-4

Authors

+ Kuker, W More by this author

Institution:: University of Oxford
Division:: MSD
Department:: Clinical Neurosciences
Role:: Author

+ Downer, J More by this author

Role:: Author

+ Cellerini, M More by this author

Role:: Author

Journal:: Neuroradiology More from this journal
Volume:: 54
Issue:: 6
Pages:: 645-648
Publication date:: 2012-06-01
DOI:: 10.1007/s00234-011-0986-4
EISSN:: 1432-1920
ISSN:: 0028-3940

Language:: English
Keywords:: Fatal Outcome

Cerebral Hemorrhage

Male

Young Adult

Intracranial Aneurysm

Humans

Aneurysm, Dissecting
Pubs id:: pubs:241335
UUID:: uuid:abdaa563-eabb-42d2-8595-b9423508141e
Local pid:: pubs:241335
Source identifiers:: 241335
Deposit date:: 2012-12-19
ARK identifier:: ark:/29072/ora_abdaa563eabb42d28595b9423508141e

Terms of use

Copyright date:: 2012

Licence:: Terms and Conditions of Use for Oxford University Research Archive

Views and Downloads

About views and downloads

If you are the owner of this record, you can report an update to it here: Report update to this record

TO TOP