How we built our cloud based physician portal web, mobile and HL7 Interface engine – 01

AZ-Tech Radiology is one of the leading medical imaging organization that provides the highest quality imaging services utilizing state-of-the-art equipment and technologies in Arizona.  Our primary goal is “Keeping the referring physician happy”, all roads lead to the ease of delivery of “radiology reports” to them and their sending of orders to the lab”

In order to meet the goal, we have to have state of the art technological solution which drove us to build the new cloud based connected IT systems:

  1. Radiology Information System
  2. HL7 Interface Engine which connects all of our modalities, external EMR and Insurance companies, pushing data to the cloud in a secure manner.
  3. Promotional Website @ https://www.aztechradiology.com
  4. Physician Portal to delivering the reports @ https://provider.aztechradiology.com/
  5. Physician mobile app @ https://m.provider.aztechradiology.com/

In this blog post I would like to share the Architecture we came up with which powers our IT systems.

HL7 Interface of our Modalities (Imaging equipment) with RIS

 

AZ-TECH HL7 ARCHITECTURE

Industry standard HL7 messages going out from RIS & coming in to Helen RIS

ADT A28 Add person information
ADT A31 Update person information
ORM O01 Order message
ORU R01 Unsolicited transmission of an Observation message
SIU S12 Notification of new appointment booking
SIU S14 Notification of appointment modification
SIU S15 Notification of appointment cancellation

End-to-end HL7 interface engine – on-prem to cloud connectivity

AZ-TECH INTERFACE ARCHITECTURE

Industry standard HL7 messages going out from RIS & coming in to Helen RIS

  1. Available On Web And Mobile
  2. Highly Secure With Two Factor Authentication
  3. Immediate Near Real Time Access To Reports
  4. Text/Email Notification When Stat Report Is Ready
  5. Reports Can Be Searched By Dob, Patient Name, Date Etc.
  6. Reports Can Be Filtered By Stat
  7. Lightning Fast Free Text (Natural Language) Search Against Reports Powered By Elasticsearch & Lucene Index
  8. Cross The Border – (we call Inter State) : Multi Location Clinics Can Search Reports /Patients Across Their Locations Served
  9. Cross The Border – (we call Inter Country) : Providers Can View Reports Of Other Providers With Online Consent
  10. Reports In Hl7 Format Can Be Exported To Import Into Their EHR System
  11. Orders Can Be Placed Online – Hl7 Upload And Forms Based Upload
  12. High Resolution Diagnostic Images Can Be Viewed Online Without Any Client Tools Installation.
  13. Real-Time Analytics / Kpi Dashboard For Clinic Administrators
  14. Create And Manage Your Users & Roles Online
  15. View Who Did What, When?
  16. Free Integration With our partner’s EHR / EMR Software’s For Orders And Reports
  17. HIPAA Compliance ready

 

End result

After we implemented the solutions in phased manner starting from Jan 2018 uptil now, following are the benefits we gained

  1. Average speed of our report delivery time reduced from days to minutes
  2. Cost of the delivery of reports reduced multi-fold otherwise we enagened half a dozen employees faxing the reports to the physician office manually
  3. We can deliver the reports to physican hands thru our mobile solution
  4. We automated the sending of Fax (reports) to the clinics who still needs paper copy of the reports
  5. Customer satisfaction thru enhanced user experience in the form of simple to use web and mobile application
  6. Powers 1000’s of reports per day with ability to auto-scale to handle more reports in the future

My Team is Ready-What do I mean by that?

Its been almost 6 months completed, we started our cross platform native mobile application development competency

When we just started this competency, Our CEO asked this question My Team is Ready-What do I mean by that?

Myself and my friend Ciby Baby, practice head of this team sat and discussed to frame the answer (plan) for his question and we came up with the following.

1. Estimation Methodology in place.

2. Process to be followed for development and testing in place.

Here, the coding part is not extensive (micro app), but the executable has to be generated for

A. Different platforms

B. Different OS Versions

C. Different Devices (Form factors)

3. Setting up of Dev/Test & build server environment in place and, ready for use.

4. 5 different demo apps will be developed and tested and ready for demonstration for the potential clients.

5. UI & coding guidelines, for mobile software development in place.

6. Team well trained in application development, and conversant with TortoiseSVN (Subversion System) in place. Training material ready for use and for future reference.

7. Marketing collaterals in place.

A. Document mentioning the service packages we can offer to a customer.

B. Document mentioning case studies, put in a format so that the marketing team can use in an effective way.

C. Document on Basic technical aspects of typical Mobile app. (Micro Apps, Server Components, Security, and Database).

D. A Document on typical queries that a potential customer can ask. And answers for the queries (FAQ).

E. Familiarize the marketing team with Demo Apps that have been developed and train the Marketing team on how to use it. Make a document to relate the Demo apps with, couple of use cases.

8. Modified website content, showing the specific services that we will be offering, along with the demo apps, and video of the demo apps in action in place.

9. DeenstDesk –Lite (our incident management product) and Redmine-Lite, hosted on Android market and App Store and ready for download.

10. App Store registration in place.

11. Complete project management will be done using Redmine, and (team will be trained for the same) will be ready for use.

A. Task Assignment.

B. Progress Tracking.

C. Time Sheet.

D. Bug reporting and tracking.

E. Documentation.

F. Mapping of SVN to Redmine and tracking the version’s, from Redmine.

12. The team will be having the following skill set /capability

A. Development of Cross platform native mobile application using HTML5, JavaScript, CSS3, Jquery on Phone gap framework.

B. Development of Cross platform native mobile application using HTML5, JavaScript, CSS3, Jquery on Rhodes framework.

C. Application development using cross platform frame work (Phone Gap, Rhodes), involving Barcode scanner.

13. The team will not be having the following skill set /capability

A. Native Application development on Android (Smart phone and tablets) platform using Java.

B. Native Application development on iOS (IPhone, IPad) platform using Objective-C.

 

And today, I can proudly say we have achieved almost everything we mentioned above.