Diagnostics
This
page
is
part
of
the
Snapshot
#3
for
FHIR
Specification
(v4.3.0:
R4B
-
STU
).
The
current
version
which
supercedes
this
version
is
5.0.0
R5
,
released
to
support
Connectathon
32
.
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 )
General Specimen Example (id = "101")
<?xml version="1.0" encoding="UTF-8"?> <Specimen xmlns="http://hl7.org/fhir"> <id value="101"/><!-- text><!-- text> <status value="generated" /> <div xmlns="http://www.w3.org/1999/xhtml">[Put rendering here]</div> </text> -->display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60% <!-- a specimen identifier - e.g. assigned when the specimen was taken this is often not done --><text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"><p> <b> Generated Narrative: Specimen</b> <a name="101"> </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 Specimen "101" </p> </div> <p> <b> identifier</b> : <span title=" text> <status value="generated" /> <div xmlns="http://www.w3.org/1999/xhtml">[Put rendering here]</div> ; </text> ">id: 23234352356</span> </p> <p> <b> accessionIdentifier</b> : id: X352356</p> <p> <b> status</b> : available</p> <p> <b> type</b> : Venous blood specimen <span style="background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki"> (<a href="https://browser.ihtsdotools.org/">SNOMED CT</a> #122555007)</span> </p> <p> <b> subject</b> : <a href="patient-example.html">Patient/example: Peter Patient</a> "Peter CHALMERS"</p> <p> <b> receivedTime</b> : 2011-03-04T07:03:00Z</p> <p> <b> request</b> : <a href="servicerequest-example.html">ServiceRequest/example</a> </p> <blockquote> <p> <b> collection</b> </p> <p> <b> collector</b> : <a href="practitioner-example.html">Practitioner/example</a> "Adam CAREFUL"</p> <p> <b> collected</b> : <span title=" 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) ">2011-05-30T06:15:00Z</span> </p> <p> <b> quantity</b> : 6 mL</p> <p> <b> method</b> : <span title=" method is usually implied by type ">Line, Venous <span style="background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki"> (<a href="http://terminology.hl7.org/4.0.0/CodeSystem-v2-0488.html">specimenCollectionMethod</a> #LNV)</span> </span> </p> <h3> BodySites</h3> <table class="grid"><tr> <td> -</td> <td> <b> Concept</b> </td> </tr> <tr> <td> *</td> <td> Structure of median cubital vein (body structure) <span style="background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki"> (<a href="https://browser.ihtsdotools.org/">SNOMED CT</a> #49852007)</span> </td> </tr> </table> </blockquote> <h3> Containers</h3> <table class="grid"><tr> <td> -</td> <td> <b> Device</b> </td> <td> <b> SpecimenQuantity</b> </td> </tr> <tr> <td> *</td> <td> <a href="broken-link.html">Specimen/specimen-device-container-example-green-gel-vacutainer</a> </td> <td> <span title=" if there's only one container, then this value is the same as .collection.quantity (usually). This is for when there is more than one container ">3 mL</span> </td> </tr> </table> <p> <b> note</b> : Specimen is grossly lipemic</p> </div> </text> <identifier> <!-- a specimen identifier - e.g. assigned when the specimen was taken this is often not done --> <system value="http://ehr.acme.org/identifiers/collections"/> <value value="23234352356"/> </identifier> <accessionIdentifier> <system value="http://lab.acme.org/specimens/2011"/> <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.<!-- 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 fieldsIf the type includes other fields, it would be normal not to populate the other fieldsNote that this practice is so widespread that it's pointless to try and stop it -->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="122555007"/> <display value="Venous blood specimen"/> </coding> </type> <subject> <reference value="Patient/example"/> <display value="Peter Patient"/> </subject> <receivedTime value="2011-03-04T07:03:00Z"/> <request><!-- this points to the order that caused the sample to be drawn --> <reference value="ServiceRequest/example"/> </request> <collection> <collector><!-- in practice, collecter is almost always recorded --> <reference value="Practitioner/example"/> </collector><!-- the time of collection is usually required. Usually a point in time, but can be a period<!-- 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-05-30T06:15:00Z"/> <quantity> <value value="6"/> <unit value="mL"/><!-- e.g. full --> </quantity><!-- method is usually implied by type --> <method> <coding> <system value="http://terminology.hl7.org/CodeSystem/v2-0488"/> <code value="LNV"/> </coding> </method><!-- bodysite is usually implied by type too its here to demonstrate its usage to indicating the draw site in this case --><!-- bodysite is usually implied by type too its here to demonstrate its usage to indicating the draw site in this case --> <bodySite><concept> <coding> <system value="http://snomed.info/sct"/> <code value="49852007"/> <display value="Structure of median cubital vein (body structure)"/> </coding> </concept> </bodySite> </collection><!--<!-- the container identifier is not the same as the specimen identifier usually, it is pre-printed/implanted etc.on the container prior to use. It might a RFID in the container, or it might be a UDI(http://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/UniqueDeviceIdentification/)(http://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/UniqueDeviceIdentificati on/) --> <container><!-- if there's only one container, then this value is the same<device> <reference value="Specimen/specimen-device-container-example-green-gel-vacutainer"/> </device> <!-- if there's only one container, then this value is the same as .collection.quantity (usually). This is for when there is more than one container --> <specimenQuantity><value value="3"/> <unit value="mL"/> </specimenQuantity></container> <note> <text value="Specimen is grossly lipemic"/> </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.
FHIR
®©
HL7.org
2011+.
FHIR
Release
4B
(v4.3.0)
hl7.fhir.r4b.core#4.3.0
R5
Ballot
hl7.fhir.core#5.0.0-snapshot3
generated
on
Sat,
May
28,
Wed,
Dec
14,
2022
12:57+1000.
07:17+1100.
Links:
Search
|
Version
History
|
Table
of
Contents
|
Glossary
|
QA
Page
|
Compare
to
R4
R4B
|
Compare
to
R5
Draft
|
|
Propose
a
change