This page is part of the FHIR Specification (v5.0.0-ballot: R5 Ballot - see ballot notes). 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 R2
FHIR Infrastructure Work Group | Maturity Level: 2 | Trial Use | Use Context: Not yet ready for Production use, Not yet ready for Production use |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/testscript-operation-codes |
Version: | 5.0.0-ballot |
Name: | TestScriptOperationCode |
Title: | |
Status: | draft |
Definition: | This value set defines a set of codes that are used to indicate the supported operations of a testing engine or tool. |
Committee: | FHIR Infrastructure Work Group |
OID: | 2.16.840.1.113883.4.642.3.704 (for OID based terminology systems) |
Flags: | Experimental |
This value set is used in the following places:
http://hl7.org/fhir/restful-interaction
This expansion generated 10 Sep 2022
This value set contains 17 concepts
Expansion based on FHIR Restful Interactions v5.0.0-ballot (CodeSystem)
Level | Code | System | Display | Definition |
1 | read | http://hl7.org/fhir/restful-interaction | read | Read the current state of the resource. |
1 | vread | http://hl7.org/fhir/restful-interaction | vread | Read the state of a specific version of the resource. |
1 | update | http://hl7.org/fhir/restful-interaction | update | Update an existing resource by its id (or create it if it is new). |
1 | patch | http://hl7.org/fhir/restful-interaction | patch | Update an existing resource by posting a set of changes to it. |
1 | delete | http://hl7.org/fhir/restful-interaction | delete | Delete a resource. |
1 | history | http://hl7.org/fhir/restful-interaction | history | Retrieve the change history for a particular resource, type of resource, or the entire system. |
2 | history-instance | http://hl7.org/fhir/restful-interaction | history-instance | Retrieve the change history for a particular resource. |
2 | history-type | http://hl7.org/fhir/restful-interaction | history-type | Retrieve the change history for all resources of a particular type. |
2 | history-system | http://hl7.org/fhir/restful-interaction | history-system | Retrieve the change history for all resources on a system. |
1 | create | http://hl7.org/fhir/restful-interaction | create | Create a new resource with a server assigned id. |
1 | search | http://hl7.org/fhir/restful-interaction | search | Search a resource type or all resources based on some filter criteria. |
2 | search-type | http://hl7.org/fhir/restful-interaction | search-type | Search all resources of the specified type based on some filter criteria. |
2 | search-system | http://hl7.org/fhir/restful-interaction | search-system | Search all resources based on some filter criteria. |
1 | capabilities | http://hl7.org/fhir/restful-interaction | capabilities | Get a Capability Statement for the system. |
1 | transaction | http://hl7.org/fhir/restful-interaction | transaction | Update, create or delete a set of resources as a single transaction. |
1 | batch | http://hl7.org/fhir/restful-interaction | batch | perform a set of a separate interactions in a single http operation |
1 | operation | http://hl7.org/fhir/restful-interaction | operation | Perform an operation as defined by an OperationDefinition. |
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 |