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

Difference between revisions of "Talk:CDA R3 NonXMLBody-Text Cardinality"

From HL7Wiki
Jump to navigation Jump to search
(New page: charliemccay: I am not sure that having multiple .text attributes makes sense - but I do support having multiple renderings of the document - this could be achieved by having 1..* for body...)
 
 
Line 1: Line 1:
 
charliemccay: I am not sure that having multiple .text attributes makes sense - but I do support having multiple renderings of the document - this could be achieved by having 1..* for bodyChoice -- the bodies would all be renderings of the same document (eg Word and PDF)
 
charliemccay: I am not sure that having multiple .text attributes makes sense - but I do support having multiple renderings of the document - this could be achieved by having 1..* for bodyChoice -- the bodies would all be renderings of the same document (eg Word and PDF)
In a similar way I would like to see the rendering separated from the entries in the RHS, and maybe alternate renderings could be conveyed as NonXMLBody.
+
In a similar way I would like to see the rendering separated from the entries in the RHS (and more than one rendering being possible), and maybe alternate renderings could be conveyed as NonXMLBody.  By rendering I mean the narrative content - not (just) then the CDA markup has been transformed to HTML or PDF for display.

Latest revision as of 12:53, 31 December 2009

charliemccay: I am not sure that having multiple .text attributes makes sense - but I do support having multiple renderings of the document - this could be achieved by having 1..* for bodyChoice -- the bodies would all be renderings of the same document (eg Word and PDF) In a similar way I would like to see the rendering separated from the entries in the RHS (and more than one rendering being possible), and maybe alternate renderings could be conveyed as NonXMLBody. By rendering I mean the narrative content - not (just) then the CDA markup has been transformed to HTML or PDF for display.