The separate raft of messaging providers we have now only exist because there are no annointed standards for secure health messaging, IMHO - they are a temporary phase (so is life...).
... and a dominant clinical application vendor seemingly completely uninterested in this area.. this too shall pass (fingers crossed)
Sure, but where is the best place to build in such alerts - in the clinical application, which has access to all the necessary data, or in the secure messaging conduit software like, say, Argus Connect or the Healthlink client application? I would suggest that the former is the sensible place, along with all the other decision support and quality assurance tools that good clinical software ought to have.
Exactly - I'm not reassured particularly that my pathology results are arriving in healthlink or medical-objects (whether they ACK or not), anymore than I am reassured by a transport level ack. For all I know, noone is looking at the medical objects document store? Maybe the message is going to get mangled in the hand off from message provider to clinical app - the place for ACK'ing messages is in the clinical app where the doctor is dealing with correspondance, managing recalls and reviewing notes. Healthlink and medical-objects should be licensing their message layers to clinical app vendors to integrate fully into their programs. The current situation (of separation) is a strange confluence of events and surely will pass? Which clinical vendor will lead the way (and step up to the plate - to horribly mix metaphors)? Andrew _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
