0.1.0 - ci-build
PatientScheduling - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Draft as of 2025-12-23 |
<ValueSet xmlns="http://hl7.org/fhir">
<id value="common-service-types-vs"/>
<text>
<status value="extensions"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ValueSet common-service-types-vs</b></p><a name="common-service-types-vs"> </a><a name="hccommon-service-types-vs"> </a><p>This value set includes codes based on the following rules:</p><ul><li>Include these codes as defined in <a href="http://terminology.hl7.org/7.0.1/CodeSystem-service-type.html"><code>http://terminology.hl7.org/CodeSystem/service-type</code></a><span title="Version is not explicitly stated, which means it is fixed to 1.1.1, the version found through the package references"> version 📦1.1.1</span><table class="none"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href="http://terminology.hl7.org/7.0.1/CodeSystem-service-type.html#service-type-88">88</a></td><td>General Dental</td><td>General dental</td></tr><tr><td><a href="http://terminology.hl7.org/7.0.1/CodeSystem-service-type.html#service-type-124">124</a></td><td>General Practice</td><td>General Practice/GP (doctor)</td></tr><tr><td><a href="http://terminology.hl7.org/7.0.1/CodeSystem-service-type.html#service-type-554">554</a></td><td>Chronic Disease Management</td><td>Chronic Disease Management</td></tr><tr><td><a href="http://terminology.hl7.org/7.0.1/CodeSystem-service-type.html#service-type-209">209</a></td><td>Diagnostic Radiology/Xray/CT/Fluoroscopy</td><td>Diagnostic Radiology/Xray/CT/Fluoroscopy</td></tr><tr><td><a href="http://terminology.hl7.org/7.0.1/CodeSystem-service-type.html#service-type-210">210</a></td><td>Diagnostic Ultrasound</td><td>Diagnostic Ultrasound</td></tr><tr><td><a href="http://terminology.hl7.org/7.0.1/CodeSystem-service-type.html#service-type-211">211</a></td><td>Magnetic Resonance Imaging (MRI)</td><td>Magnetic Resonance Imaging (MRI)</td></tr><tr><td><a href="http://terminology.hl7.org/7.0.1/CodeSystem-service-type.html#service-type-212">212</a></td><td>Nuclear Medicine</td><td>Nuclear Medicine</td></tr><tr><td><a href="http://terminology.hl7.org/7.0.1/CodeSystem-service-type.html#service-type-213">213</a></td><td>Obstetric & Gynaecological Ultrasound</td><td>Obstetric & Gynaecological Ultrasound</td></tr><tr><td><a href="http://terminology.hl7.org/7.0.1/CodeSystem-service-type.html#service-type-57">57</a></td><td>Immunization</td><td>Immunization</td></tr></table></li><li>Include these codes as defined in <a href="http://www.snomed.org/"><code>http://snomed.info/sct</code></a><span title="Version is not explicitly stated. No matching Code System found"> version Not Stated (use latest from terminology server)</span><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/396540005">396540005</a></td><td>Phlebotomy</td></tr></table></li></ul></div>
</text>
<url value="http://example.org/ValueSet/common-service-types-vs"/>
<version value="0.1.0"/>
<name value="CommonServiceTypesVS"/>
<title value="Common Service Types for Scheduling"/>
<status value="draft"/>
<experimental value="true"/>
<date value="2025-12-23T23:36:59+00:00"/>
<publisher value="haau3"/>
<contact>
<name value="haau3"/>
<telecom>
<system value="url"/>
<value value="https://haau3.com"/>
</telecom>
</contact>
<description
value="A subset of the HL7 service-type codes and possibly other code systems
to illustrate the more common service types that patients may
want to schedule appointments for. Ideally, this would be based on utilization
data and usually 1:1 with serviceType:schedule if the procedures can be performed
independently of each other (e.g. 2 x-ray machines, 2 CT machines, 3 MRI machines and the
schedule represents a pool of image technicians that can perform any of these procedures,
but are limited by the actual, physical machines). These also may likely be more limited by
both the technician/practitioner and the physical machine.
Conversely, if a provider (e.g. family medicine physician) can perform multiple
types of services (e.g. annual wellness visit, follow-up visit, chronic disease management, etc)
then it's appropriate to use serviceType to represent multiple services. "/>
<compose>
<include>
<system value="http://terminology.hl7.org/CodeSystem/service-type"/>
<concept>
<code value="88"/>
<display value="General Dental"/>
</concept>
<concept>
<code value="124"/>
<display value="General Practice"/>
</concept>
<concept>
<code value="554"/>
<display value="Chronic Disease Management"/>
</concept>
<concept>
<code value="209"/>
<display value="Diagnostic Radiology/Xray/CT/Fluoroscopy"/>
</concept>
<concept>
<code value="210"/>
<display value="Diagnostic Ultrasound"/>
</concept>
<concept>
<code value="211"/>
<display value="Magnetic Resonance Imaging (MRI)"/>
</concept>
<concept>
<code value="212"/>
<display value="Nuclear Medicine"/>
</concept>
<concept>
<code value="213"/>
<display value="Obstetric & Gynaecological Ultrasound"/>
</concept>
<concept>
<code value="57"/>
<display value="Immunization"/>
</concept>
</include>
<include>
<system value="http://snomed.info/sct"/>
<concept>
<code value="396540005"/>
<display value="Phlebotomy"/>
</concept>
</include>
</compose>
</ValueSet>