24/24 ? - maybe if it's an emergency and the patient is moribund and can't tell you, relatives aren't around,
and some key piece of history is important, like they have had a cardiac pacemaker put in 6 weeks ago,
and the patient presents with hematemesis and shock , but there's also a below normal temperature ; mind you
it might not still get through the bureaucracy of icu admits though, if the patient is deemed too close to the age of palliation (but not too old to have a pacemaker 6 weeks ago) ,
so then 24/24 is still superfluous .
On Tue May 9 11:07 , Tim Churches sent:
Peter MacIsaac wrote:
...
> Under a full web service model the IT systems of small business enterprises
> (like GPs) would need to have the capacity to be always connected to the
> internet ...
As discussed previously, I am not at all convinced that this is true.
Why does a Web service running on, say, a GP practice system, always
need to be available, 24x7? Is the practice open 24x7? Nope. So why does
the practice's Web services need to be available all the time? Of
course, other providers wishing to use the practice's Web services to,
say, deliver a report to them need to have robust retry and fallback
mechanisms to cope with a Web service not being available, but they need
those regardless, because no network, including the Internet, is 100%
reliable and to build systems of Web services based on the assumption
that everything will always be available is asking for trouble. For
further elaboration on these ideas, see
http://ozdocit.org/pipermail/gpcg_talk/2006-April/002906.html
Tim C
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
_______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
