There are stories that beg to be told. Here are some of the projects which illustrate the success dropLogic can bring to your company. Sometimes they are largely technical achievements, other times they are the result of just being observant. In each case, these milestones of success represented an outsized return on the investment made.

Solid concept, rescued from Technical Debt

A Patient Health Record (PHR) is an application which allows people to document their health conditions, history, allergies and other information vital to their care. It is most critical when changing doctors, in an emergency situation and as a way to more deeply engage people with their own healthcare. As electronic record keeping becomes more integrated and in some cases required when delivering modern healthcare services, the PHR has become more of a necessity to some companies than ever before.

A private client had produced their own Patient Health Record. It was based on internal business requirements and offshored to a foreign development shop. What was returned was functional, however fundamentally flawed:

  • Technical Debt - It was written using methods and technologies not familiar to the company’s in house development team. This meant that further work to this product would require sending it back overseas or acquiring a comparatively rare skill set in new developers locally.
  • Insecure - It relied on “dynamic SQL” to retrieve and manipulate data. While this method worked, it was in direct violation of the company’s Data Security Governance standards which prevented its use in production.
  • Minimal Compliance - HITECH requirements concerning the portability of patient data were only minimally satisfied by the ability to print the full record.
  • Non-Compliance - The system did not use clinical nomenclature (CPT4, ICD9, NDC) to most accurately represent Procedures, Diagnosis and Medications.

A thorough review of the solution, as well as industry expectations for a Patient Health Record lead to the following recommendations which were approved and executed.

  • Use Familiar Technologies – Although an attempt was made, there were few technical artifacts which could be retained. Based on the internal development team’s background, skillset and the needs of the solution the PHR was rewritten using the company’s current Microsoft technology. In brief the solution employed the .Net stack, using a Service Oriented Architecture (SOA), SQL Server and compiled Stored Procedures.
  • Portability to Microsoft HealthVault – Proper portability was achieved by choosing the Continuality of Care Record (CCR) format by the ASTM and using this universal format for exporting Patient Health information as a means to transport data into Microsoft’s HealthVault application.
  • Use of Industry Coding – Where ever Diagnosis, Procedure or Medication information was to be entered, an auto-suggest box (similar to Google’s) was created where by text matches were attempted. If the patient chose a value which was internally recognized, its medical code was likewise recorded. This information further enriched the CCR and thus the export dataset into MS HealthVault.

The effort was completed over a three month period. The resulting system was recognized as a sizable factor in the acquisition of a major new client. The PHR was also seen as a mark of legitimacy, forward thinking and judicious use of resources by a potential partner who said:

We spent more than one year and over $8 million on our PHR and it neither looks nor operates as well as this one.

New revenue stream out of thin air

While working on another project, it was identified that there were client services being performed through traditional transport mediums such as email and printed copy. Business Intelligence reports (using SSRS), training materials and programs specific to new client implementation were being printed, mailed or electronically delivered to their clients.

The client had licensed a social media suite called Telligent Community for other purposes; however it contained a feature set well suited to client communication and document storage. A solution was devised and implemented where by utilization and ROI reports designed for the client’s Program Management Team were pre-formatted and made available in near-time by logging into a private instance of the community software. By the same means, a new client roll out was better facilitated by using the community to distribute documentation, facilitate conversation and make important information easily available (such as the roll out calendar and targeted contact information).

The initiative required no additional licensing; planning was performed weekly, it did not impact other internal efforts and required very little actual new code as the solution was a “mash up” of existing internal services. This was an example where by current assets were woven together into a product which became monetized itself.