UCL IXN & GOSH Azure FHIR-Display

Published 06-09-2020 08:51 AM 1,012 Views
Microsoft

FHIR-Display - A dedicated secure IoT device for clinicians to view FHIR data

Ethan Wood


Ethan Wood is a computer science student in his second year at UCL and as part of his course competed in the FHIR (fast healthcare interoperability resources) hackathon in the internet of things category building FHIR-Display. Ethan also developed FHIR-Parser, “an elegant and simple FHIR library for Python, built for human beings”.

 

One of the problems when viewing patient data inside of a hospital is the trade-off between privacy and ease of access. You need key patient information, such as their name or medication, to be readily accessible. Currently this is in a printed form, close to their bed, so that clinicians can easily monitor lots of patients at the same time. This allows anyone with physical access to a patient to be able to read their medical records. It can also be difficult to keep track of patients when they are moving around different parts of the hospital, especially if they are out-patients and not easily recognised. Further to this, more in-depth, up to date, or complex information is held digitally and needs to be accessed via a computer or iPad.

 

This presents two problems, the first is how do we improve patient privacy while ensuring it is just as easy for clinicians to access the data they need. The second stems from the inherent difficulty of using a multi-purpose device (such as a computer or iPad) which traditionally encompasses a variety of different tasks for a clinician. When using this multi-purpose device, they end up needing to switch between different apps and services, logging in and out. As FHIR is integrated into more of the hospital ecosystem this situation is only likely to worsen with yet another system they need to connect to being created.


This is solved by FHIR-Display, a dedicated device for clinicians to access FHIR data about a patient in a secure environment. The idea is that all patients during triage are issued with a small RFID tag which contains their personal FHIR identification code. This can be in the form of a bracelet, key fob, or security tag depending on what is most appropriate for this particular patient (in-patients may prefer a bracelet if it is frequently accessed while for out-patients a key fob they can remove). RFID tags are very cheap and there is no risk of data leaking outside as it only contains their FHIR identification code for that specific hospital. When a clinician needs to see data about a particular patient, they place the FHIR-Display near the RFID tag, at which point the patient’s personal information appears on the screen. This also gives patients a feeling of control about their personal data with them being able to prevent someone they do not trust from looking at it.

 

Currently FHIR display is a small box, approximately the size of a phone, built from 3D printed PLA. It houses an Arduino Mega for the controller, an LCD keypad shield allowing up to 32 characters to be displayed, and an RFID-RC522. The RFID tag is read using the RFID-RC522 through the PLA base which is designed to be thin enough for radio waves to penetrate. The device connects to the FHIR endpoint either over WIFI, Bluetooth, or serial. During the hackathon it connected to the FHIR endpoint via FHIR-Parser which aims to simplify the FHIR standard and allow projects to be built quickly without the developer needing to fully understand how FHIR works. This allows them to instead focus on the idea of their project and let the parser handle retrieval (ideal for short hackathons). However, in the future it will be possible to connect FHIR-Display directly to an endpoint such as the Azure API for FHIR with the ATmega2560 more than powerful enough to complete the parsing and interpretation independently.

FHIRDisplay.PNG

 

While the idea presented above simplifies access to data and helps prevent “yet another app” on a clinician’s device, as of yet, it only improves security slightly by removing the need for bedside reports. However, anyone who has one of the devices is still able to access information about the patients. In the future this would be solved with some sort of biometric lock. This would most likely take the form of a fingerprint sensor with a registered list of users. Once the device detects that it has been pickup (through the inbuilt accelerometer) it will require authentication and stays active until placed back down.

 

Future work on the project will focus on increasing the amount of data which can be shown and reducing the footprint of the device. For the former using a small 3.5-inch TFT LCD touchscreen instead of an LCD keypad would allow the graphing of FHIR data and enable more complex actions, such as recording a patient’s blood oxygen levels), directly to the FHIR endpoint. During the prototyping stage, the footprint can be dramatically reduced by switching to an Arduino Nano and a more precisely printed 3D box. This could allow the device to become wearable and fit into other data display applications in the hospital. At production the device could be made smaller still, with a custom PCB and micro-controller.

 

Ethan’s linked in profile can be found at: https://www.linkedin.com/in/ethan-wood-london/ with the full project on GitHub: https://github.com/greenfrogs/GOSH-FHIRworks2020-Display/ including technical drawings, code, and instructions. FHIR-Parser can be found on PyPy: https://pypi.org/project/FHIR-Parser/

 

%3CLINGO-SUB%20id%3D%22lingo-sub-1451387%22%20slang%3D%22en-US%22%3EUCL%20IXN%20%26amp%3B%20GOSH%20Azure%20FHIR-Display%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1451387%22%20slang%3D%22en-US%22%3E%3CP%3EFHIR-Display%20-%26nbsp%3BA%20dedicated%20secure%20IoT%20device%20for%20clinicians%20to%20view%20FHIR%20data%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.linkedin.com%2Fin%2Fethan-wood-london%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EEthan%20Wood%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EEthan%20Wood%20is%20a%20computer%20science%20student%20in%20his%20second%20year%20at%20UCL%20and%20as%20part%20of%20his%20course%20competed%20in%20the%20FHIR%20(fast%20healthcare%20interoperability%20resources)%20hackathon%20in%20the%20internet%20of%20things%20category%20building%20FHIR-Display.%20Ethan%20also%20developed%20FHIR-Parser%2C%20%E2%80%9Can%20elegant%20and%20simple%20FHIR%20library%20for%20Python%2C%20built%20for%20human%20beings%E2%80%9D.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOne%20of%20the%20problems%20when%20viewing%20patient%20data%20inside%20of%20a%20hospital%20is%20the%20trade-off%20between%20privacy%20and%20ease%20of%20access.%20You%20need%20key%20patient%20information%2C%20such%20as%20their%20name%20or%20medication%2C%20to%20be%20readily%20accessible.%20Currently%20this%20is%20in%20a%20printed%20form%2C%20close%20to%20their%20bed%2C%20so%20that%20clinicians%20can%20easily%20monitor%20lots%20of%20patients%20at%20the%20same%20time.%20This%20allows%20anyone%20with%20physical%20access%20to%20a%20patient%20to%20be%20able%20to%20read%20their%20medical%20records.%20It%20can%20also%20be%20difficult%20to%20keep%20track%20of%20patients%20when%20they%20are%20moving%20around%20different%20parts%20of%20the%20hospital%2C%20especially%20if%20they%20are%20out-patients%20and%20not%20easily%20recognised.%20Further%20to%20this%2C%20more%20in-depth%2C%20up%20to%20date%2C%20or%20complex%20information%20is%20held%20digitally%20and%20needs%20to%20be%20accessed%20via%20a%20computer%20or%20iPad.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20presents%20two%20problems%2C%20the%20first%20is%20how%20do%20we%20improve%20patient%20privacy%20while%20ensuring%20it%20is%20just%20as%20easy%20for%20clinicians%20to%20access%20the%20data%20they%20need.%20The%20second%20stems%20from%20the%20inherent%20difficulty%20of%20using%20a%20multi-purpose%20device%20(such%20as%20a%20computer%20or%20iPad)%20which%20traditionally%20encompasses%20a%20variety%20of%20different%20tasks%20for%20a%20clinician.%20When%20using%20this%20multi-purpose%20device%2C%20they%20end%20up%20needing%20to%20switch%20between%20different%20apps%20and%20services%2C%20logging%20in%20and%20out.%20As%20FHIR%20is%20integrated%20into%20more%20of%20the%20hospital%20ecosystem%20this%20situation%20is%20only%20likely%20to%20worsen%20with%20yet%20another%20system%20they%20need%20to%20connect%20to%20being%20created.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EThis%20is%20solved%20by%20FHIR-Display%2C%20a%20dedicated%20device%20for%20clinicians%20to%20access%20FHIR%20data%20about%20a%20patient%20in%20a%20secure%20environment.%20The%20idea%20is%20that%20all%20patients%20during%20triage%20are%20issued%20with%20a%20small%20RFID%20tag%20which%20contains%20their%20personal%20FHIR%20identification%20code.%20This%20can%20be%20in%20the%20form%20of%20a%20bracelet%2C%20key%20fob%2C%20or%20security%20tag%20depending%20on%20what%20is%20most%20appropriate%20for%20this%20particular%20patient%20(in-patients%20may%20prefer%20a%20bracelet%20if%20it%20is%20frequently%20accessed%20while%20for%20out-patients%20a%20key%20fob%20they%20can%20remove).%20RFID%20tags%20are%20very%20cheap%20and%20there%20is%20no%20risk%20of%20data%20leaking%20outside%20as%20it%20only%20contains%20their%20FHIR%20identification%20code%20for%20that%20specific%20hospital.%20When%20a%20clinician%20needs%20to%20see%20data%20about%20a%20particular%20patient%2C%20they%20place%20the%20FHIR-Display%20near%20the%20RFID%20tag%2C%20at%20which%20point%20the%20patient%E2%80%99s%20personal%20information%20appears%20on%20the%20screen.%20This%20also%20gives%20patients%20a%20feeling%20of%20control%20about%20their%20personal%20data%20with%20them%20being%20able%20to%20prevent%20someone%20they%20do%20not%20trust%20from%20looking%20at%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECurrently%20FHIR%20display%20is%20a%20small%20box%2C%20approximately%20the%20size%20of%20a%20phone%2C%20built%20from%203D%20printed%20PLA.%20It%20houses%20an%20Arduino%20Mega%20for%20the%20controller%2C%20an%20LCD%20keypad%20shield%20allowing%20up%20to%2032%20characters%20to%20be%20displayed%2C%20and%20an%20RFID-RC522.%20The%20RFID%20tag%20is%20read%20using%20the%20RFID-RC522%20through%20the%20PLA%20base%20which%20is%20designed%20to%20be%20thin%20enough%20for%20radio%20waves%20to%20penetrate.%20The%20device%20connects%20to%20the%20FHIR%20endpoint%20either%20over%20WIFI%2C%20Bluetooth%2C%20or%20serial.%20During%20the%20hackathon%20it%20connected%20to%20the%20FHIR%20endpoint%20via%20FHIR-Parser%20which%20aims%20to%20simplify%20the%20FHIR%20standard%20and%20allow%20projects%20to%20be%20built%20quickly%20without%20the%20developer%20needing%20to%20fully%20understand%20how%20FHIR%20works.%20This%20allows%20them%20to%20instead%20focus%20on%20the%20idea%20of%20their%20project%20and%20let%20the%20parser%20handle%20retrieval%20(ideal%20for%20short%20hackathons).%20However%2C%20in%20the%20future%20it%20will%20be%20possible%20to%20connect%20FHIR-Display%20directly%20to%20an%20endpoint%20such%20as%20the%20Azure%20API%20for%20FHIR%20with%20the%20ATmega2560%20more%20than%20powerful%20enough%20to%20complete%20the%20parsing%20and%20interpretation%20independently.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22FHIRDisplay.PNG%22%20style%3D%22width%3A%20685px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F197594i6EB3C5FC92047DC6%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22FHIRDisplay.PNG%22%20alt%3D%22FHIRDisplay.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhile%20the%20idea%20presented%20above%20simplifies%20access%20to%20data%20and%20helps%20prevent%20%E2%80%9Cyet%20another%20app%E2%80%9D%20on%20a%20clinician%E2%80%99s%20device%2C%20as%20of%20yet%2C%20it%20only%20improves%20security%20slightly%20by%20removing%20the%20need%20for%20bedside%20reports.%20However%2C%20anyone%20who%20has%20one%20of%20the%20devices%20is%20still%20able%20to%20access%20information%20about%20the%20patients.%20In%20the%20future%20this%20would%20be%20solved%20with%20some%20sort%20of%20biometric%20lock.%20This%20would%20most%20likely%20take%20the%20form%20of%20a%20fingerprint%20sensor%20with%20a%20registered%20list%20of%20users.%20Once%20the%20device%20detects%20that%20it%20has%20been%20pickup%20(through%20the%20inbuilt%20accelerometer)%20it%20will%20require%20authentication%20and%20stays%20active%20until%20placed%20back%20down.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFuture%20work%20on%20the%20project%20will%20focus%20on%20increasing%20the%20amount%20of%20data%20which%20can%20be%20shown%20and%20reducing%20the%20footprint%20of%20the%20device.%20For%20the%20former%20using%20a%20small%203.5-inch%20TFT%20LCD%20touchscreen%20instead%20of%20an%20LCD%20keypad%20would%20allow%20the%20graphing%20of%20FHIR%20data%20and%20enable%20more%20complex%20actions%2C%20such%20as%20recording%20a%20patient%E2%80%99s%20blood%20oxygen%20levels)%2C%20directly%20to%20the%20FHIR%20endpoint.%20During%20the%20prototyping%20stage%2C%20the%20footprint%20can%20be%20dramatically%20reduced%20by%20switching%20to%20an%20Arduino%20Nano%20and%20a%20more%20precisely%20printed%203D%20box.%20This%20could%20allow%20the%20device%20to%20become%20wearable%20and%20fit%20into%20other%20data%20display%20applications%20in%20the%20hospital.%20At%20production%20the%20device%20could%20be%20made%20smaller%20still%2C%20with%20a%20custom%20PCB%20and%20micro-controller.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEthan%E2%80%99s%20linked%20in%20profile%20can%20be%20found%20at%3A%20%3CA%20href%3D%22https%3A%2F%2Fwww.linkedin.com%2Fin%2Fethan-wood-london%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.linkedin.com%2Fin%2Fethan-wood-london%2F%3C%2FA%3E%20with%20the%20full%20project%20on%20GitHub%3A%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fgreenfrogs%2FGOSH-FHIRworks2020-Display%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fgreenfrogs%2FGOSH-FHIRworks2020-Display%2F%3C%2FA%3E%20including%20technical%20drawings%2C%20code%2C%20and%20instructions.%20FHIR-Parser%20can%20be%20found%20on%20PyPy%3A%20%3CA%20href%3D%22https%3A%2F%2Fpypi.org%2Fproject%2FFHIR-Parser%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fpypi.org%2Fproject%2FFHIR-Parser%2F%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1451387%22%20slang%3D%22en-US%22%3E%3CP%3EOne%20of%20the%20problems%20when%20viewing%20patient%20data%20inside%20of%20a%20hospital%20is%20the%20trade-off%20between%20privacy%20and%20ease%20of%20access.%20You%20need%20key%20patient%20information%2C%20such%20as%20their%20name%20or%20medication%2C%20to%20be%20readily%20accessible.%20Currently%20this%20is%20in%20a%20printed%20form%2C%20close%20to%20their%20bed%2C%20so%20that%20clinicians%20can%20easily%20monitor%20lots%20of%20patients%20at%20the%20same%20time.%20This%20allows%20anyone%20with%20physical%20access%20to%20a%20patient%20to%20be%20able%20to%20read%20their%20medical%20records.%20It%20can%20also%20be%20difficult%20to%20keep%20track%20of%20patients%20when%20they%20are%20moving%20around%20different%20parts%20of%20the%20hospital%2C%20especially%20if%20they%20are%20out-patients%20and%20not%20easily%20recognised.%20Further%20to%20this%2C%20more%20in-depth%2C%20up%20to%20date%2C%20or%20complex%20information%20is%20held%20digitally%20and%20needs%20to%20be%20accessed%20via%20a%20computer%20or%20iPad.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1451387%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Efhir%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHackathon%20Students%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ehealthcare%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIoT%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Elearning%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Jun 09 2020 08:51 AM
Updated by: