Implementing Patient Passports

Implementing Patient Passports

Asking “why” questions during an IT's discovery process or business requirements gathering of healthcare IT would lead to the conclusion that individual patients should be required to have an information or "patient passport".

Last year, the “Patient and Family Engagement Action Team” came up with a paper form of a “patient passport” and there are some startups trying create a useful electronic version and pilot programs, such as Planetree. But the issue is how to convince healthcare systems to connect and use it has an actual passport, beyond a disconnected paper or electronic book concept.

For example, when hospitals refer a patient to a specialist, the specialist’s office software is still most likely different from the hospital’s system. This means that the content and information sent with the patient loses its context. The information is sent to the specialist in the form of paper, email attachments, faxes, website forms, etc. However, the content needs to be reconnected to the patient’s personal and health information. This process of reestablishing a patient’s information passport is usually (still) accepted as unavoidable. But, this is an example of when/where “why” questions should be asked:

  • Why should the referral of a patient to another institution be grounds for wiping out that patient’s information continuity?
  • Why are there still barriers to sharing at least the core patient information from one health system to another?
  • Why is information security still an issue in healthcare systems?
  • Why doesn’t the state have a patient information passport which, like a driver’s license, holds that patient’s vital information, healthcare history, prescriptions, allergies, etc.?
  • Why do we have to sign HIPPA agreements over and over again?
  • Why do health insurance companies accept this information disconnect?

Like traveling across international borders, patient should have the ability to prove who they are, what health issues they have, and how to access their medical records. This would all be based on the currently silo'd healthcare information exchanges and "gateways" out there, to once and for all, give patients a universal identity which, like a passport, ensures their information access and security.

Sources:

To view or add a comment, sign in

More articles by John Webber

  • Minimal Viable Product: Not So Minimal with OnBase

    Last last few projects I have worked on have applied Minimal Viable Product (MVP) to Hyland OnBase software…

  • Some Challenges of a Solution Developer

    All software-based solutions have edges, or limits, which constrain it to be applied to specific business problems…

    2 Comments
  • A Content Management Kludge

    Wikipedia defines a kludge as "a workaround or quick-and-dirty solution that is clumsy, inelegant, inefficient…

  • The Value of UAT

    When your company's IT department is big enough for a devoted QA team, the quality of your project deployment gets a…

  • Chief Dot Connector (C.C)

    In your IT department, there are certain people who know who to ask to get things done. That person who gets things…

  • Learning from a Junk Drawer

    Everyone has a junk drawer. If you open it up, you find the items that defying categorization.

  • Content Management Experts: Bringing It All Together

    When you see a content management project, what are you thinking? What the business sees The business goal is simple:…

  • Starting IT Fires and Putting Them Out

    In Ray Bradbury’s Fahrenheit 451 dystopian novel, firemen find homes with illegal books in them and start fires to burn…

  • It’s How You Use ECM

    “Its developers made it so convenient to use, and continue to make it simpler and more convenient, by watching how…

    1 Comment
  • ECM Solution Review Toolkit

    The following matrices and checklists will hopefully help prompt a comprehensive solution review. The purpose of the…

    3 Comments

Others also viewed

Explore content categories