Skip to content

Menu

LexBlog, Inc. logo
NetworkSub-MenuBrowse by SubjectBrowse by PublisherJoin the NetworkGet StartedSubscribeSupportContact
Search
Close

Inferences, burden of proof and causation

By Bill Madden on February 4, 2019
Email this postTweet this postLike this postShare this post on LinkedIn
letter-b-black-icon-2.png

With thanks to Awash Prasad for drawing attention to a recent appellate decision from Western Australia: East Metropolitan Health Service v Jane Elizabeth Popovic as executrix of the Will of Emil Popovic [2019] WASCA 18.

East Metropolitan did not challenge the finding that it was liable in negligence. Rather its appeal concerned the potential liability of the neurosurgeon Dr Popovic.

As stated at [5]:

…East Metropolitan’s case on breach was and is founded on a telephone conversation between Mr Panagoulias and Mr Popovic. It was and is common ground that Mr Popovic’s duty of care required him to give certain advice to Mr Panagoulias during that conversation. There was no direct evidence of the content of the telephone conversation from either of the parties to it. The issue as to breach was and is whether an inference could be drawn that Mr Popovic failed to give the required advice.

The hospital’s appeal failed on the breach of duty inference and in relation to causation.

The causation issue focused on the time at which Mr Panagoulias would have arrived at the hospital (if given certain advice) and the time at which antibiotics would then have been administered.

  • Posted in:
    Health Care and Life Sciences
  • Blog:
    Bill Madden's Blog
  • Organization:
    Bill Madden
  • Article: View Original Source

Call us at 1-800-913-0988 or email sales@lexblog.com.

Facebook LinkedIn Twitter RSS
The Library at LexBlog
  • About LexBlog
  • The Field We Built
  • Library at LexBlog
  • Our Beliefs
  • Our Team
  • Contact LexBlog
  • Disclaimer
  • Editorial Policy
  • Terms of Service
  • Get Started
  • Publishing Solutions
  • Compass
  • Submit a Request
  • Support Center
  • System Status
Copyright © 2026, LexBlog, Inc. All Rights Reserved.
Law blog design & platform by LexBlog LexBlog Logo