I strongly agree with one point of this strategy+business Enterprise Architecture Planning 2.0 article. That is to get Enterprise Architecture Planning out of the IT department.
A blog post by Eric McNulty reminds us of our simplicity over complexity core principle. In his post he addresses some of the reasons why simplicity is important.
Why aren't more things simple and why does complexity keep crashing in?
As Abraham Lincoln said, “I'm sorry I wrote such a long letter. I did not have the time to write a short one.” Mark Twain is also quoted as saying, "I didn't have time to write a short letter, so I wrote a long one instead."
Simplicity is hard. Simplicity requires knowing what is important and what is not. To overcompensate for not knowing organizations and people try to do everything and be everything.
So, if complex is easier, and simple is harder - why do I want to simplify?
Each of these items has a direct impact on the customer's expectations and the customer experience.
Two key approaches to remove complexity are:
Design all processes and products with the focus on the customer. Understand the needs of the customer and meet those needs as simply as possible.
Only add tasks, features, and functionality to your process and products that are absolutely required. Remove any that are no longer required. Leaving unnecessary bloat in your processes and products is a big cause of complexity.
Harvard Business Publishing Webcast - Take Complexity Out of Your Company, with Ron Ashkenas, author or Simply Effective.
We continually preach that customer experience is not user experience and user experience is not graphic design. However, a good customer experience requires a good user experience and a good user experience requires good graphic design.
Two resources that we like for learning more about graphic design are:
The InnovateNYP: Pediatric App Challenge is the first of its kind and will award $50,000 in prizes to winning applications.
The 10-week long Challenge will kick off on the weekend of March 12 with the InnovateNYP: Pediatric Appathon.
On February 11, 2016 the HHS Office for Civil Rights posted new guidance on their mHealth Developer Portal to provide scenarios where the Health Insurance Portability and Accountability Act (HIPAA) regulations might apply to mobile health applications.
The mHealth Developer Portal was launched last fall and is targeted at answering developer's questions about HIPAA.
"Naming the new, completely written from scratch ASP.NET framework “ASP.NET 5″ was a bad idea for a one major reasons: 5 > 4.6 makes it seem like ASP.NET 5 is bigger, better, and replaces ASP.NET 4.6. Not so."
The CDC National Center for Health Statistics (NCHS) has published a brief titled "Adoption of Certified Electronic Health Record Systems and Electronic Information Sharing in Physician Offices: United States, 2013 and 2014" based on data from the "2014 National Electronic Health Records Survey."
This report uses the National Electronic Health Records Survey (NEHRS) to describe physician adoption of certified EHR systems from 2013 to 2014 across the United States and the extent to which physicians with certified EHR systems share patient health information.
Good news is that certified EHR usage by office-based physicians is up and reached 74.1%.
47.8% of those with certified EHRs were sharing data, compared to 29.7% of those who didn't have a certified EHR. The unanswered question is whether the certified EHR technology was the reason for increased sharing or whether more technology advanced practices had certified EHR technology and that was also the reason for more aggressively pursuing sharing.
The ONC has launched a new 4-part micro-blog to help explain that HIPAA doesn't prevent the use of PHI for patient care. The first blog post is titled "The Real HIPAA Supports Interoperability."
They cite the misconception that HIPAA "makes it difficult, if not impossible, to move electronic health data when and where it is needed for patient care and health" as the reason to clear up the confusion.
In their words:
What many people don’t realize is that HIPAA not only protects personal health information from misuse, but also enables that personal health information to be accessed, used, or disclosed interoperably, when and where it is needed for patient care.
I believe that this misconception has been widely spread because the focus of HIPAA training and enforcement efforts have largely been related to the privacy and security components of HIPAA.
Organizations in general, and healthcare in particular, are very good at risk management and avoidance. On the flip side, they are generally bad at sharing because of time, cost, security, and risk considerations. So it shouldn't be any surprise that even though "Portability" comes before "Accountability" in HIPAA the portability part has been neglected in comparison to the accountability part.
We have been involved in many interoperability discussions, including with non-healthcare organizations, and security and risk are always major constraints. Sometimes there is the concern of being able to legally share the information, which this series should help put to rest.
However, many times it is related to concerns over securely sharing the data over a large distributed public network. Cybersecurity knowledge is still hard to come by and costs can be relatively high. Better "safe harbour" guidance and protection would go a long way to help in this area.
The ONC has announced the 2015 Edition Certification Final Test Method.
It outlines the requirements for evaluating conformance with the certification criteria defined in 45 CFR Part 170 Subpart II of the 2015 Edition Health IT Certification Criteria, 2015 Edition Base EHR Definition, and ONC Health IT Certification Program Modifications final rule as published in the Federal Register on October 16, 2015.
For each certification criteria it includes the certification companion guide, test procedures, test tools, and test data. Test tools and test data are not yet available for all criteria.
The certification criteria includes:
We will individually address some of these in future posts.
In the McKinsey&Company article "Debunking common myths about healthcare consumerism" by Jenny Cordina, Rohit Kumar, and Christa Moss they analyze the increasingly active role that consumers are taking in healthcare decision making and its impact on commonly held myths.
The first myth that they show to be false is that "consumers don't bring the same expectations about customer experience to healthcare that they bring to retail or technology companies."
The last myth that they address is "most people are willing to trust insurers to store their health records." As we have addressed many times, trust is extremely important for all customer experiences but it is critical when it comes to healthcare information. In their Consumer Health Insights Survey they found that a large majority would only trust their provider to store their patient generated health information. Only a small minority would trust their insurer or other commercial third-party companies.