Release 4 5 Snapshot #1

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

Procedure-example-appendectomy-narrative.ttl

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

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

Example of an appendectomy procedure that is primarily narrative 

@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 -------------------------------------------------------------------

<http://hl7.org/fhir/Procedure/appendectomy-narrative> a fhir:Procedure;
  fhir:nodeRole fhir:treeRoot;
  fhir:Resource.id [ fhir:value "appendectomy-narrative"];
  fhir:DomainResource.text [
     fhir:Narrative.status [ fhir:value "additional" ];
     fhir:Narrative.div "<div xmlns=\"http://www.w3.org/1999/xhtml\">Routine Appendectomy in April 2013 performed by Dr Cecil Surgeon</div>"
  ];
  fhir:Procedure.status [ fhir:value "completed"];
  fhir:Procedure.subject [
     fhir:link <http://hl7.org/fhir/Patient/example>;
     fhir:Reference.reference [ fhir:value "Patient/example" ]
  ] .

<http://hl7.org/fhir/Patient/example> a fhir:Patient .

# - ontology header ------------------------------------------------------------

<http://hl7.org/fhir/Procedure/appendectomy-narrative.ttl> a owl:Ontology;
  owl:imports fhir:fhir.ttl;
  owl:versionIRI <http://build.fhir.org/Procedure/appendectomy-narrative.ttl> .

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

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.