| Official URL: https://gematik.de/fhir/erp-servicerequest/ValueSet/service-request-status-vs | Version: 1.2.0 | |||
| Active as of 2025-07-31 | Computable Name: ServiceRequestStatusVS | |||
Auswahl von Codes zur Angabe des Status eines ServiceRequests
References
This value set includes codes based on the following rules:
http://hl7.org/fhir/request-statusThis value set excludes codes based on the following rules:
http://hl7.org/fhir/request-status| Code | Display | Definition |
| draft | Draft | The request has been created but is not yet complete or ready for action. |
| on-hold | On Hold | The request (and any implicit authorization to act) has been temporarily withdrawn but is expected to resume in the future. |
| unknown | Unknown | The authoring/source system does not know which of the status values currently applies for this request. Note: This concept is not to be used for "other" - one of the listed statuses is presumed to apply, but the authoring/source system does not know which. |
Expansion performed internally based on codesystem RequestStatus v4.0.1 (CodeSystem)
This value set contains 4 concepts
| Code | System | Display (de-DE) | Definition |
| active | http://hl7.org/fhir/request-status | The request is in force and ready to be acted upon. | |
| revoked | http://hl7.org/fhir/request-status | The request (and any implicit authorization to act) has been terminated prior to the known full completion of the intended actions. No further activity should occur. | |
| completed | http://hl7.org/fhir/request-status | The activity described by the request has been fully performed. No further activity will occur. | |
| entered-in-error | http://hl7.org/fhir/request-status | This request should never have existed and should be considered 'void'. (It is possible that real-world decisions were based on it. If real-world activity has occurred, the status should be "revoked" rather than "entered-in-error".). |
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | 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) |
| 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 |