Free Hospital EMR and EHR Newsletter Want to receive the latest news on EMR, Meaningful Use, ARRA and Healthcare IT sent straight to your email? Join thousands of healthcare pros who subscribe to Hospital EMR and EHR for FREE!

The Disconnect Between Patient Experience and Records Requests – HIM Scene

Posted on April 19, 2017 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

This post is part of the HIM Series of blog posts. If you’d like to receive future HIM posts in your inbox, you can subscribe to future HIM Scene posts here.

This week I met with one of the digital marketing team at a children’s hospital. We had a great conversation about the hospital website and the way the hospital’s website represented the organization to the patient. Plus, we talked about how patients choose to interact with the hospital through their website. There are a wide variety of patient requests through the website, but one of those requests was a request for their patient record.

It wasn’t really a surprise that this digital marketer didn’t really know the details of what’s required for a patient to make an appropriate medical record request from his hospital. In his defense, he didn’t usually answer the questions, but just created the website that collected the questions. However, it was quite clear that the workflow for any medical records request was to send it to their HIM department and let them figure it out.

Most organization then have their HIM staff play phone tag with the patient to explain how to make a proper records request which will allow them to release the information to the patient. The progressive organizations might send the patient an email. However, many of them will then ask the patient to mail, drop off or fax in the official records request. If this sounds painful, I can assure you that it’s as painful as it sounds.

This illustrates the massive disconnect between creating a great patient experience and most organization’s current records request process. Please note that I’m not blaming the digital team at hospitals for the issue and I’m not blaming the HIM people for this problem. I’m blaming the disconnect between the two organizations because the only way to solve this problem is to have both organizations involved.

The best patient experience would actually be for the patient to go to their patient portal and download their whole record. Maybe we’ll get their one day, but there are hundreds of systems in a hospital where a patient’s data is stored. So, it’s going to take a while for us to reach the point where a patient can self-service their data requests.

Since I’m not holding my breath on this amount of data sharing happening between disparate systems, I’m more interested in making the current processes so it’s a seamless experience for the patient. If you can model a medical records request on paper, then you can do it digitally. To their credit, I’ve seen a few organizations working on this. In fact, their system is part education about records requests and part getting the information that’s needed to fulfill a records request.

It’s time that HIM and a hospital’s digital and tech teams come together to make the process for requesting records a seamless patient experience. And if you think using a fax machine is a seamless experience for patients, then you’re part of the problem.

If you’d like to receive future HIM posts in your inbox, you can subscribe to future HIM Scene posts here.

A Look at the HIM World with Dr. Jon Elion from ChartWise Medical Systems – HIM Scene

Posted on April 5, 2017 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

This post is part of the HIM Series of blog posts. If you’d like to receive future HIM posts in your inbox, you can subscribe to future HIM Scene posts here.

Healthcare Scene had a chance to interview Dr. Jon Elion, founder and president of ChartWise Medical Systems where we asked him about some of the big happenings in Health Information Management (HIM) and how world of HIM is evolving. Dr. Elion offers some really great insights into the HIM profession. You can watch the full video interview embedded at the bottom of this post or click on one of the questions below to hear Dr. Elion’s answer to that question.

Find more great Healthcare Scene Interviews.

If you’d like to receive future HIM posts in your inbox, you can subscribe to future HIM Scene posts here.

Who’s Over MACRA? CIO? COO?

Posted on March 22, 2017 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

In no surprising way, MACRA is a major topic in pretty much every hospital and health system in the US. There’s a lot of money to be had or lost with MACRA. This is especially true for health systems with a lot of providers. Plus, it sets the foundation for the future as well. I believe MACRA will be as impactful as meaningful use, but without as many incentive payments (chew on that idea for a minute).

As I’ve talked to hundreds of organizations about MACRA, I’ve seen a whole array of responses for how they’re addressing MACRA and who is in charge. Is this a CIO responsibility since MACRA certainly requires EHR and other technology? Is this a COO job because MACRA is more of an operations problem than it is a technical problem? Some might make the case for the CMO/CMIO to be in charge since MACRA requires so much involvement from your providers.

From my experience, the decision usually comes down to choosing between the CIO and the COO, but with input and buy-in from the CMO/CMIO. How the CIO positions themselves will determine if they are over MACRA or not. Some CIOs see themselves as tech people and so they shy away from touching MACRA. Other CIOs see themselves as integral part of their business success and so they want to have MACRA under their purview. Most progressive CIOs that I talk to want the later.

I’m an advocate for a CIO that’s involved in the business side of things. Those CIOs that don’t want this duty are going to miss out on strategic opportunities for their organization. I heard one CIO describe that they viewed their IT organization as Information As A Service provider. Their job as the IT department was just to provide the information from the IT systems to someone else who would deal with the information, the MACRA regulations, etc.

The Information as a Service provider concept has issues on multiple levels. The most important is that if you’re just an information provider, then you lose out on the opportunity to be a strategic part of your organization. However, from a more practical MACRA level, it’s really challenging to provide the right information for MACRA when you’re just an information provider and know little about the regulation. We all know how quickly communication can break down when the person needing the information is disconnected from the people who provide the information and they’re disconnected from the people entering the information.

No doubt a healthcare CIO has to be careful what projects they add to their plate. However, I don’t think MACRA is one of those projects that should be pushed off to someone else. Certainly there can be specific organization cultures where it makes sense for the COO to run things, but I think that should be pretty rare.

How are you approaching MACRA at your organization? Who’s over it? I look forward to hearing your experiences in the comments.

EMR Replacement & Migration Perspective: Tim Schoener, VP/CIO, UPMC Susquehanna

Posted on December 8, 2016 I Written By

header-chime
In the midst of a merger with a major Pennsylvania healthcare organization, Tim Schoener is wholly focused on EHR transition. He outlines Susquennaha’s plan for each aspect of transition, offering innovative and unique approaches to each. In addition, Schoener provides cogent insights regarding the intricacies involved with a multi-database system, the expenses associated with archival solutions, and the challenges associated with migrating records. This interview touches on many of the considerations necessary for a successful EHR transition as Schoener discusses minimizing surprises during a transition; why migrating a year’s worth of results is optimal; and how their document management system fulfills archival needs.

CHIME Fall CIO Forum provides valuable education programming, tailored specifically to meet the needs of CIOs and other healthcare IT executives. Justin Campbell, of Galen Healthcare Solutions, had the opportunity to attend this year’s forum and interview CIOs from all over the country. Looking for additional EMR replacement perspectives & lessons learned? View a recent panel where HCO leaders discussed their experiences with EHR transition, data migration & archival.

KEY INSIGHTS

Absolutely, we have problem lists that can’t be reconciled; there’s a problem list in the Soarian world and a problem list in the NextGen world, and they’re not the same thing right now, not at all.

We’re being told, if you think you’re going to migrate and move all this data to some sort of other archiving solution, get ready for a sticker shock.

Our intent is to take it to each physician specialty to establish a good comfort level, so when the transition occurs, I don’t have physicians’ saying to me ‘no one ever asked me…’ or not be able to provide excellent patient care. It’s going to be critical to the success of our EMR transition to keep our physicians engaged and involved.

Let’s face it, no staff member has the desire to support the legacy application when all of their coworkers are learning the new application. That’s a career limiting move.

It used to be something that struggling organizations were forced to pursue, but now very successful organizations are starting to affiliate and merge with other organizations because it’s just the state of healthcare.

CHIME is a great way to challenge yourself as a CIO and in your leadership. It pushes me in my leadership skills and helps to focus me back to what’s critical in the industry.
tim-schoener
Campbell: Tell me a little about yourself and your organization’s initiatives

Schoener: I’m Tim Schoener, the VP/CIO of, originally Susquehanna Health, which, as of October 1st, is now a part of the University of Pittsburgh Medical Center (UPMC) and re-named to UPMC Susquehanna. We’re located in central Pennsylvania, four hours away from Pittsburgh.

A major IT initiative for us is that we’re swapping out our EMR over the next couple of years. We are currently a Cerner Soarian customer. In fact, we were the initial Soarian beta site for Financials and second for Clinicals. We determined we eventually need to migrate to something else – that’s an Epic or Cerner decision for us at this point. UPMC’s enterprise model is Cerner and Epic, Cerner on the acute care side and Epic on the ambulatory side. As of this writing, we’ve made the decision to migrate to the UPMC blended model. Over the past nine months we’ve been focused on an EMR governance process, trying to get our team aligned on the journey that we’re about to take and by late next year we will likely be starting an implementation.

We currently leverage NextGen on the Ambulatory side, with approximately 300 providers that use that software product. We’re a four hospital system: two of which are critical access, one which is predominately outpatient, and the other a predominately inpatient facility. We were about a $600MM organization prior to our UPMC acquisition.

Campbell: Related to your current implementation, tell me a little bit about your data governance strategy and dictionary mapping that may occur between NextGen and Soarian.

Schoener: We definitely have a lot of interfaces, a lot of integration between the two core systems. From an integration perspective, we have context sharing, so physicians can contextually launch and interoperate from NextGen to Soarian, and vice-versa. We do pass some data back and forth—allergies and meds can be shared through a reconciliation process—but we certainly aren’t integrated. It’s the state of healthcare.

Campbell: That’s why you anticipate moving to a single platform, single database?

Schoener: Absolutely, we have problem lists that are not reconciled. There’s a problem list in the Soarian world and a problem list in the NextGen world, and they’re not the same thing right now, not at all. Meds and allergies are pretty much all we get in terms of outpatient to inpatient clinical data sharing today.

Campbell: Do you leverage an archival solution for any legacy data?

Schoener: We use EMC and have large data storage with them. I wouldn’t call it archival, but we have an electronic document management system – Soarian’s eHIM.

There’s a huge amount of data out there and I know you have some questions related to our thinking with respect to migration. I have some thoughts around that related to levering our document management system versus archiving into a separate system. I’m pretty certain we would be thinking ‘why not use eHIM as our archival process, and just put other data in that repository as necessary?’ For results data, for instance, what we’re thinking of migrating, or what our providers are requesting, is a years’ worth of results. ‘Give me a year’s worth of results, and then make sure everything else is available in eHIM.’

Campbell: As such, your default is to migrate a year’s worth of data?

Schoener: Yes. We would presume that the provider is probably not going to refer back to lab results or radiology results beyond a year, other than for health maintenance kind of things such as mammograms, pap smears, PSAs; those types of things.

Campbell: What expectations have you set with physicians when they go live on the new EMR?

Schoener: From an ambulatory perspective, we’re thinking that it would be nice to have the most recent note from the EMR available. All of the other notes for that patient would be consolidated into one note via a single pdf attachment. The note that’s the separate most recent note, we envision that being in a folder for that particular date. That note would reside in the appropriate folder location just like it would in the current EMR. Our goal is to bring the clinical data forward to the new EMR, taking all the other notes and placing them in a “previous notes” folder.

Campbell: Can you elaborate on your consideration of PAMI (Problems, Allergies, Medications, Immunizations) as part of the data migration?

Schoener: Sure. The disaster scenario would be the physician sits down with patient for first time with new EMR, and there are no meds, no allergies, and no problems! They’ll spend 25 minutes just gathering information, that would not work.

We’re thinking of deploying a group of nurses to assist with the data conversion and migration process. Our intent is to have them to retrieve CCDAs to populate those things I mentioned by consuming them right into the medical record, based on the physicians’ input. We expect there to be a reconciliation process to clean-up potential duplicates. Or, to be candid, we’ve talked about automating the CCDA process, consuming discrete clinical items from it by writing scripts and importing into the new EMR. I think we’re leaning towards having some staff involved in the process though.

Now if you share the same database between your acute and ambulatory EMR, and the patient was in ambulatory setting but now they’ve been admitted, it’s the same database: the meds are there, the problems are there, the allergies are there; it’s beautiful, right? If they weren’t, then the admission nurse is going to have to follow the same CCDA consume process that the ambulatory nurse followed. Or you start from scratch. On the acute side, we start from scratch a lot. Patients come in and we basically just start asking questions in the ER or in an acute care setting. We start asking for their meds, allergies, or problems – whatever they may have available.

Campbell: We’ve discussed notes, results and PAMI. Are there other clinical data elements that you’ve examined? How will you handle those?

Schoener: From an acute care perspective, our physicians are very interested in seeing the last H & P (History & Physical Examination) and the last operative note, so we’re going to consider two different ideas. One would be that all of that data would still reside in document management, which has the ability to be sorted. It’s currently very chart centric. For instance, you can easily pull the patient’s last acute care stay. There is the ability, however, to sort by H & P, operative note, or discharge summary—something along those lines for the separate buckets of information. Therefore, a physician could view the most recent H & P or view all sorted chronologically. In addition, they’ll be able to seamlessly launch directly from the new EMR to the old EMR, bypassing authentication, which is important to mitigate context switching.

One of the areas we’re struggling with is the growth chart. A physician would love the ability to see a child’s information from start to finish, not just from the time of the EMR transition. So that means some sort of birth height/weight data that we would want to retrieve and import into the new system so a growth chart could be generated. The other option is to somehow generate some sort of PDF of a growth chart up until the place where we transitioned to the new EMR. The latter however, would result in multiple growth charts, and a physician’s not going to be happy with that. So we’re trying to figure that one out.

Another area of concern is blood pressure data. We’re struggling with what to do with a patient we’re monitoring for blood pressure. We’d like to see more than one blood pressure reading and have some history on that.

Campbell: Thank you for elaborating on those items. What about data that is not migrated. How will that be addressed and persisted going forward?

Schoener: For the most part, everything else would be available in the document management system. We can generate that data from document our document management system and make it available to be queried by OIG or whoever else requires that data from a quality perspective. We are aware that an archival solution is very expensive. We’re being told, ‘if you think you’re going to migrate and move all this data to some sort of other archiving solution, get ready for a sticker shock.’ If that’s what the advisors and consultants are saying, then our thought is that probably isn’t going to be the direction we’re going to go. We’re likely going to stick with some type of document management system for archival.

Campbell: Very good. How are you gathering feedback from different specialties and departments? Do you have a governance process in place?

Schoener: So as you may have gathered, we’re getting ready. I don’t want surprises. I want physicians to be prepared and to set expectations for what’s going to be available. What I just described to you, we’ve vetted that out with our primary care docs. Now we’re going to take that to our cardiologists and ask them what they think. Then on to our urologists to allow them to weigh in. Our intent is to take it to each physician specialty to establish a good comfort level, so when the transition occurs, I don’t have physicians’ saying to me ‘no one ever asked me…’ or not be able to provide excellent patient care. It’s going to be critical to the success of our EMR transition to keep our physicians engaged and involved.

There will definitely be a learning curve with the new EMR, but we want to be clear and set expectations with respect to data migration and conversion, so that when the physician does use the new EMR they’re not saying ‘that darn Cerner or Epic.’  It’s more ‘that’s a part of the data migration process and we weren’t able to accomplish that.’

Campbell: What about legacy applications support. Will all of your staff be dedicated to the new project?

Schoener: I mean, let’s face it, no staff member has the desire to support the legacy application when all of their coworkers are learning the new application. That’s a career limiting move. We still haven’t decided what to do.

Campbell: I agree that no staff member wants to be left behind. I’ve talked to organizations where they use folks for both and it just doesn’t end well. You can’t expect them to do both, learning the new system while supporting the old one.

Schoener: I guess it depends on the capacity and the expectation of that particular project they’re working on. Maybe there is a person who has less involvement with the new EMR and they have availability where they can support both, although it’s unlikely. Sometimes you end up having someone who wants to retire within the time period. In that case, they can almost work their way to retirement and then not ever support the new EMR, although that situation is also unlikely.

It’s a great question, and one we’re going to have to have folks help us determine.

Campbell: Shifting gears a little bit, what are your thoughts on health data retention requirements? Too loose? Too stringent?  As you know, it varies state-to-state, from 7-10 years, but I feel like there’s a huge responsibility that is placed on organizations to be the custodians of that data. Do you agree?

Schoener: I think that’s just healthcare. A lot of it is legal considerations and our need to protect ourselves. That’s why do we do a lot of the things we do. We’re protecting ourselves from lawsuits and litigation. I think it’s expected; it’s just the nature of the business. Just think of what we had in a paper world. We used to have rooms and rooms full of charts and now that’s all gone. With our current process, any paper that comes in is scanned in within the first 24 hours. So it’s not something I worry about. My focus now is making sure our providers can perform excellent patient care on the new EMR.

Campbell: Could you provide some advice, insight or wisdom for healthcare organizations pursuing EMR/EHR replacement & transition?

Schoener: Get ready for some fun! Affiliations and acquisitions are greatly impacting these decisions. It used to be something that struggling organizations were forced to pursue, but now very successful organizations are starting to affiliate and merge with other organizations because it’s just the state of healthcare. One bit of wisdom for anyone is: if you’re not interested in that type of transition and change occurring, healthcare’s not for you. That’s the nature of the business we’re in.

I would say from an EHR transition process, I found that having an advisor is extremely beneficial to help me think outside of my day-to-day operations. They’re able to look outside of your organization and ask the right questions. If you pick the right advisor, they’ll protect you and protect your organization. I think it’s been very healthy for us to have someone from the outside give us counsel and advice because it’s a tough process. It’s extremely expensive, and extremely polarizing.

Campbell: Outside of the networking, what did you come to CHIME focused on this year?

Schoener: CHIME is a great way to challenge yourself as a CIO and in your leadership, it pushes me in my leadership skills and helps to focus me back to what’s critical in the industry. It helps me to think more strategic and broad, not to get too engaged in one particular topic. I think it’s just great for professional development. CHIMEs the best out there with respect to what I do.

This interview has been edited and condensed.

Evaluate options, define scope and formulate a strategy for EHR data migration by downloading Galen’s EHR Migration Whitepaper.

About Tim Schoener
Tim Schoener is the Vice President/Chief Information Officer for UPMC Susquehanna, a new partner of UPMC since October 1, 2016, which is a four-hospital integrated health system in northcentral Pennsylvania including Divine Providence Hospital, Muncy Valley Hospital, Soldiers + Sailors Memorial Hospital and Williamsport Regional Medical Center. UPMC Susquehanna has been Most Wired for 14 of the last 16 years and also HIMSS Level 6. Tim has worked at Susquehanna for over 24 years, 19 of those years in Information Technology.  He also has responsibilities for health records, management engineering and biomedical engineering. He is a CHCIO, HIMSS Fellow and CPHIMS certified. Tim received his undergraduate degree from The Pennsylvania State University with a BSIE in Industrial Engineering and his MBA from Liberty University. 

About Justin Campbell
Justin is Vice President, Strategy, at Galen Healthcare Solutions. He is responsible for market intelligence, segmentation, business and market development and competitive strategy. Justin has been consulting in Health IT for over 10 years, guiding clients in the implementation, integration and optimization of clinical systems. He has been on the front lines of system replacement and data migration and is passionate about advancing interoperability in healthcare and harnessing analytical insights to realize improvements in patient care. Justin can be found on Twitter at @TJustinCampbell and LinkedIn.

About Galen Healthcare Solutions
Galen Healthcare Solutions is an award-winning, #1 in KLAS healthcare IT technical & professional services and solutions company providing high-skilled, cross-platform expertise and proud sponsor of the Tackling EHR & EMR Transition Series. For over a decade, Galen has partnered with more than 300 specialty practices, hospitals, health information exchanges, health systems and integrated delivery networks to provide high-quality, expert level IT consulting services including strategy, optimization, data migration, project management, and interoperability. Galen also delivers a suite of fully integrated products that enhance, automate, and simplify the access and use of clinical patient data within those systems to improve cost-efficiency and quality outcomes. For more information, visit www.galenhealthcare.com. Connect with us on Twitter, Facebook and LinkedIn.

HIM’s Role in Healthcare Security and Privacy – HIM Scene

Posted on November 30, 2016 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

This post is part of the HIM Series of blog posts. If you’d like to receive future HIM posts in your inbox, you can subscribe to future HIM Scene posts here.

One of my go-to experts on healthcare privacy and security is Mac McMillan, CEO and Co-Founder of CynergisTek. He’s built a really great company that focuses on privacy and security in healthcare and he’s a true expert.

While at AHIMA 2016, I talked with Mac about the role that HIM plays in healthcare privacy and security. We also talk about where healthcare privacy is heading and which part of healthcare privacy and security doesn’t get enough attention. I also asked Mac to make a big 20 year prediction on what will happen with privacy and security in healthcare.

Check out our interview with Mac McMillan, CEO and Co-Founder of CynergisTek:

We shot a number of other videos at AHIMA 2016 which we’ll be posting shortly. If you enjoyed this video, be sure to Subscribe to Healthcare Scene on YouTube and watch our full archive of Healthcare Scene interviews.

If you’d like to receive future HIM posts in your inbox, you can subscribe to future HIM Scene posts here.

EMR Data Archival Strategy Deep Dive – Tackling EHR & EMR Transition Series

Posted on November 14, 2016 I Written By

The following is a guest blog post by Robert Downey, VP of Product Development at Galen Healthcare Solutions.

Inside the world of data archival (Download this Free Data Archive Whitepaper for a deep dive into the subject), there are nearly as many different types of archives as there are vendors. Many of the existing archival solutions that have gained popularity with large healthcare organizations are ones that are also frequently utilized by other sectors and often claim to be able to “archive anything.”

This can be very appealing, as an organization going through a merger will often retire dozens or even hundreds of systems, some clinical, but most only tangentially related to the delivery of care. HR systems, general ledger financial systems, inventory management, time tracking, inventory tracking systems, and CRMs are just a few of the systems that might also be slated for the chopping block. The idea of retiring all of these into a single logical archival solution is very appealing, but this approach can be a dangerous one. The needs of healthcare organizations are not necessarily the same as the needs of other sectors.
ehr-data-archiving-process
To understand why some archival approaches are superior to others, it’s useful to visualize the way each of the solutions extract, store, and visualize data. The methodologies used typically trade fidelity (how well it preserves the original shape and precision of the data) for accessibility (how easy it is to get at the information you need), and they trade how easily the solution can archive disparate sources of data (such as archiving both an EMR and a time-tracking system) with, again, accessibility.

There are certainly other ways to judge an archival solution. For instance, an important factor may be whether or not the solution is hosted by the archival vendor on-premises or remotely. Some factors, such as the reliability of the system, service level agreements, or its overall licensing cost are big inputs into the equation as well, but those aren’t necessarily specific to the overall archival strategy utilized by the solution. There are also factors that are so critical, such as security and regulatory compliance, that deficiencies in these areas are deal-breakers. Now that we have the criteria with which to judge the solution, let’s delve into the specific archival strategies being used in the marketplace.

Raw Data Backups
raw-healthcare-data-backups
A shockingly large number of organizations treat raw data backups of the various databases and file systems as their archival solution. There are some scenarios in which this may be good enough, such as when the source system is not so much being retired as it is being upgraded or otherwise still maintained. Another scenario might be when the data in question comes from systems so well known that the organization won’t have significant issues retrieving information when it becomes necessary. The greatest benefit to this approach is that acquiring the data is fairly trivial. Underlying data stores almost always offer easy built-in backup mechanisms. Indeed, the ability to back up data is a certification requirement for EMRs, as well as a HIPAA and HITECH legal requirement. This strategy also offers “perfect” data fidelity, as the data is in the raw, original format.
health-data-archive-fidelity
Once it actually comes time to access the “archived” data, however, the organization is forced to fully reverse engineer the underlying database schemas and file system encodings. This leads to mammoth costs and protracted timelines for even simple data visualization, and it’s a major undertaking to offer any kind of significant direct clinician or compliance access to data.

Another danger with raw database backups is that many clinical system vendors have language in their licensing related to the “reverse engineering” of their products. So while it may be “your” data, the vendor may consider their schema intellectual property — and the act of deciphering it, not to mention keeping a copy of it after the licensing agreements with the system vendor have been terminated — may well be a direct violation of the original licensing agreement.

Hybrid Modeled / Extracted Schema
extracted-schema-data-archiving
A common approach utilized by healthcare-specific archival solutions is to create a lightweight EMR and practice management schema that includes the most common data attributes from many different source system vendors and then map the data in the source system to this fully modeled schema. The mapping involved is usually limited to fieldtype mapping rather than dictionary mapping, although occasionally, dictionary data which feeds user interface aspects such as grouping (problem categories, for instance) may require some high-level mapping.

This approach usually yields excellent clinical accessibility because the vendor can create highly focused clinical workflows just like an EMR vendor can. Since these visualizations don’t need to be created or altered based on the source system being archived, it means that there is generally no data visualization implementation cost.
healthcare-data-archiving
As the mapping is limited to the schema, the extraction and load phase is usually not as expensive as a full EMR data migration, but because every required source field must have a place in the target archival schema, the process is typically more time-consuming and expensive than the hybrid modeled / extracted schema or non-discrete document approaches. That said, vendors that have a solid library of extraction processes for various source systems can often offer lower initial implementation costs than would otherwise be possible.

The compliance accessibility and data fidelity of this strategy can be problematic, however, as unknown fields are often dropped and data types are frequently normalized. This fundamentally alters a substantial portion of the data being archived in the same way that a full data migration can — although, again, not as severely given the typical lack of data dictionary mapping requirements. In some cases, vendors will recommend that a full backup of the original data be kept in addition to the “live” archive, providing some level of data fidelity problem mitigation. Should a compliance request require this information, however, the organization may be left in a similar position to those utilizing raw data backups or extracted schema stores with no pre-built visualizations.

Archival solutions utilizing this strategy may also frequently require augmentation by the vendor as new sources of data are encountered. This can make the implementation phase longer, as those changes typically need to happen before any data can be loaded.

Summary
There will never be a one-size-fits-all archival solution across organizations, and even within an organization, when determining the strategy for multiple systems. Another key takeaway is to always be wary of all the “phases of implementation.” Many vendors will attempt to win deals with quick and inexpensive initial implementations, but they leave significant work for when the data actually needs to be visualized in a meaningful way. That task either falls on the organization, or it must be further contracted with the archival solution provider.

It also is valuable to consider solutions specifically designed for archival purposes and, ideally, one that focuses on the healthcare sector. There are simply too many archival-specific scenarios to utilize a general purpose data backup, and many organizations find that the healthcare-specific requirements make general purpose archival products ill-suited for their needs.

Download Galen Healthcare’s full archival whitepaper to evaluate available EMR data migration & EMR data archival options and processes critical to EMR replacement and legacy system decommissioning.

About Robert Downey
Robert is Vice President, Product Development, at Galen Healthcare Solutions. He has nearly 10 years of healthcare IT experience and over 20 years in Software Engineering. Robert is responsible for design and development of Galen’s products and supporting technology, including the VitalCenter Online Archival solution. He is an expert in healthcare IT and software development, as well as cloud based solutions delivery. Connect with Robert on LinkedIn.

About Galen Healthcare Solutions
Galen Healthcare Solutions is an award-winning, #1 in KLAS healthcare IT technical & professional services and solutions company providing high-skilled, cross-platform expertise and proud sponsor of the Tackling EHR & EMR Transition Series. For over a decade, Galen has partnered with more than 300 specialty practices, hospitals, health information exchanges, health systems and integrated delivery networks to provide high-quality, expert level IT consulting services including strategy, optimization, data migration, project management, and interoperability. Galen also delivers a suite of fully integrated products that enhance, automate, and simplify the access and use of clinical patient data within those systems to improve cost-efficiency and quality outcomes. For more information, visit www.galenhealthcare.com. Connect with us on Twitter, Facebook and LinkedIn.

Steps Hospitals Should Consider When Migrating EMR Data

Posted on November 2, 2016 I Written By

Anne Zieger is veteran healthcare editor and analyst with 25 years of industry experience. Zieger formerly served as editor-in-chief of FierceHealthcare.com and her commentaries have appeared in dozens of international business publications, including Forbes, Business Week and Information Week. She has also contributed content to hundreds of healthcare and health IT organizations, including several Fortune 500 companies. She can be reached at @ziegerhealth or www.ziegerhealthcare.com.

When your organization decides to convert to a new EMR, the problems it faces extend beyond having to put the right technical architecture in place. Deciding which data to migrate and how much data to migrate from the previous EMR poses additional challenges, and they’re not trivial.

On the one hand, moving over all of your data is expensive (and probably not necessary). On the other, if you migrate too little data, clinicians won’t have an adequate patient history to work from, and what’s more, may not be in compliance with legal requirements.

But there are methods for determining how to make the transition successfully. HCI Group Data Technical Lead Mustafa Raja, argues that there are three key factors hospitals should consider when planning to migrate legacy EMR data into a new system:

  • Decide which data you will archive and which you will migrate. While many organizations fall back on moving six months of acute care data and a year’s worth of ambulatory data, Raja recommends looking deeper. Specifically, while ambulatory transitions may just include medications the patients are on and diagnostic codes in the past year, acute care data encompasses many different data types, including allergies, medications, orders, labs and radiology reports. So deciding what should transition isn’t a one-size-fits-all decision. Once you’ve made the decision as to what data will be transitioned, see that whatever archival storage system you decide upon is easily accessible and not too costly, Raja suggests. You’ll want to have the data available, in part, to respond to security audits.
  • Consider how complex the data is before you choose it for transition to the new EMR. Bear in mind that data types will vary, and that storage methods within the new system may vary from the old. If you are migrating from a nonstandard legacy system to an EMR with data standards in place — which is often the case — you’ll need to decide whether you are willing to go through the standardization process to make the old data available. If not, bear in mind that the nonstandard data won’t be easily accessible or usable, which can generate headaches.
  • Be prepared for the effect of changes in clinical rules and workflow. When upgrading from your legacy system, you’ll probably find that some of its functionality doesn’t work well with the new system, as the new system’s better-optimized workflows will be compatible with the old system, Raja notes. What kind of problems will you encounter? Raja offers the example of a legacy system which includes non-required fields in one of its forms, transitioning to a system that DOES require the fields. Since the data for the newly-required fields doesn’t exist, how do you handle the problem?

Of course, your plans for data migration will be governed by many other considerations, including the speed at which you have to transition, the purposes to which you plan to put your new EMR, your budget, staffing levels and more. But these guidelines should offer a useful look at how to begin thinking about the data migration process.

Will Medical Coders Be Needed in the Future? – HIM Scene

Posted on October 26, 2016 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

This post is part of the HIM Series of blog posts. If you’d like to receive future HIM posts in your inbox, you can subscribe to future HIM Scene posts here.

After spending time with so many HIM professionals at the AHIMA Annual conference, I’ve come back thinking about the future of medical coders. No doubt, many HIM professionals are moving well beyond medical coding into other areas such as healthcare analytics, clinical documentation improvement (CDI), EHR optimization, and much more. However, there’s still a massive need for high quality medical coding and the HIM professionals that provide that service.

As we look into the future, the techie in me feels like medical coding should be automated. Why are we paying people to do medical coding? Why can’t that be automated and be done by robots? It’s not like medical coding is a particularly fun job. I’m sure there are some times it’s fun working on unique cases, but it can be quite monotonous and tedious. Why not have a computer do it instead?

What I’ve learned over the years is that medical coding is more art than it is science. Certainly there are some clear cut cases where it’s basically science. However, a large part of what a coder does isn’t set in stone. There’s some artistic licence if you will, or at least some interpretation that has to happen in order to code a visit properly. Computers aren’t good at interpretation, but humans are.

The other reality is that doctors don’t produce perfect documentation. If they did, then we probably could code a robot to code a patient visit. Since there are nuances to every physician’s documentation, we’re going to need humans that interpret those nuances as part of the coding process. I don’t see this changing in our lifetimes.

One word of caution. Many people fall into the trap that we need automated robot coding to be perfect for it to accepted. That’s just not the case, because human coders aren’t perfect either. In fact, there’s some research that human coders aren’t as good as we thought they were at coding, but I digress. The reality is that automated coding just has to be better than humans, it doesn’t have to be perfect. Even with this said, I don’t see it happening for a while.

What we do see happening now is a collaboration between humans and computers: computer assisted coding. While we don’t have to worry about computers replacing humans in medical coding, we do need to focus on ways that technology can make the work humans do better. That’s a powerful concept that we’re starting to see happen already.

If you’d like to receive future HIM posts in your inbox, you can subscribe to future HIM Scene posts here.

Integrating CDI Efforts Across Inpatient and Outpatient – HIM Scene

Posted on October 19, 2016 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

This post is part of the HIM Series of blog posts. If you’d like to receive future HIM posts in your inbox, you can subscribe to future HIM Scene posts here.

One of the main topics HIM professionals have been discussing for a couple years is around CDI (Clinical Documentation Improvement). These programs have taken all sorts of shapes and sizes. Some are completely human driven. Others are largely tech driven, but most are a mix of the two. In fact, most CDI programs have gotten quite sophisticated and are really impacting the bottom line of healthcare organizations.

While most healthcare organizations realize that there are benefits to CDI, most of them have restricted these programs to the inpatient environment only. This was illustrated to me really well when I ran into a transcription vendor from India. It was his first time attending AHIMA and he was considering new areas of business including CDI. When we talked about CDI, his first comment was that he’d only ever seen CDI in hospitals, not in the ambulatory world.

While this is the case today, one HIM expert at AHIMA told me that one of the next big frontiers for CDI is going to be outpatient CDI. She went on to tell me that it’s fertile ground that could really benefit every healthcare organization. However, she also suggested that there shouldn’t be two CDI programs: 1 for inpatient and 1 for outpatient. Instead, CDI should be an integrated effort across inpatient and outpatient.

Clinical documentation improvement is only going to become more important in healthcare. Certainly, most CDI projects were started as a way to improve reimbursement. That’s a good goal and a benefit of a high quality CDI project. However, over time CDI is going to become even more important to an organization’s value based reimbursement efforts. In fact, if your clinical documentation isn’t accurate your reimbursement will really suffer. How can you keep a patient healthy if you’ve documented the wrong information for a patient?

How is your organization approaching CDI? Are you doing CDI in both inpatient and outpatient?

If you’d like to receive future HIM posts in your inbox, you can subscribe to future HIM Scene posts here.

Looking Forward to #AHIMACon16 – HIM Scene

Posted on October 12, 2016 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

This post is part of the HIM Series of blog posts. If you’d like to receive future HIM posts in your inbox, you can subscribe to future HIM Scene posts here.

As we prepare to head to the 2016 AHIMA Annual convention (see our full list of conferences we attend), we’re excited to talk about how we’re planning to expand HIM Scene to include as many HIM voices and perspectives as possible. HIM Scene will still be hosted here on Hospital EMR and EHR and will still have its own email list where HIM professionals can receive great HIM related content from thought leaders across the industry. However, we’ll be using HIM Scene to share a wide variety of people and perspectives.

The HIM industry is an amazing group of devoted people and that really comes through at every AHIMA annual convention I attend. Plus, HIM has a lot more influence than many people realize. So, we’re happy to do what we can to raise the voices and perspectives of HIM professionals here at HIM Scene.

Looking forward to the AHIMA Annual convention next week in Baltimore, we’re excited to learn about a number of important topics. Here are a few we’ll be sure to report on in future HIM Scene posts:

ICD-10 – A year after implementation, I’m really interested to hear the real stories of how ICD-10 has impacted healthcare organizations for good and bad. I bet there will be a lot of stories that haven’t been shared. I’ll also asking the HIM professionals I meet what they think the impact of the end of the ICD-10 grace period will have on healthcare. I wonder how many will have stories of ICD-10 improving care versus stories of ICD-10 for reimbursement.

Information Governance – This is an eternally hot topic in HIM, but it always continues to evolve. This is particularly true as records have gone electronic. This year I wonder how many people have been involved in some sort of health data sharing project. Information governance can get pretty tricky as healthcare organizations start to share data with each other electronically.

HIPAA Privacy and Security – A really hot topic given all the HIPAA breaches and ransomware incidents in healthcare. I’m sure I’ll find a number of HIPAA privacy officers that will share some good insights into how they’re dealing with these security and privacy challenges. I’m afraid many of them will give me exasperated responses about how their leadership isn’t taking it serious enough.

Informatics – I’ve been really intrigued with HIM’s role in healthcare informatics. Once you dive in, it makes since why HIM would be involved, but I don’t think most people saw that at first. What’s also been interesting to watch is many HIM professionals who’ve kind of shunned their involvement in healthcare informatics. We’ll see if many are still in that position or if most HIM professionals are starting to embrace and participate in the informatics efforts of their organizations.

What hot topics will you be looking for at the 2016 AHIMA Annual Convention? The AHIMA 2016 theme is to “Inspire Big Thinking to Launch Our Future.” We’ll be sure to report back any big thinking we hear from people we meet.

ahima-2016

If you’d like to receive future HIM posts in your inbox, you can subscribe to future HIM Scene posts here.