Monday, February 29, 2016

How to Execute and Implement a Cross-enterprise Imaging Strategy.

In the US, more than 90 percent of healthcare institutions have a radiology PACS (Picture Archiving and Communication System) in place managing medical images in a digital format. However, sharing these images has been a challenge, especially when they are to be shared among different enterprises. There are many barriers, ranging from lack of infrastructure, non-unique patient identifiers needing patient information reconciliation, security and privacy issues, and a lack of incentives by the providers to share them to begin with. This lack of incentives can only be solved by having the proper policies and motivation in place, possibly using federal regulations such as the Meaningful Use incentive program, which, along with other quality criteria, has now been rolled into Medicare Access and CHIP Reauthorization (MACRA) requirement in the US. However, incentives won’t work unless the infrastructure and right architecture is in place.

How are images exchanged within an enterprise? There are two options: If there is a VNA, one could access the VNA through a universal viewer, or if not, one can provide a workflow manager that sits in between the viewer and multiple image sources (i.e. PACS systems) and is able to provide a universal worklist. These workflow engines are available from third parties and/or PACS vendors and are useful as long as they know how to interface with the different PACS vendors’ archive/image management systems.

To access images from outside the enterprise, one can use image brokers that allow for storage of the images in the cloud, basically managing the access by external physicians. This is a good solution for big institutions that have a large referral base: The institution will tell a physician to sign up with the broker/service provider, and, if authorized, will have access to the studies of his or her patients. The disadvantage is that the interface protocols are often proprietary. Therefore, if you need to access images from multiple enterprises you might need to sign up for their affiliated providers/brokers and have multiple gateways connecting to your PACS.

What is needed to implement a cross-enterprise imaging strategy? First of all, it is NOT necessary to have a deconstructed PACS, VNA, uni-viewer, or anything else that is touted as the latest and greatest by imaging vendors. One needs to look at its use case and find the best solution depending on access to the existing PACS and/or VNA’s, and available infrastructure such as gateways and HIE’s.

When implementing cross-enterprise imaging one should be prepared to a deal with interoperability issues such as finding the right comparisons and priors from other image sources as body part descriptions and protocol definitions are non-standard and likely differ. Hanging protocols for studies from different enterprises might not work requiring configuration changes and/or changes in the image metadata to make them consistent. Look for a vendor who has experience with this and is able to map and/or facilitate these. The same applies to interfacing to the different PACS/Image managers, especially for the workflow engine as each vendor has its own proprietary protocol for synchronizing the worklists, look for proven performance.

Do your homework, check with colleagues and friends who have the same vendor and/or use case and find out what their issues are and how they got resolved. If you take these pre-cautions, you will likely succeed, but expect it to be a bumpy but fun ride. For an in-depth discussion on this topic you can download a comprehensive six page white paper here.

Wednesday, February 24, 2016

Top ten PACS SA skills to support new trends and technologies.

The PACS system administrators’ (SA) profession is relatively young, i.e. 15 years at the most.
As a PACS SA professional, it is critical to keep up with new developments to make sure that you can support the intricacies and ever widening range of clinical specialties and technologies of these systems. Let’s look at some of the major changes in technology and their scope and how they impact the required competencies needed to support these.

1.       Detailed DICOM data format knowledge and basic coding familiarity.
2.       Familiarity with HL7 order structure to perform the DICOM mapping correctly.
3.       Implementing basic security measures and creating tools for data mining and analyzing audit trails.
4.       A SA needs to know how to use the most common tools such as Crystal reporting and even basic SQL commands to perform custom queries of databases.
5.       Familiarity with the EMR, and with mobile applications to support the remote image access.
6.       Evaluate the specifications of the HIE’s and match those with the ones of his or her PACS system.
7.       A good understanding of the so-called DICOM SOP Classes to anticipate new modalities.
8.       Implementing a “Deconstructed PACS, requiring a SA to have troubleshooting skills, and know how to evaluate log files, use DICOM sniffers and validation tools.
9.       Know how to look at HL7 messages and interpret them to allow for testing, integration and troubleshooting.
10.   Last but not least, the SA becomes, not only a mentor, but also trainer and second level support, otherwise it becomes unmanageable. This requires very good teaching and training skills.

As a healthcare imaging and IT professional it is important to stay up-to-date, and there are plenty of learning opportunities to do this, so there is no excuse for a lack of knowledge and/or skills to meet the increasing demands of this exciting field. For a more detailed breakdown and about the why and how of these skills, you can access the complete white paper from OTPedia, our healthcare IT web resource here.