Nurse Found dead after prank Call Hoax


Recommended Posts

A female nurse who took a prank call at the London hospital that treated Prince William?s pregnant wife Kate for morning sickness has been found dead, the hospital said on Friday.

The death, which police said they were treating as unexplained, comes days after the King Edward VII hospital apologised after falling for the call from an Australian radio station and relaying details about the Duchess of Cambridge?s condition.

http://www.theglobeandmail.com/life/the-royals/uk-hospital-nurse-who-took-kate-prank-call-found-dead/article6078780/

"A hospital nurse caring for the Duchess of Cambridge, who was duped by two DJs pretending to be the Queen and Prince Charles, is understood to have committed suicide.

Jacintha Saldanha, who has worked at the hospital for four years, was found at an address near the hospital".

http://news.sky.com/...commits-suicide

that is just horrible. not really sure the prank was that horrible. i would assume there was more than that going on and it was just the last push however, its still horrible.

This is horrible news. I can only assume she killed herself out of guilt or pressure or something :( So, so sad :( I should imagine those DJ's bitterly regret the idea to do that prank call now :(

I don't know if they should be "held accountable", but certainly they will be vilified for this. Sometimes radio DJs do some really terrible things for 'shock value ratings'.

  • Like 3

Thing is all she did was transfer the call she did not give out any personal details

The DJ's should be held accountable for her killing herself

No they shouldn't.

It was a pretty dick move though. I think a lot of us will be writing to the standards board about it >.>

The DJs said themselves they never thought that that the call would be taken seriously.

They will probably lose their jobs.

I found the call amusing it made me laugh.

Im not laughing now though.

Im sure William and Kate also found it amusing, its a shame they hadn't said so earlier.

Im not blaming them though.

A nurse at a London hospital who took a hoax call about the Duchess of Cambridge has been found dead.

The Duke and Duchess of Cambridge said in a statement they were "deeply saddened" by the death of the nurse, named as Jacintha Saldanha.

King Edward VII hospital paid tribute to "a first class nurse who cared diligently for hundreds of patients".

Details of the pregnant duchess's medical condition were unwittingly revealed to two Australian DJs.

Mel Greig and Michael Christian, from Sydney radio station 2Day FM - which says it is preparing a statement - posed as the Queen and Prince Charles in a call early on Tuesday morning.

Source

http://www.bbc.co.uk/news/uk-20645838

Why is this in "It's a conspiracy!" ? Well, why not, something to talk about, was she pushed or did she fall :p

Such a bizarre and tragic story. While yes the DJs were ultimately responsible and definitely should be reprimanded now that their actions indirectly led to a death, one still needs to ask how hospital protocol could have broken down that easily by forging voices.

And yes, from some publication I read in the past, nurses work in a very stressful environment, with very few hospitals taking initiatives to help improve working conditions such that they'll make fewer mistakes on the job (or if they do err, that they're not immediately castrated for making mistakes).

It's sad that - if it's confirmed as a suicide - these DJs have cost a life in the name of low-brow entertainment. While they couldn't have foreseen such an outcome they should be held responsible to the maximum extent that the law allows. I hope this rests heavy on their consciences.

Such a sad story. :cry:

This topic is now closed to further replies.
  • Posts

    • But the reality is it will work for people's needs, and they don't care about the technology that makes it. Clearly not everyone's needs, but that low end space where personal laptops were only used to type emails, watch content and browse websites, but they didn't want to do that on a small screen device. Heck, writing that out I can now see the connection and reason it'll do so well. Apple is about experience. If the experience is bad, they don't release it. Low end Windows laptop manufacturers up until this point have not taken that into consideration ever before, so slow laggy usage with brittle slimey plastic shells were common. I hope that the low end space at least creates better physical products that last a bit longer, and if Microsoft get their act together, they could also have a solid OS on such low end hardware that would actually make the experience work for what the hardware was intended for. The fact that the CPU is a "cellphone", sorry mobile phone processor is irrelevant. It's about the experience, and so far, that sounds quite solid.
    • Hello, Bonjour is Apple's implementation of a multicast-DNS service, which allows devices running Apple's software and/or hardware to find each other on your local network.  I believe the Windows version was last updated around 2010. If you do not need it, you can stop and disable the Bonjour service in the Services Control Manager (filename: SERVICES.MSC).  Once you have done that, the operating system will no longer attempt to load the service. Regards, Aryeh Goretsky  
    • This AMD RX 9070 16GB GPU that performs close to Nvidia 5070 is under $600 by Sayan Sen With the memory shortage that's prevalent nowadays, discounts are super-hard to get. As such we post good deals whenever they pop up. Recently, we covered a few great discounts on SSDs wherein you can get a 4TB TeamGroup NVMe PCIe Gen4 drive for just $400 thanks to a special coupon. If you want a faster product but don't need all that capacity, you can also opt for Samsung's 990 PRO 2TB that is on sale for its lowest price in over three months. Let's say though that you are on the hunt for a 1440p gaming card. In that case AMD's RX 9070 non-XT can help, and with its 16GB VRAM, you can also run AI models locally without worrying about bottlenecking (check out our recent 9070 GRE reviews for gaming and productivity to get an idea). The PowerColor Reaper variant of the RX 9070 is currently on sale for just $580 which is a very good price in the current state of affairs (purchase link under the specs table down below). The Reaper cooler on this 9070 uses a triple‑fan design with ring‑blade fans, paired with premium dual ball bearings to extend lifespan and reduce friction. "Intelligent" fan control allows the fans to remain idle at lower temperatures, only spinning up when the GPU is under load. A nickel‑plated copper base makes direct contact with both the GPU and memory modules, helping to spread heat evenly. PowerColor also applies Honeywell PTM7950 phase‑change thermal interface material (TIM), which fills microscopic gaps between the die and heatsink for more efficient thermal transfer. The fan shroud is shorter in height as the firm has made it such that it can be used in certain SFF (small form factor) cases. The technical specifications of the Reaper RX 9070 are given in the table below: Specification Value Stream Processors 3584 Units Video Memory 16GB GDDR6 Memory Speed 20.0 Gbps Memory Interface 256-bit Engine Clock Game Clock: up to 2070 MHz Boost Clock: up to 2520 MHz Bus Standard PCI Express 5.0 x16 Display Connectors 1 x HDMI 2.1b, 3 x DisplayPort 2.1a Maximum Resolution DisplayPort: 7680 × 4320 HDMI: 7680 × 4320 Board Dimensions 289mm × 111mm × 41mm 304mm × 127mm × 42mm (with bracket) Slot 2 Minimum System Power Requirement 600W Power Connectors Two 8-pin PCI Express Get the PowerColor Reaper RX 9070 at the links below (you get only a 90-day warranty on Woot): PowerColor Reaper Radeon RX 9070 16GB Graphics Card (RX9070 16G-A): $579.99 (Sold and Shipped by Amazon US) (Was: $700) PowerColor Reaper Radeon RX 9070 16GB Graphics Card (RX9070 16G-A): $559.99 (Sold and Shipped by Woot US) Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • Are they marketed as an entry into astronomy or astrophotography? I do astrophotography. With big rigs, lots of computers, cables and headaches. I love it. And by learning this ridiculously complex hobby, I’ve learned about the objects I’m shooting. Astronomy followed from photography.
    • Microsoft confirms Recycle Bin bug across all versions of Windows by Usama Jawad A couple of days ago, we reported that the latest Patch Tuesday update has seemingly resulted in a lot of issues for many users, including OneDrive and Dropbox access problems, BitLocker recovery lockouts, and BSODs. Although Microsoft is yet to acknowledge these bugs, it has confirmed another, relatively smaller issue across all supported versions of Windows. In an update on its Windows Release Health Dashboard, Microsoft has confirmed that after installing June's Patch Tuesday update (KB5094126), you'll experience unexpected behavior when leveraging Recycle Bin. Basically, when you attempt to delete an item from the Recycle Bin, the confirm dialog will show you the internal file name of that content rather than the actual name. For example, the file may be named abc.png, but the confirm dialog will ask if you're sure that you want to permanently delete $Rxxxxx.png from the Recycle Bin. This is pretty much it for the scope of the bug itself; it just displays the wrong name in the confirm dialog. The correct name will be shown in the list view of the Recycle Bin and if you restore the file, it will return with the correct name as well. This issue affects pretty much all supported versions of Windows client and server, including: Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSB 2016 Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012 As things currently stand, Microsoft is working on a concrete solution that will be released in a "future" Windows update. It remains to be seen if the firm will wait till the next Patch Tuesday or roll out an out-of-band (OOB) fix. The good news is that commercial customers can deploy a workaround right now, but they will have to reach out to Microsoft Support for Business for additional details.
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      579
    2. 2
      +Edouard
      184
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      72
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!