Software for administrative workflows in health organisations. We do not provide care or clinical advice.

Mon–Fri, 09:00–18:00 UK time · Contact

Tamispace Arrange a conversation

Tamispace · Fitzrovia, London

For the people who keep healthcare organised.

We design and build software for the administrative work behind health organisations: rotas, requests, onboarding, rooms and the reporting that ties them together. Quietly, carefully, and with a firm line between administration and care.

A calm room with green panelled walls, a burgundy chair, a wooden desk with a lamp and a framed abstract painting

Who we work with

  • Practice and service managers
  • Rota and scheduling coordinators
  • Referral and bookings administrators
  • HR, onboarding and operations teams

Arrange a conversation

Why we exist

The work nobody sees until it goes wrong

Behind every clinic, practice, charity or community health service is a layer of administration: who is working when, which request is with whom, which documents a new colleague still needs, which room is free on Thursday.

It is skilled work, and it is often supported by tools that were never designed for it: shared spreadsheets, colour-coded calendars, long email chains and the memory of one or two experienced people. That works until someone is on leave, a request is missed, or a rota error lands at the worst moment.

Tamispace exists to make that work calmer. We build focused software that fits the way your administrative teams already think, removes the repetitive copying and chasing, and makes the state of things visible to the people who need it, without asking clinical staff to learn yet another system.

Scope

A clear line, drawn early

What we build

  • Rota, scheduling and leave tools
  • Request, referral and booking administration queues
  • Onboarding and staff-document workflows
  • Room and equipment booking
  • Operational reporting from administrative data

What we never build

  • Clinical records or decision support
  • Anything that diagnoses, treats or advises on care
  • Software regulated as a medical device
  • Patient-facing medical advice
  • Emergency or out-of-hours operational systems

When a workflow touches clinical information, we design around it: an administrative tool can record that a referral was received and who owns it, without holding the clinical content itself. If the clinical content is essential, we will tell you plainly that you need a specialist clinical system instead.

Find your starting point

What would help your role first?

Choose the role closest to yours. We will show the kinds of tools that usually help most, and a question worth bringing to a first conversation.

Oversight without chasing

  • A single view of open administrative tasks by team and due date
  • Approval routes for leave, purchases or room changes with a clear audit trail
  • Weekly operational summaries drawn from data your team already enters

A question to bring to us: Which three questions do you answer by asking colleagues every week?

Approach

How we work with you

  1. Listen. We spend time with the administrators who do the work, using fictional or anonymised examples rather than real records.
  2. Describe. A short written outline: the workflow, roles, data needed (and not needed), retention, and what is out of scope. Reviewed with your data protection lead.
  3. Build gently. Small releases, tested by the people who will use them, alongside existing processes until everyone is confident.
  4. Hand over and support. Training for administrators, plain documentation and support during UK working hours.
How we work, in more detail
A burgundy upholstered chair beside a window and a small plant in a green room
Illustrative image

Data care

Careful with information, by design

Health organisations hold some of the most sensitive information there is. Even administrative systems carry names, contact details and sometimes the fact that a person is in contact with a service. We treat that seriously:

  • Collect only what each workflow needs, agreed field by field
  • Role-based access, with significant actions logged
  • Hosting in the UK or EU, in accounts you control
  • Retention and deletion agreed with your information governance lead
  • No real records used in design or testing

We are not a certification body and do not claim to make you compliant. We work alongside the people in your organisation who are responsible for that.

Data care and boundaries

Deliverables

What you receive

A workflow outline
Roles, steps, data, retention and exclusions, written for your managers and your DPO.
Working software in small releases
Each tested by the administrators who will use it.
Plain documentation
Guides for administrators, and a technical handover for whoever looks after the system.
Ownership
Code in your repository, hosting in your accounts, nothing held back.
A support arrangement
Weekday support with a clear distinction between fixes and changes.

Readiness

Is this workflow ready to be designed?

Eight questions about information handling. None of them asks for any real data. Tick what is already true; each unticked item shows a short note.

  1. If you cannot list it, the first step is a data inventory for this one workflow.

  2. Access rules are easier to agree on paper before software enforces them.

  3. Your DPO or information governance lead should be involved from the start.

  4. Retention is a policy decision; software can only follow it.

  5. We build administrative tools. If clinical content is essential, a specialist clinical system is needed.

  6. Real-looking but fictional examples let us design without seeing real patient or staff data.

  7. Even a list of names helps us assess connections early.

  8. An hour a fortnight from the people doing the work is enough.

0/8

Standards

Quality, in practice

  • Accessible. Keyboard use, screen readers, clear contrast and readable type, checked against WCAG 2.2 AA criteria; administrators often work long days on these screens.
  • Gentle on attention. Few notifications, clear states and no clutter.
  • Tested with real users. The people doing the work test each release before it replaces anything.
  • Reversible. We run alongside existing processes until the new one is trusted.

Aftercare

Support, during working hours

Once a tool is live, you can reach us Monday to Friday, 09:00–18:00 UK time. We acknowledge requests within one working day. We do not provide out-of-hours or emergency cover, which is why we only build administrative tools that can safely wait until the next working day; anything that cannot should not depend on us.

Support and requests

Questions

Questions people ask us

Do you work with NHS organisations?
We can work with NHS, independent and voluntary-sector organisations on administrative workflows. Procurement routes vary; we will be clear about what we can and cannot offer, and we do not claim framework membership.
Will you need access to patient records?
No. We design with fictional or anonymised examples, and our tools are built to avoid holding clinical content.
Can you connect to our existing systems?
Where they offer a documented interface or export and your organisation permits it. We will assess this early and say plainly if a connection is not sensible.
Are you a medical software company?
No. We build administrative software. We do not provide care, clinical advice or regulated medical devices.
How long does a first tool take?
A focused first release is often six to twelve weeks after the outline is agreed, depending on connections and approvals.

Tell us which part of the week is hardest.

Write a few lines about the workflow that takes the most chasing. Please do not include any patient or staff personal information. We reply within two working days.

Arrange a conversation Check readiness first