FOI/25/068

Read more about this page below
Reference FOI/25/068
Description Medical Device Integration; Electronic Patient Record Applications & Data Warehouses
Date requested 30/05/2024
Attachments N/A

Request

Medical Device Integration

  1. Is the Trust HIMMS accredited? If so, what level of accreditation has been achieved?
    No, the Trust is not HIMMS accredited.
     
  2. Does the organisation have an existing Electronic Patient Record (EPR) system? If yes, please provide details of the EPR product, including the provider and product name.
    EMIS/SYSTM1
     
  3. When is the renewal date for the current EPR system?
    March 2026
     
  4. Does the Trust have a solution in place to automatically send patient data from medical devices to the main Hospital Information System / EPR?
    Yes
     
  5. Is there a single interoperability platform for all medical devices that automatically sends data to the main hospital information system? N/A
     
  6. If yes to question 5, who is the supplier and what is the name of the product?
    N/A
     
  7. If yes to question 5, when does the current contract end?
    N/A
     
  8. Is the Trust reviewing any projects that require the integration of medical devices with the main hospital information system / EPR?
    No
     
  9. If no to question 5, is the Trust currently evaluating suppliers and product options for medical device interoperability with the main hospital information system (PAS/EPR)?
    No
     
  10. If no to question 5, is the Trust interested in learning about Enovacom’s software-only solution and how other NHS customers are adopting our technology?
    No
     
  11. Who is the lead person to contact regarding projects of this nature? Typically, we would connect with the Chief Clinical Information Officer, Chief Digital Transformation Officer, or EPR Programme Director.
    Helen Cassidy, Chief Clinical Information Officer, h.cassidy@nhs.net

    Enterprise Application Integration
  12. Does the Trust currently have an integration engine for securely exchanging data between software systems both internally and externally?
    No
     
  13. If yes to question 12, what is the product name?
    N/A
     
  14. If yes to question 12, do you intend to change your current integration engine?
    N/A
  15. If yes to question 14, when does the contract for your current integration engine end?
    N/A
     
  16. If no to question 12, do you intend to purchase an integration engine?
    No
     
  17. If yes to question 16, when do you plan to purchase it?
    N/A
     
  18. Who is the lead person to contact about projects of this nature? Please provide their name, email, and phone number if possible. Andrew Chronias, Chief Information Officer. Andrew.chronias@nhs.net

 

Data Warehouse

Our existing NHS clients must share a basic level of data with their main ICS (Integrated Care System). They have chosen a Federated Model over a single centralised data repository in a regional external HIE solution, due to the sensitivity of some patient data. In this model, they maintain their own local FHIR-based data repository on-premises and provide a reference to the file to the regional HIE.

 

  1. There are three main architecture patterns for delivering a Shared Care Record to share data with the ICS. Please identify the Trust’s chosen option:
    a. Centralised Model – Data is stored in a centralised, consolidated data repository. Data shared by HIE participants is normalised, housed in, and accessed from a central data repository.
     
  2. Does the Trust currently have a data repository for the above requirement if selecting b or c?
    N/A
     
  3. If yes, is it FHIR-based?
    N/A
     
  4. What is the name of the product?
    N/A
     
  5. Who is the supplier?
    N/A
     
  6. When is the contract renewal date?
    N/A
     
  7. Is the Trust looking to purchase a data repository?
    N/A
     
  8. If yes, when does it plan to purchase it?
    N/A
     
  9. Who is responsible for sourcing the data repository? (Please provide name, email, and phone number if possible.) 
    N/A

 

Accessibility tools