vci091812

Moderator: At this time, I would like to introduce our speakers for today, Neil Evans, MD, and Deyne Bentt, MD. Dr. Evans is the Associate Chief of Staff for Informatics and Co-Chief of Primary Care at the Washington DC VA Medical Center. He holds faculty appointments at the George Washington University School of Medicine and the Uniformed Services University of the Health Sciences. Dr. Bentt is the Assistant Chief of Anesthesia and the Assistant Chief of Informatics at the Washington DC VA Medical Center. Without further ado, may I present Dr. Evans and Dr. Bentt.

Dr. Neil Evans: Thanks, everybody, for joining us today. We are excited to talk to you about the VA’s efforts in Provider-Facing mHealth. And as many of you are probably aware, mHealth is really considered a subset of eHealth. It is the use and delivery of – the use of mobile devices to promote health supporting both patients themselves as they manage their own health, and the healthcare team as they partner with our patients in delivering healthcare.

As was mentioned, both Deyne and I are here at the Washington DC VA and we are just going to dive right in. And again, we are more than happy to take questions at the end. We are hoping to leave about 15 minutes at the end for questions. And so be sure to submit those as you are just – as just described and we would be happy to get to those.

Just to get a sense for the audience, I am first going to go to a poll question. Let me – there we are. So this first poll question is a question of actually who is here. Are you a VA healthcare provider, a healthcare provider from outside the VA, a research professional, an administrator, an IT professional, or otherwise? And go ahead and select one at GoToWebinar.

Heidi Schleuter:And responses are coming in. We are at about 79 percent right now. I will give it just another second or two and then I will show the results.

Dr. Neil Evans:Excellent.

Heidi Schleuter:And there we go. 

Dr. Neil Evans:Okay. So it looks like many of you are research professionals and we have some VA healthcare providers, some administrators, and IT folks. So folks from across the spectrum. That is helpful for us. And here is our next poll question. Do you own a smartphone? ... There is – a yes or no question. Do you own a smartphone?

Heidi Schleuter:The answers are coming in really quick. Give me just a second and I will show that here. ... There you go.

Dr. Neil Evans:And there we are. Seventy-seven percent of you own a smartphone and 23 percent do not. And as you are going to see, that falls right along the national data. So we in the VA are apparently like everyone else. Let us move to our third poll question. Do you own a tablet, either an iPad, a Kindle Fire, an Android tablet or something of that sort? ... And again, the questions are yes and no. ... And ...

Heidi Schleuter:And there you go.

Dr. Neil Evans:Go ahead. So 67 percent own a tablet and 33 percent do not, which also is right along the lines of the national data. So that is great. Well, let us take a look at that national data. We are going to go ahead and go back to the slide presentation. And what we can see here is that in a study in a research – in a survey, I am sorry, in May of 2011, this was less than a year after the iPad initially came out. In that survey of 2000 U.S. physicians, 30 percent of U.S. physicians owned an iPad and 28 percent of physicians planned to purchase one in the next six months. And in addition, 81 percent of U.S. physicians owned a smartphone at that time. And from our brief, informal survey of the audience here for this presentation, 77 percent of you owned a smartphone, so again pretty close. 

Just one year later in May of 2012, Manhattan Research surveyed again a collection of U.S. physicians, this time 3,000 U.S. physicians, and tablet use had increased up to 62 percent of physicians. So if you recall from the prior slide, 30 percent owned one and 28 percent planned to buy one. And in fact more than 28 percent in the end did buy a tablet over that year. So tablet use made its way up to 62 percent of physicians.

And what is very interesting is that 50 percent of tablet-owning physicians of those 62 percent reported having used those at the point of care in the context of caring for patients—a very high level of use. And in addition, smartphone use remained very high in the mid-80 percent amongst U.S. physicians.

In this – in a context of this degree of use of mobile technology, smartphones and tablets, and the knowledge that this is something that the healthcare market – that is, practitioners within the healthcare system are using, the VA Innovation Initiative put forward a proposal to our industry partners to say can we partner together as part of the Innovation Issue which you see described here, the purpose of the Innovation Issue on the slide, to begin to investigate our ability to securely deliver VA-specific information to mobile devices. In particular, information from our electronic health record—patients’ personal health information—to the – to mobile devices. And this was in late 2010 that the VA Innovation Initiative put this proposal out.

And a company called Agilex, a contractor with the U.S. Government, won that innovation competition—there were many companies which submitted proposals—and began working with us here at the Washington DC VA as well as with some of our partners in the Office of Information Technology, OIT. From January 2011 through December 2011 to pursue a pilot to work through the goals that you see listed here. 

First, can we figure out a way to allow successful use—and in this initial pilot the plan was simply to concentrate on one platform, in this case the iOS platform, not Android. I will talk about Android a little later in this presentation. Could we work through the security issues to allow use of iOS devices within the VA environment. 

And assuming that was possible and we were able to get these devices in the VA environment in a way that met VA security requirements, could we then develop an application to allow display of selected patient data from this electronic health record on mobile devices?

Could we develop a prototype VA App Library? Apple prohibits anyone else from using the term App Store, so library is a synonym. And since VA Apps would not be purchased by their employees, it makes sense to be a library rather than a store.

And then to run a pilot using iOS devices and the patient viewer app as well as the library at the DC VAMC.

So this is our goal. And this is the main purpose of today’s presentation is to talk to you about the results of this innovation project that was run last year; and then briefly to talk about future plans as we move forward in the field of mobile health in the VA. 

So our vision for – and the reason this project was even started was that the VA desires to embrace innovation and mobile health. We recognize that among US physicians, again 50 percent of US physicians have used their tablet device at the point of care, that is, taking care of patients.

And so we know that our staff members want this technology. We know that patients want this technology as they interact with us in the healthcare system. And we would like to embrace that and move forward. We have been a leader in the electronic health record space and we would like to remain so in the area of mobile health.

By providing this information on a mobile device, we are going to improve the ability for VA – the hypothesis – our vision is that we would be able to improve decision support and improve the ability for VA clinicians to access the data they need at the point of care as well as to improve our ability to interact with veterans and for veterans to access information about their own healthcare and benefits.

I am going to come back to this slide a few times to talk about the value of mobile smart devices to improve workplace productivity. And this is a – sort of a four-stage approach to how mobile devices can actually help improve productivity. So the first level is simply that if you have a smartphone in your pocket, you by definition have Internet access in your pocket, which gives you a resource, allows you to access Google or just find something on the Internet itself.

The second level of increased productivity is allowing you to connect securely to your own email or communication technologies, to be able to text message and communicate with other individuals with whom you are working.

The third level are private applications – I am sorry. Well, applications developed in the private sector, various useful applications that bring resources to the provider or the patient that they might find hard to find simply through an Internet search, but that when collated in an application that is designed and optimized for the platform—that is touch optimized—allows them to access resources. 

I want to give you an example of a resource we have here in the VA that fits perfectly in this third level. This is providing, for example, to the clinician access to an application with a medical database or a pharmacology database on their device so that information is readily available and they have a trusted source of that information in a way that is optimized for use in that touch environment on the tablet or a smartphone.

But the fourth level, and really the focus of this pilot, was to say, can we securely give access to VA-specific applications and data. And to make the mobile device, tablets or smartphones, tools that can be used in people’s daily work taking care of patients.

In order to get anywhere close to these four levels of maturation, we first had to sort out the security issues. How would we provision and configure the devices? What were the profiles that needed to be set up on the devices? How could we assure that these devices were managed appropriately? What could we do to be able to track a device if it was stolen and to enforce VA policy, for example? So a considerable portion of the pilot was spent working through these issues and testing out our security.

And we considered security in two ways. First, the security of data as it was in transit and then in the next level we will talk about the security of data as it is at rest.

Data, including personal health information that we were delivering to mobile devices, was always encrypted, often triply encrypted, sometimes singly or doubly encrypted, in transit. This is a little bit of an overwhelming slide, but for some of you, maybe IT professionals, I just wanted to give you just a quick snapshot here in this presentation of the architecture of the system that we were able to set up.

And you will see here we have what is called the iHealth Adapter. The iHealth Adapter simply made RPC calls to Vista and then during the pilot exposed that data to the mobile device through an encrypted tunnel via RESTful Web Services. We also tied in with the Exchange Server to be able to deliver email and calendar functionality and delivered all of that again through encrypted connection. And the encryption varied whether the provider was actually connecting to our internal wireless network within the hospital or whether they were connecting through the VPN one outside of the hospital, for example.

Also, we needed to consider the encryption of data at rest. And briefly the data was always encrypted at rest on the device itself. And in fact the personal health information data that we delivered to the patient viewer app that you will see actually never rested on the device. It did not reside there. When the application was closed or the iPad turned off, basically put to sleep, any of the personal health information which had been loaded into the application was wiped. And we tested that extensively to make sure that there was no personal health information that could be recovered from the device itself.

Email was secured through a program called GOOD which provides us a FIPS certified encryption wrapper for email. And in fact, all of the iOS devices are encrypted themselves. That is not yet FIPS 140-2 certified, but the encryption definitely is there and Apple is pursuing FIPS certification for their devices as well. The fact that did not exist meant that we had to make sure that we did not store any personal health information on the device, however, to be in compliance with federal regulations.

So right now I am going to go ahead and turn things over to Deyne. Deyne is going to begin to take us through a – he is going to walk us through a demonstration of the patient viewer app that we developed, starting here actually with the enterprise. We initially called it an app store, but as I mentioned before, it is now called the App Library. Which really shifts the paradigm. It is just a way we can deliver VA-developed software in a way that a provider can simply update it with a single click similar to just the app store model that both Apple and the Android platform have. And this is the first part and we will go here. You will see over there in the lower left the patient viewer, which Deyne is going to now talk about, how that was developed, and he will take you through. 

This was actually – this demonstration to allow us to show it to you – on the – on this webinar is actually a simulated app of the app that is running both here on both Deyne’s iPad and my iPad as we go through it. But you will see the simulation and we will be happy to answer any further questions, again, at the end of the presentation about it, if you have it. So let me hand things over to Deyne.

Dr. Deyne Bentt:Good afternoon, everyone. And as you can see, the application looks like any other app that you might find on the screen of the iPad or iPhone. And when you click on the app you will [laughter]  ...  hold on one second.

Dr. Neil Evans:Yeah. I forgot I was going to mention this. Anyway, thanks for handing the phone back, Deyne. I – before we get – this is the app store. I wanted to just talk about briefly about that third level of care. I forgot I had inserted these slides in here. This is just – this is a decision support tool called VisualDX. For any of the VA healthcare providers who are in the audience, I strongly recommend use of this tool. It is an outstanding visual clinical decision-support tool which allows you to build differential diagnosis of visual findings in medicine. Dermatologic findings, oral mucosa findings, et cetera. 

The VA, through the VA Library Network as well as Patient Care Services, has a national contract and this iPad and iPhone app is available for free for any VA healthcare provider. You just have to access VisualDX at www.visualdx.com through a VA computer and there’s a link there once you have logged into the app – once you connect into the app to say that you would like them to send you a code to access the mobile app.

But this is an example of that third level of support. This is an application that is a third-party application but available to VA providers, a resource that gives them essentially a massive dermatology atlas that is far larger than any paper dermatology atlas would be in their pocket, as well as a clinical decision support tool to pull up multiple images and actually search based on clinical findings for images. And so again, that is an example of this third level of access.

The application that Deyne is going to show you is our delivery of VA-specific data. So I will now hand the phone back over to him.

Dr. Deyne Bentt:So this would be a typical screen on an iPad and clicking on the Patient Viewer application, we will get to the log-on screen, which asks for an access code and verify code, which is exactly the same authentication information that a VA employee would use to access the CPRS while within the hospital or remotely.

So here is an example of an access and verify code, and once you hit enter, it takes you to the Patient Search Screen. On the top left you will type in Smith, for example, which will return 20 matches for Smith. And if we choose the first patient, that will give you on the right side of the screen the summary view which includes some patient demographics. On the top right is also a photograph if available. And the other information that is retrieved for the Patient Summary Screen is a problem list, list of allergies, and the medications, which are separated into inpatient and outpatient and non-VA medications.

Looking to the left side of the screen you will notice there are four tabs. One is the magnifying glass. It indicates the search screen. The next tab, which looks like a head and shoulders, indicates the – takes you back to the patient summary screen. And the next two tabs, Rx, gives us a more detailed view of the patient medication list, which you can see has been displayed. If you click on one of the medications, that will – we have clicked on lisinopril. That will then give us the more details in the right pane including the full administration – prescription and administration information.

The section beneath the label medication details is exactly the same text one would see in the CPRS if one was to pull up the medication details there.

Going back to the left side of the screen, the tab that looks like a stock graph represents – takes you to the lab results. These are displayed – organized into sections. You can see that there is a CBC profile. There is also a chemistry profile. These sections are collapsible; but however, right now they are expanded and we have a display of the most current lab value in the left pane. So for the hemoglobin, we can see that the most recent value is 12.6.

By clicking on one of these lab values—here you can see that the hemoglobin has been selected—the trend, graphical trend of that lab value is displayed in the right pane. Looking along the top of the screen you can see that the timeframe can be selected from one day to one week to one month, one year or two years. Also all lab values for that patient. 

The normal range for the lab value is displayed graphically using the – on this screen you can see that there is a brown background spanning 10.5 roughly to 13.7. That background indicates the normal range for that lab value, which gives you a range reference when you get the graphical history display for each lab value.

The other functionality built into this application is that by touching the screen on the graph at any point will give you the discreet value for that laboratory test at that point in time. Here you can see that the screen was touched roughly on 10/9 of ’09 giving a value of 15.3 mg/dl.

You can also see two buttons on the bottom right of the screen indicating inpatient meds or outpatient meds. I will scroll backwards one slide. You can see that they are – neither one of them is selected in this slide. However, when the outpatient meds are selected, they are superimposed on the graphical display giving you the medications that the patient is taking listed in textual form and also the – a bar graph display of the start and stop times of the administration or prescription of these medications. So this would be very useful to rapidly give the ability to compare start and stop times for medications in relation to changes in laboratory values.

The pilot was run for a period of three months from September to December of 2011. There were 30 providers using 15 iPads and 15 iPhones and the metrics that we looked at were the technical performance of the devices, the usage patterns. And we surveyed the providers at four intervals, before the pilot started and then three other events during the pilot. We were looking for satisfaction, usability, and clinical impact.

This slide shows the performance details. In particular we are looking at the speed of retrieval of information. And we can see that in the initial part of the pilot, indicated by number one on this graph, we can see that the response times were fairly slow and that we are looking at 30-second response time for information from the patient record. That is obviously unacceptable for usability for clinical care.

However, the fault, or the issue was rapidly discovered to be located in the way that the RPCs were made, and once that was corrected you can see that in general the response times from 9/7/11 onwards were around the three-second or below—lower than three seconds—in time.

You can see that on the screen there are some spikes in the response time indicated by number two. These were all related to version updates. When a new version of the app was placed and downloaded, it required some form of additional time for initial use. 

The spike seen at number three was a technical failure on the server, which was rapidly corrected.

So you can see that with a response time of less than three seconds, that was considered very satisfactory by users and was completely in line with the needs for using this application by providers to access the patient information.

The next slide shows the data usage. Basically, what it shows is that the data and minutes usage increased gradually through the pilot. But the significant information to gain from this slide is that there was no extraordinary usage of data—meaning that the providers were using the application and the devices as intended, for patient data access, and not for – they were not incurring large data transfer statistics. For example, downloading videos or long-duration international calls or things such.

The next slide shows given an idea of the frequency of usage of the devices, the 31 percent in dark blue and 38 percent in light blue represent that the devices were used to access patient data at least once a day and up to five or more times a day. We can see that 23 percent of providers reported that they did not use the app or device every day, but at least once a week; and eight percent of users did not even use it once per week.

We polled device and network satisfaction. This slide indicates that any responses in green or blue show either somewhat satisfied or high satisfaction with the device functionality and network connection. 

We polled connection to the VA by VPN while on 3G, connection to the network by VPN while on Wi-Fi, the usability of the device as a touch screen input device, and the ability to become familiar with the device for those who had not used one before or had very little usage. So on the whole we can see that the large bars are green or blue, indicating that in most cases connectivity and usability of the devices were either – there was either a high or average or above-average satisfaction with the device.

We also polled application performance and using the same color scheme, we can see that in general the overarching satisfaction was either somewhat satisfied or very satisfied. And we polled use of the device for email access to access the clinical schedule, which was integrated with their Outlook Business Calendars and the ability to display clinical information on the device; the ability for the device to support effective workflow; the time taken for the screen to refresh; to upload data; using pharmacy application; using the lab application; and also for loading the patient summary. 

So in general the impact on healthcare delivery shows that the – we can see that the blue and gray bars are the predominant results in this poll. The first area polled was, did it increase your productivity. We can see that over 50 percent of providers said there was a moderate impact. We had the ability to share information with the patient, again overarchingly this is moderate improvement or moderate impact in this area. We had the ability to communicate with the patient, the ability to review important information—important patient information; the ability to communicate with other providers using the device and applications; and overall the ability to deliver healthcare. We can see that over 60 percent of providers said that this made a moderate impact in their ability.

So I am going to pass you back to Neil, who will talk about some of the Key Findings of the Pilot.

Dr. Neil Evans:That was fun. Thanks, Deyne. So as you just saw what Deyne just showed you, especially in this last slide, I think it is probably the most important slide of our results. And again this is just a survey of a limited number of providers; but we were trying to get a sense of people’s interest in it. And the fact that there is – everything is either neutral or positive with one exception suggests that people did feel that this did help them.

But we did need to tease that a little bit more about why was the impact as neutral or moderate? Why were some people feeling that this had a very large positive impact on their productivity or their ability to review patient information? And why were some feeling more neutral or moderate about it? 

And we ran several focus groups with our providers where we actually sat down with them and used the app and talked about their experience over the three-month pilot. And it became clear that the issue—one of the primary issues was that we were delivering through the application just a subset of the data that providers wanted to be able to use from Vista.

So as Deyne showed you, we were delivering laboratory results, microbiology results—well, we did not actually show you that, but those were being delivered—a problem list, allergies, demographics, medications including refill history. But we were not delivering progress notes or vital signs or imaging reports.

And so providers found themselves occasionally frustrated because they found the mobile device very useful. They were all very optimistic about its utility, having this information in their pocket and available to them if they were actually out on rounds or seeing patients in the home. We deployed these devices with home-based primary care providers, with Intensive Care Unit providers, with primary care providers, with nurses, social workers, physicians, nurse practitioners, basically we tried to have a sample size that was from across the spectrum of clinical care.

But regardless of the setting where they were, they would find themselves stuck at some point in time without data.

Now the people who were the most satisfied with what we delivered were people who were on call outside of the hospital where they would have had no ability to access anything else without an awkward interface, either having to try to log in through Citrix to their mobile device and it would take quite some time to get logged in and find the data, and then they would be trying to interact with CPRS, not a touch-optimized application, on a touch device.

Or they would have to – an example would be a primary care provider who was getting a call about an abnormal lab result and they were out to dinner. Or maybe like me at the playground with my kids and I would get that call and normally I am completely powerless to make any decisions because I do not know what the prior laboratory results are. I do not know what the patient’s phone number is. I do not know what medications they are taking. But when I have all that information now in my pocket on a mobile device, I can actually let the sliding and swinging continue as I deal with the issue that has come up based on this abnormal lab result. So folks like our home-based primary care providers and our primary care providers who are taking call outside the hospital who are very happy with the benefits.

But individuals who are trying to use it as a replacement device in the hospital, for example rounding on the inpatient wards, some of our inpatient hospitalists or in the ICU, were less enthusiastic because they found themselves getting halfway down the path to the data they needed and then having to turn off the mobile device and turn back to the laptop bolted to the cart or the PC on the workstation at the nursing station. 

So that led to that third key finding, give providers access to some data and they will immediately want it all.

And the other key findings were the touch-enabled devices deserved touch-optimized apps, that is the data was available to providers on the iPad, for example, and later in the pilot on the iPhone when Citrix, released their updated application to allow iPhone use. They could get to all data through CPRS, but that interface was not considered acceptable for on-the-go use.

It was clear that folks wanted these applications to interact seamlessly with the electronic health record. They wanted quick delivery of data, the ability to find what they wanted quickly.

The other thing we learned in our pilot sessions were that there are no – there is no limit to ideas for niche or focused apps. For tasks that we do in the medical center all the time, over and over again, for which an application on a mobile device would be a perfect setting—for example, an influenza vaccination application. An application to allow us while we are running our big flu vaccine campaigns, which are all about to kick off, to welcome patients to the atrium of our hospital, sign them in right there on the device, provide them education that they need, and then seamlessly document the administration of the vaccine and have that go right back to VISTA, all from one device.

It would be a great opportunity for a niche or a focused app. And there is a lot of interest in developing those.

So that is really our experience in the pilot. People were enthusiastic about using these mobile devices at the point of care, but recognized that we had made, over the course of really six months of development that these applications, a lot of progress. But there was still more that needed to be done. So that leads us to the next question.

That is, what is next?

Well, the answer is that there is a lot that is next. The first is, let us think about this from the perspective of both VA providers as well as for our patients.

We know that chronic disease trends are shaping the way we are going to have to deliver healthcare in America. Chronic disease spending comprises a huge proportion of the amount of money we spend every year on healthcare. It is not news to anybody on this call or at least working in the healthcare environment that the incidence of diabetes has been increasing, obesity and other chronic diseases.

And in the context of this increase in chronic disease, we have the mobile phone, which has become the biggest platform for change—the biggest platform from an IT perspective—in the history of mankind. There are more than 1 billion 3G subscribers today in the world, expected to be 2.8 billion by 2014. And cell phones are by far the number one global computing device, certainly beyond computers, laptops or anything of that sort.

And so mobile health allows us to reach veterans at a level before even they have found their way into our facilities. It is an engagement model for healthcare, not a treatment model. So on the veteran-facing piece, we are really enthusiastic about being able to push forward with some development that will allow us to really meet veterans earlier in their disease process. Or earlier, before they are even aware of a potential disease to help intervene in some of these chronic conditions to helping manage weight issues and health issues and diet issues much earlier in the game than when patients typically end up in our clinics.

It is certainly understood that this is not just the VA who is interested in doing this. Global Smartphone mHealth Apps have increased by a factor of seven in just one year. If you look on the app stores, there were on the order of a hundred apps and now – I am sorry, $100 million spent on smartphone mHealth apps and now there’s over $700 million spent on it.

So the idea is that we would like to deliver care for our patients that is personalized, convenient, that is on the mobile device that they have that is coordinated and accessible.

And very soon a pilot is going to kick off that is the VA Caregiver Mobile Health Pilot. A thousand of the caregivers enrolled in the family caregiver program. There are approximately, I believe, between 4,000 and 5,000 people enrolled in that program. But 1,000 of them will be given preloaded iPads with the VA Mobile Health apps, which are currently in development. And a research study will be done as part of that pilot evaluation to inform our next steps in patient-facing apps.

And I just thought I would give you a quick preview of some of the apps that are being developed, since this is a natural follow-along to the pilot that we have been talking about for the bulk of this presentation.

Here is an application that allows patients to see that very same data, data from their electric health record delivered directly to them.

Here is a journaling application to allow patients to monitor on their own device their own blood pressures, vital signs, exercise, diet and the like.

And here you can see how they are able to enter those vital signs and track them over time.

Here is a prescription refill application to allow patients on their mobile device to process prescription refills.

And here is an application where we as VA healthcare providers hopefully will soon be able to deliver reminders and notifications directly to patients from our system to theirs to remind them of certain things.

There are several other applications. Of course there are very well recognized PTSD app that has been developed and is actually out on the iTunes app store. There is a pain management app and many others to secure messaging client, to Connect to My Healthy Vet, Secure Messaging from mobile devices, that are all part of that pilot.

There are further plans that host this in the cloud to make it accessible to veterans so that they can access all of their VA information regardless of what facility they have been to. Those will be a consolidated view from all facilities. And also to allow all VA staff to begin to access these resources. Currently the pilot is only functioning at Washington, DC, but there are plans in place to push this out to several more pilot sites and then nationally. Also to do cross-platform development using HTML5 so that we can display these on Android devices, Windows, phone devices and others.

There are several other provider applications that are going into development, that are planned, that are here at the end of this presentation which you are welcome to review. These are plans that are not yet in place but where planning is occurring that hopefully in the next several months there will be forward movement in developing some of these. These are just examples of functionalities being considered: the ability to look at vital signs, progress notes, to expand secure messaging, to allow providers to access secure messaging on mobile devices, to manage orders, to start right back app—at the moment it is read only—but to explore the ability to actually write progress notes from the app or place orders from the applications on mobile devices and customize use, et cetera. You can see all those listed here on these slides.

So that is kind of a whirlwind tour through the future plans, but since the main purpose of this presentation was to talk about our experience in the pilot of providing this data to providers, but I wanted to give you just a preview of what is to come as well at the end of the presentation. So we would be happy to take any questions now.

Heidi Schleuter:Great, thank you so much. There are a few questions from the audience. The first two questions are specifically about the app and the graph you were showing with the modifications and the question is, are you able to zoom in on the graph for closer looks?

Dr. Neil Evans:Yes. So you are able to zoom in on the graph for a closer look. You can actually – I can strain the graph based on – at the moment based on how much data you want to pull back. You can see here actually this is the patient graph, which is through the next iteration we are going to be releasing this in the provider app soon. You can look at it back just one month, one year, two years or all; and we will be setting up a custom date range as well so that you can zoom in on any particular location.

Heidi Schleuter:All right, thanks. Another question regarding the graph when you were superimposing the medications, does the graph display the daily dose of medications?

Dr. Neil Evans:No. The graph does not. When you superimpose medications, it does not currently display the daily dose. We are hoping in further development to actually be able to deliver this laboratory data in different ways that providers might view. We have been meeting with providers and also working and making plans to do usability testing to determine – this is a different display than providers are used to in CPRS and so determining the best way. One thing we that  definitely are committed to developing is a tabular view of data. This what you are looking at right here is a graphical view, obviously. And then to consider ways to integrate unique views like this, a super imposition of the medications. To be honest with you, actually, in the pilot that the providers did not find the ability to look at medications over top of lab results to be the most useful feature and did not – the providers in the pilot did not feel like that was something that we should spend a lot of time doing further development on. They actually were more enthusiastic about being able to see essentially a custom worksheet view of lab data.

Heidi Schleuter:Okay, great. Thank you. Okay. Quite a few other questions have just come in. Will there be any apps or tools for patients that will work on feature phones, or will they have to have a smartphone?

Dr. Neil Evans:This is a very good question. At the moment they will have to have a smartphone and I do not think that it has really been – one of the issues is that we have to be able to effectively secure the device to be assured that patient data that is delivered to these devices can be done so in a secure fashion. And there are some architecture issues that the smartphones bring to the table that allow us to do that, that I suspect would not be as easy with feature phones. And that leads naturally to another question of, if this is going to be available to providers, what is the VA’s strategy going to be about these devices? Will they adopt a bring-your-own device policy, as many private industries have done where providers who already own a smartphone or already own a tablet are able to bring that in, install some software that allows the VA to secure or assure that the device meets our security requirements but use their own device? Some companies actually provide a subsidy to their employees to go along with that. And for some employees they may have provided them with a device otherwise and now the employees bring their own device and securing it. Or will the VA require that these applications be used on VA-owned devices? And that has not really been worked out. And I am not the person to ask that question.

Heidi Schleuter:Okay, great. Another question. Do you have an automatic fail over process to input is to prevent or minimize data loss?

Dr. Neil Evans:So there are several answers to that question. The first answer is the Personal Health Information never resides on the device, again. So it is delivered in an encrypted fashion. As soon as this application is closed and you move to another application, it wipes all of the data that was loaded on that patient. And we have tested that extensively. There is no recoverable data of personal health information data on the device. So if, in fact, the device were lost, an individual would not be able to recover patient-specific data from that device.

Furthermore, these devices are all secured by what is called Mobile Device Management software. This allows us to know the location of the device, if we choose to look for it, through the management portal, also to remotely wipe the device. A mobile device, if it is lost for example, and it gets confirmation that it has been fully wiped. And also to enforce certain policies that the VA has put in place with regard to mobile device security including passcode policies. So for any of these devices, a complex passcode is required to access or even get into the device. If you enter that complex passcode wrong ten times in a row, it wipes the device regardless. So there is an awful lot of security in place that would make it basically impossible for somebody to – and of course there is never a bother. There is always some kind of risk. But we are taking it with IT security. But again the mobile device management enforces complex passcodes and has a remote wiping policy if somebody is trying to get in who should not be getting in. If the device is lost, we can track it to recover it. But we can also remote wipe it and then the general security does not allow data to rest on the device.

Heidi Schleuter:Great. It does look like we are at the top of the hour right now. There are quite a few questions left if you do not mind if I forward them to you for some answers so everybody else gets their questions answered.

Dr. Neil Evans:Sure.

Heidi Schleuter:Great. So I would like to thank Dr. Evans and Deyne for taking the time to develop and present this talk. And if you have any remaining questions, please forward them to VIREC’s help desk, VIREC@va.gov, and our next session is scheduled for Tuesday, October 16 and the topic is “A Patient-Centered Approach to Improved Screening for the Metabolic Side Effects of Second-Generation Antipsychotic Medications.” Thank you again for joining us.

Dr. Neil Evans:Thanks a lot.

Dr. Deyne Bentt:Thank you, everyone.

Heidi Schleuter:Thank you, everyone, for joining us and we will see you at a future HSR&D Cyber Seminar. Thank you.

Page 1 of 13