Call +44 800 9755 164

Public tenders for consultant in Salford United Kingdom

Find all Consulting tenders in the world.
Finding business opportunities has never been easier.

Results for consulting. Make a new search!

Provision of a Consultant and Contractor Framework.

Salford Royal NHS Foundation Trust | Published February 12, 2016  -  Deadline March 14, 2016
cpvs
71500000, 09000000, 09300000, 09330000, 24000000, 24100000, 24110000, 24900000, 31000000, 31100000, 31200000, 31300000, 31400000, 31500000, 31600000, 31700000, 32000000, 32200000, 32300000, 32400000, 32500000, 35000000, 35100000, 35110000, 35120000, 41000000, 41100000, 44000000, 44100000, 44200000, 44300000, 44400000, 44500000, 44600000, 44800000, 44900000, 45000000, 45100000, 45200000, 45300000, 45400000, 45500000, 51000000, 51100000, 51200000, 51300000, 51400000, 51500000, 51600000, 51700000, 51800000, 71000000, 71200000, 71300000, 71400000, 71600000, 45000000, 09000000, 09300000, 09330000, 24000000, 24100000, 24110000, 24900000, 31000000, 31100000, 31200000, 31300000, 31400000, 31500000, 31600000, 31700000, 32000000, 32200000, 32300000, 32400000, 32500000, 35000000, 35100000, 35110000, 35120000, 41000000, 41100000, 44000000, 44100000, 44200000, 44300000, 44400000, 44500000, 44600000, 44800000, 44900000, 45100000, 45200000, 45300000, 45400000, 45500000, 51000000, 51100000, 51200000, 51300000, 51400000, 51500000, 51600000, 51700000, 51800000, 71000000, 71200000, 71300000, 71400000, 71500000, 71600000, 71300000, 09000000, 09300000, 09330000, 24000000, 24100000, 24110000, 24900000, 31000000, 31100000, 31200000, 31300000, 31400000, 31500000, 31600000, 31700000, 32000000, 32200000, 32300000, 32400000, 32500000, 35000000, 35100000, 35110000, 35120000, 41000000, 41100000, 44000000, 44100000, 44200000, 44300000, 44400000, 44500000, 44600000, 44800000, 44900000, 45000000, 45100000, 45200000, 45300000, 45400000, 45500000, 51000000, 51100000, 51200000, 51300000, 51400000, 51500000, 51600000, 51700000, 51800000, 71000000, 71200000, 71400000, 71500000, 71600000, 71200000, 09000000, 09300000, 09330000, 24000000, 24100000, 24110000, 24900000, 31000000, 31100000, 31200000, 31300000, 31400000, 31500000, 31600000, 31700000, 32000000, 32200000, 32300000, 32400000, 32500000, 35000000, 35100000, 35110000, 35120000, 41000000, 41100000, 44000000, 44100000, 44200000, 44300000, 44400000, 44500000, 44600000, 44800000, 44900000, 45000000, 45100000, 45200000, 45300000, 45400000, 45500000, 51000000, 51100000, 51200000, 51300000, 51400000, 51500000, 51600000, 51700000, 51800000, 71000000, 71300000, 71400000, 71500000, 71600000

Salford Royal NHS Foundation Trust are issuing this notice to source expressions

of interest for the provision of a Consultant and Contractor Framework consisting

of 3 lots. Lot 1 — Main Contractor. Lot 2 — M&E Consultant. Lot 3 — Architect.

RA191806 - NHS Consultancy

 | Published February 15, 2016  -  Deadline February 26, 2016
cpvs
79000000

This invitation to Quote is subject to NHS England Terms & Conditions:- http://www.commissioningboard.nhs.uk/files/2012/10/purch-servs.pdf - Submissions must be sent via the portal by Friday 26th February 12pm. Clarification questions must be submitted by Monday 22nd February, Responses will be sent back by 24th February. Successful suppliers invited to the next stage of the process will be notified by Wednesday 2nd March 5pm. Interviews will take place on 4th March in London, details will be sent closer to the date to successful suppliers. - To access this competition: login to https://suppliers.multiquote.com and view the opportunity RA191806. Not registered on MultiQuote - visit https://suppliers.multiquote.com then register and quote RA191806 as the reason for registration. Any queries please contact MultiQuote on 0151 482 9230.

Financial consultancy, financial transaction processing and clearing-house services

HMRC | Published February 18, 2017
Winner
KPMG LLP
cpvs
66170000

API Banking Integration Consultancy.

Architectural, construction, engineering and inspection services

NHS Shared Business Services Ltd (NHS SBS) | Published May 4, 2017
cpvs
71000000

To provide Estate, Facilities and Capital teams a compliant route to market for the provision of Consultancy Services from a wide range of specialisms, utilising both SME and national providers, to deliver either a single service or provide a one-stop shop for a range of services. The framework delivers a range of pricing options for both Traditional and Design and Build Options, and New and Refurbished projects.

Providing design options based upon initial brief including outline design schematics, staging and programme advice, buildability and maintenance issues

— Advising on and where required providing such site investigation, topographical surveys,

testing and the like as is required to progress the design;

— Providing advice and inputting into value engineering studies, optioneering studies and/or life cycle cost studies including where required, attendance at Workshops;

— Providing advice and inputting into BREEAM, AEDET and other such reviews including

where required, attendance at Workshops;

— Advising on and where requested appointing such other specialist contractors/consultants required to support the design process;

— Consulting as required with local and/or statutory authorities;

— Working with the Employer to review the Capital Plan and provide a clear Project Brief for and Project Management Plan for the delivery of the Work Package(s);

— Developing in conjunction with the Employer and/or implement a procurement strategy to engage the required works, services and/or

goods for each Work Package;

— Developing in conjunction with the Employer a Programme for the

delivery of the Work Package(s);

— Undertaking Risk and Value Engineering workshops at appropriate times

during the life cycle of the Work Package(s).

The Services comprise design, technical consultancy and engineering including but are not limited to:

— Providing of structural options based upon initial brief including outline design schematics, staging and programme advice, buildability and maintenance issues;

— Advising on and where required providing such site investigation,

topographical surveys, testing and the like as is required to progress the design;

— Providing advice and input into value engineering studies, optioneering

studies and/or life cycle cost studies including where required, attendance

at Workshops;

— Providing advice and inputting into BREEAM, AEDET and other such

Reviews where required, attendance at Workshops.

The Services comprise the provision of cost and contract advice including but not limited to:

— Preparing of cost estimates to support the Employer's Capital Planning and Business Planning activities.

— Providing cost advice to support value engineering studies, BREEAM studies, AEDET studies, life cycle cost studies, optioneering and risk management including where required attendance at Workshops

— Undertaking value engineering and risk management activities including where required, convening and facilitating Workshops and preparing all

associated pre-workshop and post-workshop documentation

— Preparing and maintaining through all stages/phases of the Work Package

cost plans for all elements of the Work Package

— Providing contractual advice in relation to the Employer's procurement

strategy and where requested, preparing the same

— Assist in preparing and/or prepare OJEU notices.

The Services comprise design, technical consultancy and engineering including but not limited to:

— Providing design options based upon initial brief including outline design schematics, staging and programme advice, buildability and maintenance issues;

— Advising on and where required providing such site investigation, topographical surveys, testing and the like as is required to progress the design;

— Providing advice and inputting into value engineering studies, optioneering studies and/or life cycle cost studies including where required, attendance at Workshops;

— Providing advice and inputting into BREEAM, AEDET and other such reviews including where required, attendance at Workshops;

— Advising on and where requested appointing such other specialist contractors/consultants required to support the design process;

— Consulting as required with local and/or statutory authorities.

The Services comprise the provision of advice and support to the Employer in respect of the CDM Regulations including but not limited to:

— Advising the Employer on their obligations as Client under the CDM Regulations

— Advising on the methods to be adopted to check the competence and adequacy of resources of proposed Designers and the proposed Principal Supplier

— Reviewing with the Employer and/or their appointed representative, the competence and

— adequacy of resources of all proposed Designers and the proposed Principal Supplier for the Work Package

— Advising on the service related information concerning the Site, which the Employer and/or their appointed representative should make available to both the Supplier and to the Design team and the Principal Supplier.

To provide Building Surveying services in accordance with RICS professional standards and competencies. The client Trust will at mini-competition stage provide specific instructions in respect of the project(s) for which offers are sought.

— Undertake general building condition surveys and prepare reports

— Undertake structural surveys and prepare specifications

— Provide Whole Life Cost considerations

— Preparation of works packages suitable to tender

— Monitoring of construction works

— Advising on the preservation/conservation of historic buildings

— Provide assistance with planning applications and advising on property legislation and building regulations

— Providing assistance with design and regulations on access to the needs of people with disabilities

These services to include any other services as undertaken by a consultant within this role.

The production of Affordable and Sustainable buildings, upgrades and

Refurbishment projects

— Preparation of Schedules

— General Building Condition Surveys

— Structural surveys preparation of specifications and design solutions taking into

account Legal and legislative requirements

— Provide professional design and installation/ maintenance/whole life cost advice on the following services:-

— Energy Supply — Gas, Electricity and renewable sources

— Heating and Ventilating

— Water, drainage and plumbing

— Day-lighting and artificial lighting

— Escalators and lifts

— Ventilation and refrigeration

— Harnessing solar, wind and biomass energy

— Communications, telephones and IT networks

— Security and alarm systems

— Fire detection and protection

— Air conditioning and refrigeration.

To provide Health and Safety Consultancy Services to assist NHS customers to manage and comply with UK safety regulations, including support, advice, training and consultancy including Risk Assessments; Accident Investigations; Fire Training; COSH; Health and Safety Plans; Employee Handbooks; Asbestos Awareness; Legal Advice; CRB Clearance: ISA Checks;

On-site training and Expert Witness Representation.

To provide Environmental services advice in accordance with professional standards and competencies. The client trust will at mini competition stage provide specific instructions In respect of the project(s) for which offers are being sought Provide guidance on Carbon Reduction

Sustainability Innovation: Buildings, communities, Environmental management services

Provide advice on best practice and meeting statutory requirements

Undertake feasibility studies, and Regulatory Assessments of contaminated land, Waste management, and remediation management and reclamation, Ecology, Archaeology, Sustainability, Renewable Energies, BREEAM, CEEQUAL, Environmental Technologies and Services ,Pollution Control, Flooding, Invasive Weeds, Noise and Air Quality, Rural and Coastal Issues ,Health, Design, Regeneration and Skills, Whole Life Costings.

Accessible Environment

BIM Management

BREEAM

Estates Advice

Facility Management

Health & Medical Planners

Procurement Advice

Landscape Architecture Acoustics

ICT

Logistics

One-Stop Shop

Town Planning

Transport

Fire.

To develop and implement the Datawell Platform.

Salford Royal NHS Foundation Trust | Published January 26, 2016
Winner
Lumira Holdings Limited
cpvs
72000000

Datawell is an innovative informatics platform that enables health data to be shared and provides Greater Manchester, East Cheshire and East Lancashire with a development resource that accelerates the delivery of improvements in health outcomes and costs-effectiveness. Datawell consists of 2 complementary programmes: The Datawell Exchange and the Datawell Accelerator; a) The Datawell Exchange will enable efficient sharing of data and provide the appropriate safeguards for privacy, in order to provide a platform which member organisations, including clinicians and researchers, will be able to build on to create innovative solutions for care. This will be the core technological environment that will need to be developed to make the existing ground-breaking innovation routine and simple for all members; b) The Datawell. Accelerator will be a collection of project-driven partnerships combining resource from NHS members, our Universities and industry to create an affordable, enhanced capability to run evaluations and pilots of new ideas. These partnerships will build on existing locality plans and support better knowledge sharing between members.

The minimum requirements of the solution are set out below. Bidders must be able to demonstrate their ability to meet all of these minimum requirements.

Datawell Node:

Storage of structured and unstructured data.

— The system must allow the storage of structured and unstructured data, including free text, coded data and semi-structured information;

— Data must be searchable by patient or data types. For example the results returned may be for a selected patient, or select data for all patients matching set criteria such as diagnosis or pathology result;

— The application must be able to use NHS numbers to identify patients;

— Each Dataset Definition and Dataset must have a unique reference identifier within the Exchange. All individual data items (Attributes) within a Dataset Definition must be associated with a corresponding entry from the Universal Data Dictionary. The same Attribute may be referenced in any number of Dataset Definitions.

— Data will include health data sources and ETL processes must link to existing systems as data sources with near live updates of information.

Metadata catalogue of available data and metadata/entity management:

— A catalogue of available data and data types must be available and searchable to support the generation of new Dataset definitions, and to support the ability to compare related or similar data.

Universal data dictionary — OpenEHR, HL7, ICD9, ICD10, Read, SnomedCT:

— A standard semantic data dictionary must be defined to enable disparately sourced data to be linkable across the Exchange regardless of its originating representation. For example, a data source may record a patient's blood pressure in a database table with a column named ‘BP’, whilst another data source may record the same information in a database table column named ‘BloodPressure’. Critically, we must be able to interpret both these attributes as equivalent, by mapping both such attributes onto the same semantic term ‘Measurement. BloodPressure’, and also ensure that the value representation is consistent — 1 source system might record blood pressure as mm of Hg (millimetres of Mercury displacement, UK) whilst another might use kPa (kilopascals, USA).

— The Universal Data Dictionary forms the domain of attributes, known as Archetypes, that can be selected from to form a Dataset Definition. The Universal Data Dictionary will evolve over time with the accrual of new Archetype definitions. Such changes must be carefully managed and a scheme implemented to enable Nodes to maintain synchronised versions of the Universal Data Dictionary.

— Healthcare information such as medications, procedures, diagnoses, lab tests, etc. are normally encoded with reference to a well-defined vocabulary. Examples of such coding schemes currently in use include SNOMED-CT, ICD-10, LOINC. The Universal Data Dictionary must make reference to such vocabularies as part of the semantic definition for an Archetype.

— Medical ontologies are versioned and updated on a regular basis. Exchange Nodes must have a mechanism that enables them to accrue such updates over time and for this to be synchronised across all Nodes in the Exchange.

Security and access:

— Exchange nodes must maintain data query and transfer logs for reporting on information flow to enable governance audit, systems performance and security monitoring.

— The system must enforce the principle of ‘least permission respected’ when assessing whether a use or system has access to an individual data item, taking into account user authentication and authorisation against roles permissions and data sharing agreements. ‘Break the Glass’ scenarios may override this but must be appropriate alerted and audited.

Administration Portal:

— Each Exchange Node must have its own secure administration portal to enable all aspects of the system to be controlled and maintained by local users (Administrators) with the specific authority to do so.

— The portal must provide all aspects of system monitoring for performance and user behaviour tracking, and for configuration and management of the various components and associated metadata that constitute the Node.

— All changes effected by Administrators to the system configuration must be logged, and made visible within the portal and available for separate audit report.

— The web user interface must include meaningful visual dashboard presentation to show the current state of the system, to generate alerts where parts of the system may not be functioning correctly, and to highlight where end user or external system behaviour is out with normal operating parameters.

— All data transfer activity that passes through the Exchange Node must be logged and made accessible within the Administration portal, providing tabular presentation and visual graphs over time and enabling instantaneous reporting through dynamic selection and aggregation on the various dimensions of Requests/Responses such as Requester, Responder, EndUser, Query, Status, etc.

Basic analytics capability for reporting of data:

— The node must have a core set of web-based applications that are available ‘out of the box’ in order to demonstrate immediate value and capability for the node.

— 1 application must have the ability to view all data, or a defined type of data, about a single patient. For example, to be able to show a complete medical history, or a list of pathology results.

Exchange Node Clocks:

— A common time reference must be used by all Nodes throughout the Exchange, namely coordinated Universal Time (UTC) resolvable to the calendar date (century, year, month, day) and time of day (to the nearest millisecond). Although leap days/seconds must be incorporated, no adjustment for daylight savings is required — UTC is equivalent to Greenwich Mean Time (GMT).

— Individual Node clocks must be kept in sync to the nearest millisecond.

Datawell Exchange;

Managed sharing.

— The Exchange must directly implement managed sharing, connecting each participating organisation's Exchange Node and filtering data transfers to enforce the rules defined through the combination of data sharing agreements from organisational through to an individual's permission settings.

— The Exchange must immediately honour any changes made to the deployed sharing agreements, whether to restrict or to expand.

— The Exchange must also provide the facility to transform data before delivery, specifically to apply de-identification according to the rules defined in the Data Sharing Agreement currently in effect between the sender and receiver.

Governance audit:

— Exchange nodes must maintain data query and transfer logs for reporting on information flow to enable governance audit, systems performance and security monitoring.

Flexible data exchange:

— The Exchange must support different modes of transfer including pull requests, for small scale on demand distributed queries for individual data item sets (e.g. for servicing a patient point-of-care application); push requests, for large scale scheduled bulk dataset delivery (e.g. for servicing a secondary population research analysis).

— The Exchange must support both standard core Dataset Definitions to drive a minimum level of application functionality.

Standards conforming:

— The Exchange must implement a range of healthcare interoperability standards including but not limited to NHS Information Toolkit (ITK), HL7-V2, HL7-FHIR, ITU- T-H.860, IHE XDS, OpenEHR as required to support a range of downstream applications.

Security and Audit:

— All data transfers between nodes must be encrypted ‘in-flight’. Transfers between specific pairs of Exchange Nodes should be encrypted with different keys, such that compromise or publication of a key pair does not expose data exchanged between other pairs of Nodes. In case of such a security breach, it must be possible to invoke an immediate change of encryption keys used throughout the Exchange.

— The data transfer logs must record sufficient information to enable audit of who/when/what for each transfer event, but also for unusual patterns of access to be identified and flagged for further investigation. FairWarning is an example of a commercial product, currently used by the NHS, for analysing data access logs for potentially inappropriate activity.

— An Exchange Administrator must have the facility to immediately disable responses being generated to queries originating from a specific End User across the entire Exchange.

End User Registry:

— An End User Register must be implemented across all Nodes in the Exchange to ensure a consistent view of the same user is maintained regardless which organisations they may be employed by over time, or their level of site to site mobility that may be a characteristic of their job. The same single unique identifier must apply to the same user irrespective of their original registration Node. This requires Exchange Nodes to participate in shared End User Register updates and to implement a scheme for resolving potential duality of user identity.

— The Administration and Audit Portal must support the creation, update, suspension and deletion of an End User, recording a range of descriptive and contact information for each person.

Repeatability:

— Whilst the Transfer Log does not make record of the Response Datasets generated, it must capture sufficient information to enable the Request to be rerun under the same system-wide state in order to generate the same Response Datasets, and in particular the same cohorts of individuals.

Break-The-Glass:

— Certain AccessRoles, e.g. a consultant in A&E, must be able to be given the special permission ‘Break-The- Glass’. This follows the standard procedure within the medical profession, whereby an EndUser with this permission can access an individual's data after interacting with a separate challenge and response mechanism within an EHR application for example. Break-The-Glass events are typically separately monitored and audited with professionals having to justify their use. The Exchange must be able to support this scenario.

Datawell Exchange API:

— A set of open Datawell APIs must be defined for specifying on-demand broadcast data transfer queries, scheduled transfer queries, audit queries, data sharing agreements and system management such as registration/withdrawal of Nodes from the Exchange network.

— The Datawell APIs must include a separately secured Administration API and Data Transfer API. Only the basic requirements for these APIs are described in the following sections, additional capabilities remain to be defined.

Data:

— In order to support the successful use of the Datawell Exchange bidders must have or develop a common information architecture that defines the format and definition for health information to be shared. This definition will constitute the minimum core dataset for the exchange, and provide the core structures that will need to be mapped to individual systems within Exchange member environments. The benefits of this common data architecture must include:

— Identify and source the data needed to share between organisations and to support the development of new applications;

— Make it possible to uniquely define a new data element within a minimum data set;

— Establish the derivation of a given data element from its root sources;

— Build common business rules about data and have them apply across the conurbation.

— The key purpose in developing the Data Architecture must be to support the software applications that will use and access shared data across the Exchange. It will also facilitate the ability to link datasets between different sources and third party datasets.

— The model must balance this flexibility against the need to provide a concrete software implementation that can be assured to meet external data standards and be optimised to provide rapid, appropriate and secure access to data.

— A recommended data model must be flexible enough to accommodate multiple types of use, including export for inclusion in other clinical record systems, point of care use, research, clinical audit, business intelligence and quality and safety monitoring.

— The node solution must provide a basic dataset definition in-line with national and international standards such that access to the data by the data owners is always possible. There are a number of standards for the storage and interchange of health data for use by electronic health record systems. Examples of Reference Models include HL7, NHS Interoperability Toolkit (based on HL7), XDS, EN13606 European Standard for Health Informatics and openEHR.

— The data owner must always be able to extract or completely remove their own data.

— The data owner must always be able to add additional datasets based on own data sources and extend the nodes data catalogue as required. Data that can be included in the node will cover: PAS, pathology, medications and prescribing, health resource utilisation, critical care, speciality data, outpatient information, emergency admissions (A&E), community and intermediate care, mental health, social care, GP and other primary care.

— It must not be possible for any system to access data, either locally or via the Exchange, without the appropriate information sharing agreements permitting use. Patient consent models must also be respected.

Analytics and Business Development:

A core objective for Datawell is to support the innovative use of data to improve outcomes for patients and the efficiencies of the whole GM health and social care system. Therefore there is a requirement for provision of business analysis and data analysis support of the program, as well as provision of specific support to members during roll-out to help identify value and project opportunities created by the Datawell platform.

Specific tasks must include:

— Map current organisational data flows, both internal and external, that are relevant to Datawell projects. At a minimum this must include hospital episode statistics, pathology, prescribing, admissions, diagnosis and other patient episode data.

— To identify metadata definitions and potential quality issues to create dataset definitions and metadata that will help Datawell users in accessing and using the data. Create a metadata catalogue that must define data content, including coding schemes.

— Establish working groups internal to members in order to develop informed knowledge about the use and purpose of the data, identify requirements for data sharing and requirements that may be relevant to future Accelerator projects.

— Identify and document local value propositions, within the framework established in the Business Case, and develop bespoke business cases for Accelerator projects that will support the development of Datawell and demonstrate its effectiveness in improving patient safety and outcomes, reducing costs and creating efficiencies.

— To identify and map existing applications and APIs within member organisations.

— Support the development of data models for use in the Nodes and Exchange.

— Maintain the programme governance framework, including reporting to Board meetings, setting up and maintaining the Reference group and maintaining Public Patient Involvement plans.

— Develop an information governance framework and common information sharing agreements for use in the Datawell Exchange. Where possible existing best practice should be maintained.

— Create a catalogue of existing data sharing agreements and establish a plan where migration to a new data sharing agreement is required.

— Ensure that the design of the Datawell programme complies with essential legal and ethical frameworks and supports national and local initiatives for data sharing. Links with appropriate national and local groups, including HSCIC, the GM Informatics Board, local Health and Wellbeing Board, Directors of Public Health, and others, should be maintained and reported. Datawell must also fit with Local Authority plans, directed by AGMA and the future development of Devolution in Greater Manchester.

— Continue the promotion of the objectives of the Datawell programme through member engagement, local workshop and conference activity.

— Develop a Datawell Business Model which will create a sustainability plan for beyond the initial 3 year funding plan.

This service is being potentially being procured on behalf of:

Bolton Clinical Commissioning Group, Bury Clinical Commissioning Group, Central Manchester Clinical Commissioning Group, Eastern Cheshire Clinical Commissioning Group, Heywood Middleton and Rochdale Clinical Commissioning Group, North Manchester Clinical Commissioning Group, Oldham Clinical Commissioning Group, Salford Clinical Commissioning Group, South Manchester Clinical Commissioning Group, Stockport Clinical Commissioning Group, Tameside and Glossop Clinical Commissioning Group, Trafford Clinical Commissioning Group, Wigan Borough Clinical Commissioning Group.

Bridgewater Community Healthcare NHS Trust, Central Manchester University Hospital NHS Foundation Trust, East Cheshire NHS Trust, East Lancashire Hospitals NHS Trust, Greater Manchester West Mental Health NHS Foundation Trust, North West Ambulance Service NHS Trust, Pennine Acute Hospitals NHS Trust, Pennine Care NHS Foundation Trust, Royal Bolton Hospitals NHS Foundation Trust, Salford Royal NHS Foundation Trust, Stockport NHS Foundation Trust, Tameside Hospital NHS Foundation Trust, The Christie NHS Foundation Trust, Wrightington, Wigan and Leigh NHS Foundation Trust, University Hospital of South Manchester FT.

Blackburn with Darwen Borough Council, Bolton Council, Bury Council, Cheshire East Council, Manchester City Council, Oldham Council, Rochdale Metropolitan Borough Council, Salford City Council, Stockport Metropolitan Borough Council, Tameside Metropolitan Borough Council, Trafford Council, Wigan Council.

The duration of the contract is 30 months with the option to extend for an additional 36 months and then a further 24 months if required. The innovation partnership procedure is being adopted. It is intended that 3 economic operators will be taken forward following PQQ.

To develop and implement the Datawell Platform.

Salford Royal NHS Foundation Trust | Published June 6, 2015  -  Deadline July 6, 2015
cpvs
72000000

Datawell is an innovative informatics platform that enables health data to be shared and provides Greater Manchester, East Cheshire and East Lancashire with a development resource that accelerates the delivery of improvements in health outcomes and costs effectiveness. Datawell consists of two complementary programmes: The Datawell Exchange and the Datawell Accelerator. a) The Datawell Exchange will enable efficient sharing of data and provide the appropriate safeguards for privacy, in order to provide a platform which member organisations, including clinicians and researchers, will be able to build on to create innovative solutions for care. This will be the core technological environment that will need to be developed to make the existing ground-breaking innovation routine and simple for all members. b) The Datawell Accelerator will be a collection of project-driven partnerships combining resource from NHS members, our Universities and industry to create an affordable, enhanced capability to run evaluations and pilots of new ideas. These partnerships will build on existing locality plans and support better knowledge sharing between members. The minimum requirements of the solution are set out below. Bidders must be able to demonstrate their ability to meet all of these minimum requirements. Datawell Node Storage of structured and unstructured data. — The system must allow the storage of structured and unstructured data, including free text, coded data and semi-structured information — Data must be searchable by patient or data types. For example the results returned may be for a selected patient, or select data for all patients matching set criteria such as diagnosis or pathology result. — The application must be able to use NHS numbers to identify patients. — Each Dataset Definition and Dataset must have a unique reference identifier within the Exchange. All individual data items (Attributes) within a Dataset Definition must be associated with a corresponding entry from the Universal Data Dictionary. The same Attribute may be referenced in any number of Dataset Definitions. — Data will include health data sources and ETL processes must link to existing systems as data sources with near live updates of information. Metadata catalogue of available data and metadata/entity management — A catalogue of available data and data types must be available and searchable to support the generation of new Dataset definitions, and to support the ability to compare related or similar data. Universal data dictionary — OpenEHR, HL7, ICD9, ICD10, Read, SnomedCT — A standard semantic data dictionary must be defined to enable disparately sourced data to be linkable across the Exchange regardless of its originating representation. For example, a data source may record a patient's blood pressure in a database table with a column named ‘BP', whilst another data source may record the same information in a database table column named ‘BloodPressure'. Critically, we must be able to interpret both these attributes as equivalent, by mapping both such attributes onto the same semantic term ‘Measurement. BloodPressure‘, and also ensure that the value representation is consistent — one source system might record blood pressure as mmHg (millimetres of Mercury displacement, UK) whilst another might use kPa (kilopascals, USA). — The Universal Data Dictionary forms the domain of attributes, known as Archetypes, that can be selected from to form a Dataset Definition. The Universal Data Dictionary will evolve over time with the accrual of new Archetype definitions. Such changes must be carefully managed and a scheme implemented to enable Nodes to maintain synchronised versions of the Universal Data Dictionary. — Healthcare information such as medications, procedures, diagnoses, lab tests etc, are normally encoded with reference to a well-defined vocabulary. Examples of such coding schemes currently in use include SNOMED-CT, ICD-10, LOINC. The Universal Data Dictionary must make reference to such vocabularies as part of the semantic definition for an Archetype. — Medical ontologies are versioned and updated on a regular basis. Exchange Nodes must have a mechanism that enables them to accrue such updates over time, and for this to be synchronised across all Nodes in the Exchange. Security and access . — Exchange nodes must maintain data query and transfer logs for reporting on information flow to enable governance audit, systems performance and security monitoring. — The system must enforce the principle of “least permission respected” when assessing whether a use or system has access to an individual data item, taking into account user authentication and authorisation against roles permissions and data sharing agreements. “Break the Glass” scenarios may override this but must be appropriate alerted and audited. Adminstration Portal — Each Exchange Node must have its own secure administration portal to enable all aspects of the system to be controlled and maintained by local users (Administrators) with the specific authority to do so. — The portal must provide all aspects of system monitoring for performance and user behaviour tracking, and for configuration and management of the various components and associated metadata that constitute the Node. — All changes effected by Administrators to the system configuration must be logged, and made visible within the portal and available for separate audit report. — The web user interface must include meaningful visual dashboard presentation to show the current state of the system, to generate alerts where parts of the system may not be functioning correctly, and to highlight where End User or external system behaviour is outwith normal operating parameters. — All data transfer activity that passes through the Exchange Node must be logged and made accessible within the Administration portal, providing tabular presentation and visual graphs over time and enabling instantaneous reporting through dynamic selection and aggregation on the various dimensions of Requests/Responses such as Requester, Responder, EndUser, Query, Status etc. Basic analytics capability for reporting of data — The node must have a core set of web-based applications that are available “out of the box” in order to demonstrate immediate value and capability for the node. — One application must have the ability to view all data, or a defined type of data, about a single patient. For example, to be able to show a complete medical history, or a list of pathology results. Exchange Node Clocks — A common time reference must be used by all Nodes throughout the Exchange, namely Co- ordinated Universal Time (UTC) resolvable to the calendar date (century, year, month, day) and time of day (to the nearest millisecond). Although leap days/seconds must be incorporated, no adjustment for daylight savings is required — UTC is equivalent to Greenwich Mean Time (GMT). — Individual Node clocks must be kept in sync to the nearest millisecond. Datawell Exchange Managed sharing — The Exchange must directly implement managed sharing, connecting each participating organisation's Exchange Node and filtering data transfers to enforce the rules defined through the combination of data sharing agreements from organisational through to an individual's permission settings. — The Exchange must immediately honour any changes made to the deployed sharing agreements, whether to restrict or to expand. — The Exchange must also provide the facility to transform data before delivery, specifically to apply de-identification according to the rules defined in the Data Sharing Agreement currently in effect between the sender and receiver. Governance audit — Exchange nodes must maintain data query and transfer logs for reporting on information flow to enable governance audit, systems performance and security monitoring. Flexible data exchange — The Exchange must support different modes of transfer including: pull requests, for small scale on demand distributed queries for individual data item sets (e.g. for servicing a patient point-of-care application); push requests, for large scale scheduled bulk dataset delivery (e.g. for servicing a secondary population research analysis). — The Exchange must support both standard core Dataset Definitions to drive a minimum level of application functionality Standards conforming — The Exchange must implement a range of healthcare interoperability standards including but not limited to: NHS Information Toolkit (ITK), HL7-V2, HL7-FHIR, ITU- T-H.860, IHE XDS, OpenEHR as required to support a range of downstream applications. Security and Audit — All data transfers between nodes must be encrypted ‘in flight'. Transfers between specific pairs of Exchange Nodes should be encrypted with different keys, such that compromise or publication of a key pair does not expose data exchanged between other pairs of Nodes. In case of such a security breach, it must be possible to invoke an immediate change of encryption keys used throughout the Exchange. — The data transfer logs must record sufficient information to enable audit of who/when/what for each transfer event, but also for unusual patterns of access to be identified and flagged for further investigation. FairWarning is an example of a commercial product, currently used by the NHS, for analysing data access logs for potentially inappropriate activity. — An Exchange Administrator must have the facility to immediately disable responses being generated to queries originating from a specific End User across the entire Exchange. End User Registry — An End User Register must be implemented across all Nodes in the Exchange to ensure a consistent view of the same user is maintained regardless which Organisations they may be employed by over time, or their level of site to site mobility that may be a characteristic of their job. The same single unique identifier must apply to the same user irrespective of their original registration Node. This requires Exchange Nodes to participate in shared End User Register updates and to implement a scheme for resolving potential duality of user identity. — The Administration and Audit Portal must support the creation, update, suspension and deletion of an End User, recording a range of descriptive and contact information for each person. Repeatability — Whilst the Transfer Log does not make record of the Response Datasets generated, it must capture sufficient information to enable the Request to be rerun under the same system-wide state in order to generate the same Response Datasets, and in particular the same cohorts of individuals. Break the Glass — Certain AccessRoles, e.g. a consultant in A&E, must be able to be given the special permission ‘Break-The- Glass'. This follows the standard procedure within the medical profession, whereby an EndUser with this permission can access an individual's data after interacting with a separate challenge and response mechanism within an EHR application for example. Break-The-Glass events are typically separately monitored and audited with professionals having to justify their use. The Exchange must be able to support this scenario. Datawell Exchange API — A set of open Datawell APIs must be defined for specifying on-demand broadcast data transfer queries, scheduled transfer queries, audit queries, data sharing agreements and system management such as registration/withdrawal of Nodes from the Exchange network. — The Datawell APIs must include a separately secured Administration API and Data Transfer API. Only the basic requirements for these APIs are described in the following sections, additional capabilities remain to be defined. Data — In order to support the successful use of the Datawell Exchange bidders must have or develop a common information architecture that defines the format and definition for health information to be shared. This definition will constitute the minimum core dataset for the exchange, and provide the core structures that will need to be mapped to individual systems within Exchange member environments. The benefits of this common data architecture must include: — Identify and source the data needed to share between organisations and to support the development of new applications — Make it possible to uniquely define a new data element within a minimum data set — Establish the derivation of a given data element from its root sources. — Build common business rules about data and have them apply across the conurbation. — The key purpose in developing the Data Architecture must be to support the software applications that will use and access shared data across the Exchange. It will also facilitate the ability to link datasets between different sources and 3rd party datasets. — The model must balance this flexibility against the need to provide a concrete software implementation that can be assured to meet external data standards and be optimised to provide rapid, appropriate and secure access to data. — A recommended data model must be flexible enough to accommodate multiple types of use, including export for inclusion in other clinical record systems, point of care use, research, clinical audit, business intelligence and quality and safety monitoring — The node solution must provide a basic dataset definition in line with national and international standards such that access to the data by the data owners is always possible. There are a number of standards for the storage and interchange of health data for use by electronic health record systems. Examples of Reference Models include HL7, NHS Interoperability Toolkit (based on HL7), XDS, EN13606 European Standard for Health Informatics, and openEHR. — The data owner must always be able to extract or completely remove their own data — The data owner must always be able to add additional datasets based on own data sources and extend the nodes data catalogue as required. Data that can be included in the node will cover: PAS, pathology, medications and prescribing, health resource utilisation, critical care, speciality data, out patient information, emergency admissions (A&E), community and intermediate care, mental health, social care, GP and other primary care. — It must not be possible for any system to access data, either locally or via the Exchange, without the appropriate information sharing agreements permitting use. Patient consent models must also be respected. Analytics and Business Development A core objective for Datawell is to support the innovative use of data to improve outcomes for patients and the efficiencies of the whole GM health and social care system. Therefore there is a requirement for provision of business analysis and data analysis support of the program, as well as provision of specific support to members during roll-out to help identify value and project opportunities created by the Datawell platform. Specific tasks must include: — Map current organisational data flows, both internal and external, that are relevant to Datawell projects. At a minimum this must include Hospital Episode Statistics, pathology, prescribing, admissions, diagnosis and other patient episode data. — To identify metadata definitions and potential quality issues to create dataset definitions and metadata that will help Datawell users in accessing and using the data. Create a metadata catalogue that must define data content, including coding schemes. — Establish working groups internal to members in order to develop informed knowledge about the use and purpose of the data, identify requirements for data sharing and requirements that may be relevant to future Accelerator projects — Identify and document local value propositions, within the framework established in the Business Case, and develop bespoke business cases for Accelerator projects that will support the development of Datawell and demonstrate its effectiveness in improving patient safety and outcomes, reducing costs and creating efficiencies. — To identify and map existing applications and APIs within member organisations. — Support the development of data models for use in the Nodes and Exchange. — Maintain the programme governance framework, including reporting to Board meetings, setting up and maintaining the Reference group and maintaining Public Patient Involvement plans. — Develop an information governance framework and common information sharing agreements for use in the Datawell Exchange. Where possible existing best practice should be maintained. — Create a catalogue of existing data sharing agreements and establish a plan where migration to a new data sharing agreement is required. — Ensure that the design of the Datawell programme complies with essential legal and ethical frameworks and supports national and local initiatives for data sharing. Links with appropriate national and local groups, including HSCIC, the GM Informatics Board, local Health and Wellbeing Board, Directors of Public Health, and others, should be maintained and reported. Datawell must also fit with Local Authority plans, directed by AGMA, and the future development of Devolution in Greater Manchester. — Continue the promotion of the objectives of the Datawell programme through member engagement, local workshop and conference activity. — Develop a Datawell Business Model which will create a sustainability plan for beyond the initial three year funding plan. . This service is being potentially being procured on behalf of: Bolton Clinical Commissioning Group, Bury Clinical Commissioning Group, Central Manchester Clinical Commissioning Group, Eastern Cheshire Clinical Commissioning Group, Heywood Middleton and Rochdale Clinical Commissioning Group, North Manchester Clinical Commissioning Group, Oldham Clinical Commissioning Group, Salford Clinical Commissioning Group, South Manchester Clinical Commissioning Group, Stockport Clinical Commissioning Group, Tameside and Glossop Clinical Commissioning Group, Trafford Clinical Commissioning Group, Wigan Borough Clinical Commissioning Group Bridgewater Community Healthcare NHS Trust, Central Manchester University Hospital NHS Foundation Trust, East Cheshire NHS Trust, East Lancashire Hospitals NHS Trust, Greater Manchester West Mental Health NHS Foundation Trust, North West Ambulance Service NHS Trust, Pennine Acute Hospitals NHS Trust, Pennine Care NHS Foundation Trust, Royal Bolton Hospitals NHS Foundation Trust, Salford Royal NHS Foundation Trust, Stockport NHS Foundation Trust, Tameside Hospital NHS Foundation Trust, The Christie NHS Foundation Trust, Wrightington, Wigan and Leigh NHS Foundation Trust, University Hospital of South Manchester FT Blackburn with Darwen Borough Council, Bolton Council, Bury Council, Cheshire East Council, Manchester City Council, Oldham Council, Rochdale Metropolitan Borough Council, Salford City Council, Stockport Metropolitan Borough Council, Tameside Metropolitan Borough Council, Trafford Council, Wigan Council The duration of the contract is 30 months with the option to extend for an additional 36 months and then a further 24 months if required. The innovation partnership procedure is being adopted. It is intended that 3 economic operators will be taken forward following PQQ.

“Move More” Physical Activity Behaviour Change Care Pathway

 | Published May 25, 2016  -  Deadline June 15, 2016
cpvs
85000000

The Ambition of the Move More Programme is to ensure that everyone living with and beyond cancer are aware of the benefits of physical activity are enabled to choose to become and to stay active at a level that’s right for them. Keeping active throughout the cancer journey can preserve or improve physical function and psychological well-being, reducing the negative impact of some cancer related side-effects. Regular physical activity also has a potential role in reducing risk of cancer recurrence and increasing survival. The aim of the service is to provide all patients with a cancer diagnosis appropriate advice on the effects of physical activity on cancer including behaviour change support over a minimum of 12 months; this would include subsequent, signposting to appropriate physical activities as identified by the patient. The service will be offered to all patients who live in Wandsworth and who are treated within Wandsworth. It will be offered through health and social care and primary and secondary care professionals (such as consultants, specialist nurses and Allied Health Care Professionals). The service will allow for self-referrals by patients living in Wandsworth and receiving treatment in Wandsworth. The CCG will award a contract for 3 years to the appointed provider. The expected service commencement date is 1st October 2016. The total contract value for the full 3 year contract term is estimated at £100,000. *** Potential bidders, intending to participate through the procurement process are now invited to register an interest and access the procurement documents (service specification, bidder instructions, bidder application questionnaire, etc.) via the electronic procurement portal EU-Supply available at https://nhssbs.eu-supply.com. Once you have logged into the EU-Supply Portal, SEARCH FOR TENDER REFERENCE 23723 (Move More Service) *** ***THE DEADLINE FOR SUBMITTING AN APPLICATION FOR THIS OPPORTUNITY IS 12.00 NOON WEDNESDAY 15TH JUNE 2016***
  • 1