Release 4 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ) in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see times).
See the Directory of published versions . Page versions: R5 R4B R4 R3 R2

Relatedperson-example-f001-sarah.xml

Example RelatedPerson/f001 (XML)

Maturity Level : N/A
Responsible Owner: Patient Administration Work Group Standards Status : Informative Compartments : Patient , RelatedPerson

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

Jump past Narrative

Sarah Abels (id = "f001") 

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


 
  

    
    
     Sarah Abels
    
  

  
    
    
    
    
  
  
  
    
  
  
  
    
      
      
        
  
  
  
    
    
    
  
  
    
    
    
  
  
    
    
    
  
  
  

<RelatedPerson xmlns="http://hl7.org/fhir">
  <id value="f001"/> 
  <text> 
    <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml">
     Sarah Abels
    </div>   </text>   <!--   Dutch BSN identification system   -->  <identifier>     <use value="official"/>     <type>       <text value="BSN"/>     </type>     <system value="urn:oid:2.16.840.1.113883.2.4.6.3"/>   </identifier>   <patient>     <reference value="Patient/f001"/>   </patient>   <relationship>     <coding>       <system value="http://terminology.hl7.org/CodeSystem/v3-RoleCode"/>       <code value="SIGOTHR"/>     </coding>   </relationship>   <name>     <use value="usual"/>     <family value="Abels"/>     <given value="Sarah"/>   </name>   <telecom>     <system value="phone"/>     <value value="0690383372"/>     <use value="mobile"/>   </telecom>   <telecom>     <system value="email"/>     <value value="s.abels@kpn.nl"/>     <use value="home"/>   </telecom>   <gender value="female"/> 


</

RelatedPerson

>

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.