XDS-FHIR-mapping

From IHE Wiki
Revision as of 13:31, 24 March 2014 by BillM (talk | contribs) (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...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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>
   <identifier>
     <system value="urn:ietf:rfc:3986"/>
     <value value="Document01"/>
   </identifier>
   <mimeType mimeType="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.