Tenancy FAQs

Home > Tenancy FAQs

Welcome to our tenancy FAQs page, where we address common queries associated with Interweave tenancies to enhance your understanding of the topic. If you have any additional questions, please get in touch.

The Interweave Care Portal is what is referred to as multi-tenanted. Simply put, this means multiple organisations are able to use the same platform, whilst keeping data and configurations specific to their own needs. When we refer to a tenancy, this means a particular instance of the Care Portal associated with a given region.

Consuming organisations who are using Interweave Portal or context launching from their system.

Tenancies are supported in a number of ways. Typically, organisations have support teams that assist with questions and concerns. There is also an Interweave Service Desk who work to answer questions, log bugs and communicate changes.

This varies, but tenancy deployments take, on average, around 30 days. This gives us time to ensure we have the correct information, appropriate sign-offs, and to complete the technical delivery.

It is important that the tenancy name is both explicit and instructive. The tenancy name should be noticeable at a glance so users can identify themselves with the correct tenancy. In addition, a number of our reports are generated based on tenancy name, so it is essential that the names are identifiable.

As such, the tenancy name should be easily distinguishable. It must be between 4 and 20 characters with no hyphens or spaces.

The Project Manager or Delivery Lead from the respective organisation should request tenancies.

The Project Manager or Delivery Lead should raise a ticket in our JIRA system. You will be prompted to complete a tenancy request form and, when approved, your request will progress.

When you have completed assurance activities and Interweave have approved your request to move to your production / live environment.

Sandpit

Sandpit tenancies are typically deployed to support with testing activities. For example, if an organisation is configuring a context launch or a single sign on, we will deploy a sandpit environment to ensure the function works as expected before pushing to production.

Production

Your production tenancy is your live environment where you can expect to see real patient data.

This answer can be established by consultation with the Project Team. In most circumstances, one tenancy is adequate to service an organisation’s needs. However, there are exceptions where this is not the case. In those circumstances, please consult with your Project Manger for advice on how to proceed.

The ODS code is required when setting a tenancy. We use this identifier to obtain an ASID code from NHSE. Without the ASID code, an organisation will be unable to view data supplied via GP Connect.

The Portal Admin application is an essential part of the Interweave product set. It serves a number of important functions such as:

  • User management
  • Feature management
  • Notifications

Portal Admins should not be a clinical user. The person assigned to fulfil this role is often Support Staff, Admin Staff or IT Professionals.

Yes. It’s a good idea to have at least two Portal Admins. This covers you in case of unforeseen sickness or annual leave.

Portal Admins are responsible for a number of things. Below is a list of examples, broken down by the way users will access the system.

Interweave Care Portal (stand-alone)

  • Initial portal configuration – ensuring the correct features and panels are switched on for users.
  • Adding users.
    • With new tenancies, users can be added in bulk by uploading a CSV file. If you need support with this, please let us know).
  • Removing users.
    • It is important to ensure access is provided only to those that need it. The Portal Admin will regularly review starters and leavers, and update the user list accordingly.

SystmOne Context Launch

Other / EPR Context Launches

  • Initial portal configuration – ensuring the correct features and panels are switched on for users.
  • Does not need to register staff.
  • Will need to monitor and remove users who have left the organisation.