Also, a refinement of the RFC 3881can be found at: ftp://medical.nema.org/medical/dicom/supps/sup95_fz.pdf
This takes the general framework of RFC 3881 and further specifies requirements for how particular events are to be encoded for medical devices. One of the interesting things learned in the early work with this is that describing events in XML consumes quite a few bytes. Really simple events fit under 1024 bytes, but it does not take much complexity to push past that limit. A much more realistic limit to impose is a 64KB limit. The commonplace event that "PACS archive sent study X about patient Y to workstation A to prestage it for physician Z based on current appointment schedules" chews up a surprisingly large message if you include full details about the study, machines, and times. Since these messages are defined by multiple schema with namespaces (to manage inheritance properly) fully qualified XML tags can become quite large all on their own. The ability of the COOKED transport to indicate the schema is also useful for the receiving servers so that they can route and parse much more effectively. R Horn _______________________________________________ Syslog-sec mailing list Syslog-sec@www.employees.org http://www.employees.org/mailman/listinfo/syslog-sec
