Respect Form Application

Tender description

Summary of the work Building a ReSPECT form application using OpenEHR and HL7 FIHR on top of an open health platform comprising the EtherCIS CDR, PulseTile UX framework and QewdJS integration framework. Underlying technologies are redux, NodeJS and Angular. Expected Contract Length 1 month Latest start date Friday 1 February 2019 Budget Range N/A Why the Work is Being Done Domain E of the Scottish digital health care and strategy calls for a National Digital Platform. This is the first application of this requirement. The end date for this work to be completed shall be 1st March 2019 however this shall not restrict suppliers from delivering the solutions earlier than this date. Problem to Be Solved There is currently a paper form that cannot be accessed across the system. Therefore, NES wish to create a form that can be accessed across NHS Scotland and Social Care Scotland. Who Are the Users As a person delivering Care in Scotland I need access to a patient’s wishes at end of life (e.g. DnR) so that the appropriate care can be delivered when a patient is unable to communicate their wishes. Early Market Engagement Nothing at this stage. Usage of free tools/ open source design principles has been considered at the earliest stage. Work Already Done Nothing at this stage. Existing Team The winning supplier will be working with the internal NHS Education for Scotland Team only during this phase. Current Phase Not started Skills & Experience • Experience designing applications for clinicians • Use of openEHR to model clinical data • Experience of working on open source projects • Experience developing nodeJS, Redux, and Angular Work Location The work done by NHS Education for Scotland shall be done in Edinburgh. However, it is anticipated that remote working will be done by the winning supplier. Working Arrangments An initial face to face meeting is required. Once the initial face to face meeting has been completed the use of online collaboration tools should be utilised to the fullest extent for the contract duration. Security Clearance No security clearance during this phase. Additional T&Cs N/A No. of Suppliers to Evaluate 3 Proposal Criteria • Technical solution • Approach and methodology • How the approach or solution meets user needs • How the approach or solution meets your organisation’s policy or goal • Estimated timeframes for the work • How they’ve identified risks and dependencies and offered approaches to manage them • Value for money • Approach to open platforms Cultural Fit Criteria • Work as a team with our organisation and other suppliers • Be transparent and collaborative when making decisions • Take responsibility for their work • Share knowledge and experience with other team members • Challenge the status quo • desire to contribute to open source softwae Payment Approach Fixed price Evaluation Weighting Technical competence 70% Cultural fit 10% Price 20% Questions from Suppliers 1. What is the budget for this tender? NHS Education for Scotland wishes potential suppliers to propose a competitive quote in lines with the requirements therefore the budget has not been provided. The supplier should suggest the best approach to the requirement alongside a competitive commercial quote. 2. Is Angular a hard requirement? Angular is not a hard requirement, however experience with React would be beneficial. 3. In the summary you mention OpenEHR and FHIR. In the skills and experience you ask only for OpenEHR. Is the intention to use both as part of the solution, or are you considering selecting one standard but have not yet decided which one? Both will need to be part of the solution. 4. We want to assume that this is just a single (one) form application and not multiple forms. Is this assumption correct? The purpose of the application is capture the data that is part of the ReSPECT form https://www.respectprocess.org.uk/_pdfs/ReSPECT-Specimen-Form.pdf . In order for that to be as easy as possible, it may be split across multiple screens. 5. Will authentication be required in order to access and process the form? Yes, the form will need to be accessible via an OAuth2 provider that is already being used