Release 5 Ballot

This page is part of the FHIR Specification (v0.0.82: DSTU (v5.0.0-ballot: R5 Ballot - see ballot notes 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 R3

Obs-uslab-example4.xml

4.4.1.233 ValueSet http://hl7.org/fhir/ValueSet/http-operations

Raw
FHIR Infrastructure icon Work Group   Maturity Level : 2 Trial Use Use Context : Any

This is a value set defined by the FHIR project.

Summary

Defining URL: http://hl7.org/fhir/ValueSet/http-operations
Version: 5.0.0-ballot
Name: TestScriptRequestMethodCode
Title: TestScriptRequestMethodCode
Status: draft
Definition:

The allowable request method or HTTP operation codes.

Committee: FHIR Infrastructure icon Work Group
OID: 2.16.840.1.113883.4.642.3.716 (for OID based terminology systems)
Flags: Immutable

This value set is used in the following places:

4.4.1.233.1 Content Logical Definition

 

4.4.1.233.2 Expansion

USLab Ratio Observation Profile Example: Dengue Titer (id = "uslab-example4") This expansion generated 10 Sep 2022

This value set contains 7 concepts

Raw XML

Expansion based on TestScriptRequestMethodCode v5.0.0-ballot (CodeSystem)

<!-- FHIR build is generating the narratives &lt;text&gt; &lt;status value=&quot;generated&quot;/&gt; &lt;div xmlns=&quot;http://www.w3.org/1999/xhtml&quot;&gt; &lt;ul&gt; &lt;li&gt; obs-uslab-example4.xml&lt;/li&gt; &lt;li&gt; id: uslab-example4&lt;/li&gt; &lt;li&gt; Name: USLab Observation Example4&lt;/li&gt; &lt;li&gt;Description: USLab Ratio Observation Profile Canonical Example: Dengue Virus&lt;/li&gt ; &lt;/ul&gt; &lt;/div&gt; &lt;/text&gt; --><!-- extension for specimen reject goes here - not for this use case &lt;extension url=&quot;http://hl7.org/fhir/StructureDefinition/uslabspecimenrejectreason&quot;&gt; &lt;valueCodeableConcept&gt; &lt;coding&gt; &lt;system value=&quot;http://hl7.org/fhir/v2/0490&quot;/&gt; &lt;code value=&quot;EX&quot;/&gt; &lt;display value=&quot;Expired&quot;/&gt; &lt;/coding&gt; &lt;/valueCodeableConcept&gt; &lt;/extension&gt; --> <!-- In FHIR, units may be represented twice. Once in the agreed human representation, and once in a coded form. Both is best, since it's not always possible to infer one from the other in code. When a computable unit is provided, UCUM (http://unitsofmeasure.org) is always preferred, but it doesn't provide notional units (such as &quot;tablet&quot;), etc. For these, something else is required (e.g. Snomed-CT) --> <!-- eH dataabsent reason would go here if valueQuantity was empty e.g.: &lt;dataAbsentReason value=&quot;error&quot;/&gt; -->
Code </Observation> System Display Definition
   delete http://hl7.org/fhir/http-operations DELETE

HTTP DELETE operation.

   get http://hl7.org/fhir/http-operations GET

HTTP GET operation.

   options http://hl7.org/fhir/http-operations OPTIONS

Usage note: every effort has been made to ensure that HTTP OPTIONS operation.

   patch http://hl7.org/fhir/http-operations PATCH

HTTP PATCH operation.

   post http://hl7.org/fhir/http-operations POST

HTTP POST operation.

   put http://hl7.org/fhir/http-operations PUT

HTTP PUT operation.

   head http://hl7.org/fhir/http-operations HEAD

HTTP HEAD operation.

 

See the examples full registry of value sets defined as part of FHIR.

Explanation of the columns that may appear on this page:

Lvl A few code lists that FHIR defines are correct and useful, but they hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
Source The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
Display The display (used in the display element of a normative part Coding ). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the specification. meaning of the concept
Comments Additional notes about how to use the code