Darling to shelve NHS IT system

[oracleslave]

I know something about implementing large scale databases on a shoestring budget.

Sorry, don't often call you out on it but in this instance it's true.

[AtW]

The NHS's database requirements sound much like Amazons system with a few bits of other stuff thrown in: http://www.businessintelligencelowdo..._largest_.html

Its all been done before and for not much money.

Exactly.

The main difference is that customers will probably have images stored in their accounts - think flickr.com or even youtube.com.

[oracleslave]

I know something about implementing large scale databases on a shoestring budget.

As has already been pointed out to you repeatedly, there is a little more to this programme than that.

[AtW]

Sorry, don't often call you out on it but in this instance it's true.

Give me £10 mln NHS contract for central DB, I'll sign it and have it implemented within a year and make profit on it: now should I fail, only then you can say you "called me out".

Remember - if you think it's impossible to achieve then you are not good enough to have an opinion about it

[AtW]

As has already been pointed out to you repeatedly, there is a little more to this programme than that.

What I say is that if electronic patient record is the main objective, then FIRST it should be reached and any future work should should be incremental and based on that easy to achieve success.

Building the whole complex thing in one go is insane thing to agree to.

[Mr.Whippy]

Exactly.

The main difference is that customers will probably have images stored in their accounts - think flickr.com or even youtube.com.

That's it! why dont the NHS just use flickr to store x-rays! would save a fortune!

Perhaps you should read up here : http://www.connectingforhealth.nhs.uk/

Oh and a bunch of 7.2k rpm disks probably won't cut it, if you're having every NHS system stuffed into one central database......

[stek]

Exactly.

The main difference is that customers will probably have images stored in their accounts - think flickr.com or even youtube.com.

What about PACS then, where u gonna store patients X-rays? On Photobucket?

[AtW]

Oh and a bunch of 7.2k rpm disks probably won't cut it, if you're having every NHS system stuffed into one central database......

Yeah, a bunch of those disks won't work - tell this to Google who handle real time complex queries!

Viewing a large image is a very easy sequential operation - as long as you have enough bandwidth to sent it out it is easy to implement, especially given that patient records will not be hot spots - you won't 1 mln people looking at Xray of Cherie Blair or something, unlike what youtube has to handle.

[AtW]

What about PACS then, where u gonna store patients X-rays? On Photobucket?

Have you thought of being able to license for a few millions source code of photobucket or such and use it on your own internal secure network? That sure beats paying to reinvent the wheel!

Frankly, this won't be necessary - storing large images that will be accessed sequentially on per patient basis (only few doctors will access same record at the same time) is trivial given current hardware.

[Mr.Whippy]

Frankly, this won't be necessary - storing large images that will be accessed sequentially on per patient basis (only few doctors will access same record at the same time) is trivial given current hardware.

The whole NPfIT is practically trivial according to you.

Seriously, you're talking tulip and making yourself look pretty ignorant.