as a service, the messaging application could provide a call for the clinical application to pass on a user acknowledgement. Does it, and do any clinical applications use it , or does the messaging application just sends files on behalf of the clinical application, sort of like bidirectional ftp (i.e. dumps into a directory at each end, after all the hl7 / secure messaging transport aka smime stuff ) ? On Thu, 2007-05-03 at 11:00 +1000, Ross Davey wrote: > Simon James wrote: > > > > CC: Chris Lynton-Moll (Executive Director of AHML) > > > > Can this point be clarified for the list please Tom/Ross/Andrew/Chris? > > > > Is there any need for message "transport" solutions to be certified by AHML? > > As it is the clinical application (or clinical part of the application > > suite) that generates both the message and the application level ACKs (or > > doesn't), I've always been under the impression that it is the clinical > > application (or clinical part of the application suite) that needs to be > > compliant with AHML requirements? > > > > Surely message transport (integrity of security, speed through the system, > > cost, availability etc) is completely independent of the contents of the > > message, and should be tested accordingly? > > > > > > > If we acted purely as a messaging service and remained strictly in that > role, your comment would be correct. ie the applications would need to > be compliant and it is not a concern of the messaging service. > > However the world being imperfect, there is a need in certain > circumstances for the messaging service/client to create the HL7 > 'packet' using information passed to it from the clinical application. > > Ross > ArgusConnect > > _______________________________________________ > 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
