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 Healthcare IT. Show all posts
Showing posts with label Healthcare IT. Show all posts

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, November 29, 2012

Intelligent Healthcare Capabilities

We introduced the concept of Intelligent Healthcare across several posts so far:


Over the next several months we're going to cover a number of related IH topics and we thought it would be worthwhile to capture some of what we consider to be the most important IH-related enterprise level solution capabilities.

Next Generation Healthcare IT innovation begins with vision...
There are two perspectives into Intelligent Healthcare (IH) capabilities; the first is based upon how IH can be exploited as a methodology to orchestrate the design and implementation of Healthcare IT solutions. The second perspective is based upon how those solutions developed using the IH methodology actually impact the practice of Healthcare. Both perspectives are vital in helping to understand and support the eventual realization of the benefits implicit with Intelligent Healthcare

ID
Capability Title
Capability Description
C1
Patient-Focused Performance Engineering
Attributes that can be identified and included within any Healthcare solution design paradigm.
C2
Agile Lifecycle Federation
The ability to define solution best practices and make those practices available to communities either as recommendations or solution compliance guidelines.
C3
Solution Performance Metrics
Definition of systems performance expectations with strategies for mitigation of issues when or if they may realized. (SLAs with engineering support)
C4
Scenario-based Design Patterns
Definition of integration patterns; at the data level, services level, infrastructure level and combined. 
C5
Dynamic Collaboration
Web 2.0 morphing into 3.0 – using Social Publishing capabilities to replace other traditional software support and tie together communities at a more detailed level. This covers project management, requirements management, COI management etc.
C6
Community Process Management
The ability to collaboratively define, publish and share process-based knowledge and functionality.
C7
Clinical Decision Support (CDS) Reference EA
Definition of follow-on architectures that can benefit from the Connect core – these reference architectures can help to further harmonize inter-operability initiatives.
C8
Semantic Reference Architecture - (plus management of Healthcare Ontologies)  
Illustrating prototypical architectures for extending data inter-operability using emerging technologies such as RDF databases.
C9
Federated Enterprise Architecture
The ability to reconcile EA’s across domains using a Wiki-based knowledge framework rather than through proprietary EA tools.
C10
Innovation Management
Development of Innovation techniques, tools and processes designed to support integration of new technologies into existing initiatives. This capability provides IH with the proactive perspective needed to anticipate issues years ahead of time.
C11
Trend Identification
The ability to engineer trend management capabilities both within individual (local) and group (global) perspectives.
C12
Automated Data Collection
Self-configuring interface negotiation and message transport. 

All of these capabilities are designed to facilitate a new paradigm wherein medical information becomes dynamic and problem-solving becomes collaborative.


Copyright 2012  - Technovation Talks, Semantech Inc.

Wednesday, November 14, 2012

Understanding Healthcare Inter-operability

by Stephen Lahanas

Over the past twenty years or so, a number of standards groups have arisen to develop, manage or reconcile Healthcare data or IT-related standards. Much of the focus over the past decade has been dedicated specifically to data exchange standards and identifying standard data elements for various sub-domains of Healthcare practice automation. The primary standards bodies involved in these activities include but are not limited to the following organizations:

·       International Standards Organization (ISO)
·       International Electrical and Electronics Engineers (IEEE)
·       World Wide Web Consortium, Health Care and Life Sciences Interest Group (W3C-HLC)
·       Health Level 7 (HL7)
·       The American Society for Testing and Materials (ASTM)
·       National Institute of Standards and Technology (NIST)
·       Integrating The Healthcare Enterprise (IHE)
·       The Accredited Standards Committee X12 (ACS X12)
·       The National Council for Prescription Drug Programs Standards Charter Organization (SCO)
·       Clinical Data Interchange Standards Consortium (CDISC)
·       Certification Commission for Healthcare In-formation Technology (CCHIT)
·       Federal Health Architecture (FHA)
·       Office of the National Coordinator for Health IT (ONC)
·       American National Standards Institute, Healthcare Information Technology Standards Panel (ANSI HITSP)
·       Workgroup for Electronic Data Interchange for Healthcare (WEDI)
·       Digital Imaging and Communications in Medicine (DICOM)
·       The International Health Terminology Standards Development Organization (IHTSDO)
·       Association for Healthcare Resource and Materials Management (AHRMM)
·       The OMG Healthcare Domain Task Force (DTF)
·       American Dental Association (ADA)
·       International Council on Medical & Care Compunetics (ICMCC)
·       Health Care Financing Association (HCFA)
·       European Health Management Association (EHMA)
·       Healthcare Information and Management Systems Society (HIMSS)
·       Health Industry Business Communications Council (HIBCC)
·       Emergency Care Research Institute (ECRI)
·       Canadian Standards Association (CSA)

Believe it or not, this is not an exhaustive list and there are literally hundreds of formally published Healthcare IT related standards to contend with. In many cases, the function of Healthcare Inter-operability has become a “standards integration” or reconciliation activity. 

Principles of Healthcare Inter-operability within "Intelligent Healthcare"

Healthcare Inter-operability is largely today a review of data exchange considerations. The reason for this is simple; passing data is or should be far less complex than designing application capabilities in unison across the multitude of systems and organizations that employ some form of Healthcare automation. This is the essence of ‘loosely coupled’ integration, the notion that the source systems are largely abstracted from the design conventions of any other source system and can send or receive data externally as long as those data sources can be mapped to some part of the source system schema. The prevailing theory of how those data exchanges should be managed is that specific formatting standards ought to be used to more or less regulate the message structures. This standardization approach began before the advent of XML, through Electronic Data Interchange (EDI) approaches and others but has since accelerated. EDI while successful depended upon relatively simple data exchanges and complete agreement across industry segment participants in order to enjoy the full benefit of the resulting standard message formats. This approach works to a degree, but does not often support complex requirements.

The good thing about specialized IT standards is that they can help to coordinate best practices amongst hundreds or thousands of organizations working in the same industry domain. The bad thing about specialized IT standards is that they don’t always keep pace with technological change and they may not support extremely complex environments well. Healthcare represents perhaps the most complicated single practice community of its size in the world. While there are many areas within which standardization can be easily achieved in Healthcare, data management is not one of them. Not only that, though, there is a serious argument to be made that extreme data standardization (or specialization) in Healthcare might actually prove to be counter-productive and could degrade the overall quality of care.


Copyright 2012  - Technovation Talks, Semantech Inc.

Tuesday, October 30, 2012

The Intelligent Healthcare Manifesto

The United States is poised for a revolutionary change in how Healthcare is perceived, how it is managed and how it serves us; both as patients and as a society. For many, the only solution to better Healthcare lies entirely in massive amounts of new spending – however a reexamination of the processes underlying Healthcare suggests that money and technology alone can be wasted if not properly orchestrated. The true potential for the next generation of Healthcare provision in this country requires a paradigm shift in perceptions, a recognition of several fundamental truths that when taken together will redefine the practice of medicine in our lifetime.
Truth 1 - Technology has always played a pivotal role in medicine across the ages, yet today technology is much more than an enabler - it is transformative force. Technology is becoming intelligent.

This is not the same as Artificial Intelligence (AI), in the sense that the technology thinks for itself or for us. Rather, the intelligence we're talking about here refers to the ability to combine and contrast information and infuse that data within the day to day practice of medicine and to view medicine as continuum rather than a series of potentially unrelated events or incidents.

Truth 2 – Healthcare is a system of systems. The human body is an integrated mechanism rather than a set of disconnected parts and pieces to be managed in care “stovepipes.” Every element within any given hospital exists symbiotically with every other to form a single, working entity. And every hospital, doctor’s office and clinic forms a symbiotic relationship with every other throughout the nation to comprise our Healthcare infrastructure. Impacts to any portion of this delicate, tiered structure affect every other aspect of Healthcare provision.

Truth 3 – The number one challenge in medicine is now and has always been complexity. Complexity takes its form in the vast wealth of medical knowledge, techniques and tools available to us, as well as in the monumental amount of biological diversity present within each and every human body. Defeating complexity requires the ability to adapt rapidly to changing paradigms and situations – institutions too rooted in tradition often loose opportunities to excel and overcome previously insurmountable challenges.

Truth 4 – The time spent outside of the healthcare system is just as important or perhaps even more important than time spent within it. Quality of care outcomes do not begin or end based upon treatment events – they are the result of a continuum care that lasts a lifetime.

Truth 5 – When comprehensive Healthcare isn’t provided to all, all are placed at risk. This imbalance costs more than having paid for everyone’s care as it throws the entire system into havoc and introduces an element of chaos that cannot be properly mitigated. All care may not be equal, but there are standards for adequate care that can be followed as a public health safeguard that can and will improve our current situation.
The potential that is nearly upon us is staggering - we are close to being able to position all medical knowledge at any practitioner's fingertips and provide it to them in such a way that allows for efficient contextualization, per patient and per scenario. Intelligent Healthcare is a responsive interactive process - a dynamic collaboration between caregivers from across the globe and between individual caregivers and patients.




Intelligent Healthcare is Patient-Centric

Intelligent Healthcare recognizes that healthcare quality and the ability to de-conflict knowledge are intricately intertwined. As the nation stands ready to reexamine its Healthcare policies, we have an opportunity to extend that exploration beyond considerations of access, affordability and insurance coverage options to a core examination of the processes of Healthcare itself.

We don’t need more money, more equipment more prescription drugs, more genetic testing per se, what we need first is the ability to correlate the capabilities and knowledge we’ve already attained, and a way to provide generic care options to all – doing that would provide us with a phenomenal increase in efficiency and quality of care in the very near future.


Copyright 2012  - Technovation Talks, Semantech Inc.