This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Supplemental text

From HL7Wiki
Revision as of 14:54, 8 May 2007 by Riksmithies (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

How to represent "Supplemental Text"

Re: definition of Act.text

"To communicate "supplemental text", an act relationship (e.g. "component" or "subject of") should be created to a separate Act with a bare Act.text attribute should be used to convey the supplemental information, possibly with a code indicating "annotation" or some similar concept."

We could do with a standard pattern for sending this.

Issue

There are several possible ways, one being:

classCode="ACT"
moodCode="EVN"
id=<some id> [optional]
text="this text supports a parent act"
The act relationship to connect this to the act that it supports would be fixed at COMP[any need for another code?].
No other attributes are permitted.

The reason for no further attributes is that as soon as you use them the act.text would need expanding to cover a rendering of those attributes. For example, if you added effectiveTime, I believe you would then need to include this in the act.text too, probably not what you wanted.

Straight away there are some problems with the above. It's not Clinical Statement compliant, since the Act class has mandatory act.code (as does Observation). We could have an act.code of "annotation", as mentioned, but being literal this still breaks the rule that act.text must summarise the whole act. Perhaps we can get away with that, or change the act.text rule to specifically allow not rendering the redundant "annotation" code's display name.

Otherwise we could have something like classCode="TEXT" (though I would hate to elevate text statements in such a way).