Graphnet Health Limited

Graphnet Shared Care Record

Graphnet Shared Record Integration Exchange Platform provides real-time, secure, unified shared care records via Clinical & Patient Portals; system integration/interoperability; CareConnect FHIR standards support; data capture forms, care plans, End of Life including workflow; mobile solutions; Personal Health Records, Population Health, Analytics and innovative long term condition management solutions.

Features

• Real-time shared record solutions, used by 120,000+ care professionals
• Engaging and intuitive to use, with local configuration options
• Browser and mobile access, including support for offline working
• Seamless and secure navigation from local systems
• Pre-configured data feeds available from leading care systems
• Secure access, robust consent models and comprehensive audit trails
• Simple creation of rule-based forms, including assessments and plans
• Innovative use of wearable technologies/Apps/monitoring devices
• Patient Portal enabling citizen engagement in their care
• Proven business intelligence and reporting

Benefits

• Safer, more targeted, coordinated and timely care across settings
• Reductions in A&E attendances, unscheduled admissions and Length of Stay
• Cost savings for unwarranted activities, e.g., appointments, admissions and tests
• Improved communication and access to information for care professionals
• Reduced clinical risk e.g. through more efficient medicines reconciliation
• ‘Do once and share’: A reduction in duplication of effort
• A reduction in the need for, and use of, paper
• Improved management of complex and life-limiting conditions
• Enablement of patient participation and engagement in their care
• Better outcomes and improved quality of life

£120,000.00 a unit a year

• Free trial available

Service documents

• Pricing document

  PDF

• Skills Framework for the Information Age rate card

  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 salesandbids@graphnethealth.com. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 14

Service ID

329024527242106

Contact

Lisa Haslam
03330771988
salesandbids@graphnethealth.com

Service scope

• Software add-on or extension: No
• Cloud deployment model: Public cloud
• Service constraints: The service is based upon a very 'open' software stack and deployment model. Specifically though; - Browser access must be based on the approved list below - Mobile device access must be based on supported mobile operating systems (IOS, Android as primary platforms) - Mobile device management is not included - just the clinical applications - The local deployment model *may* by constrained by local IG and security policies regarding presentation of secure information via N3 or public networks.
• System requirements: Web: Microsoft Edge (Chromium); Google Chrome; Firefox

User support

• Email or online ticketing support: Email or online ticketing
• Support response times: Support is available on commencement of the project and we offer a variety of support packages. Each support package includes full details of call priority rankings and the corresponding response times agreed with the customer.
• User can manage status and priority of support tickets: Yes
• Online ticketing support accessibility: WCAG 2.1 AA or EN 301 549
• Phone support: Yes
• Phone support availability: 9 to 5 (UK time), Monday to Friday
• Web chat support: No
• Onsite support: Yes, at extra cost
• Support levels: Options to suit customer's need. Typically 9 - 5.30pm, 24/7 or other daily times possible subject to agreed SLA and commercials. Costings depend on the number of product and user licences required. Support engineers are supplied as part of the Service Desk provision as specified under the Service Level T&Cs for each customer.
• Support available to third parties: No

Onboarding and offboarding

• Getting started: When onboarding a user, Graphnet distinguishes between -; ; 1. The ‘Organisations’ providing Health and Social Care Services.; 2. The individual users employed by the Health and Social Care organisations.; 3. Patients using the Shared Record. ; ; Helping ‘Organisations’ involves;-; ; •Supporting organisations to provide an interface or data feed into the Shared Care Record (SCR). ; •Supporting ‘In Context Single Sign-On (SSO) from the organisation’s Electronic Patient Record (EPR) into the SCR.; •Information Governance – we have an information governance team who help the customer attain the necessary DPIAs and with any public consultation etc.; •Project Management – including the supply of fully populated Prince artefacts such as Project Initiation Documentation, project plans, risk logs etc. ; ; Supporting the individual users involves;-; ; •Training - Graphnet provides a tailored Train the Trainer programme and specialist training for end users (including both clinicians and specialist users such as system administrators). We have clinicians who support this.; •On line videos and eLearning packages.; •Drop in sessions and floorwalking support.; ; Supporting patients;-; ; In order to enthuse patient engagement and ensure patients are fully informed as to their rights around data sharing a series of patient inclusive events will be hosted to explain the SCR and the benefits available.
• Service documentation: Yes
• Documentation formats:
  • HTML
  • PDF
• End-of-contract data extraction: In each agreement Graphnet provides a Project Initiation Document (PID), a component of which is an agreed exit plan detailing how data would be provided back to the customer should the contract end. The documentation always includes details of Graphnet’s obligations to transfer data and will detail an agreed format.; ; The exit plan details the various aspects of the shared record, specifically.; ; Data Sharing: Data supplied from the provider organisations into the Shared Record.; Care Planning: Data entered directly into the Shared Record. ; Population Health: Data analysed including feeds direct to the Population Health platform.; Personal Health Record: Data supplied by the citizen. ; ; Users can then extract their data at the end of the contract through a process facilitated by Graphnet. This involves accessing a designated data extraction tool. Users can select the data they wish to export, specifying the format and destination for the extracted data. Graphnet also commit to provide additional support to ensure a smooth transition and compliance with data protection regulations. Clear communication and documentation will be provided to support users throughout the extraction process adhering to industry best practices and regulatory requirements.
• End-of-contract process: 6 to 12 months prior to the contract expiry, Graphnet will work with the customers senior leadership, finance and contract management teams to discuss what options are available. Options to discuss would include.; ; Non-Renewal: Clearly we hope that all contracts are renewed, but in some rare cases contracts do expire. In such cases where appropriate provisions are made such that any information entered into the Shared Record is returned in a format agreed with the customer and that here is a managed transition to a new system.; ; Renewal: Contract is renewed. Contracted components and/or participant organisations may alter. ; ; Hosting: In a number of cases Graphnet customers have opted to renew, but rather than remain on their own hosted instance they have opted to join a neighboring ICS’ Graphnet Shared Care Record instance. ; ; Should the contract actually no longer be required Graphnet will offer the provision of other reasonable termination assistance at the Authority’s request at the Supplier’s standard rates (e.g. to assist with data migration to the replacement contractor’s system). In addition, if necessary, a “read only licence” for historic data is offered.

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Firefox
  • Chrome
• Application to install: Yes
• Compatible operating systems:
  • Android
  • IOS
  • Linux or Unix
  • MacOS
  • Windows
• Designed for use on mobile devices: Yes
• Differences between the mobile and desktop service: The clinicians view of the Shared Record is via a Web Browser. The Patients view of the Shared Record is via the App. ; ; Subject to Role Based Access Controls (RBAC) a Clinician can see the whole or part of the Shared Record including Primary, Secondary, Social, Emergency and 3rd Sector data. Clinicians can create Care Plans which are shared to other NHS and provider organisations. ; ; App access is for the Patient to view information and is metered to ensure only Patient facing content is surfaced. Patients can add data to their record such as measurements (BP/weight etc.) or care preferences.
• Service interface: Yes
• User support accessibility: WCAG 2.1 AA or EN 301 549
• Description of service interface: Graphnet Shared Care Record has a clean, modern and intuitive user interface, designed in collaboration with a wide-range of our users. The system uses native operating systems, with screens designed for each device to achieve the best user experience. Secure access to information is rapid, with meaningful landing page views, pre-configured to meet the requirements of specific groups of users. Consistent screen layouts and unambiguous, familiar navigation tools simplify use and engage users. Landing page summary tiles display key information, with further details a click away.
• Accessibility standards: WCAG 2.1 AA or EN 301 549
• Accessibility testing: The solution has been designed taking into account the W3C Web Content Accessibility Guidelines and also to meet NHS CUI guidelines and general user experience (UX) standards such as material design and iOS human interface guidelines for mobile products. We undergo testing during the design process to support colour blindness, high contrast settings and use of iconography as well as colour in key areas of the application, and the system works with screen readers via the browser and is tested with leading screen readers. We offer an intuitive system. In particular: • Information tiles can be configured to present data in a variety of formats, font sizes etc. • Tiles have a simple and clear layout, with a consistent, easy to read text spacing, and colour contrast • Graphnet Shared Care Record uses a standard CUI interface, users can interact with both keyboard and mouse, navigation is consistent throughout. • Headings and labels describing content, simple and unambiguous • Our Personal Health Record has simplified views with information presented in a way consistent with non-clinical users. • Icons are intuitive, graphics are used where possible to simplify content meaning.
• API: Yes
• What users can and can't do using the API: Third parties can embed Graphnet Shared Care Record in their software in user and/or patient context sync. Conversely, Graphnet Shared Care Record can launch third party software in user and/or patient context. Third parties can surface data in Graphnet Shared Care Record using the Highway data adapter layer. Third parties can interact with Graphnet Shared Cared Record using a RESTful OpenAPI. The current API supports retrieval of patient lists, user authentication, patient consent, recording audit log entries, patient alerts, and patient record retrieval. Potential integrators with our API can access the API documentation free of charge and also access the API free of charge. Our API access falls within the identified usage model due to the nature of the data being accessed, there would need to be identified access by this consuming system i.e. identified usage of the API.
• API documentation: Yes
• API documentation formats: Open API (also known as Swagger)
• API sandbox or test environment: Yes
• Customisation available: Yes
• Description of customisation: Graphnet utilises Roles Based Access Controls (RBAC) to govern both the extent of the patient data user can see, but also the format of such data. Within each of the 5 RBAC levels, there are multiple different specific job roles which each can be configured to a specific view. This allows amongst other things for users to define which landing page is most pertinent to their role. ; ; RBAC allows for further levels of customisation. These are:; ; Functional access: what functions the user can access in the system.; Data access: which categories of the patient’s information the user can view (via hub tiles); ; Users access can be customised by utilising the “Patient Groups” functionality, allowing configuration of which organisation’s records users can access.; ; SysAdmin functionality from Graphnet Shared Care Record management module allows further means of tailoring the solution to meet your local preferences and configuration requirements; . ; • Choice of Data Integrations ; • Choice of Optional Modules ; • Choice of 3rd party system interoperability integrations.; ; There can also be local forms in a system such as assessments and care plans and these can be designed and customised locally.; ; Configuration would be implemented either by Graphnet or by customer authorised staff.

Scaling

• Independence of resources: We use Microsoft Azure as our platform which has limitless scaling capability and we configure our solutions to access this resource on demand. Availability / Capacity is a key consideration in our comprehensive approach which covers the hardware platform, software design and associated processes which cover Support and Maintenance, Business Continuity and Disaster Recovery. For a cloud hosted solution we provide an auto-scalable compute layer along with dedicated storage that has been sized appropriately for current and agreed future expansion requirements, with redundancy built in.

Analytics

• Service usage metrics: Yes
• Metrics types: Too many to cover in 100 words but Key Performance Indicators include;-; ; Usage; ; Unique users accessing the system –showing growth; Patient records accessed –showing growth; Number of tiles viewed –showing growth; Number of live data feeds ; Number of organisations accessing the system –showing growth; Number of API calls and response times –showing growth; Number of patients with care plans –showing growth; Care plans viewed –showing growth; Pop health reports run per month –showing growth; Number of Pop Health users –showing growth; Number of Remote Monitoring alerts ; ; Performance; ; Availability; Calls closed within and out of SLA; Screen/transaction response performance at Azure
• Reporting types:
  • Real-time dashboards
  • Regular reports
  • Reports on request

Resellers

• Supplier type: Not a reseller

Staff security

• Staff security clearance: Conforms to BS7858:2019
• Government security clearance: Up to Baseline Personnel Security Standard (BPSS)

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: Yes
• Datacentre security standards: Complies with a recognised standard (for example CSA CCM version 3.0)
• Penetration testing frequency: At least once a year
• Penetration testing approach: ‘IT Health Check’ performed by a CHECK service provider
• Protecting data at rest: Physical access control, complying with another standard
• Data sanitisation process: Yes
• Data sanitisation type:
  • Explicit overwriting of storage before reallocation
  • Deleted data can’t be directly accessed
• Equipment disposal approach: Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001

Data importing and exporting

• Data export approach: Users export their data through a user-friendly interface provided by Graphnet. Upon accessing the designated export feature, users can select the specific datasets they wish to export, choosing from various formats such as CSV, Excel, or PDF. The software offers options to customize the export settings, allowing users to tailor the output to their requirements. ; These extracts can be ad-hoc or scheduled. Bespoke extracts can also be setup using Microsoft Azure functionality into any supported system, and this service is further enhanced by our population health module that has riche features for data analysis and extraction.
• Data export formats: CSV
• Data import formats: CSV

Data-in-transit protection

• Data protection between buyer and supplier networks:
  • TLS (version 1.2 or above)
  • Other
• Other protection between networks: The service uses "allow lists" to accept connections from customer sites only.
• Data protection within supplier network:
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway

Availability and resilience

• Guaranteed availability: 99.9% excluding agreed maintenance windows out of hours.; ; Graphnet recognise that each solution provided are all critical solutions for the provision of safe and effective care. To that end Graphnet have multiple systems and procedures to ensure the solution(s) are available.; ; When deployment issues are logged they are immediately triaged to determine the extent to which the availability has been affected. The levels of severity and the associated resolution time are detailed below. ; ; P1 (Critical) Entire system unavailable/unusable. Resolution: within four hours ; P2 (High) Significant loss of the service but the impacted business function is not halted. Resolution: within eight Hours. ; P3 (Medium) Significant loss of the service but the impacted business function is not halted. Resolution: Resolved within one hundred and twenty Hours. ; P4 (Low) defined as Intermittent or partial faults resulting in loss of non-critical functionality where the software is still useable or there is a suitable alternative. Resolution: within twenty days ; ; The recovery time objective (RTO) is four hours and the recovery point objective (RPO) is 0.5 hours from the initial incident.
• Approach to resilience: Graphnet recognise the fact that sharing patient data from disparate Electronic Patient Records (EPRs) into a single patient record is now fundamentally relied upon for the provision of safe patient care. ; ; Graphnet's hosted Azure service is robust, secure and highly available hosting service. Microsoft Azure meets a broad set of international and industry-specific compliance standards, such as ISO 27001, HIPAA, FedRAMP, SOC 1 and SOC 2, as well as country-specific standards.; ; Graphnet maintain numerous Operational standards which are designed to further ensure the provision of a resilient service. These include:; ; Business Continuity Process: Mitigation against, fire, bombing, flooding and area wide outage etc. ; Quality & Security Processes: Ensure quality solutions are deployed safely and securely. ; Risk Assessment Processes: Continually reviewing recognised risks and mitigation processes. ; Access Controls: Ensure only approved staff have access to customer environments. ; Penetration Testing: To mitigate against malicious attacks. ; ; In the rare case of a system outage, Graphnet will declare a “Priority 1” incident whereby support services are as a norm extended to 24/7 with a target resolution of 4 hours.
• Outage reporting: All outages are recorded as part of the incident management process and should a problem be detected then the service desk will inform the customer by phone, email, and via the automated Jira alerting system that also gives a link to a dashboard. There are alerts configured for the application that trigger an automated ticket creation in Jira (service desk) and these are automatically sent to the customer. Thus the customers are alerted in 3 separate ways, telephone, email and Jira alert.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Username or password
• Access restrictions in management interfaces and support channels: All Graphnet Shared Care Record applications support in-built Role Based Access Control (RBAC) functionality which manages which functions a user has access to and which views of data they are able to see. The system includes 25 pre-configured roles, which align with the National Registration Authority Smart Card access roles and are grouped into 5 granular levels of system functionality. Graphnet Shared Care Record has a well-established concept of Patient Groups, which supports the ability to control which users, roles and groups of users have access to which groups of patients. System Administrators can also further refine permissions, as required.
• Access restriction testing frequency: At least once a year
• Management access authentication:
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Username or password

Audit information for users

• Access to user activity audit information: Users have access to real-time audit information
• How long user audit data is stored for: User-defined
• Access to supplier activity audit information: Users have access to real-time audit information
• How long supplier audit data is stored for: User-defined
• How long system logs are stored for: User-defined

Standards and certifications

• ISO/IEC 27001 certification: Yes
• Who accredited the ISO/IEC 27001: BSI ISO/IEC 27001:2013 - IS 614375
• ISO/IEC 27001 accreditation date: 15/07/2021
• What the ISO/IEC 27001 doesn’t cover: Our 27001 covers the full business operation without exclusions. Graphnet holds Certification number IS 614375 and operates Information Management Systems which comply with the requirements of ISO/IEC 27001:2013 for: All automated information systems under the direct control of Graphnet Health Limited. All employees and agents of Graphnet Health Limited. All employees and agents of other organisations who directly or indirectly make use of or support the use of information systems under the direct control of Graphnet Health Limited.
• ISO 28000:2007 certification: No
• CSA STAR certification: No
• PCI certification: No
• Cyber essentials: Yes
• Cyber essentials plus: Yes
• Other security certifications: Yes
• Any other security certifications:
  • IG toolkit (NHS Digital ODS code 8GX89).
  • ISO9001:2015, (FS614373);
  • Data Protection Act 1998 (DPA)
  • Level 3 compliance with NHS IGSoC

Security governance

• Named board-level person responsible for service security: Yes
• Security governance certified: Yes
• Security governance standards:
  • ISO/IEC 27001
  • Other
• Other security governance standards: We comply with NHS standards and best practice guidelines. Standards/accreditations include; •ISO27001:2013 •ISO9001:2015 •Data Security and Protection Toolkit •Cyber Essentials Plus Graphnet's ICO Registration is Z1045461. Other SCCIs/ISNs applicable to shared care record solutions, including DCB 0129 and DSCN14-2009.
• Information security policies and processes: We have ISO 27001 and Cyber Essentials Plus certification a range of policies to ensure we adhere to IG and Information Security arrangements. These include:; ; -Access Control ; -Information Governance ; -Project and Security Coding ; -Clean Screen and Clear Desk; -PID ; -Secure Software; -Solution Development Procedure; -Data Transfer (Encryption) ; -Secure Disposal; -Acceptable Use; -Network Control.; We have other specific guidance and polices available to provide assurance with our Data Processor and internal responsibilities.; ; We have a Governance Board which our CFO and SIRO, Director of Information Governance, Cyber and Compliance (Data Protection Officer), Information Security Manager, ISO Compliance Manager, all sit on. Through these key roles we ensure policies are reviewed and amended in light of any issues arising, audit reviews and process changes etc.; ; Policies are available to all staff via our employee hub system which requires staff to read all required policies. ; We incorporate the Crown Commercial Service’s Generic Standard GDPR clauses in all our contracts where we process personal data; we process in compliance with Article 32. Where services use the “cloud” this processing adheres to the fourteen National Cyber Security Centre cloud service security principles as applicable to UK OFFICIAL and the cloud host complies with ISO27018.

Operational security

• Configuration and change management standard: Supplier-defined controls
• Configuration and change management approach: To ensure the security and reliability of Graphnet's solutions, Graphnet follow a 5 phase configuration and change management process. ; •Development and QA and internal only proof of concept (POC) activities ; •Customer facing POC work.; •Build of all pre-production systems that may go on to hold customer or Graphnet data (deployment phase work); •BAU customer systems provided by Graphnet including all UAT, Sandpit, Training, Testing, Production or Live systems.; •All systems managed out or curtailed (including part of customer and data egress) where there is a requirement for secure planning for data clearance and reuse for other purposes or secure disposal.
• Vulnerability management type: Supplier-defined controls
• Vulnerability management approach: We use a combination of internal vulnerability scanners, system monitoring and industry sources to monitor for possible threats, applying patches within 14 days of their release. Additionally, we use NHS CARE-cert, US-Cert and industry publications to assess threats weekly and respond accordingly. Out Of Band patch releases are investigated and installed immediately if appropriate.
• Protective monitoring type: Supplier-defined controls
• Protective monitoring approach: The application undergoes continuous monitoring by a third-party Security Operation Centre (SOC) using Microsoft's Sentinel, Defender for Cloud, and Azure policies. Anomalies trigger alerts, including suspicious/malicious activities. Audit logs for Azure, web app, and SQL server activities are retained for one year, while application logs are kept indefinitely. The SOC responds to alerts within agreed SLAs, escalating critical issues to Graphnet staff. Operational support receives email alerts for audit findings, investigating them promptly. Proactive monitoring addresses environmental triggers like low disk space and high CPU usage. Anti-malware software ensures vigilance against malicious software or activities.
• Incident management type: Supplier-defined controls
• Incident management approach: Incidents are formally managed through Graphnet's Support Desk, using an ITIL focused call logging application to record, track and manage issues through all stages of the incident lifecycle. The Service Desk is also briefed on the service responses agreed through the customer contracts and use the incident logging application to monitor incidents’ service level response times. Problems are identified through incident reviews and managed through diagnosis, resolution and planned changes. These reviews of issues attempt to identify trends/recurrent issues; when identified, these undergo a root cause analysis and recommendations are made for changes to the product based on the analysis.

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 v3.0)

Public sector networks

• Connection to public sector networks: Yes
• Connected networks:
  • NHS Network (N3)
  • Health and Social Care Network (HSCN)

Social Value

• Social Value:

  Social Value

  • Fighting climate change
  • Covid-19 recovery
  • Tackling economic inequality
  • Equal opportunity
  • Wellbeing

  Fighting climate change

  Helping to tackle climate change is a key objective for Graphnet. Our deployments are delivered remotely and we are striving to achieve Net Zero Carbon emissions before 2050. ; ; Our procurement team prioritise suppliers with sustainable practices and environmentally friendly materials and equipment. ; ; We conduct an environmental assessment at the outset of any project, identifying specific targets and areas for improvement. ; ; Our Standards and Compliance team collaborate with stakeholders to integrate environmental considerations, such as energy-efficient technologies, waste reduction measures, and carbon mitigation strategies. ; ; Monitoring systems track progress and measure the effectiveness of our commitments. For example, assessing whether travel was necessary and conducted in the most environmentally friendly way practical. ; ; Audits provide an independent assessment to validate our environmental performance and following project completion, a comprehensive evaluation assesses the success of our initiatives, incorporating lessons learned for future projects. ; ; Measurement and reporting utilises quantitative and qualitative metrics, tracking energy consumption, waste diversion rates, carbon emissions, and employee engagement in sustainability initiatives. ; ; This approach ensures that our efforts go beyond our core service offering, integrating environmental best practices into each project to make substantial contributions to carbon reduction, sustainable waste management, and energy efficiency.; ; Our solutions are designed to help customers become paper-free or paper-lite. This enables customers to minimise the need for medical records libraries, reducing their need to store and dispose of paper-based records. Our mobile capability reduces carbon footprints by eliminating the need to travel, and our Docobo Remote Monitoring provides a trusted and highly effective remote patient monitoring solution that allows patients to be monitored and supported within their home. This reduces or even removes the need for patients to regularly visit the hospital for monitoring and removes the environmental impact of having to travel to and from the hospital.

  Covid-19 recovery

  Graphnet has a strong track record in supporting COVID-19 recovery. We delivered the original and successful NHS Vaccination system and supported 12 ICBS with their Covid monitoring work whilst the pandemic was in its first 18 months. We have continued to help these customers fight Covid in various ways including the following examples:; ; Graphnet’s Care@Home solutions enable individuals with COVID-19 to be remotely managed at home by Virtual Ward Care Teams.; ; Our Covid-19 dashboards enable community teams to view and be alerted to changes to patients’ status including Covid-19 Infection status and exposure. We support alerts for vulnerable or shielded patients and offer care planning functionality including a PRSB accredited RESPECT form.; ; Covid-19 highlighted the significant health inequalities that exist in maternity and neonatal care and Graphnet developed an interactive pregnancy dashboard. This has allowed customers to see a clear picture of women’s vaccination status, which stage at gestation they were in, ethnicity, any long-term conditions and socioeconomic factors. This enabled targeted intervention where it was needed most. It also enabled direct engagement with pregnant women shielding from Covid though a patient app.; ; During and since the pandemic there is concern that there has been an increase in the number of patients with COPD that have yet to be properly diagnosed. Our at scale identification of these patients, based on a set of clinical criteria, enables cohorts to be referred to an appropriate service, for example a Community COPD Hub for a differential diagnosis and where necessary onward referral for specialist MDT assessment, diagnostics and treatment. These people are vulnerable to Covid and this work is seen as early Covid protection by our customers who use this facility from us.; ; Graphnet’s population health, shared care records and remote monitoring have played a key role for our customers in fighting Covid.

  Tackling economic inequality

  Graphnet commit to 100% of staff being paid above the relevant Real Living Wage as specified by the Living Wage Foundation. This is monitored by Graphnet’s Programme Director for this framework and across the company and reported up to Graphnet’s Compliance Board. We also report to the customer programme board for each contract.; ; Our solutions target health inequalities and this can be seen on our web site. Examples of these are:; ; •Core 20 +5 directly supporting this NHS approach to health inequalities via a series of subject specific use cases including an overarching summary dashboard.; ; •Working with multiple customers Graphnet developed a fuel poverty dashboard linking UPRN data with Energy Performance Certificate information and drawing health and care information from all parts of the care system. For example, people with respiratory conditions who are also in lower quality housing are at risk of harm from fuel poverty. ; ; Our work aided customers to identify cohorts of citizens most at risk of health complications and hospital admissions to establish an evidence base for an initiative to prescribe heat for those most in need.; ; We also enable customers to drill further into the fuel poverty dashboard with a focus on those who have a 50% or higher risk of emergency admission in the next 12 months, are not in a care home, and are living in the most deprived and fuel poor geographies. This allows a future focus on citizens where it is possible to improve outcomes, and then learn from that to develop other pathways.; ; Another similar initiative is our work to identify multigenerational households where data shows there is a high prevalence of health inequalities. Customers have used this data to visit these houses and facilitate vaccine take up, better management of conditions such as diabetes, asthma, and CVD.

  Equal opportunity

  Our solutions support diverse workforces and help encourage more disabled people into work, especially through our ability to identify cohorts of people who need targeted assistance and then to provide a multi agency care co-ordination platform for them. ; ; As well as the benefits of our solutions for disabled people we seek to have 5% of full time equivalent disabled employees (FTE) hired or retained on the contract.; ; Our solutions are designed to be usable by people with disabilities. The accessibility of our web offering is underpinned by the VEUTIFY framework, the A11Y project and NHSE guidance. We also meet the Web Content Accessibility Guidelines (WCAG) for the public facing aspects of our application.; ; Staff and users with visual impairments can adjust font sizes and colours to help them read and process information. Controls are designed to support users with colour-blindness. The solution can be used with screen readers and we work to optimise this.; ; For staff with physical disabilities, working from a desktop may not be appropriate. So, we have designed our solutions to work from handheld devices or mobiles. This means staff choose the best device for them rather than trying to accommodate a device that doesn’t take their disability into account. ; ; Our Docobo Remote Monitoring solution provides the means for disabled people to be monitored and supported in their own home. Expectant mothers with a disability can benefit from community midwifery care at home because of our My Maternity App. In both examples, our solutions empower disabled people rather than expect them to accommodate the traditional care model of visiting a physical location – which in itself can be challenging.; ; Within the company, Employees with a disability can be home-based and special arrangements are made to include them in physical events such as meetings or staff socials.

  Wellbeing

  Graphnet work with customers to co-design solutions to support wellbeing initiatives. For example: ; •Improving health outcomes: Ensuring professionals have the information needed. Feedback from a diabetes consultant who helped design our shared care record -“Access to the Care Record is helping me ensure that diabetes patients are on the correct medical regime for them, which is vitally important for this group of patients whose wellbeing depends on their medication”.; ; •Achieving better outcomes: Frimley ICB worked in close partnership with Graphnet to develop analytics that a) identified cohorts of patients who would benefit from remote monitoring, and b) monitored their results. This evidenced a 40% reduction in hospital admissions for the treated cohort and a 30% reduction in GP face to face consultations. ; ; •Reducing inequalities: Our Fuel Poverty and Health Inequalities with Cheshire and Mersey ICB are two examples of co-design that have supported communities. ; ; Dianne Green COPD service manager -; ; “Through the fuel poverty dashboard, we’ve been able to target patients in a completely different way. At the click of a button we now have all the information that we need. We can see whether they’ve been immunized, whether they’re still smokers, whether they’re on the best treatment, and what quintile of poverty they are living in. That has helped us to prioritise people that are most in need.” ; ; “It is hard not to cry when speaking about the importance of this work. It is truly proactive.”; ; “I’ve been a nurse since 1986, and we’ve never transformed lives like this.”; ; •The Frailty module we built with customers analyses the over 65s to identify cohorts for early intervention, they are then given care plans.; ; Supporting independent living - Our remote monitoring solutions are currently helping 40,000 people to stay connected to their healthcare professionals and live independently in their own homes.

Pricing

• Price: £120,000.00 a unit a year
• Discount for educational organisations: No
• Free trial available: Yes
• Description of free trial: This would be a test system with dummy data in it. We would allow access to this for the purposes of trialling the product.
• Link to free trial: We don't have a generic link as each customer's requirements are slightly different. We make test systems available on request with them configured as per the customer's requirements.

Service documents

• Pricing document

  PDF

• Skills Framework for the Information Age rate card

  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 salesandbids@graphnethealth.com. Tell them what format you need. It will help if you say what assistive technology you use.