XDS-FHIR-mapping

From IHE Wiki
Revision as of 14:19, 24 March 2014 by BillM (talk | contribs) (→‎mimeType)
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 
<DocumentReference>
   <text>
      <status value="generated"/>
      <div  xmlns="http://www.w3.org/1999/xhtml">
      </div>
   </text>
 </DocumentReference>

The text element represents an HTML rendition of the DocumentReference. This example shows that the HTML has been generated.

mimeType

    mimeType="text/plain"
   <mimeType value="text/plain"/>

uniqueId

<ExternalIdentifier
  identificationScheme="urn:uuid:2e82c1f6-a085-4c72-9da3-8640a32e42ab"
  value="1.3.6.1.4.1.21367.2005.3.7"
  objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:ExternalIdentifier"
  id="id_10" registryObject="Document01">
  <Name>
    <LocalizedString value="XDSDocumentEntry.uniqueId"/>
  </Name>
</ExternalIdentifier>
  <masterIdentifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:1.3.6.1.4.1.21367.2005.3.7"/>
  </masterIdentifier>

The uniqueId is represented by the masterIdentifier. The big different is that in XDS the value is an OID and in FHIR it is a fully qualified OID.