Difference between revisions of "XDS-FHIR-mapping"
Jump to navigation
Jump to search
Line 10: | Line 10: | ||
|<pre> | |<pre> | ||
<ExtrinsicObject | <ExtrinsicObject | ||
− | |||
mimeType="text/plain" | mimeType="text/plain" | ||
− | |||
</pre> | </pre> | ||
|<pre> | |<pre> | ||
<DocumentReference> | <DocumentReference> | ||
− | < | + | <text> |
− | + | <status value="generated"/> | |
− | </ | + | <div xmlns="http://www.w3.org/1999/xhtml"> |
+ | </div> | ||
+ | </text> | ||
<mimeType value="text/plain"/> | <mimeType value="text/plain"/> | ||
</DocumentReference> | </DocumentReference> | ||
Line 25: | Line 25: | ||
|} | |} | ||
− | This | + | The text element represents an HTML rendition of the DocumentReference. This example shows that the HTML has been generated. |
+ | |||
+ | DocumentReference shall have on masterIdentifier (1..1) and my have many additional identifiers. It is not clear that we use any other identifiers (check uniqueID). | ||
+ | |||
+ | In the FHIR DocumentReference example, the masterIdentifier is coded as a urn:oid:. |
Revision as of 14:13, 24 March 2014
These notes contain the current thinking on how to map Document Sharing attributes to FHIR. This page will be updated as we learn more.
In the tables below, the left side is the current ebRIM content and the right side is the proposed FHIR content.
DocumentEntry
DocumentEntry Wrapper
<ExtrinsicObject mimeType="text/plain" |
<DocumentReference> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> </div> </text> <mimeType value="text/plain"/> </DocumentReference> |
The text element represents an HTML rendition of the DocumentReference. This example shows that the HTML has been generated.
DocumentReference shall have on masterIdentifier (1..1) and my have many additional identifiers. It is not clear that we use any other identifiers (check uniqueID).
In the FHIR DocumentReference example, the masterIdentifier is coded as a urn:oid:.