Changes to a service tree
A service tree may need to change over time, to best reflect the services provided by the organisation at the present moment. There may be different reasons for a service tree to change:
- The service was not previously on the service tree
- There may be mistakes to be corrected
- New services may open
- Old services may close
- A service may change its name or function
- A service may move from one location or grouping to another
Services which are moving need extra thought: is the service itself (the whole team of people) moving from A to B, or would it be truer to say that the service at A is closing, and a new and different service is starting at B?
Who can request service tree changes, and how often?
Your initial service tree will have been modified or created by the Care Opinion support team in consultation with you, at the start of your subscription. This would have covered key service areas and locations, but may not have included all services.
After this initial setup, your service tree can evolve as your services change or as more services roll our Care Opinion and need to be added to your service tree. This is subject to a few constraints, your change requests must be:
- Sent via a subscription administrator
- About the service tree owned by your organisation
- Submitted using the Excel template provided
How do you submit a request, or batch of requests?
As noted, there are different types of change request. The information we need to action a request depends on the type, as follows:
*** Table to be inserted **
Change requests should be submitted in an Excel file. Using an Excel file makes it far easier for you and us to keep track when a batch contains a number of different kinds of request.
Excel templates
To help you, we have created a template Excel file which you can download and complete for each batch of change requests you plant to submit.
service-tree-change-request-template-apr24.xlsx
In the file there is a separate worksheet for you to list requests of each type. There is a list of available treatment functions which help describe what the service does in the spreadsheet and you can also see list of treatment functions on this page:
https://www.careopinion.org.uk/tfs
Effect on member alerts, reports and digests
Moving a service may affect saved member assets such as alerts, reports and digests. For example, imagine the podiatry service is based in hospital A, but then the whole podiatry team moves to hospital B to provide the same service, so you ask us to move the service in our tree.
- An alert which lists that specific podiatry service will not be affected
- An alert for all stories about hospital A will no longer be alerted to podiatry stories
- An alert for all stories about hospital B will now be alerted to podiatry stories
Effect on invitation links
An invitation link may be set to suggest a specific service during “tell your story”, or to offer a kiosk page for the service. If the service is deleted, any kiosk page for the service can no longer be displayed. The “tell your story” workflow will still work, but will not suggest deleted or closed services.