Release 4B 5

This page is part of the FHIR Specification (v4.3.0: R4B (v5.0.0: R5 - STU ). The This is the current published version which supercedes in it's permanent home (it will always be available at this version is 5.0.0 . URL). For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R5 R4B R4 R3

Communication-example-fm-solicited-attachment.xml

Example Communication/fm-solicited (XML)

Patient Care Work Group Maturity Level : N/A Standards Status : Informative Compartments : Device , Encounter , Patient , Practitioner , RelatedPerson

Raw XML ( canonical form + also see XML Format Specification )

Jump past Narrative

An example of a response to a request for additional information (id = "fm-solicited") 

<?xml version="1.0" encoding="UTF-8"?>


  
  
    
    
  
   
    
      
      
        
        
      
    
  

  
    
      
      
        
        
      
    
  

  
    
      
      
        
        
      
    
      
        
      
    
  

  
  
  
    
    
  
  
    
  
  
  
    
      
      
    
  
  
    
  
  
  
  
    
  
  
    
  
  
  
    
    
    
    
    
    
   
  
    
    
    
    
    
    
    
  

<Communication xmlns="http://hl7.org/fhir">
  <id value="fm-solicited"/> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">Attachment in response to a Request</div> 
  </text> 
   <contained> 
    <Organization> 
      <id value="provider"/> 
      <identifier> 
        <system value="http://www.jurisdiction.com/provideroffices"/> 
        <value value="3456"/> 
      </identifier> 
    </Organization> 
  </contained> 
  <contained> 
    <Organization> 
      <id value="payor"/> 
      <identifier> 
        <system value="http://www.jurisdiction.com/insurer"/> 
        <value value="123456"/> 
      </identifier> 
    </Organization> 
  </contained> 
  <contained> 
    <CommunicationRequest> 
      <id value="request"/> 
      <identifier> 
        <system value="http://www.jurisdiction.com/insurer/123456"/> 
        <value value="ABC123"/> 
      </identifier> 
    <status value="completed"/> 
    <intent value="proposal"/> 
      <subject> 
        <reference value="Patient/1"/> 
      </subject> 
    </CommunicationRequest> 
  </contained> 
    <!--   body of the resource   -->
  
  <identifier>     <system value="http://www.providerco.com/communication"/>     <value value="12345"/>   </identifier>   <basedOn>     <reference value="#request"/>   </basedOn>   <status value="completed"/>   <category>     <coding>       <system value="http://acme.org/messagetypes"/>       <code value="SolicitedAttachment"/>     </coding>   </category>   <subject>     <reference value="Patient/1"/>   </subject> 
  
  <sent value="2016-06-12T18:01:10-08:00"/>   <recipient>     <reference value="#payor"/>   </recipient>   <sender>     <reference value="#provider"/>   </sender> 
  
  <payload>     <contentAttachment>     <contentType value="application/pdf"/>     <data value="SGVsbG8="/>     <title value="accident notes 20100201.pdf"/>     <creation value="2010-02-01T11:50:23-05:00"/>     </contentAttachment>   </payload>    <payload>     <contentAttachment>     <contentType value="application/pdf"/>     <url value="http://happyvalley.com/docs/AB12345"/>     <size value="104274"/>     <hash value="SGVsbG8gdGhlcmU="/>     <creation value="2010-02-01T10:57:34+01:00"/>     </contentAttachment>   </payload> 


</

Communication

>

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.