EMS Insider, Healthcare Reform

Healthcare Information Technology & Healthcare Reform


Much has been written about the healthcare reforms contained in the Affordable Care Act, and the ways in which EMS and mobile integrated healthcare can incorporate those changes into their delivery systems. But one thing which has not been discussed much in the EMS and mobile integrated healthcare field is the role and requirements of information technology in the global vision of healthcare reform.


The ultimate goal of healthcare reform is to create a seamless, universal, interoperable electronic record system. This means that if a patient from one place has a medical emergency in another location, the healthcare providers at that location will be able to access the patient’s full medical record—in real time—and thus, treat them more appropriately and effectively. Not surprisingly, there are many obstacles to achieving this goal, including privacy and security, interoperability, differing data dictionaries, intellectual property concerns, consumer acceptance and cost.


By now, most EMS providers are moving in the direction of electronic patient care records (ePCRs), but few are aware of the real reasons behind this move and the greater implications for healthcare reform compliance. Most agencies see ePCRs as a way to collect and compile data, and there has been much discussion about using data to prove your agency’s worth to payers and other third parties. So what are the benefits of this new technology, and what considerations do you need to take into account when adding, changing, upgrading or replacing health information technology?


Meaningful use


In 2009, Congress passed the Health Information Technology for Economic and Clinical Health (HITECH) Act, which authorized incentive payments to clinicians and hospitals through Medicare and Medicaid for using electronic health records (EHRs) to achieve specified improvements in patient care. The incentive payments total up to $27 billion over 10 years, with the ultimate goal of creating a nationwide system of EHRs.


However, HITECH’s goal is not just the adoption of EHRs, but “meaningful use” to achieve significant improvements in caregivers’ decisions and patient outcomes. The regulation spells out what healthcare providers must do with EHRs to be considered meaningful users, including the entry of basic data such as vital signs and demographics, active medications and allergies, up-to-date diagnoses, smoking status and adult weight screening. There are also requirements for the use of clinical decision-making software applications designed to help caregivers make better clinical decisions and avoid preventable errors. Finally, the meaningful use requirements also include providing patients with electronic versions of their health information following treatment and office visits. In short, meaningful use is designed to be a universal minimum set of required data points to measure value and quality, and the rule is part of a larger set of regulations designed to move the health system in a positive direction toward improved quality and effectiveness in healthcare.1


Unfortunately, since some of the meaningful use data points are not things EMS providers have traditionally asked of or provided for patients, some of the care requirements are not even on the collective EMS radar (let alone built into ePCR systems). But as our nation’s healthcare system moves from a fee-for-service to a fee-for-value model, meaningful use standards and rules will have significant implications for EMS and mobile integrated healthcare providers, especially in light of healthcare reform initiatives such as community paramedicine.


As EMS evolves and expands its role in the healthcare system, meeting meaningful use standards may very well become a requirement. For example, accountable care organizations (ACOs), health systems and other payers will probably require compliance with meaningful use standards as part of payment contracting terms. Community paramedics will likely be required to ask additional questions of patients related to smoking cessation and weight gain/loss during each visit with the patient. For example, community para-medicine programs that are able to bill their state’s Medicaid program will have to record the answers to these types of questions in patient care records, since they will be eligible for receiving reimbursement based upon the quality of care and value they provide, which is measured by the meaningful use standards. It is also foreseeable—as ridiculous as it might seem—that an ACO or payer may require an EMS service to ask the same questions of trauma patients with severe injuries, simply because that is the standard the payer requires from their contracted entities.


Furthermore, if your EMS system is hospital-based, you will almost certainly have to ask meaningful use questions, especially in the case of refusals/treat-and-release situations, and be prepared to provide information, such as discharge and follow-up instructions, to patients out in the field. Remember that under the Emergency Medical Treatment and Active Labor Act (EMTALA), the patient “has come to the emergency department” when they set foot inside your ambulance because the hospital-based EMS unit is deemed an extension of the emergency department. If a patient is refusing transport—or is being treated and released on scene—as an extension of that emergency department, EMS personnel must comply with the same meaningful use standards that the hospital would if the patient were actually transported.




As discussed above, one of the ultimate goals of healthcare reform is to create a nationwide system of EHRs based on the idea that global access to a patient’s medical records will result in better quality, better outcomes, better value and lower costs. To achieve this vision, there must be interoperability.


Interoperability is the concept of diverse software systems, platforms and computer languages all being able to share data. Eventually, all of a patient’s healthcare providers will be able to access the patient’s medical records, regardless of where, when or with what software those records were created.


Aside from the complex technological issues of developing interoperable health information technology, there are other practical obstacles to overcome. For example, a number of EMS agencies have already encountered resistance from hospitals and health systems in their area when they have asked for permission to upload their ePCRs into the hospital’s EHR system or have their quality assurance (QA) manager be granted access to patient charts for follow-up, research and feedback. The hospitals have expressed concern about security and privacy issues, which is understandable; an outside third party over which the hospital has little to no control accessing protected health information (PHI) contained in the system is a scary proposition. As a result, many hospitals do not allow outside healthcare providers to access or upload directly to their software systems.


In addition, the EHR systems used by most hospital systems were not designed with EMS in mind. Likewise, the ePCR systems in use by many EMS agencies were not designed with hospitals and physician practices in mind. As discussed in the December 2012


EMS Insider article, “The Changing Face of Medical Reimbursement: A Difficult Road Ahead for EMS?” EMS agencies and ePCR vendors need to take the lead on this issue; otherwise hospitals may end up dictating which software healthcare providers in their network can use and the results could be extremely costly for EMS agencies. The good news is that a number of the larger ePCR vendors are already developing interoperability tools, but EMS agencies need to get to the table and control the conversation with the hospitals and health systems in their area so they are not forced to switch to an EHR system that was not designed for the EMS environment.


Privacy & security


As discussed above, one of the problems with interoperability is concerns regarding privacy and security of PHI contained in EHR and ePCR systems. Much has been written and will continue to be written about the privacy, security and breach notification requirements contained in HIPAA, so we won’t belabor the point here. However, EMS and mobile integrated healthcare agencies are well advised to think long and hard about the process and procedures for implementing new technologies and maintaining legacy data and information within their own systems; securing and auditing electronic devices such as laptops, tablets and medical equipment that contain patient information to prevent theft, loss or hacking; and developing strong device policies regarding the prohibition or use of personal electronic devices for job-related functions.


Other considerations


If all of this sounds like just another headache to add to the already overwhelming list of healthcare reform changes, here are some recommendations to make things run more smoothly for your agency:


• Think big, start small, move fast.2 It’s easy to fall into the trap of focusing on one particular piece of technology without thinking about how it will serve the agency in the long term. Whether it’s a new cardiac monitor, a new pulse oximeter or glucometer, or new ePCR software, it’s important to think strategically and approach each new implementation with an eye toward the “big picture.” In other words, how will this technology grow with us over time? What are its larger capabilities beyond what we plan to use it for right now? Will it be something that needs to or is able to interface with other electronic systems or software and, if so, what are the limitations, obstacles and benefits?


• Don’t be overwhelmed by the idea that you have to have every system or piece of software in place today. Implementation takes time, and begins one piece at a time.


• Don’t jump into new technology without doing proper research and due diligence. On the other hand, don’t get bogged down spending so much time analyzing and researching one item that you fail to move forward.


• Set realistic goals and timelines, do your homework, then move forward. Remember, technology is already outdated as soon as it hits the market, so taking too long to make decisions may mean that you have to start over again if you take too long.


• Have solid policies and compliance and audit systems in place before you add, change, or upgrade anything.


• Protect legacy data and be mindful of vendors who may go out of business or stop supporting current technology. The cost of migrating data from old to new systems is high and the process is time-consuming. Patients (or their lawyers) may request records in “native format” or at an inconvenient time for your organization (for example, while you are in the midst of lengthy data migration), yet you still have an obligation to provide the information upon request and in the form requested (provided the request is reasonable). Before doing anything that requires a data migration, talk with your vendor and come up with a plan that will allow you to meet all obligations seamlessly.


• Read up on HITECH and be prepared for meaningful use to come up in your discussions with ACOs and health systems. At a minimum, they will probably ask about your system capabilities for compliance and information gathering, and it is highly possible they will require compliance with their technology and meaningful use standards as part of a contract for services and/or reimbursement.


• If you are designing a home-grown database for your community para-medicine initiatives, incorporate as many of the meaningful use data points as possible at the outset. For software vendors, as you design and build interoperable ePCR/EHR software, plan to incorporate the meaningful use data points.


• As you implement new technologies designed to interface with and even upload data into your charts, be sure to create a data map of where information is coming from, where it is going to, where it is stored, who or what other device(s) has access to it and the security protocols or features in place. Also, have policies in place that identify those same items and state how long the data created will be retained for, and how you plan to handle upgrades or changes in devices so that legacy data is either preserved in its original form, or migrated to the new system or software.


“It’s easy to get pulled into complex healthcare information projects that can eat up your time and money,” says Todd Stout, president of FirstWatch, a healthcare information technology company. “So it’s important to try to participate in ways and phases that your organization can handle. Also, some of these projects are ‘pilot’ projects, and implementation processes and standards that are not yet proven. Even great approaches can fail due to no fault of the EMS agency, but they can be left with systems, software or hardware that isn’t supported anymore due to a project failure.”


This article scratches only the surface. Be sure to consult with an attorney and a health information technology consultant to review your organization’s specific needs and obtain appropriate advice on these and related issues.




1. Blumenthal D, Tavenner M. The “meaningful use” regulation for electronic health records. N Engl J Med. 2010;363(6):501–504.


2. Credit for this phrase goes to Dave Page from FISDAP.