Media Capture App - Lewisham and Greenwich NHS Trust (ST22-P155)

Description

Summary of the work The Trust requires a system based around an app to allow Trust staff to securely capture, store, view and share clinical media (photographs and video) on mobile devices as well as desktop computers. Expected Contract Length Desirable project timeline 3 months. Hosting and support contract for 2 years from go-live. Latest start date Wednesday 1 February 2023 Budget Range £110,000 capital plus revenue costs for storage and licencing. Why the Work is Being Done Clinical media is used by specialties throughout the Trust, including but not limited to, Tissue Viability, Foot Health, Dermatology, Home Enteral Nutrition Team, ENT, ED, Speech and Language Therapy, Neighbourhood Health Visitors, Community Physios, Children’s Community Services, and other stakeholder organisations. In addition to media being used by the Trust for treatment, monitoring and smart referral purposes, there is a requirement by most of these specialties to share media with the wider healthcare community, Clinical Commissioning Groups (CCGs), social services, and GPs. This can be for advice, diagnosis, referrals, and safeguarding. There may also be times when it is deemed appropriate and beneficial for patients to submit media. For example, if a baby is prone to fitting it may not be possible for a clinician to observe a fit at a one-to-one consultation. Allowing the parent to film a fit as it happens and submit the video can help clinicians to provide a more accurate diagnosis. Current systems do not facilitate this. This functionality is desirable but not necessarily essential for the MVP and could be developed in another phase of the project. Problem to Be Solved The objective is to provide relevant staff with a solution that allows them to capture and view clinical media (video and photo) using mobile devices, both Trust and personal, that is stable and secure and in accordance with general data protection regulations. This solution will build on the strategic investment the Trust and the wider NHS has made via the buy in to the Microsoft 365 platform and would replace LGT Portal, which is not stable and is prone to technical issues. The solution would move to media being stored on the NHS certified Dataverse (or other cloud storage), making it accessible to wider approved audiences without requirement for access to multiple EPRs i.e., Rio, iCare, Epic, System One. This is the same as the NHS LGT Anywhere remote access solution. There is a requirement for links or similar connector to be created within EPRs for users to be able to launch a system and view media stored in the cloud. A Power App for clinical media capture, storage and sharing, can either be a standalone app, downloadable by the necessary staff or be embedded within Teams for seamless integration. Who Are the Users Clinical media is used by specialties throughout the Trust, including but not limited to, Tissue Viability, Foot Health, Dermatology, Home Enteral Nutrition Team, ENT, ED, Speech and Language Therapy, Neighbourhood Health Visitors, Community Physios, Children’s Community Services, and other stakeholder organisations. Work Already Done This should use the Microsoft 365 platform and would replace LGT Portal, which is not stable and is prone to technical issues. The should store on the NHS certified Dataverse (or other cloud storage), There is a requirement for links or similar connector to be created within EPRs for users to be able to launch a system and view media stored in the cloud. The Power App would sit within our Trust Tenant or the national NHS mail Tenant giving LGT ownership of it. It would be fully auditable and complies with IG requirements. Existing Team The supplier will be working with the Trusts ICT Team and clinicians. There are no other suppliers involved. Current Phase Not started Skills & Experience • Significant, demonstrable experience in the full life-cycle of the development of large Media Capture Apps • Experience running UX and design workshops. Agile user testing • Experience of working with NHS or public-sector, knowledge of health technology, NHS identity guidelines, technical standards from NHS Digital • Evidence of providing a 24-hour customer support service, and account manager • Expert SEO skills and the ability to advise on best practice. • Experience of App Development using the Microsoft 365 platform • Ability to deliver high quality but low technical maintenance solutions • Experience of developing portals that allows patients and GPs to submit media to support patient care • Can demonstrate effective options for integration with other websites and systems, including EPR platforms such as Epic and Cerner • Experience of solutions that stores data on azure blob or dataverse • Experience of Web portal design to allow partner organisations/those with parental responsibility/patients can upload media • Can explore options for personalisation and user authentication Work Location University Hospital Lewisham, Lewisham High Street, Lewisham, London SE13 6LH Working Arrangments Mainly off-site, with visits to our offices as required by the project. Additional T&Cs Standard contract will be used along with selected optional schedules No. of Suppliers to Evaluate 5 Proposal Criteria • Technical solution • Approach and methodology • Matching of user needs • Estimated timeframes • Delivery Team • Risks and caveats • Longevity off solution against Trust IT roadmap • Value for Money Cultural Fit Criteria • We are looking to appoint a partner company that can demonstrate to us that they are thinking about our future • Will need the expertise and experience to understand emerging technology that will make a difference to our user • While we want to be a leader in NHS technology, we also want to make sure we are only taking advantage of technology that adds true value • Works as a team with our organisation and other suppliers where necessaryWorks as a team with our organisation and other suppliers where necessary • Ready to challenge the status quo • Champions equality, diversity and digital inclusion • Is innovative and forward thinking • Shares knowledge and experience with clients • Provides honest and expert feedback • Uses innovative, cost effective techniques to engage website users • Takes responsibility for the quality of their work • Transparent and collaborative when making decisions • Works well with clients of varying technical expertise • Able to demonstrate the value of their approach and understands the value of data and analytics Payment Approach Capped time and materials Assessment Method Presentation Evaluation Weighting Technical competence 60% Cultural fit 15% Price 25% Questions from Suppliers 1. Around the SEO requirement – are L&G looking for anything specific in this are? E.g. do L&G already have a dedicated marketing resource focussing on SEO and are they looking for the supplier to simply support this function within the context of Power Pages and advise on best practise? No requirements from supplier. 2. The budget provided – please could you confirm if this excludes Hosting and the support contract for 2 years from go-live and VAT? The budget is for devoplment and delivery of the Power App using the Microsoft Power platform. The Power app will use the existing NHS mail tenant so will not need to be hosted and we do not anticipate any need for support as the finished Power App will be run and maintained by L&G staff. We may purchase extra PS in subsequent years if needed to enhance the application. 3. Regarding this item – Evidence of providing a 24-hour customer support service – are L&G looking for a supplier to provide to L&G a 24 hour customer service function? Is the 24hour capability simply the ability for L&G to raise support tickets 24 hours a day or is anything further required e.g. 24 hours a day Helpdesk function with SLAs running 24 hours a day We do not anticipate having any kind of support service as the app using the power platform will be run and maintaned by L&G staff. This tender is for developoment and delivery of Power App using the Microsoft Power Platform only. We may purchase extra PS in subsequent years if needed to enhance the application. 4. We are an idependent Quality Engineering company that only provide Test Services and would very much like to bid to be part of the project. Please can you share if we can bid direct or whether we might need to partner, hopefully you understand the great value aligning a Quality Engineering team can deliver, or if not happy to share why many of your Healthcare colleagues are engaging these types of services. appreciate your response.’ Hi, we are looking for a sole primary supplier and we would expect the primary supplier to source and sub-contract testing services if necessary 5. From the clarification answers, we understand that SEO and 24 hour customer support service are not required. This being the case, will supplier answers to these questions be scored and if so, how? Please do not answer these questions. And they will not be included in the evaluation. 6. What does the organisation consider ‘large media’ and are there any expected protocols or additional security requirements that need to be factored in when considering the solution? Large media is in relation to file size and amount of images/potentially video we capture. Medical photography is growing we require high quality images and expect to be capturing several thousand images a year. Currently we capture around 20,000 anually, this has increased from 10,000 six years ago. We understand the Microsoft Power platform and the NHS tenant has been approved for transfer and storage of patientsensitvie information however we would like some kind of PIN or biometric access to launch the app, ideally linked to the NHS smartcard or through administration by the team when activating accounts for users. 7. Do the EPR platforms have a known API with access to the data expected in this new solution, or is this yet to be discovered? There is no requirement to connect to the EPR at this stage. The patient demographic lookup will be to NHS spine/Mini spine and all images and media will be stored in the Dataverse (we have seen proof of concept for this) . We are intending to build a link in to our EPR that launches the app so users can then access media stored in Dataverse or similar. 8. Our development lead has questioned if Microsoft Azure will be suitable for a standalone app, as a Power App with similar options and portal will not work within the current budget or time constraints? We are open to storage solutions. We are not technicians and will look for guidance on this. The initial budget listed here is capital for development and build of the Power App only. We have separate additional revenue funding secured for licensing and storage to cover the next few years. 9. What types of devices will be used – desktop, tablet, phone, BYOD/standard build? The Power app should be accesible from desktop and Trust issued and BYOD, much like the MS Teams app works on Desktop and mobile devices 10. Would staff access only be considered acceptable for the MVP with potentially partner organisations/those with parental responsibility/patient access coming in a later phase? Yes, we are aware of the extar complexities of implementing a portal for external stakeholders so although a nice to have, we don't expect this to be a must have for the the MVP. We do have some development budget allocated for future iterations of the solution. 11. What capability level do internal resources currently have in Power Platform? Would there need be an element of upskilling? Enthusiastic amateur is probably best to describe capabilities in the Medical Photography team. Some team members have experience with Teams, Power Automate, Forms Streams Etc and are willing and able to go on training. The Trust IT team have more extensive knowledge and capabilities but may not be actively enghaged oin the day to day running of the Power App There will undoubtedly need to be some upskilling. 12. What is the current licensing situation? As Dataverse is mentioned, will all users be accessing the app be covered by premium licensing over and above M365 Power Apps licenses? All Trust Employees have the standard N365 license assigned to them when they start. We have looked in to and secured revenue funding for the additional licensing and storage from the Trust's current supplier. The budget described here is capital only for development and build. We envisage the app being hosted on the National NHS Tennant. 13. We have a software as service product in use in the NHS which we feel could meet your requirements. Would you consider purchasing an available solution instead of developing something bespoke? We would be more than happy to do a demo and discuss your requirements further. If this is based on the Microsft Power Platform then potentially. We are aiming for increased integration with theNational N365 agreement and NHS Microsoft mail tennant so that as NHS Trusts increasingly work together we are able to utilise this existing infrastructure without having to introduce new systems. 14. What sort of personalisation is envisaged?Are there accessibility requirements for the solution? Basic level of personalisation. At this stage we are looking for an MVP which would be the same for all users, but ideaaly would like to allow users to be able to curate theur own 'Lists' of patients so they could bookmark certain patient if they are monitoring them over an extended period or want to create a patient list to review later in the day. We have some additional funding for further development of the app in the future. 15. Is the expectation that integration with EPR platforms will be through standard formats? e.g. FHIR or REST? We don’t require integration with the EPR at this stage. The app will work outside of the EPR and all media will be stored in Dataverse or alternative. We are expecting our IT teams to add a link or launch button in to the EPR which will launch the app to view the media and after the media has bee stored for around 6 months it will be moved manually or by RPA to the Trust EPR. 16. Do you anticipate that patients will authenticate through Azure Active Directory or some other means? This is an unkown and we understand the complexities surrounding this, so for the MVP we are not expecting external users such as patients and partner organisations to be able to upload through a portal - this may be best left for future iterations, but we did think along the lines of one time codes being sent to external users to be able to access a portal for upload or some other authentication process. 17. Do you require a wholly low-code solution, or can some aspects be bespoke development (e.g. C# /.NET), where appropriate? Yes low code only. It has to be as simple as possible for Trust staff to use and maintain.