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)
VMA, Random Urine Sample (id = "vma-urine")
<?xml version="1.0" encoding="UTF-8"?> <Specimen xmlns="http://hl7.org/fhir"> <id value="vma-urine"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"><p> <b> Generated Narrative with Details</b> </p> <p> <b> id</b> : vma-urine</p> <p> <b> accessionIdentifier</b> : X352356</p> <p> <b> status</b> : available</p> <p> <b> type</b> : Urine, Random <span> (Details : {http://terminology.hl7.org/CodeSystem/v2-0487 code 'RANDU' = 'Urine, Random', given as 'Urine, Random'})</span> </p> <p> <b> subject</b> : <a> Patient/example</a> </p> <p> <b> receivedTime</b> : 18/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> </tr> <tr> <td> *</td> <td> <a> Practitioner/f202</a> </td> <td> 18/08/2015 5:03:00 PM</td> </tr> </table> <h3> Processings</h3> <table> <tr> <td> -</td> <td> <b> Description</b> </td> <td> <b> Procedure</b> </td> <td> <b> Additive</b> </td> <td> <b> Time[x]</b> </td> </tr> <tr> <td> *</td> <td> Acidify to pH < 3.0 with 6 N HCl.</td> <td> Acidification <span> (Details : {http://terminology.hl7.org/CodeSystem/v2-0373 code 'ACID' = 'Acidification)</span> </td> <td> 6 N HCl</td> <td> 18/08/2015 6:10:00 PM</td> </tr> </table> <h3> Containers</h3> <table> <tr> <td> -</td> <td> <b> Type</b> </td> <td> <b> Capacity</b> </td> <td> <b> SpecimenQuantity</b> </td> </tr> <tr> <td> *</td> <td> Non-sterile specimen container <span> (Details )</span> </td> <td> 50 mls</td> <td> 10 mls</td> </tr> </table> </div> </text> <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="available"/> <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://terminology.hl7.org/CodeSystem/v2-0487"/> <code value="RANDU"/> <display value="Urine, Random"/> </coding> </type> <subject> <reference value="Patient/example"/> </subject> <receivedTime value="2015-08-18T07:03:00Z"/> <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-18T07:03:00Z"/> <!-- method is usually implied by type --> </collection> <processing> <description value="Acidify to pH < 3.0 with 6 N HCl."/> <procedure> <coding> <system value="http://terminology.hl7.org/CodeSystem/v2-0373"/> <code value="ACID"/> </coding> </procedure> <additive> <display value="6 N HCl"/> </additive> <timeDateTime value="2015-08-18T08:10:00Z"/> </processing> <container> <type> <text value="Non-sterile specimen container"/> </type> <capacity> <value value="50"/> <unit value="mls"/> </capacity> <specimenQuantity> <value value="10"/> <unit value="mls"/> </specimenQuantity> </container> </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.