This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Relationship between a section and its entries"

From HL7Wiki
Jump to navigation Jump to search
(initial content)
 
Line 8: Line 8:
 
==Entry to narrative==
 
==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.  
 
*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?
The entry relationship is defaulted to "COMP" (component), for the general case where the only assertion is that the related entries are contained within the source section and no other semantics are implied.
+
*coded datatype.orignalText is ..., which suggests that the <content> being linked has to ..
 
 
The entry relationship "DRIV" (is derived from) can be used in the special case where the narrative is fully derived from CDA Entries. When a report consisting entirely of structured entries is transformed into CDA, the encoding application must ensure that the authenticated content (narrative plus multimedia) is a faithful and complete rendering of the clinical content of the structured source data. This ensures that the narrative plus multimedia represents, as in all CDA documents, the complete authenticated content of the Section. In this case, narrative plus multimedia does not contain any clinical content that is not present in the Entries.
 

Revision as of 01:48, 9 January 2007

Relationship between an entry and its narrative text. (not about relationships bewteen entries, or between entries and "objects external to the document"). See 4.3.4.2 and 4.3.5.12.

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 ..., which suggests that the <content> being linked has to ..