This page is part of the FHIR Specification (v4.4.0: R5 Preview #2). 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 R2
Orders and Observations Work Group | Maturity Level: N/A | Standards Status: Informative | Compartments: Device, Patient, Practitioner |
Raw XML (canonical form + also see XML Format Specification)
Bacterial Isolate from Stool sample (id = "isolate")
<?xml version="1.0" encoding="UTF-8"?> <Specimen xmlns="http://hl7.org/fhir"> <id value="isolate"/> <!-- text> <status value="generated" /> <div xmlns="http://www.w3.org/1999/xhtml">[Put rendering here]</div> </text> --> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"><p> <b> Generated Narrative with Details</b> </p> <p> <b> id</b> : isolate</p> <p> <b> contained</b> : </p> <p> <b> accessionIdentifier</b> : X352356-ISO1</p> <p> <b> status</b> : available</p> <p> <b> type</b> : Bacterial isolate specimen <span> (Details : {SNOMED CT code '429951000124103' = 'Bacterial isolate specimen (specimen)', given as 'Bacterial isolate specimen'})</span> </p> <p> <b> subject</b> : <a> Patient/example</a> </p> <p> <b> receivedTime</b> : 18/08/2015 5:03:00 PM</p> <p> <b> parent</b> : id: stool; X352356; status: unavailable; Stool specimen <span> (Details : {SNOMED CT code '119339001' = 'Stool specimen', given as 'Stool specimen'})</span> ; receivedTime: 16/08/2015 5:03:00 PM</p> <h3> Collections</h3> <table> <tr> <td> -</td> <td> <b> Collector</b> </td> <td> <b> Collected[x]</b> </td> <td> <b> Method</b> </td> </tr> <tr> <td> *</td> <td> <a> Practitioner/f202</a> </td> <td> 16/08/2015 5:03:00 PM</td> <td> Plates, Blood Agar <span> (Details : {http://terminology.hl7.org/CodeSystem/v2-0488 code 'BAP' = 'Plates, Blood Agar)</span> </td> </tr> </table> <p> <b> note</b> : Patient dropped off specimen</p> </div> </text> <contained> <Specimen> <id value="stool"/> <accessionIdentifier> <!-- accession identifier - e.g. assigned by the labaratory when it is received. This is common, unlike specimen identifier --> <system value="http://lab.acme.org/specimens/2015"/> <value value="X352356"/> </accessionIdentifier> <status value="unavailable"/> <type> <!-- Type is a loosely defined field because there is such a lot of variation in how it is used. The principal variation is how much information that could be represented elsewhere is also represented here. For instance, here's some possible types: lithium heparin plasma (+ .container.additive) (e.g. SNOMED CT 446272009) transfusion bag of blood (+ container.type) Peritoneal lavage (+ collection.bodySite) If the type includes other fields, it would be normal not to populate the other fields Note that this practice is so widespread that it's pointless to try and stop it --> <coding> <system value="http://snomed.info/sct"/> <code value="119339001"/> <display value="Stool specimen"/> </coding> </type> <subject> <reference value="Patient/example"/> </subject> <receivedTime value="2015-08-16T07:03:00Z"/> <collection> <collector> <!-- in practice, collecter is almost always recorded --> <display value="Patient"/> </collector> <!-- the time of collection is usually required. Usually a point in time, but can be a period (collectedPeriod) if it's a timed collection (e.g. a 24 hour urine) --> <collectedDateTime value="2011-08-16T06:15:00Z"/> <!-- method is usually implied by type --> <method> <coding> <system value="http://terminology.hl7.org/CodeSystem/v2-0488"/> <code value="LNV"/> </coding> </method> </collection> </Specimen> </contained> <accessionIdentifier> <system value="http://lab.acme.org/specimens/2011"/> <value value="X352356-ISO1"/> </accessionIdentifier> <status value="available"/> <type> <coding> <system value="http://snomed.info/sct"/> <code value="429951000124103"/> <display value="Bacterial isolate specimen"/> </coding> </type> <subject> <reference value="Patient/example"/> </subject> <receivedTime value="2015-08-18T07:03:00Z"/> <parent> <reference value="#stool"/> </parent> <collection> <collector> <!-- in practice, collecter is almost always recorded --> <reference value="Practitioner/f202"/> </collector> <!-- the time of collection is usually required. Usually a point in time, but can be a period (collectedPeriod) if it's a timed collection (e.g. a 24 hour urine) --> <collectedDateTime value="2015-08-16T07:03:00Z"/> <!-- method is usually implied by type --> <method> <coding> <system value="http://terminology.hl7.org/CodeSystem/v2-0488"/> <code value="BAP"/> </coding> </method> </collection> <note> <text value="Patient dropped off specimen"/> </note> </Specimen>
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.