Release 5

This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Example Practitioner/xcda1 (Turtle)

Patient Administration Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Practitioner

Raw Turtle (+ also see Turtle/RDF Format Specification)

2nd CDA Example Author

@prefix fhir: <http://hl7.org/fhir/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

# - resource -------------------------------------------------------------------

[a fhir:Practitioner ;
  fhir:nodeRole fhir:treeRoot ;
  fhir:id [ fhir:v "xcda1"] ; # 
  fhir:text [
     fhir:status [ fhir:v "generated" ] ;
     fhir:div "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p><b>Generated Narrative: Practitioner</b><a name=\"xcda1\"> </a></p><div style=\"display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%\"><p style=\"margin-bottom: 0px\">Resource Practitioner &quot;xcda1&quot; </p></div><p><b>identifier</b>: id: D234123 (use: OFFICIAL)</p><p><b>name</b>: Sherry Dopplemeyer </p><p><b>telecom</b>: <a href=\"mailto:john.doe@healthcare.example.org\">john.doe@healthcare.example.org</a></p></div>"
  ] ; # 
  fhir:identifier ( [
     fhir:use [ fhir:v "official" ] ;
     fhir:system [ fhir:v "http://healthcare.example.org/identifiers/staff"^^xsd:anyURI ] ;
     fhir:value [ fhir:v "D234123" ]
  ] ) ; # 
  fhir:name ( [
     fhir:family [ fhir:v "Dopplemeyer" ] ;
     fhir:given ( [ fhir:v "Sherry" ] )
  ] ) ; # 
  fhir:telecom ( [
     fhir:system [ fhir:v "email" ] ;
     fhir:value [ fhir:v "john.doe@healthcare.example.org" ]
  ] )] . # 

# -------------------------------------------------------------------------------------

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.