hi Sam > The summary of the time series can be as structured as you like. No limit ? > just archetypes. The fact that the first requirement you expressed was a > graphic as part of the report, but it has never been archetyped.
except that the definition is "optional summary data expressing e.g. text or image which summarises entire history." I don't think this definition is sufficiently broad, and I always get unaccountably uncomfortable when people ignore the restrictions imposed by definitions. > Protocol began as there is a lot of data about how information is captured > that is of secondary importance. This does not mean it is not important to > some key users. The good part about having this set of data is that it can > be agreed that by clinicians that they do not want this data ?in their face? > when looking at the EHR. This means that there can be a generic display > archetype for the different entries that can group this data and make it > available through a click, mouse over or whatever. It is pragmatic in a > world where we start to share structured data that is not known to a > particular system (at least not until a later release.) except that we face the situation where the structuring data is "protocol", the details are very much "in the face" kind of stuff, and therefore this coupling of "paradigm" and "not in the face" breaks down. Grahame
