These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- ITSM for Healthcare and Hospitals
- Features
- Service requests
Service requests
Track hospital staff requests through a dated outcome.
OverviewSubmitted Service Requests×
ITSM for Healthcare and Hospitals · Service requests
New
Submitted Service Requests
Approval conditions
| Id | Request type | Status | Requested at | Due at | Requester | |
|---|---|---|---|---|---|---|
| IDD-582 | RT-682 | Submitted | 09 Oct | 13 Oct | ||
| IDD-466 | RT-685 | Submitted | 25 Oct | 01 Nov | ||
| IDD-556 | RT-100 | Submitted | 19 Oct | 25 Oct | ||
| IDD-698 | RT-457 | Submitted | 06 Oct | 09 Oct | ||
| IDD-677 | RT-752 | Submitted | 08 Oct | 14 Oct |
6 of 6 records
IDD-582Service requests · SR-71938
SubmittedRequest typeRT-682
Requested at09 Oct
Due at13 Oct
ServiceSRV-3252
What you can do
Follow the working record
A ward requests access to a clinical service. The desk analyst records the requester, request type, service and due date. The manager reviews the submitted request before the fulfillment team starts work. An approved request can move into progress and then completion. Its completed date lets the manager compare the result with the original due date.
The request record contains the requester, service, request type, due date and completion date. The team agrees who handles fulfillment and keeps that responsibility clear during handoff. The completion workflow runs when a request is updated; the manager should inspect the resulting state and date rather than assume approval was automatic.
How the work is organized
- Intake. The Clinical Service Desk Analyst records who asked, the request type, service and due date.
- Decision. The Service Manager reviews a Submitted request and records whether it is Approved or Rejected.
- Completion. Record in progress work and retain the Completed date for comparison with the original due date.
A rejected request remains a distinct outcome. A request marked Completed should carry the date that the work finished, so late work can be identified from the same record.
What to agree during setup
Agree which request types require manager approval and how the team will identify the person doing fulfillment. Set due dates according to the clinical area’s need, then verify that the requester and service references point to the right records. Define who can reject a request and who may mark it complete.
Use a Submitted request and a rejected request in the pilot. Test the completion update against both. Check that a rejected request is not presented as completed and that the due date survives later status changes.
Check the handoff on an actual case
Rehearse a ward access request. The analyst enters the requester, service and due date; the manager reviews it while it is Submitted. For an approved request, move the record through in progress to Completed and compare the completion date with the original deadline.
Have the requester confirm the result. If work is delayed, leave its current status visible and explain the next action in the team handoff. Check that the manager can distinguish a completed request from a rejected one.
Use the submitted queue to separate a new request from work already approved. The requester and service references should remain stable while the status changes. At completion, the manager can see whether the work met the due date and can ask the requesting area to confirm the practical result before treating the handoff as finished.
What your team sees
- Active Clinical Service Requests — Review the filtered records and choose the next action.
- Submitted Service Requests — Open related records before the handoff.
Follow the work through
What it keeps track of
Data model- Service requests
- Clinical service requests raised by hospital staff.
- Services
- Clinical and IT services delivered across the hospital and health system.
- People
- People records for IT service and asset operations.
Who uses it
Permissions- Clinical Service Desk Analyst
- , Service Manager, Admin
Set up ITSM for Healthcare and Hospitals your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.