I am co-chairing the first Hackathon at the SIIM 2014 Annual Meeting along with Chris Meenan. Check out participation details here.
If the initial interest expressed is any indication, it is going to be an awesome event. I hope that you can join us.
Interoperability
JDI Article Published – REST Enabling the Report Template Library
I contributed to an article recently published in the Journal of Digital Imaging. The primary author is Brad Genereaux (@IntegratorBrad). His blog is here.
This article examines the use of a REST API to discover, retrieve and use structured radiology report templates from an on-line report repository.
Check it out and let me know what you think.
Favorite Blog Posts of 2013
As the first calendar year of my blog draw to a close, I thought I would compile a list of my favorite blog posts from 2013. I hope everyone has a safe, happy, healthy and prosperous New Year.
- 100th Blog Post: What I know about Software Development and Crisis Management
- The rise of the mobile-only user …and how this helps the underpriviliged
- Review of Stage 2 Meaningful Use Test Procedure for Image Results …and other MU tests
- Quebec EHR …the difference 2 years makes
- Video – Empathy: The Human Connection to Patient Care
- Designing for the ‘Public’ and the ‘Pros’
- Articles on Mobile Health Applications and FDA Regulation
- Plug-ins vs. APIs
- Article from HIMSS: PACS will not remain a self-contained data silo
- Blog posts on SIIM Web site (Part 1 and Part 2)
JDI Article Published – PACS 2018: An Autopsy
An article I submitted to the Journal of Digital Imaging has been published electronically.
Told from the year 2018, it looks back at the market and technical forces that results in the deconstruction of PACS (and RIS) as we know it.
Check it out and let me know what you think.
Check out the Blog Post: Driving Developer Adoption
Brad Genereaux, co-chair of DICOM Working Group 27, posts on how to drive developer adoption.
Definitely worth a read (be sure to follow him if you work in healthcare IT).
Article – Privacy guru knocks patient ID as ploy
I posted some thoughts recently about an article on impact of privacy on patient record sharing.
Now, here is an article that discusses the merits of giving the patient control over how they are identified and how their records should be shared.
Fundamental to this are the two approaches:
- A formal managed infrastructure that provides (cross-)identification and record transport services (like eHealth Exchange, formerly NwHIN), or;
- An ad hoc one that allows participants to send record information from point-to-point (ala the DIRECT or Blue Button Plus projects).
Some thoughts…
- As I discussed with a respected colleague of mine at the recent ACR Informatics Summit, I believe that new standards like the emerging DICOMweb (aka QIDO-RS, WADO-RS, STOW-RS) and HL7 FHIR will more easily enable ad hoc exchange of records, but the role of more formal application infrastructures, like those defined by IHE XDS (and its domain specific variants, like XDS-I) will still be used where a mandate for managed patient records across a consortium exists (such as in Canada with the Canada Health Infoway).
- As I mentioned in my prior post, society may have different motivations than those paying for the infrastructure and tools. This article attempts to express some of the concerns consumers may have about how their data is handled, which contrasts with the prior article’s statements about how “nobody under 30 cares about privacy”.
Article – CIOs push for patient ID progress
For those of you faced with connecting patient records with different patient ID domains across enterprises, or within an enterprise, this article is worth a read.
Some thoughts…
- The need/want for privacy is not the real issue. The issue is the general lack of understanding in patient ID management and strategies for dealing with them.
- I am interested to see what the ONC (through their new Patient Matching Initiative) does to solve this issue. Many enterprises have invested heavily to implement solutions (technical and staffing and policies) for dealing with multiple patient IDs. A new solution, however novel, will not be enthusiastically embraced by organizations that are committed to a path already.
- Beyond cost and technical issues, there are societal ones. Not all people will be willing to be assigned a number by their government to track all their health data.
- I believe observations that “nobody under 30 cares about privacy” are misguided and just wrong. It is true that younger people are more open about their social lives and personal interests, but that does not mean they want their sensitive health (or banking) information in the public domain.
Article – New HIPAA rule could change BAA talks
As this article explains, the rules of accountability need to apply to all parts of the delivery chain, from the healthcare provider to the infrastructure vendor.
It is my experience that the readiness of the vendor to provide the necessary security controls (technical, policy, etc.) is usually not the issue. It is often the healthcare provider staff that lacks the knowledge of appropriate and effective controls that prevents proper security from being in place.
For example, even when proper single sign-on (SSO) methods are available in systems, rather than taking the time to implement this between systems (which often requires some learning), staff will often default back to wanting to simply pass a user ID and password (often a generic one) from one system to the next, because that was all they could do 10 years ago to avoid having the user log into multiple systems.
Key Images are… well, key!
As I discuss key images with vendor and healthcare provider staff, I have come to the realization that they are not well understood. Let’s see if we can correct that.
What are key images?
In most contexts, they are images within a medical imaging exams that the Radiologist reviewing the exam wishes to indicate for others, such as the referring physician and clinicians, that they are important in understanding the diagnosis.
In other context, they may represent important images for teaching purposes, quality control, surgical planning or other purposes.
In any case, they serve some importance over other images in the exam and the user wishes to communicate this. That’s why they are ‘key’.
Who creates key images and how?
In the digital world, any authorized user can mark an image as a key image on any system that supports this function. Typically, this function is restricted to authorized users like Radiologists on systems like PACS; however, they may also be created by Technologists/Radiographers on modality workstations or clinical imaging systems, like an Enterprise Viewer in an EMR.
Key images are normally created in one of two ways:
- Manually by selecting an image and choosing a key image method
- Automatically by creating some other form of markup or measurement on the image (implying that it has some importance)
The latter capability is important as getting Radiologists to take the time to mark images as key is often difficult. And if they are not created, the consumer does not benefit from them.
Special case: In systems that allow the user to create spine labels, these should not result in automatic key image creation.
ACR 2013 – Patient Engagement for Radiology
Presentation by Dr. Alan Kaye (Advanced Radiology Consultants) at ACR 2013 Imaging Informatics Summit, quoting Dr. Rawsson: “It’s hard to put the patient at the center of the universe if you’re sitting there yourself.”
Don K Dennison 