pApp allows doctors to easily create patient specific medical apps without coding knowledge

Post image for pApp allows doctors to easily create patient specific medical apps without coding knowledge

One of the recent developments to come out of the recent Doctors 2.0 conference in Paris was pApp.

The idea behind pApp is that it allows doctors and other healthcare professionals the ability to create mobile apps for their patients without any advanced coding knowledge.

The concept of the app is that healthcare professionals can select the functions necessary for the app which are then combined into a patient specific downloadable app.

pApp is based on a web platform which allows any user the ability to create a medical app and share it with the community.

Users can select from a range of bundles which are then combined into a unique app for a specific patient.

The advantage of this method is that doctors can simply create a one stop medical app which caters to specific patients needs. This would reduce the need for a range of medical apps for one patient. The ability for healthcare professionals to build patient specific apps  has potential implications for a range of areas including but not limited to:

  • Clinical uses
  • Data collection
  • Health promotion
  • Research
  • Patient Education

At this stage, the range of modules (functions) available is relatively limited and includes bundles that offer the ability to track medicines, cardiovascular, urinary as well as gastrointestinal symptoms. Each individual pApp runs within a mobile phone app which patients can put data into.

p

From a developers perspective, there is scope to link pApp to a range of other data sources given the back-end which uses the latest standards and protocols in healthcare to store and export data. This is coupled with API’s which offer the potential to link to wearable devices, sensors and other platforms.

The most exciting aspect of pApp is the fact that it is breaking down barriers for doctors to create mobile medical apps. As the feature set of pApp grows, doctors will be able to build more advanced apps with increased functionality. There is also the ability for healthcare professionals to access and note the data within each app remotely which would perhaps make telemonitoring and telehealthcare a more straightforward process.

36622778

At the moment, pApp is still in development and not on general release; however, iMedicalApps will continue to cover pApp and its potential to enhance patient centered medical app care.

Source: ScienceRoll

Discussion ( 12 comments ) Post a Comment
  • very interested about the potential of pApp on the elderly care market, I operate three care centres at the moment and have ideas about what we could/should be monitoring daily with our residents. would be happy to talk to anyone and share my thoughts.

    regards

  • I would prefer to read reviews about mobile apps that are actually available. Reading the article from Science Roll it is not clear that this idea is not much more than that- in idea, or vapor ware stage. I think iMedicalApps should limit reviews only to apps that are available for download and use- hence the term application.

  • Very interesting,
    however it has been my experience that software engineering works better when you let the experts do the job that they were trained for. Physicians are the domain experts that provide requirements and Computer Scientist develop, test and maintain the software.
    Not that Physicians can’t write software, it is just more efficient.

    Jeff Brandt
    Chief Informatics Officer

    • The problem can often be that each expert is great in their own field, but do they listen to each other – my view (albeit limited) is that the software looks great & on demo is great , but often is not as user friendly as it should be. Patients need to be able to collect data for physicians to interpret & utilise – that is where the apps should be going – see Eric Topology. Regards David Walsh (physician)

  • Bringing app development closer to the stakeholder is always a good thing – they know their end user best. MobileSmith.com allows non-developers to create custom patient-facing apps without writing a line of code – and deploy them natively to iPhone, Android, and iPad with 1 click. Our clients are marketing (non-IT) people in major hospitals, making native apps themselves from scratch in as little as a couple of weeks.

  • Many people want mobile apps but think it is too hard to create them. Fortunately now there are quite a lot of useful online services which allow building apps without programming skills and in hours. I am using SnAPPii at the moment and really pleased I can feel like a mobile app developer and make apps on my own.

    • It is great when you find docs so interested in CS, however there are a lot of regulation that you need to know about before distributing your app to patients.

      Alexandra would you and your vendor of the app building software sign a BAA with your health organization (see OmniBus rules)? Are you confident that your PHI is secure? Does your app provide compliant audit trail information? Have you performed a standard risk assessment and are you prepared for an Audit?… If not, the fines can be up to $1.5m per year.

      Jeff

  • As a digital communications professional, I foresee serious complications with this idea. mHealth is ideally positioned to support (and enable) HCPs in engaging, encouraging and caring for patients; however promoting ‘off-the-shelf’ technology as a physician’s panacea is a little like prescribing aspirin for all. Technology frequently fails to serve simply because it’s not needed in the first place – innovation isn’t always the best way… With increasing demand for elderly patient care (in many Western and Asian countries), what looks attractive to the HCP can be seen as alien and threatening to the patient… And whilst there is scope for bespoke content here, there needs to be far greater emphasis on providing relevant functionality and secure operation. Processes that are safe from hacking and simple to operate – at both ends (patient and HCP) have real potential – but a single failure could have devastating consequences for patient, professional and practice. There are reasons skilled individuals elect to work in digital communications, largely creating unseen ways of making critical content work regardless of the individual demands of smartphone or tablet platforms. In addition to technological imperatives, laws surrounding not only patient confidentiality but telecommunications need to be fully acknowledged – a given with agencies like mine – before any application can be offered to the public. From back end development to front end visualisation, and each step in between, communication by app, email or print is a complex, creative and scientific process – in this case one that’s even more vital to perfect, as the purpose is so absolutely critical.

    Hugh Beardesmore Billings
  • I am a practicing physician and programmer for 20 years now, and I am a senior director at a company that runs community based emergency care centers. We have a proprietary EMR that has been in continuous use and development for over 10 years.

    I am very interested in your product. It could definitely help us quickly build apps that would be used not only by our patients but also by our doctors

    Thank you
    Dr Nahum Kovalski
    http://www.terem.com

  • What other platforms and/or tools are out there for physician non-programmers to build usable software? So far we’ve heard of pApp, MobileSmith, please cite more.
    –JS

Comment on this discussion

Your email is never published nor shared.