Cyber Security Predictions for 2017

2016 was a big year in the annals of Cyber Security, and 2017 promises to eclipse it.

Creating an Enterprise Data Strategy

An introduction to the process of developing comprehensive strategies for enterprise data manangement and exploitation.

A Framework for Evolutionary Artificial Thought

Let’s start at the beginning – what does this or any such “Framework” buy us?

The Innovation Dilemma

What things actually promote or discourage innovation? We'll examine a few in this post...

Digitial Transformation, Defined

Digitial Transformation is a hot topic in IT and big money maker for consultants - but what does it really mean?.

Showing posts with label EHR. Show all posts
Showing posts with label EHR. Show all posts

Wednesday, December 5, 2012

The Healthcare Portfolio

Today's post is a continuation of the discussion from yesterday's post:


“Nearly all existing EHR systems are built with an explicit domain model– a common approach in current EHR software development practice. This means that the hard coded medical domain knowledge in the system results in higher cost when new requirements in clinical documentation routines occur.” Weber-Jahnke, J. & Price, M. (2007).   

One of the major limitations in regards to the current generation of Healthcare IT capabilities is the relative lack of ability to integrate multiple structured and unstructured data sources. Most if not all EHR/EMR systems today are built utilizing a single relational database structure with minimal consideration of how to manage data structures that do not easily fit within the “record” itself. It occurred to us that the problem here is both technical and derived partly from the metaphor chosen to build these solutions around. The current metaphor; an “Electronic Record,” does not properly approximate the traditional capability encompassed within the Medical Chart. A more accurate context is the ability to exist as a continuous “Healthcare Portfolio.” The Portfolio as a metaphor is a flexible and infinitely extensible instrument. This instrument can hold or point to “n” records from “n” different providers or systems. This instrument can also provide an information and collaboration ‘portal’ interface for the patient, all associated caregivers and administrative personnel.



The Portfolio metaphor can also be extended to the Group level rather gracefully which also helps to serve as natural mechanism for shielding certain types of privacy data per HIPAA regulations for group-level analytics. This paradigm shift is founded upon the realization that a complex architecture can be centrally managed “logically” yet manifested across a federated environment. In other words, all elements of a patient’s portfolio do not need to exist in one location; however the central management mechanism requires access to the portfolio to be controlled to ensure data integrity and to allow the portfolio to retrieve information from the appropriate data stores and caches. This is referred to as “meta-information” and can be considered a Semantic Layer that binds that federated environment into a logical integration. 

The core architectural paradigm behind the next generation of automated Healthcare solutions is likely to be data fusion. The reason for this is simple – complexity. The key enabling mechanism within data fusion is reliance on metadata or meta-information. Metadata has been managed historically within individual system stacks. What that means is that the metadata was usually stored within the same system or if in more complex configurations within the system or component close to the primary user interface (and in the case of EMR solutions, the Medical Chart UI). The problem with this for Healthcare is that the community of Medical knowledge is expanding exponentially. Any attempt to centrally manage all types of medical knowledge in one system’s metadata framework is bound to fail. Part of the true strength of any such solution ought to be the ability to accommodate information not originally anticipated.

The implications of this are important, as there is no consistent method of coordinating metadata across multiple metadata sources except through custom interface development or management in most of today’s EHRs. As the scope of custom integration grows, interface management and integration become mores difficult to manage. In other words, those architectures simply are not scalable.  


Copyright 2012  - Technovation Talks, Semantech Inc

Tuesday, December 4, 2012

Medical Charts & the EHR

Today's post is a continuation of the Intelligent Healthcare theme. We're going to talk about the current relationship between Electronic Healthcare Records (EHRs) and the practice of using medical charts.



Even with the advent of new technologies, processes are slow to change, most healthcare is still managed using medical charts (although often now supplemented by or delivered through EHR systems). Ordinary diagnostic and care-related tasks such as data correlation, symptom evaluation and patient management remain part of an intuitive process with only partial system level support. In most cases healthcare system support has not led to widespread process transformation. The possibility for wide variations in both the types and quality of patient care is likely in this type of purely ‘intuitive’ environment. While there are now and have been a wide variety of diagnostic algorithms and treatment paths available to medical practitioners to choose from, determining which ones to apply has always been problematic and the lack of consistent standards in this regard is one of the main reasons for the relatively large number of quality of care issues.

The medical chart as a non-technical entity has never been fully standardized in Healthcare practice. The chart is both an information “form” for individual case incidents and is also used as the folder for iterative versions of the form across cases and related patient documents. Depending on the nature of a patient’s condition or conditions the size and complexity of the paper folder can become quite intimidating.

While there are federally mandated standards for Medical Records Information Privacy (The HIPAA Act), there are still no universally recognized standards for healthcare record data capture and exchange. The closest emerging standards are HL7 Clinical Document Architecture (CDA) and the Continuity of Care Record (CCR). While the vast majority of EHR solutions do not follow the same set of standards, there are in fact generally a number of similarities between most EHR/EMRs. A typical Electronic Medical Record application like a medical chart tends to include the following elements:

  • Some level of patient demographic information.
  • Patient medical history, examination and progress reports of health and illnesses.
  • Medicine and allergy lists, and immunization status.
  • Radiology images (X-rays, CTs, MRIs, etc.), Laboratory test results.
  • Photographs, from endoscopy or laparoscopy or clinical photographs.
  • Medication information, including side-effects and interactions.
  • Evidence-based recommendations for specific medical conditions
  • A record of appointments and other reminders, Billing records.
  • Advanced directives, living wills, and health powers of attorney
The reality is that a complex case can very easily overwhelm a traditional chart or even an EMR. The amount of information collected can in some cases rival a mid-sized database. A single patient can have multiple problems, be served by multiple specialists and can have variations of their care record which extends across multiple case instances over the years.



Copyright 2012  - Technovation Talks, Semantech Inc

Friday, November 30, 2012

Intelligent Healthcare Scenarios

In yesterday's post, we introduced a number of core capabilities that would facilitate deployment of enterprise-wide Intelligent Healthcare solutions. In today's post, we're looking at the core problems and specific scenarios under which those capabilities might be applied.

Inter-operability is over-arching problem set behind most Healthcare related innovation

There are a number of what might be considered ‘problems’ associated with Healthcare-related data inter-operability. In this context, a “Problem Set” represents a meta-category of related aspects that together comprise all elements of a problem.

The initial problem sets for Healthcare Inter-operability are:

  • Document-centric message focused integration.
  • Conflicting (Healthcare-related) terminology.
  • Conflicting standards and resulting implementations.
  • Exclusion of free text data in traditional EHR/EMR systems.
  • Lack of specific support for Healthcare practices / processes.
  • Security & Data Integrity of exchange transactions.


ID
Scenario Title
Description
S01
Cross-Provider Diagnostics
Care scenarios involving more than one diagnostic participant.
S02
Cross-Provider Treatment
Care scenarios involving more than one treatment provider.
S03
Multi-Provider Care Management
This refers to situations where care is spread across many different offices / organizations, some perhaps not affiliated.
S04
Multi-National Incident Response
For epidemic, pandemic or bio-terrorism events.
S05
Group Characteristic/s Identification
Requires access to wide ranging data sources
S06
Group Pattern/s Identification
Requires analytical capabilities and access to wide range of data sources
S07
Patient Pattern/s Identification
Even at patient level, data may be required from multiple caregivers, systems
S08
Lessons-Learned Capture
At the organization, personal or regional level
S09
Lessons-Learned Dissemination
No real mechanism exists for this besides medical journals which are proprietary, costly and restricted
S10
Intra-Organizational Integration
Enterprise level integration within the caregiver organization today is costly and complicated
S11
Organizational Healthcare Reporting
Reporting requires access to all pertinent data sources
S12
Regional Healthcare Reporting
Regional reporting requires access to all pertinent data sources
S13
Cross-Organizational Research
Currently difficult due to access issues
S14
Communities of Practice Knowledge Sharing
Today this occurs through continuing education and conferences (indirectly), there is no real-time feedback mechanism
S15
Trend Visualization & Statistical Analysis
Usually requires manual support to accomplish





Healthcare Scenarios which may apply core IH capabilities



Copyright 2012  - Technovation Talks, Semantech Inc.

Thursday, October 11, 2012

Intelligent Healthcare: EHR Assumptions

The term, Electronic Health Record (EHR), is often used synonymously with Electronic Medical Record (EMR) or Longitudinal Health Record to describe systems that capture medical chart data in electronic format. The nature of the data being captured and how it is used varies from system category to system category as well as across individual vendor implementations in every category. There is no standard solution configuration in terms of features, functions and performance. There is some standardization in relation to the data elements employed though as many vendors have attempted compliance with one or more Healthcare Interoperability standards. The design and implementation of EHRs does not necessarily take into consideration the larger ecosystem in which it will inhabit and in fact there are many different types of environments that they may be built to support including:

•    Smaller medical practices
•    Mid-sized Healthcare providers (clinics, specialty care)
•    Larger Healthcare providers (Hospitals)
•    Health Networks
•    Agency / National level (NHS SCR, DoD AHTLA, States etc.)

By now EHRs should be universal and fully interoperable - they're not...

The development and use of EHRs has in many instances been controversial and there has been significant resistance to it by practitioners and limited evidence of improved outcomes from organizations which have adopted them. One particular area of controversy revolves around whether the family of EHR solutions has either accurately understood and supported existing Healthcare processes or made any headway in actually improving those processes. Despite this situation, EHR technology has remained the primary focus for Healthcare solutions modernization or transformation. To understand why EHRs have not lived up to their potential, it is worthwhile to explore some of the (perhaps false) assumptions behind them:

•    Assumption 1 – That because much or most of current Healthcare process is ‘paper-based’ that it is necessarily inefficient. Paper-based process can in fact be highly optimized, or sub-optimized thus facilitating processes in situ. The enterprise perspective must also support the needs of component Healthcare delivery.

•    Assumption 2 – That full standardization of a domain of practice as complex and evolutionary in nature as Healthcare is even possible. And that the domain would become subordinated to the woefully incomplete (lagging) standardized view and thus tolerate degradation of care to support the larger goal of automation.

•    Assumption 3 – That technology might be imposed without engaging in full partnership with both care providers and patients. This is particularly critical in determining performance expectations in relation to care practice. In other words, if it takes a doctor 15 minutes to manage a typical patient encounter using a paper-based approach and 30 using an EHR then the EHR has failed to meet minimum expectations and communication between the IT provider and care provider failed.


Copyright 2012, Semantech Inc. All rights Reserved 

Wednesday, October 10, 2012

What is Intelligent Healthcare ?

A definition and introduction...

“Intelligent Healthcare” (IH) is a metaphor both for design and for practice with the explicit understanding that through emerging technologies those two will become ever more closely intertwined. IH recognizes that there are or will be innumerable potential domain boundaries both internally and externally that will necessarily segment ‘islands of information.’ Those islands of information represent individual and community knowledge and practice options. The role of IH is to both harness those diverse information resources dynamically and apply them back to their respective communities to enable continuous practice improvements. So at the lowest level, Intelligent Healthcare requires tools and techniques that can access and distribute data across domains as needed. As the Healthcare environment becomes more sophisticated the technical goals will evolve to encompass:

  • Pattern identification & management.
  • Trend prediction and dashboards.
  • Process and scenario driven dynamic integration of enterprise-wide data sources (the full spectrum of clinical systems).
  • Multi-level Collaboration, from the immediate organizational perspective through to Global Communities of Practice.
  • Symbiotic performance engineering (of both patient outcomes and solution service level expectations).
Intelligent Healthcare is a concept, a methodology as well as an architectural approach

The IH metaphor allows us to grow in evolutionary directions in order to achieve our primary goals with relation to Healthcare. It places all enabling technology in the context of a set of functional goals which are not likely to change anytime soon:

  1. Improved patient outcomes.

  1. Cost reduction and greater efficiency through practice / process improvement.

  1. Rapid / agile adoption of innovation or emerging technologies which enhance Healthcare provision. 

Intelligent Healthcare is more than any single technical solution, more than any single standardized approach – it finally places the real challenges up front and ensures that all component elements targeted to those challenges do not become larger than the primary functional goals. Future posts will examine the architecture of IH in greater depth...


Copyright 2012, Semantech Inc. All rights Reserved