Difference between revisions of "FHIR document Page"
Line 15: | Line 15: | ||
== Mapping between CDA Narrative and FHIR text == | == Mapping between CDA Narrative and FHIR text == | ||
+ | When transforming between CDA and FHIR documents, a particular issue is the CDA Narrative to/from FHIR Text, as the formed is a set of elements that is specific to CDA (and only loosely modelled in HTML), while FHIR is a subset of XHTML. The following tables give a suggested mapping between the two - accepting that it will not be possible to achieve a perfect mapping with regard to format, but at least the textual parts should be able to be mapped. | ||
− | === CDA Narrative to FHIR Text | + | === CDA Narrative to FHIR Text === |
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
Line 24: | Line 25: | ||
|- | |- | ||
| content | | content | ||
− | | | + | | div |
| | | | ||
|- | |- | ||
Line 32: | Line 33: | ||
|- | |- | ||
| sub | | sub | ||
− | | | + | | div/@class=sub |
| | | | ||
|- | |- | ||
| sup | | sup | ||
− | | | + | | div/@class=sup |
| | | | ||
|- | |- | ||
| br | | br | ||
− | | | + | | br |
| | | | ||
|- | |- | ||
| footnote | | footnote | ||
− | | | + | | div/@class=footnote |
| | | | ||
|- | |- | ||
Line 56: | Line 57: | ||
|- | |- | ||
| paragraph | | paragraph | ||
− | | | + | | p |
| | | | ||
|- | |- | ||
| list | | list | ||
+ | | ul | ||
| | | | ||
+ | |- | ||
+ | | list.caption | ||
+ | | ul/@class=caption | ||
| | | | ||
|- | |- | ||
| table | | table | ||
− | | | + | | table |
| | | | ||
|- | |- | ||
| @ID | | @ID | ||
− | | | + | | @id |
| | | | ||
|- | |- | ||
Line 76: | Line 81: | ||
|- | |- | ||
| @stylecode | | @stylecode | ||
− | | | + | | @class<value> |
| | | | ||
|- | |- |
Revision as of 22:37, 16 June 2013
Welcome to "Document" discussion page. Please put any comments about this page here. Contents will be reviewed periodically.
Contents
Discussion
- MessageHeader.instant - why not call this "created" or "creationTime", "instant" does not carry meaning of what the instant is capturing.
Section vs. Resource disconnect and requirements for Organizer
CCDA has a number of sections that are essentially rooted in Organizer. The section represents a Collection of things, and thus the text rendering also reflects a collection rather than having separate text for each element in the collection. This rendering might be as a list with items or even as a table. With FHIR, we render resources individually and have not (yet) introduced the idea of Organizers. Introducing Organizers creates a number of issues in terms of ensuring consistency across paradigms.
One possible solution is to allow text to appear any place we allow a collection of resource references. This could either be handled by the tooling or by always referencing a particular construct whenever we reference a collection of resources.
Mapping between CDA Narrative and FHIR text
When transforming between CDA and FHIR documents, a particular issue is the CDA Narrative to/from FHIR Text, as the formed is a set of elements that is specific to CDA (and only loosely modelled in HTML), while FHIR is a subset of XHTML. The following tables give a suggested mapping between the two - accepting that it will not be possible to achieve a perfect mapping with regard to format, but at least the textual parts should be able to be mapped.
CDA Narrative to FHIR Text
CDA Narrative Element | FHIR Text equivalent | Comment |
---|---|---|
content | div | |
linkHtml | ||
sub | div/@class=sub | |
sup | div/@class=sup | |
br | br | |
footnote | div/@class=footnote | |
footnoteRef | ||
renderMultiMedia | ||
paragraph | p | |
list | ul | |
list.caption | ul/@class=caption | |
table | table | |
@ID | @id | |
@language | ||
@stylecode | @class<value> | |
@mediaType |
header 1 | header 2 | header 3 |
---|---|---|
row 1, cell 1 | row 1, cell 2 | row 1, cell 3 |
row 2, cell 1 | row 2, cell 2 | row 2, cell 3 |