HUMA THERAPEUTICS LIMITED

Huma Virtual Care / Remote Patient Monitoring

Huma’s remote patient monitoring / virtual care platform connects patients and clinicians through a smartphone Patient App and a web-browser Clinician Portal. Care teams can increase capacity, safely monitor more patients, spot deterioration and deliver proactive care. Our disease-agnostic software-as-a-medical device platform holds EU MDR Class IIb certification.

Features

• Highly configurable platform powering virtual care and remote patient monitoring
• Capture information remotely including vital signs, symptoms and patient-reported outcomes
• Award-winning smartphone app accessible on iOS and Android devices
• Clinician portal accessible via web-browser with Generative AI capabilities
• Library of configurable modules for primary, community and acute services
• Dedicated, configurable App learn / education section enabling patient self-management
• Telemedicine and messaging functionality to enhance engagement with patients
• Device-agnostic, connect with Bluetooth devices or use standalone devices
• Traffic-light thresholds/flags and biomarkers to identify deterioration and prioritise patients
• Supports electronic health record integration with FHIR HL7 compliance

Benefits

• Increase clinical capacity (~x2) evidenced through Huma NHS programmes
• Earlier discharge (40% shorter stay seen using Huma technology)
• Safely monitor patients at home avoiding unnecessary admissions/outpatient demand
• Safely manage elective waitlists / support people wait-well and recover
• >30% reduction in hospital admission and readmission
• Improve patient outcomes (e.g. 3-4 times lower mortality rate)
• Help spot deterioration earlier (88% at-risk patients had surgery prioritised)
• Facilitates multi-disciplinary working across clinical teams and different care settings
• Enhance patient self-management and understanding of their condition
• Market-leading patient experience (NPS +71) and adherence rates (>90%)

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at aman.kundraw@huma.com. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

810617856464959

Contact

Aman Kundraw
07943881778
aman.kundraw@huma.com

About your service

• Service categories:

  Applications

  Production and operations

  Service industry and public sector operations

  • Healthcare
  • Defence
• Multi cloud support: No

Service scope

• Software add-on or extension: No
• Cloud deployment model: Public cloud
• Service constraints: The Clinician Portal is accessible from any device via standard internet access and is compatible with the following web-browsers (most recent version and one previous version of each web-browser are supported): Chrome, Firefox, Safari, Opera, Electron and Microsoft Edge.; ; The Patient App is available on Android and iOS smartphones (device agnostic). The Huma Patient App is compatible with iOS 13 or above, and Android minimum 6 and maximum Android 12. (6.0). The Software Solution language is English (UK).
• System requirements:
  • Clinician Portal available on all major web-browsers
  • Patient App available on Android and iOS smartphones

User support

• Email or online ticketing support: Yes
• Support response times: Ongoing support is provided via the support@huma.com and through our embedded conversation tool (powered by Intercom).; ; Huma’s resolution times are generally <2 hours for queries within working hours.
• User can manage status and priority of support tickets: No
• Phone support: Yes
• Phone support availability: 9 to 5 (UK time), Monday to Friday
• Web chat support: Yes
• Web chat support availability: 9 to 5 (UK time), Monday to Friday
• Web chat support accessibility standard: WCAG 2.2 AA
• Web chat accessibility testing: Huma undertakes web-chat testing with assistive technology users as part of it's compliance to WCAG 2.2 standards
• Onsite support: Yes
• Support levels: Huma provides both initial on-boarding support and readily available ongoing support via a Customer Success Team.; ; Onboarding support is provided from configuration of the platform until the tool is officially launched. The Huma Customer Success team will provide onboarding support via the following:; i) A bespoke implementation plan outlining the steps necessary to complete transition from platform configuration to providing access for go-live; ii) Customer success plan including clinical and non-clinical KPIs which have been pre-defined, and; iii) Product training to be completed by all relevant team members prior to being provided access to the Huma platform.; ; Ongoing and technical support is provided via the support@huma.com email address and through an embedded conversation tool within (powered by Intercom).; ; Huma’s resolution times are <2 hours for most queries.; ; Where on-site support is required, Huma will work with the organisation to agree the level of support and develop a suitable plan to meet requirements.
• Support available to third parties: Yes
• AI chatbot: Yes

Onboarding and offboarding

• Getting started: Huma provides both initial on-boarding support and readily available ongoing support via a remote Customer Success Team.; ; Onboarding support is provided from configuration of the platform until the tool is officially launched and access is provided to the clinical team. The Huma Customer Success team will provide onboarding support via the following:; ; i) Huma will present a bespoke implementation plan outlining the steps necessary to complete transition from platform configuration to providing access for go-live; ; ii) Customer success plan defined as per clinical and non-clinical KPIs which have been pre-defined, and; iii) Product training to be completed by all relevant team members prior to being provided access to the Huma platform.
• Service documentation: Yes
• Documentation formats: HTML
• End-of-contract data extraction: All data can be exported from the Clinician Portal at any time through the export feature.
• End-of-contract process: At the end of a contract, Huma would work with the client to agree a full handover process.
• Documentation accessibility standard: WCAG 2.2 AA

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari
  • Opera
• Application to install: Yes
• Compatible operating systems:
  • Android
  • IOS
• Designed for use on mobile devices: Yes
• Differences between the mobile and desktop service: The Patient App is available on Android and iOS devices.
• Service interface: Yes
• User support accessibility: WCAG 2.2 AA
• Description of service interface: Huma’s digital virtual care platform connects patients and clinical teams, facilitated by real-time visualisation of data, without recourse to face-to-face appointments. Huma’s technology comprises a smartphone Patient App (available on Android and iOS) and a web-browser based Clinician Portal.
• Accessibility standards: WCAG 2.2 AA
• Accessibility testing: Huma works with assistive technology users to complete interface testing as part of our compliance to WCAG 2.1 standards
• API: Yes
• What users can and can't do using the API: Huma provides both FHIR client and server schemes to support interoperability. The client sends a FHIR request to a REST endpoint for operations such as creating a resource, reading from the server, updating or deleting the resource.; ; The Huma FHIR server implements several parts of FHIR RESTful API and resources (patient, observation, etc.) which are pertinent to the Huma platform. Huma FHIR server provides:; Capabilities; Store resources; Search; Validation against a structured definition (profile); Supports JSON and XML; Supports transactions and batches; SNOMED CT architecture
• API documentation: Yes
• API documentation formats:
  • HTML
  • PDF
• API sandbox or test environment: Yes
• Customisation available: Yes
• Description of customisation: Huma’s platform is highly configurable, enabling rapid development of different pathway or speciality applications. For example, it has been deployed to manage patients on cardiac and orthopaedic surgery waiting lists, to monitor people at home with acute respiratory diseases, and to support people with chronic disease such as type 2 diabetes and heart disease / heart failure in primary or community care settings. It provides a ‘one-stop shop’ for patients, avoiding multiple individual point solutions - and we are continually developing new data collection modules to support enhance remote monitoring capabilities.; ; Where customers require Huma to develop bespoke modules or services, we scope this during mobilisation and provide a timeline for delivery as part of our deployment plan. This could be supported through self-service functionality enabling care teams to build their own remote patient monitoring solutions, using our EU MDR Class IIb platform.

Scaling

• Independence of resources: Huma's platform is cloud-based provided by UK based cloud partners (including Amazon, Google and Microsoft). The platform undergoes frequent load testing to ensure users aren't affected by the demands of other users.

Analytics

• Service usage metrics: Yes
• Metrics types: Huma's analytics platform provides insights into platform usage. Typical standard usage metrics that can be reported include, for example: number of user / patient registrations, number of active users / patients, time spent using the Clinician Portal, user / patient gender comparison, user / patient age comparison, usage per App data collection module. This data can be analysed over various time periods.
• Reporting types:
  • Regular reports
  • Reports on request
• Resource tagging: No
• FOCUS resource tagging: No

Resellers

• Supplier type: Not a reseller

Staff security

• Staff security clearance: Conforms to BS7858:2019
• Government security clearance: Security Clearance (SC)

Asset protection

• Knowledge of data storage and processing locations: Yes
• Data storage and processing locations: United Kingdom
• User control over data storage and processing locations: No
• Datacentre security standards: Complies with a recognised standard (for example CSA CCM version 4.0)
• Penetration testing frequency: At least once a year
• Penetration testing approach: Another external penetration testing organisation
• Protecting data at rest:
  • Physical access control, complying with another standard
  • Encryption of all physical media
  • Scale, obfuscating techniques, or data storage sharding
• Data sanitisation process: No
• Equipment disposal approach: In-house destruction process

Data importing and exporting

• Data export approach: Users can export all data directly from the Clinician Portal at any time.
• Data export formats:
  • CSV
  • Other
• Other data export formats: JSON
• Data import formats: Other
• Other data import formats:
  • Manual health data through Patient App
  • Through connected medical devices
  • Captured through the Smartphone (e.g. Heart Rate)
  • Passive collection through Smartphone HealthKit

Data-in-transit protection

• Data protection between buyer and supplier networks: TLS (version 1.2 or above)
• Data protection within supplier network: TLS (version 1.2 or above)

Availability and resilience

• Guaranteed availability: Target Uptime – subject to the exclusions set out below, Huma shall aim to make the Software Solution available 24 hours per day, 7 days per week, 365 days per Year at the below service availability levels.; ; Service Availability – 99%, measured on a Quarterly basis.; ; Exclusions; The following shall not be included in the calculation of service availability: (i) outages, disruption or downtime caused by the Client; (ii) a Force Majeure event; or (iii) Scheduled Downtime.; ; Reporting; Service levels will be reported every 6 months (the “Reporting Period”) from the date of first user onboarded onto the solution.; ; Service Credits are available when guaranteed levels of availability are not met.
• Approach to resilience: The platform is hosted UK based cloud servers provided by either Amazon Web Services, Google Cloud or Microsoft Azure.; ; All data is backed-up and stored in line with national standards and policies. Our approach enables the service to use multiple servers in different locations if the is a outage / service disruption in one centre.
• Outage reporting: Users are contacted through the Intercom service and service outages are reported on our platform status page.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Multi-Factor Authentication (MFA)
  • Username or password
• Access restrictions in management interfaces and support channels: All API's require the user to have authenticated
• Access restriction testing frequency: At least every 6 months
• Management access authentication:
  • Multi-Factor Authentication (MFA)
  • Username or password

Audit information for users

• Access to user activity audit information: Users contact the support team to get audit information
• How long user audit data is stored for: User-defined
• Access to supplier activity audit information: Users contact the support team to get audit information
• How long supplier audit data is stored for: User-defined
• How long system logs are stored for: User-defined

Security governance

• Named board-level person responsible for service security: Yes
• Security governance certified: Yes
• Security governance standards: ISO/IEC 27001
• Information security policies and processes: The information security policies and processes are all contained within the company Quality Management System and Technical Files. This includes the information security policies and processes that satisfy the requirements for the Information Governance Toolkit produced by the Department of Health (DH) and hosted by the Health and Social Care Information Centre (HSCIC). Huma's Quality Representative ensures that these policies and conveyed to the company. The Quality representative reports to Huma's Executive Leadership Team, including board-level person(s) responsible for service security. The processes include periodic audit, penetration testing - where appropriate, the results of these are reported to the Executive Leadership.
• Software Security Code of Practice: Yes

Operational security

• Configuration and change management standard: Supplier-defined controls
• Configuration and change management approach: All configuration is managed in our source repository which gets reviewed and versioned prior to release
• Vulnerability management type: Supplier-defined controls
• Vulnerability management approach: Huma servers are patched monthly and we can deploy critical fixes within 12 hours after going through integration testing; ; We asses threats using various online resources
• Protective monitoring type: Supplier-defined controls
• Protective monitoring approach: Huma deploys various forms of integration tests which ensure the API is fit for purpose and can deploy fixes within 12 hours
• Incident management type: Supplier-defined controls
• Incident management approach: Huma follows a lightweight ITIL Incident management process
• Post-quantum cryptography secure: No

Secure development

• Approach to secure software development best practice: Independent review of processes (for example CESG CPA Build Standard, ISO/IEC 27034, ISO/IEC 27001 or CSA CCM v4.0)

Public sector networks

• Connection to public sector networks: No

Pricing

• Discount for educational organisations: No
• Free trial available: No

Discount percentage by annual call-off contract value (excluding VAT)

• Less than £250,000: 0%
• Between £250,000 and £500,000: 15%
• Between £500,001 and £1,000,000: 20%
• Between £1,000,001 and £2,500,000: 25%
• Between £2,500,001 and £5,000,000: 30%
• Over £5,000,001: 30%

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: Yes
• Who accredited the ISO/IEC 27001: BSI
• ISO/IEC 27001 accreditation date: Tuesday 25 November 2025
• What the ISO/IEC 27001 doesn’t cover: There are no exclusions in the scope of our ISMS
• ISO 28000:2022 certification: No
• ISO 9001 certification: No
• Quality management systems (QMS): No
• CSA STAR certification: No
• PCI certification: No
• Cyber essentials: Yes
• Please provide your Cyber Essentials Certificate Number: 675a6f9c-077b-430b-93e0-9ba0084dcaec
• Cyber essentials plus: Yes
• Please provide your Cyber Essentials Plus Certificate Number: Ee13ea4d-c95d-4488-82ad-053361c91272
• Other security certifications: No

Social value

• Section B - Commitment for Future: Delivery:

  • Mission: Build an NHS fit for the future: That is there when people need it; with fewer lives lost to the biggest killers; in a fairer Britain, where everyone lives well for longer.

    Policy Outcome 8: Increasing productivity through physical and mental wellbeing: In the supply chain and communities in the relevant area.

    • Understanding of issues relating to health and wellbeing, including physical and mental health, in the contract workforce
    • Understanding barriers to access to health and social care services or employment opportunities e.g. digital inclusion

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at aman.kundraw@huma.com. Tell them what format you need. It will help if you say what assistive technology you use.