Nov 272014
 

Your action IS required.

Passing on the request from Dr Marcus Baw

I've mentioned this on the list before, but there is an area on StackExchange where suggestions are accepted for new areas. A Healthcare IT section has been suggested but the first time it did not get enough votes to become an official Beta.

This time, we have a limited opportunity to get it voted up enough it will be created.

This is a potentially helpful resource for discussing the technical aspects of healthcare IT and I think would overall benefit the NHSHD community. Could I therefore ask you ALL to take the 30 seconds to go to this site, login or create an account, and vote for the Healthcare IT Forum.

Of course, if you already know everything there is to know about Apple HealthKit, FHIR, HL7, SNOMED-CT, Read Codes, CTV3, openEHR, IHE, CE marking of medical devices, medical UX, etc, then you personally have no need of it - although I'd still like you to vote because we'd need a place to ask you questions 😉

Sep 172014
 

OPENeP has selected the HANDI-HOPD to built its initial prototype app. It will provide further proof of concept and is the most ambitious project to be attempted on HANDI-HOPD so far.

OPENeP is an open source project intended to deliver a suite of medicines management apps to improve the safety and efficiency of prescribing and medicines management and demonstrate how new business models can create commercial opportunities for vendors focussed on delivering high quality service.

Medication errors and one of the biggest single cause of harm to patients in NHS Hospitals, causing death, disability and suffering and represent a significant cost to the NHS with wider negative economic impacts.  Many errors are amenable to mitigation through the application of digital technology and OPENeP is intended to help address these problems.

There are already a number of digital tools that support various aspects of the medicines management process, most are proprietary products and many of these are of good quality, but they are not designed to fit in the emerging open digital health ecosystem or take advantage of the latest technology.

OPENeP is intended to  explore how we build apps for the emerging digital ecosystem and  to enhance, not replace, existing EHR and Pharmacy systems and create new opportunities for vendors of such systems, who we hope might  include these components to enhance their existing product and service offerings. OPENeP apps  will be designed to facilitate integration with PAS, EHR, order communication and  pharmacy systems as well as proprietary  knowledge and decision support components.

The starting point for OPENeP will be the ePrescribing and Medicines Administration modules of  Think!Med Clinical which its creators Marand have agreed to release under the GPL open source licence. This product which is based on OpenEHR provides a proven solution using the latest technology  already successfully deployed in a large hospital and gives us a great starting point for our work. Our aim is to develop this to provide the suite of apps described below which will initially be deployable via a common interface (API) as either the eP/eMA component of a OpenMaxims EHR or as a "standalone" solution which will operate on any OpenEHR backend

The focus of OPENeP is on the hospital inpatient setting, where it is intended to integrate with existing systems and other apps to deliver digital care at the beside. However, it is designed so that it can be extended to deliver facilities in other settings.

The currently identified components of the OPENeP suite are:

  • Medicines reconciliation – With modules for both the patient and healthcare professionals to ensure an accurate view of a patient’s medication at handovers of care.
  • ePrescribing – To help ensure safe, efficient and appropriate prescribing compliant with national guidance and local policies.
  • Medicines Administration – To help ensure safe, accurate and timely medicines administration.
  • Personal Medication Record – To give patients a view of their medication to support self-care, concordance and the safe and effective use of their medication.
  • Medicines Utilisation and Audit – To support pharmacists and others in the review totality of a patient’s medication and monitor and audit medication usage, administration and patient concordance.
  • Medicines supply management  – To support the transfer of orders for medication both for individual patients and for local stock to pharmacies, including support for orders for discharge medication to hospital or community pharmacy.

The Initial focus with be on prescribing and administration and we intend to use HANDI-HOPD to build some initial prototypes. Like everything on HANDI-HOPD these prototypes will be purely experimental and will not be used with real patient data. However, because HANDI-HOPD uses open standards we expect others to take them and deploy them in an operation environment.

Our priority is to create a user interface (UI) that delivers a user experience (UX) that make the apps a joy to use and in doing some makes the processes they support more efficient, easier and safer. To do this we want to bring together domain expertise in medicines management, frontline clinicians and patients with engineers, designers and informaticians working together using user centred design techniques.

In order to operate effectively and efficiently OPENeP apps will need to interoperate with a range of others systems including:

  • GP Systems – To support medicines reconciliation on admission and discharge
  • Patient Administration Systems (PAS)  - To identify and track patients
  • EHR Systems (EHR) – Access the clinical data about patients needed for safe, effective prescribing.
  • Hospital Pharmacy Systems – To manage medication orders and supply
  • Community Pharmacy System – To support delivery of discharge medication in the community.

We will use existing open interface and define new open interfaces where none exist, ideally in collaboration with target system vendors.  The OPENeP apps will be designed to work with FHIR APIs on target systems (with openEHR archetypes mapped to FIHR resource profiles) but we will provide middleware components to allow interworking with APIs based on other standards.

Basic functionality can be implemented without interfaces to most of the above systems, but certain basic EHR data is essential for safe prescribing and OPENeP will provide basic EHR functionality, using openEHR to allow these data to be recorded with within the OPENeP suite when an external EHR data source is not available.

Partners in the project are:

  • NHS England Open Source and e Prescribing Programmes
  • Fivium http://www.fivium.co.uk/ - A mid-sized SME with experience of delivery solutions based on source to Government in the UK and elsewhere including the provision of the system to operate the Pharmacy Benefit Scheme to the Australian Government. http://www.fivium.com.au/health.html
  • First Data Bank http://www.fdbhealth.co.uk/ –The UKs most experienced provider of drug knowledge for use in ePrescribing systems.
  • Neova Health www.neovahealth.co.uk/  – A UK based SME successfully delivering open source solution in the NHS include eObs a nursing observation app which is a natural companion to OPENeP at the bedside.
  • Marand  www.marand-think.com/   – A Slovenian SME that already provides much of the technology for HANDI-HOPD and who have delivered ePrescribing for the Slovenian Health System
  • IMS Maxims - http://www.imsmaxims.com/opensource/ - Original authors of OpenMaxims open source EHR

 

Jul 302014
 

An opportunity has arisen for software development intern to work with HANDI on the HANDI-HOPD project www.handi-hopd.org

The role will involve developing the platform software, which is already deployed in prototype form, to extend the range of components and content available via the platform and improve the facilities it provides to support health and care professionals and software developers to use the platform to learn how to use open standards based systems to create and curate clinical content and build apps able to participate in the emerging open digital ecosystem in the NHS.

Candidates should have completed at least two years of an undergraduate course in computer science, software engineering or a scientific/mathematical discipline with a strong computing element, have an evidenced expectation of a first class or upper second degree and demonstrable experience of software development in a Internet/Cloud environment with a good working knowledge of Linux and at least two programming languages preferable including either Javascript, Python or Ruby.

We are also interested in hearing from candidates who have completed their first degree and who might be able to pursue HANDI HOPD as part time as an element of study for a higher degree.

Candidates should have some knowledge of the health and care sector and a desire to pursue a career in digital healthcare or healthcare informatics.

The initial engagement would be for approximately 3 months and there is the possibility of an extension beyond this for candidates in a position to offer a longer commitment.

Location would be Central London or Central Birmingham (to be agreed) and payment would be between £12.5k and £25k pa depending on qualification, experience and length of commitment offered (the lower rate would apply to a short term undergraduate internship.)

Candidates MUST be able to start immediately and have substantially unrestricted availability over the summer period.

Interested candidates should send a CV and covering email to jobs@handihealth.org – All applications will be acknowledged and we will also endeavour to answer any questions you may have via this email.

Closing Date – Due  to our desire to make an appointment quickly we will process applications on receipt and close applications once we have a pool of suitable candidates.  Applications for this post are currently open.

Date issued 29 July 2014