Seamless Transition

The Public Health Division of the Wyoming Department of Health was faced with several challenges with their existing NEDSS Base System (NBS) implementation. These included the need to modernize their electronic laboratory reporting (ELR) architecture to respond to the demands of Meaningful Use and expand their surveillance capacity by using a up-to-date system implementation. After selecting InductiveHealth’s NBS hosting and support offering, within two weeks the Wyoming Department of Health’s NBS implementation was transitioned to InductiveHealth’s secure private cloud environment and fully upgraded and operational. This included a full round of testing with the new release and migrated historical data, along with transitioning of all of the Wyoming Department of Health’s existing ELR feeds. All of this was accomplished with nearly zero downtime for end-users.

Since then, InductiveHealth has dramatically increased ELR onboarding into Wyoming’s NBS implementation utilizing our Engage, Connect, Validate, Operate onboarding methodology. The result is more high-quality data available to epidemiologists with up-to-date system features and enhanced support.

“We are very happy with our partnership with InductiveHealth.  In just a few months they’ve made significant strides on-boarding laboratories for electronic lab reporting.  We are so excited about the progress and look forward to continuing our partnership.” – Clay Van Houten, Wyoming Department of Health

Supporting BioSense

InductiveHealth is proud to have been selected, along with team members ICF International and Deloitte Consulting, to support, operate, and enhance the BioSense system for the Centers for Disease Control and Prevention (CDC), Center for Surveillance, Epidemiology, and Laboratory Services (CSELS). In support of this effort, InductiveHealth will provide surveillance expertise, information management and technology services, and data management and analytics support for multiple aspects of BioSense, CDC’s cloud-based public health surveillance system.

“BioSense is an exciting program that supports the collection of some of the largest quantities of electronic healthcare data reported to public health.  We look forward to working with CDC to enhance and support BioSense to increase the ability of local, state, and national health officials to monitor and respond to conditions that affect the public’s health.” – Matthew Dollacker, Managing Director, InductiveHealth Informatics

 

 

Thought Leadership

Thought leadership is just a part of what we do to help advance the practice of public health.  InductiveHealth was honored to be able to present at the 2014 Public Health Informatics Conference on topics surrounding how the public health space can make effective use of big data technologies.  Clearly this is an area of interest, as evidenced by the standing room only crowd!

Thanks to everyone who attended and for the insightful questions.

 

Delivering GIS Capabilities

Since John Snow’s original map charting London Cholera cases, geographic analysis of data has been a core capability for the practice of public health.  Geographic analysis has, however, been a gap in the standard functionality in the CDC’s NEDSS Base System (NBS), requiring jurisdictions to manage their own external processes for exporting and analyzing NBS surveillance information in geospatial tools.  This time-intensive and error-prone process limits the effectiveness of geospatial analysis for data collected by the NBS.

InductiveHealth was engaged earlier this year by the District of Columbia Department of Health to solve this problem to enable rapid geo-analysis and mapping of public health surveillance data.  This has involved an automated integration with the District’s centralized ArcGIS and Google Maps installations, providing automated geo-coding of NBS case information and an integrated geographic mapping view for cases managed by the DC NBS instance.  This week InductiveHealth completed the Implementation Phase for our main deliverables for this contract and we hope to demonstrate these new capabilities to the broader NBS community in the near future.

Stay tuned for more exciting updates in this area!

 

 

 

Strengthening Your ELR Strategy

With the recent publication of CDC’s guidance for public health agencies for Meaningful Use Stage 2, InductiveHealth’s Director of Professional Services, Stephen Macauley, shares his perspective on why now is the time for jurisdictions to rethink their ELR strategy.

Why Now?
CDC just released guidance for public health agencies for MU Stage 2, and jurisdictions are in the process of applying for the ELC ACA FOA which has specific ELR performance measures.

Further, with shrinking state budgets and reductions in federal grant dollars, jurisdictions have to identify how to drive down costs associated with ELR while simultaneously maintain the existing ELR infrastructure and expanding the the number of electronic trading partners.

What is the role of Key Performance Indicators (KPIs)?
Simply, you can only assess what you can measure. For the last decade a few KPIs have dominated ELR assessment discussions — primarily the “% of Laboratory Reports Received Electronically” and “Timeliness of ELR versus Paper reporting” metrics. We agree that these historical measures should continue to be used for assessment, especially at the national level.

However, just as ELR has evolved over the last decade, so should the KPIs used for assessment. Ultimately, no one set of KPIs are right for every jurisdiction. When we sit down with a jurisdiction we focus on mapping the jurisdiction’s ELR maturity to the right mix of KPIs. By aligning KPIs to maturity, jurisdictions can set a multi-year roadmap for advancing ELR capabilities.

Further, we stress that jurisdictions should adopt no more than 2 to 3 new KPIs as part of their strategy. We have found that this helps jurisdictions focus their efforts across the year.

What is one KPI that should be a part of any ELR Strategy?
With the above said, if I had to recommend one KPI, it would be Cost Per Transaction.

While fairly self-descriptive, this KPI measures the total cost of your ELR infrastructure and activities at a per laboratory report unit.

Say for example your jurisdiction spent $200,000 on ELR in 2012 and received 20,000 individual ELRs in 2012, the Cost Per Transaction would be $10.00.

Understanding the per unit cost allows the jurisdiction to rethink their ELR strategy from two angles:

1)  How to lower the Cost Per Transaction for existing operations through process optimization, technical infrastructure, and the targeting of high volume, mature electronic trading partners.

2)  Assessing the impact of MU Stage 2 on Cost Per Transaction by focusing on how to drive down the incremental cost to onboard a new electronic trading partner measured against the incremental increase in the number of new ELRs to be received.

While your KPIs are important, it is also important to put these in context. When I discuss Cost Per Transaction with jurisdictions I am often reminded that not all ELRs are treated equally. For example, a Pertussis culture for an unvaccinated 5 year old can be of higher epidemiological value than an annual Hepatitis C Chronic panel test.

Ultimately, KPIs such as Cost Per Transaction help to focus jurisdictions on driving down ELR costs which allow savings to be re-invested in resources that increase epidemiological capacity.

Where does Scalability fit into an ELR strategy?
At the center.

For the last decade, public health jurisdictions focused on transitioning from paper to electronic laboratory reporting for a relatively small number of electronic trading partners, including key national laboratories, state public health laboratories, and high volume regional / local laboratories. Having worked with many states to execute this transition, it was a multi-year marathon that some state are still running.

Now, with Meaningful Use Stage 2, the number of trading partners is expected to grow exponentially in a condensed time frame measured in a months versus years. Further, jurisdictions will have to also support the Syndromic and Immunization population health measures of MU.

So if your strategy cannot scale, you will have problems down the road. In addition to this influx, it is important to remember that jurisdictions also have to continue to work with non MU electronic trading partners.

How Can InductiveHealth Help?
We have series of offerings that are tailored based on the ELR needs of a jurisdiction. For example, a jurisdiction may leverage our ELR consulting services to assist in rethinking their ELR strategy including defining KPIs. Or a jurisdiction may engage our ELR Managed Service offering whereby InductiveHealth handles all aspects of the ELR infrastructure and onboarding for a fixed monthly fee.

Continue the dialogue with Stephen at [email protected]

 

Clearing the Release Log Jam

With the majority of states using a version of the NBS that is almost a year old, InductiveHealth’s Director of Professional Services, Stephen Macauley, recently sat down for a Q & A on how states can clear the release log jam.

How would you describe the NBS release landscape?

Complicated. With the release of 4.4.1 in January, most NBS states are now faced with sun setting Sun One Directory Server (4.4.1), the retirement of eWebIT(4.4), and upgrading of Operating Systems and Relational Databases (4.4.1). Simultaneously, states are having to respond to attestation requests for Meaningful Use, onboard reference laboratories, and participate in other state and federal initiatives.

Why do we have a release log jam?

Each recent release of the NBS impacts a critical part of the NBS architecture — 4.4.1 changes how user profiles are stored along with changing to a 64 Bit architecture whereas 4.4 changes how ELRs are consumed into the NBS. These releases are also cumulative in nature so you cannot move to 4.4.1 without first addressing the retirement of eWebIT. States have every reason to move slowly given problems encountered with these releases can render the NBS unusable. If even for just a few days, it would be catastrophic for a state to not process electronic laboratory reports.

Everyone has to remember that upgrading the NBS is not the primary job duty of state resources involved in the NEDSS initiative. These resources have to focus on their day jobs of monitoring and improving the health of their citizens.

What advice do you have for states in moving forward?

Simple — build and document a state specific release roadmap. Specifically, define the state’s capacity to implement major releases, determine the order of implementation based on business value, and determine what will happen when things go wrong. No state’s implementation plan will be the same, but each state should have a plan. Given the complexity of the NBS and the high cost to remediate data, plan for the worse and hope for the best.

Inversely, what should states not do to clear the log jam?

Rush. If your end users are satisfied with the current version of the NBS, why rush into something that may upset them. Remember, within each state only one or two technical administrators know the nuts and bolts of the NBS. However, hundreds of end users know they rely on the NBS every day to perform their job duties.

How can InductiveHealth help?

Our capabilities serve as accelerators for states clearing the release log jam. For example, our free trial offering provides states with a safe environment to evaluate new releases before even bringing them into their own environments. This a huge time saver thereby reducing the overall cost of implementing a new release.

Continue the dialogue with Stephen at [email protected].

InductiveHealth on Big Data

InductiveHealth’s Managing Director, Matthew Dollacker, was recently covered in a piece by the Robert Wood Johnson Foundation’s New Public Health Blog.  The article focused on key topics from Matthew’s recent APHA talk on big data in the public health arena.

Though highly-structured, coded data will continue to be a mainstay in public health and healthcare, there is an ongoing revolution taking place in the use of extremely large, semi-structured and unstructured data sets to gather new insights through advanced machine learning techniques.

InductiveHealth is at the forefront of this revolution, which promises to transform the information tools available to public health institutions.

From the article:

“Data production will be 44 times greater in 2020 than it was in 2009,” said Dollacker. “And those who are positioned to take advantage of this data explosion are those that are aware of it, can access it, and can handle it.” …

 

Dollacker highlighted a couple of recent examples that show the potential big data has for public health. One instance was the Google Flu project – merely based on what users were searching on google.com, the search engine was able to take that data and help predict flu outbreaks at a regional and city level – ahead of official sources.

 

“What this highlights,” said Dollacker, “is the tremendous value that is sitting out there in data right now. Who would have thought we could have address this issue by looking at nothing more than existing search terms?”

Free Evaluation Instance Launch

Today InductiveHealth launches a new free offering to assist public health departments in testing and evaluation of the NEDSS Base System.  This is a dedicated instance for your public health department to evaluate new versions of the NBS, test configuration changes, validate upgrades, perform ELR back-testing, and many other uses (outside of Production operations). We support this offering either using our base install or, with an appropriate data-use agreement, using your NBS configuration and test data.

To learn more, visit our offering page or contact us at [email protected].