< Back to Resource Library
Vidyard lightbox thumbnail

HealthData Talks: Data Procurement & Extraction

In this episode, host, Amy Holmes, and Solutions Engineer Director, Darryl Mais at Harmony Healthcare IT, discuss data procurement and extraction, focusing on the challenges of handling legacy data in healthcare, particularly for large organizations like Integrated Delivery Networks (IDNs).

Subscribe
You can subscribe to the HealthData Talks Podcast on SpotifyAmazon MusicApple Podcasts and more.

 

Transcript

[00:00:02.548] – [00:00:40.000]

Welcome to HealthData Talks where industry experts offer bite sized tips and trends for managing legacy data. Hello, thank you for joining us. I’m Amy Holmes with Harmony Healthcare IT, at Harmony, our specialty is working with legacy data. We’ve been focusing on that in healthcare for the past 17 years. So, we’ve encountered a lot of extraction work over that time and we work on data migration and archive projects for our customers. So today we have Darryl Mais, our Solution Engineer Director at Harmony joining me to talk about this topic. Thanks for being here today, Darryl. Thanks Amy. Happy to join.

 

[00:00:42.810] – [00:01:01.889]

So, Darryl to start, can you give us just a brief background on yourself and your role here at Harmony? Yeah, sure thing. I’ve been at Harmony Healthcare IT for about 12 years now. I started off in the data extraction and integration services side of the fence. Built up the Solutions Analyst team and then moved over on the solutions engineering side of the fence.

 

[00:01:05.189] – [00:01:47.150]

So, what does solution engineering mean? Like what is your team responsible for? The Solutions Engineering team is really a precontract function and our job is to understand the client needs around an archive or migration so that we can craft the proper solution to solve a particular client ask. So, our work kind of meets at the crossroads of architectural engineering and data engineering and sales operations and product knowledge. There’s a lot of technical aspects to it, but at the end of the day, it really is about asking questions and understanding the core of the client need. Otherwise, it’s kind of like building a vehicle. As I like to say, you can build a really nice car. But if the client really wanted a Jeep, you haven’t done your job. That’s true.

 

[00:01:48.150] – [00:02:48.409]

So generally speaking, how important is understanding data lineage and dependencies before digging into an extraction project, especially when it comes to the database types platforms, data scope? I’ve been in the medical automation and data space for a little over 30 years now. And the idea of data lineage is just another name for knowing the data you’re working with. I think without having context to the data, it really is a quote, our CEO likes of mine, all ones and zeros. In that understanding of the data, you have to get down in the dirt of things. And what I mean by that is you have to know what platform products are running on and the data lives, on how it’s used, how it’s structured, who the consumers are, those kinds of things. And knowing those kinds of things, both in the extraction of the build work, you’re going to be much more effective in whatever you’re delivering. Whether that happens to be an archive or migration, you’re doing data analytics reporting, any of those types of activities. That’s certainly true.

 

[00:02:50.808] – [00:04:32.649]

Speaking of understanding the data, I know non-structured data like notes and images are the bane of many of the people working on extractions. So, let’s hear about the challenges of extracting that non-structured content from diverse data sets. What are Harmony’s kind of go to strategies for wrangling it that we’ve seen success with? Well, I think the most complex thing you run into in the non-structured content and is and what lends a little bit of complexity to it or makes it tricky is because it can be such a vast set of content. It can be scanned, documents, images, forms, worksheets or anything the rigid any product needs to capture. Our strategy around it though it is very similar to what we do with discrete data is to get an understanding of what it is and how it’s used in the context of the product and the data consumer. Once we have that knowledge, we can then go about determining the technical underpinnings whether it is in the database or stored outside of it, what format it’s in, whether it’s encrypted or it’s compressed in a format that’s not standard industry standard. Those kinds of things I’d say in that chain, the last step really is how you’re going to convert that to something that is industry standard if it’s required. I think a lot of data engineers tend to look at it through the other end of the tunnel and come at it from a oh, is this in a format that I know angle and when it isn’t then either considered a dead end altogether or try to back into its technology and purpose to gain context of that content. I think that kind of point of view is one of the reasons why we’ve had success serving many health systems and IDNs that often have that larger, more complex data sets.

 

[00:04:34.798 – [00:05:24.139]

Can you talk a little bit about how Harmony services, the unique needs of these large organizations? Well, there’s certainly some, you know, shifts and pivots that we do in working with large healthcare systems. and IDNs. We generally leverage our standard processes, we might eliminate some high-level steps in the introduction processes because many of these entities and organizations were working with time and again, they already understand those steps. We also might have personnel on the other end that are responsible for the content, you know, the care and feeding of it in the legacy application or the legacy infrastructure. So they’ll know where that content lives. They can provide us backups versus you know, us going and getting them those kinds of things. But I’d say that, you know, the real core of what we do within our proven standard processes serves us well, whether that be in a small organization or a large IDN.

 

[00:05:26.298] – [00:06:24.449

So, what are some of the unique data challenges faced by those larger IDNs given their multi-hospital structures and often the larger number of applications that they have under their management? Yeah, I’d say that the real challenge within a multi-hospital structure versus maybe a single clinic entity, those two big challenges within there are within the terms of legacy data that needs to be archived or migrated around the mix of the platforms and the legacy software solutions that make up their decommissioning portfolio and personnel who have experience with those legacy solutions. It can make the route to understand the what of the legacy solution difficult and the what is what drives the route to the solve at the end of the day? Fortunately, in a lot of those cases, we can assist clients with those legacy systems in terms of some of their infrastructure and by infrastructure. I mean, both what it runs on database platforms, those kinds of things due to our vast experience with over 550 software brands that we’ve worked with over the years.

 

[00:06:26.750] – [00:07:33.189]

So, thinking about those challenges that they’re facing, do you have a kind of ideal engineering process when working with an IDN client, from that initial consultation to the implementation and then the support afterwards? Kind of a difficult question to answer because I don’t think it’s a one size fits all kind of framework. More generally, I’d say the biggest advantage, whether it’s in IDNs or clients with a small set of legacy solutions is to have someone that knows the product on staff. And by knows that, I mean, can know it from a usage standpoint, can know it from an infrastructure standpoint, those kinds of things because if you strip away all the technical wizardry involved in the process, at the end of the day, you’re trying to preserve patient care data and have it accessible to the staff, having that person that can ensure that the critical content that existed previously is somewhere that is accessed and secured and can provide context in both what is needed for retention as well as looking at through the right lens in the target endpoint. And by target endpoint there, I mean, the consumers that are going to use it once, once that legacy applications retire is really key to successful outcomes.

 

[00:07:39.809] – [00:08:40.710]

So you’re working with a lot of different organizations. How do you help foster the strong relationships with IT teams and stakeholders within the IDNs to ensure a successful data extraction project? Well, I think that comes back to one of our core values here at Harmony, which is to be easy to work with as we’re working with client resources and teams, not just on the extraction engineering side, but throughout we try to be supportive of what clients are ultimately attempting to accomplish. I’ve had an opportunity where we’ve been collaborating with the client on it for a number of months. So instead of coming at it, like some votes would by saying, Yep, looks like you have a real problem there. I’ve tried to be and I think we all do within Harmony Healthcare IT collaborative with them as an extension of their own team. I think the fact that we do that a lot here at Harmony is what has allowed us to have strong long-term relationships with any of our clients. That’s true. We have strong devotion to our core values, which I think helps serve us well for your sales engineers on your team that are working with these IDNs or other organizations.

 

[00:08:42.960] – [00:09:32.428]

What are some of the best tips for identifying needs? Showing ROI and navigating those kind of complex procurement processes when we’re trying to get a process going or project going. I say on the need in the ROI side of the fence, we, we pretty much covered that in some of the topics we talked about before but to summarize it, it really comes down to understanding what is historically significant and necessary for content consumers and ongoing patient care. On the procurement side of the fence, I’d say, you know, no one to raise your hand. We’re always willing to collaborate with outgoing legacy solution vendors go-forward target system vendors, etc, as a client advocate again, we handled a lot of knowledge around many legacy solutions and their respective vendors and that tends to reduce some of the complexity around those procurement and delivery processes.

 

[00:09:34.599] – [00:10:26.308]

So, looking ahead, what do you see as emerging trends and technologies that will shape kind of the future of data extraction in health care? I think we’re going to continue to see data platforms that become a lack better way to put it more agnostic. The players in this space were able to look at data transport, whether it be medical data or other kinds of data. For more of an efficiency angle and have agility versus a rigid set of well, we’ve always used X platform or X technology are going to emerge as leaders. I also think the whole notion of proprietary closed off data storage platforms are going to continue to die off. It’s not to say they’ll be less secure. Certainly. And the idea that you have to lock down the technology or product uses in such a way that one of ten people in the world can use it or more importantly in in the functions that we do in the services we provide the data related to it. It is in a viable future model.

 

[00:10:28.649] – [00:11:26.389]

That makes sense. And of course, we’d be remiss not to talk about perhaps the biggest trending topic in healthcare, which is AI. How do you see that affecting what we’ve talked about? Yeah, that certainly is the big buzzword right now. AI and I don’t think there’s any denying that has implications both on the data extraction and delivery side of the fence. If you just think about that as kind of a slice from the security angle and the ability for human touches to be removed from the process. It’s significant. I think AI will also play a major role in the management and cataloging. An incredible amount of data organizations have under management and stewardship. One thing we talked about internally is just making sure that AI is well vetted and secure and you’re thinking about it from all angles before adopting it in an organization, whether it’s ours or you know, a healthcare provider. So it’s a responsible adoption of it. Right. Absolutely.

 

[00:11:28.469] – [00:12:03.340]

Well, Darryl, thank you so much for taking time out to join us today. I think that was a good overview of data extraction challenges and addresses, you know, a lot of the questions that we field from healthcare organizations every day. Appreciate you jumping on. Thank you. It’s been a pleasure to speak with you today and enjoyed it. And to our listeners, thank you for joining us. Be sure to tune in next time for another discussion about legacy data and healthcare. That’s it for this session of HealthData Talks, check out helpful resources at harmonyhit.com and follow us in your favorite podcast app to catch future episodes.

 

Speakers

Host:
Amy Holmes, Director of Marketing, has gained over 15 years of diverse marketing experience. At Harmony Healthcare IT, she is responsible for all aspects of marketing, helping connect the healthcare market with our legacy data management solutions.

Darryl Mais, Darryl has worked in the healthcare automation and data space for over 30 years. Currently at Harmony Healthcare IT, Darryl is the Director of the Solutions Engineering team. His daily activities include infrastructure, data, and platform design to support both our Sales Team and our clients. He takes a lot of pride in making sure we have the right solution for the opportunities presented to us and that our clients feel like they’re well-informed about the details of our offerings.

 

Was the Resource Helpful?

Talk to the experts. Harmony Healthcare IT is an award-winning data management firm with a proven ability to extract, migrate and archive data with 100% integrity.

Black Book 2022 LogoKLAS Category Leader 2020 in Data Archiving LogoAppOrchard
First Name *
Last Name *
Email *