|Speed Bump Comic Strip|
I predicted three themes for 2013: Mobile, Privacy, and Services. The following themes that appeared throughout the year nicely fit these three high level themes, most of the time fitting all three (Accounting of Disclosures).
Measurements toward Predicted Theme
The themes that appear in 2013 posts
- mHealth Security (1), (2), (3), (4), (5), (6), (7), (8), (9), (10), (11), (12)
- FHIR (1), (2), (3), (4), (5), (6), (7), (8)
- Safety (1), (2), (3),
- Privacy (1), (2), (3),
- DS4P (1), (2), (3),
- De-Identification (1), (2), (3),
- Accounting of Disclosures (1), (2), (3), (4),
- HIE (1), (2), (3), (4), (5), (6), (7), (8),
- Digital Signatures (1), (2)
This is satisfying to me, but not what my blog Google Analytics show was most interesting to the readers during 2013. The top most viewed articles are all from 2011 and 2012. One of them I didn’t even write.. In order, the most popular Posts in 2013 by click count:
- Meaningful Use Stage 2 - Audit Logging - Privacy and Security
- Meaningful Use Stage 2 -- 170.202 Transport
- How to apply Risk Assessment to get your Security and Privacy and Security requirements
- IHE - Privacy and Security Profiles - Audit Trail and Node Authentication
- Creating and using Unique ID - UUID - OID
- Topics (my table of contents)
- Patient Portal - view, download, TRANSMIT
- IHE - Privacy and Security Profiles - Basic Patient Privacy Consents
- How granular does an EHR Security Audit Log need to be?
- The Basics of Cross-Community Patient Discovery (XCPD) - Guest blog by Karen Witting
- Meaningful Use Encryption - passing the tests
- Meaningful Use Certification issue with Encryption of data-at-rest
- Meaningful Use Security Capabilities for Engineers
I am very happy that the most top viewed article posted in 2013 during 2013 was the one where I Define Privacy. This comes in at the 15th most popular article this year. The other articles written in 2013 that breaks the top 40 are where I Define Security Audit, and try to Define mHealth. Is this telling me that I should be in the Definition or Vocabulary space? I also posted this year that Vocabulary Standards make poor User Interfaces.
HIE Patient Identity. We will continue to work on the Patient Identity problem, more so this year. There was much talk in the past few years. There was some intense, urgent, work done in CCC and CommonWell. This work will be brought out into the open. We will learn that this is NOT at technical problem, the standards support what is needed. This is a 'business' operational issue, and a 'privacy' issue. Meaning businesses don't want to change what they are gathering, yet everyone gathers different information. If we must do patient matching, then we must all gather the same demographics with the same level of accuracy (Level of Assurance). For example, everyone must gather the SSN completely, not just the last four digits. This brings up the 'privacy' problem that this creates. We will not see a universal patient ID, but we will see what sure looks like one. It will simply be a well-structured-and-normalized mashup of the demographics all hashed together. This will fail to match sometimes, but it won't have false matches (false-positive).
Profiles. Simply the USA will realize the need for Profiles. This might not be "IHE" profiles universally. I am okay with that. I fully expect that HL7-FHIR will produce some profiles this year. I fully expect that HHS/ONC/HIT-Sc/HIT-Pol/S&I-Framework will come up with a concept closer to a 'profile'. This is not far off, but not being done today with purpose. The purpose will come when the community sees what IHE does with DS4P. The result is simple and measurable.