Welcome to our Resource Hub

If you’ve not done so already, we suggest you do an informal trial (or ‘pre-pilot trial’) of the app by getting your hands on an iPad and downloading the app from the Apple App Store for free.

While you can’t sign off cases without an account, it’s ideal for trauma simulation scenarios to assess its suitability for your team. Data remains secure on the device and can be fully deleted after use to comply with governance. Check out our demos or training resources to equip your team to have a go now.

Following successful initial trial and validation of the solution, you can move towards running a 6 Month pilot in your Emergency Department.

*The Software Licence is offered free during the period of the pilot, with reduced setup and integration fees depending on requirements.

The Pilot enables fully integrated use of the Trauma App live in Resus, experiencing all the benefits and evaluating/validating its full deployment post-pilot

This is a document sometimes required which initially outlines the plan and purpose for deploying the Trauma App into your Trauma Care workflow. It can set the ball rolling and ensure you have clearance to proceed to set up a Project Team, etc. Find out from your CCIO or equivalent to understand the relevant stages required from your Hospital.

To streamline the process, we highly recommend forming a project team to lead deployment of the Trauma App into a formal pilot phase. Below, we’ve outlined who typically takes responsibility for each area, helping you identify key roles within your hospital. There will be a member of the Trauma App team assigned to your deployment and able to join your kickoff and monthly meetings.

• Senior Responsible Officer – A senior individual should be named as overall project lead, sometimes referred to as the senior responsible officer (SRO) for the project. Depending on local context this may be the Chief Clinical Information Officer, Chief Nursing Information Officer (CNIO), or Director of Innovation etc.
• Clinical Lead – A Clinical lead should be assigned to the project. This will usually be a consultant and performed alongside usual clinical duties.
• Trauma App Champion – Usually a Trauma Coordinator, or senior level Nurse who, in support of the clinical lead, drives the deployment and adoption of the tool
• Technical Lead – Required to oversee software services setup and integration into hospital IT systems/environment.
• Governance & Procurement – This can be one or multiple people who have oversight of Clinical Safety, Data & Security Protection, and procurement requirements.

Trauma case data generated by the app is hosted entirely on the hospital’s servers and set up by the Trauma App Integrations team in collaboration with your eHealth/IT team, ensuring that data remains within the hospital’s ecosystem for complete customer control.

The app allows for offline data collection on an iPad, with regular syncing to the cloud for continuity, and upon case closure, verified data is transferred to the cloud and deleted from the device.

1. Authentication – Utilises your existing identity management system allowing staff to login using credentials they are familiar with. 
2. Patient Identity – Verify patient details through a lookup service (e.g. CHI Lookup in Scotland, or NHS Number via the Spine network in England). The Trauma App supports identifier lookup from demographics or demographics from patient identifier
3. EPR Document repository – Push PDF case reports into the hospital’s EPR. 
4. EPR Direct – Push structured data into the hospital’s EPR. Pull physiology, interventions, notes, results etc. from the hospital’s EPR. 

We recommend you engage your eHealth/IT team early in the process to look over the Project and System description document and set up a call with the Trauma App integrations team to discuss the options.

You will need to ensure you source the following devices and equipment to use the Trauma App software, which is an iOS iPad application. 

• iPads – You will need to have at least 1 iPad (8th generation or higher) per resus bay, and 1 spare for the department. Some hospitals choose to operate with multiple iPads during a single case.  
• Charging Station – You are required to have a charging station capable of charging all iPads at once.
• Device Management – If not already in place, remote management systems (e.g. ‘Workspace ONE‘ or Microsoft InTune) can be installed to ensure that passcodes and auto updates are enabled for safety and security purposes.
• Wifi printer – It is a clinical safety risk mitigation to ensure that the final report can be printed to follow the patient in the event that the final report can’t be automatically uploaded to the Electronic Patient Record (EPR).

Trauma App integrates seamlessly into existing trauma teams, covering documentation typically handled by scribes in UK trauma booklets. The main challenge for scribes is adapting to the new data capture processes, for which you have free access to the training videos and guides here. You can also request a qualified scribe to join you at a simulation and provide bespoke training for your team.

You will get access to the Dashboard online portal once your site is set up with the Trauma App.. This allows you to add (or bulk upload) users with varying permissions of access from administration, case input, and case involvement.

This is a key document required in order to obtain board/trust level approval to proceed with the onboarding process of the App beyond the Pilot phase. The business case format varies between different health boards, but generally follows this ‘Five Case Model’ for evaluation: 

You’ll need to provide evidence that the Trauma App is…

• Supported by a robust Case for Change – the strategic case;
• Able to deliver Value for Money – the economic case;
• Commercially viable – the commercial case;
• Financially affordable – the financial case; and
• Capable of being delivered – the management case.

You will need to review the pricing and, together with the Trauma App team and your Hospital Procurement team, formalise a draft proposal and licence agreement as suited to the level of setup and integrations agreed.

Note: Piloting the app for 6 months comes with a free software licence and reduced setup costs to support evaluation and validation of the tool for procurement beyond the pilot.

We’re also listed on the G-Cloud-14 UK Government public sector procurement framework which offers you a faster way of buying software services.