FHIR Specification (v0.0.82: DSTU CI-Build
1). The current version which supercedes this version

This is 5.0.0 . For a full list the Continuous Integration Build of available versions, see FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions . Page versions: R3

Example ServiceRequest/example (XML)

Responsible Owner: Orders and Observations R2 Work Group Standards Status : Informative Compartments : Device , Encounter , Group , Patient , Practitioner , RelatedPerson Processrequest-example-poll-exclusive.json

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

Jump past Narrative

Check for responses for excluding types An example of resources a Head CT procedure (id = "example")

{ "resourceType": "ProcessRequest", "id": "1113", "text": { "status": "generated", "div": "<div>!-- Snipped for Brevity --></div>" }, "action": "poll", "identifier": [ { "system": "http://happyvalley.com/processrequest", "value": "113" } ], "created": "2014-08-16", "organization": { "reference": "Organization/1" }, "exclude": [ "SupportingDocumentation", "Reconciliation" ] } 
<?xml version="1.0" encoding="UTF-8"?>

<ServiceRequest xmlns="http://hl7.org/fhir">  <id value="example"/>   <text>     <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml">To be added</div>   </text>   <!--   insert contents here   -->  <status value="completed"/>   <intent value="order"/>   <category>     <coding>       <system value="http://snomed.info/sct"/>       <code value="103693007"/>       <display value="Diagnostic procedure (procedure)"/>     </coding>     <text value="Diagnostics Procedure"/>   </category>   <code>     <concept>       <coding>         <system value="http://snomed.info/sct"/>         <code value="303653007"/>         <display value="Computed tomography of head"/>       </coding>     </concept>   </code>   <subject>     <reference value="Patient/example"/>   </subject> 
</

ServiceRequest

>

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.