Difference between revisions of "XDS-FHIR-mapping"
Jump to navigation
Jump to search
(Created page with "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 th...") |
|||
| Line 17: | Line 17: | ||
|<pre> | |<pre> | ||
<DocumentReference> | <DocumentReference> | ||
| − | < | + | <masterIdentifier> |
| − | + | <value value="118ff02f-1001-4548-925f-cf68cc8780d7"/> | |
| − | <value value=" | + | </masterIdentifier> |
| − | </ | + | <mimeType value="text/plain"/> |
| − | <mimeType | ||
</DocumentReference> | </DocumentReference> | ||
</pre> | </pre> | ||
|} | |} | ||
| − | This includes the entryUUID and mimeType attributes. The handling of symbolic/local vs permanent/global ids is reversed in FHIR. In ebRIM a permanent/global ID is a UUID and a symbolic/local id is always a non-UUID (does not have the urn:uuid: prefix). In FHIR, local/symbolic IDs are coded as UUIDs and permanent/global IDs are non-UUIDs. | + | This includes the entryUUID and mimeType attributes. The handling of symbolic/local vs permanent/global ids is reversed in FHIR. In ebRIM a permanent/global ID is a UUID and a symbolic/local id is always a non-UUID (does not have the urn:uuid: prefix). In FHIR, local/symbolic IDs are coded as UUIDs and permanent/global IDs are non-UUIDs. FHIR and ebRIM agree that local IDs have transaction scope. |
Revision as of 13:46, 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
id="Document01"
mimeType="text/plain"
objectType="urn:uuid:7edca82f-054d-47f2-a032-9b2a5b5186c1"/>
|
<DocumentReference>
<masterIdentifier>
<value value="118ff02f-1001-4548-925f-cf68cc8780d7"/>
</masterIdentifier>
<mimeType value="text/plain"/>
</DocumentReference>
|
This includes the entryUUID and mimeType attributes. The handling of symbolic/local vs permanent/global ids is reversed in FHIR. In ebRIM a permanent/global ID is a UUID and a symbolic/local id is always a non-UUID (does not have the urn:uuid: prefix). In FHIR, local/symbolic IDs are coded as UUIDs and permanent/global IDs are non-UUIDs. FHIR and ebRIM agree that local IDs have transaction scope.