This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times). 
See the Directory of published versions 
Responsible Owner: Orders and Observations   Work Group | 
Draft | Use Context: Country: World | 
      Official URL: http://hl7.org/fhir/ValueSet/processingdevice-code
     | 
    
Version: 6.0.0-ballot3 | |||
| draft as of 2025-11-03 | Computable Name: ProcessingDeviceCode | |||
| Flags: | OID: | |||
This value set is used in the following places:
Codes for devices used in specimen processing.
Generated Narrative: ValueSet processingdevice-code
Last updated: 2025-11-03T21:06:08.628Z
Profile: Shareable ValueSet
http://snomed.info/sct 
 version Not Stated (use latest from terminology server)| Code | Display | 
465735003 ![]()  | Sliding microtome | 
701945002 ![]()  | Blood centrifugation system processing unit | 
This expansion generated 03 Nov 2025
ValueSet
Expansion from tx.fhir.org based on SNOMED CT International edition 01-Feb 2025
This value set contains 2 concepts
| System | Code | Display | Display (English) | 
 http://snomed.info/sct | 
  465735003 ![]()  | 
Sliding microtome | Sliding microtome (physical object) | 
 http://snomed.info/sct | 
  701945002 ![]()  | 
Blood centrifugation system processing unit | Blood centrifugation system processing unit (physical object) | 
See the 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 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 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 meaning of the concept | 
| Comments | Additional notes about how to use the code |