>> That is what we are talking about. The application ACK is generated when the >> human commits the report to the patient record after reviewing and taking >> action (eg. Urgent recall, No action required) from within the clinical >> application's holding file or inbox. The duty of care for the patient has >> been passed over to the clinician at this point. > > Ok, thanks for clearing that up Geoff. > > I take it the Healthlink client integrates quite tightly > with the clinical application to mesh in with it's recall > system etc. Is this integration done to a standard > interface or is it on a case by case basis with the > clinical vendor? > > Andrew
Hi Andrew, Most of the "interfaces" I've come across are simply drop boxes residing in the file system i.e. the messaging software dumps incoming files into a directory the clinical software is configured to interrogate. The reverse is true for outgoing correspondence i.e. The clinical software dumps a file into the file system and the messaging software knows where to look to scoop it up for encryption and sending. Some (most?) clinical apps are hard coded as to where they look for incoming correspondence and where they dump their outgoing correspondence, however messaging software (including HealthLink and Argus et al) can be configured to drop and collect files to suit the clinical software. As such, getting messaging software to interface with clinical software (via drop boxes) is relatively simple and I don't see this as a major impediment to interoperability. Getting clinical software vendors at each end of the chain to generate and deal with the messages correctly (including ACKs) is where improvement is needed. Regards, Simon -- Simon James Publisher Pulse IT M: 0402 149 859 F: 02 9475 0029 E: [EMAIL PROTECTED] W: http://www.pulsemagazine.com.au PO Box 52 Coogee NSW 2034 _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
