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
| Vocabulary Work Group | Maturity Level : N/A | Standards Status : Informative |
Raw XML ( canonical form + also see XML Format Specification )
Definition for Value SetService Request Category Codes
<?xml version="1.0" encoding="UTF-8"?> <ValueSet xmlns="http://hl7.org/fhir"> <id value="servicerequest-category"/> <meta><lastUpdated value="2021-12-19T08:15:41.873+11:00"/> <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml">This specification includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact http://www.snomed.org/snomed-ct/get-snomed-ct or info@snomed.org.<ul> <li> Include these codes as defined in <a href="http://www.snomed.org/"> <code> http://snomed.info/sct</code> </a> <table class="none"> <tr> <td style="white-space:nowrap"> <b> Code</b> </td> <td> <b> Display</b> </td> </tr> <tr> <td><a href="http://snomed.info/id/108252007">108252007</a> </td> <td> Laboratory procedure</td></tr> <tr> <td><a href="http://snomed.info/id/363679005">363679005</a> </td> <td> Imaging</td></tr> <tr> <td><a href="http://snomed.info/id/409063005">409063005</a> </td> <td> Counselling</td></tr> <tr> <td><a href="http://snomed.info/id/409073007">409073007</a> </td> <td> Education</td></tr> <tr> <td><a href="http://snomed.info/id/387713003">387713003</a> </td> <td> Surgical procedure</td></tr> </table> </li> </ul> </div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"> <valueCode value="oo"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status"> <valueCode value="draft"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm"> <valueInteger value="1"/> </extension> <url value="http://hl7.org/fhir/ValueSet/servicerequest-category"/> <identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:oid:2.16.840.1.113883.4.642.3.434"/> </identifier><version value="5.0.0-snapshot1"/> <name value="ServiceRequestCategoryCodes"/> <title value="Service Request Category Codes"/> <status value="draft"/><experimental value="true"/> <publisher value="Orders and Observations Workgroup"/> <contact> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/orders/index.cfm"/> </telecom> </contact> <description value="An example value set of SNOMED CT concepts that can classify a requested service"/>This specification includes content from SNOMED Clinical Terms® (SNOMED CT®) which is<copyright value="This specification includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact http://www.snomed.org/snomed-ct/get-snomed-ct or info@snomed.org."/> <compose> <include> <system value="http://snomed.info/sct"/> <concept> <code value="108252007"/> <display value="Laboratory procedure"/> </concept> <concept> <code value="363679005"/> <display value="Imaging"/> </concept> <concept> <code value="409063005"/> <display value="Counselling"/> </concept> <concept> <code value="409073007"/> <display value="Education"/> </concept> <concept> <code value="387713003"/> <display value="Surgical procedure"/> </concept> </include> </compose> </ ValueSet >
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.