Many organizations – public and private – use formal competitive bidding instruments to procure technical products and services. This may be done by law, policy or practice. The driving reasons are to help ensure both clear understanding of the organization’s requirements and expectations, as well as fairness in the marketplace to all potential respondents who wish to do business with the organization. HLN’s new white paper, Effective Technical RFP Development: A Guide for Jurisdictions and Other Organizations, offers some practical advice for organizations issuing competitive solicitations.
Read our new article in the October 2016 supplement to Biomedical Informatics Insights:
This article focuses on the requirements and current developments in clinical decision support technologies for immunizations (CDSi) in both the public health and clinical communities, with an emphasis on shareable solutions. The requirements of the Electronic Health Record Incentive Programs have raised some unique challenges for the clinical community, including vocabulary mapping, update of changing guidelines, single immunization schedule, and scalability. This article discusses new, collaborative approaches whose long-term goal is to make CDSi more sustainable for both the public and private sectors.
See full article (Open Access – no fee to download and read)
Some organizations have the need for a web application that can translate street addresses into latitude/longitude coordinates. Ideally, the web application could process addresses in bulk, either supplied from an Excel spreadsheet or from an enterprise data source such as a relational database; and output would be either in spreadsheet format or inserted back into a database. This brief discussion paper provides some potential solutions and strategies.
(D3) Trying on the RCKMS Glass Slipper: How Well Do Jurisdictional Reporting Criteria Fit? (HLN’s part of this larger session encompasses slides 55-67 and slides 82-103)
By Noam H. Arzt and Michael Berry
It is common practice today to encrypt data at rest, that is, data stored on servers. To build off an old adage, no one ever got fired for encrypting their data. But what protection does that really provide? Is just encrypting data enough?
First, let’s distinguish between three methods for encrypting data at rest.