Relationship between a section and its entries
This page identifies some open issues related to the relationship between an entry and its narrative text. (this is not about relationships bewteen entries, nor between entries and "objects external to the document"). See 18.104.22.168 and 22.214.171.124 in the CDA R2 specification for details. The resolution of these issues should be part of CDA R3.
The fact that specific pieces of narrative text can be tagged/highlighted and linked to entries suggests a possibility to render the narrative text ("Asthma") in some special highlighted manner, where e.g. the code (e.g. ICD-10) from the related entry is shown when the mouse hovers over the text, or where the details entry will be displayed if the tagget snippet of original text is selected. The use of <content> tags is entirely optional however - which raises the question when and how it should be used.
Narrative to entry
- content: The CDA <content> element is used to wrap a string of text so that it can be explicitly referenced, or so that it can suggest rendering characteristics. The <content> element can nest recursively, which enables wrapping a string of plain text down to as small a chunk as desired.
- renderMultiMedia: What, if anything, do the renderMultimedia XML tags in a narrative block encapsulate?
- linkHTML: What, if anything, do the linkHTML XML tags in a narrative block encapuslate?
Entry to narrative
- The originalText component of a RIM attribute present in any CDA entry can make explicit reference to the identifier (contained in a content element in the narrative block), thereby indicating the original text associated with the attribute in the CDA entry.
- In the case of DRIV, is there an expectation (should it be required) that content tags be used in the generated narrative at the same level of granularity as the data contained in the Entries?
- coded_datatype.orignalText is "The text or phrase used as the basis for the coding", "The original text exists in a scenario where an originator of the information does not assign a code, but where the code is assigned later by a coder (post-coding.) NOTE: The original text property is not meant to be a link into the entire source document. The link between different artifacts of medical information (e.g., document and coded result) is outside the scope of this specification and is maintained elsewhere in the HL7 standards. The original text is an excerpt of the relevant information in the original sources, rather than a pointer or exact reproduction. Thus the original text is to be represented in plain text form"
- which suggests a partcular relationship bewteen the text encapsulated between content tags,
- in the case of DRIV, originalText doesn't seem applicable. If we want to link from en entry to the fragment of text that was generated based on that entry, we'd either need a new mechanism or the definition of originalText will need to be changed.
- If one switches language or locale, in a document with DRIV text sections, and <content> links bewteen the entry and the text, is it OK to replace the text with a translated/transformed version? (example: ...<content>200 [miles/gallon]</content>.. with an entry Act which has a value of "200 miles/gallon": if the physician has sleceted a metric locale, can the TEXT be changed to "90 km/l"?)
- How does one enforce or express any relationship requirements one may have in a template or in a constraint language? (example: in medication sections, where text has been DRIV from an entry, each and every entry SHALL have a corresponding <content> enclosed part in the narrative)
- (related, though different) How does one enforce or express requirements related to the structure of narrative text? (e.g. Lab results SHALL be sent in the form of a table with 5 columns)