Open source presence

My current open source presence looks like this -

I want to change it. Contribute more to open source projects. Instead of just saying more my goal this year for open source contribution is to spend at least 20 hours every month on open source projects.

Why contribute to open source? This is very well answered on Quora - https://www.quora.com/Career-wise-which-option-is-better-Open-source-contributions-or-competitive-programming

My goals to contribute to open source -

  • Pay it forward
  • Become a better programmer

Use API or build the functionality

Should I use an API or build the functionality? Depends :) an architect would say.

Questions to ask before you choose
Is the API functionality core to the business function?
Do you need the API to be highly available?
Are there any compliance issues protecting the data flow in your application?
Is the API functionality available from multiple vendors?
In house expertise available to create the API? (NLP API)
Time to market?

Also a good practice should be to wrap the API into a vendor independent interface before using it in your application. So that you have flexibility to swap vendors or implement your own if you need to.


Design of domain specific database technologies

Is it required to design a database technology specific to a domain? A typical example of this maybe design a database which has Healthcare Ontologies as a supported datatypes. Common database operations or database functions can be healthcare specific for coding, grouping and billing.

Today healthcare standards are closed and ruled by organizations like Optum, 3M and AMA. They charge for the use of code libraries, standards and standard groupers. I think there is an opportunity for startups to understand and disrupt this space.

Not sure if it applies to other domains like Retail, Banking, Education, Gaming, Automotive, Operating System Vendors and Telecom vendors. As we have been successfully able to map the data into pure relational form. Like Sales, Product, Geographies, etc. but then there is connections data which can be expressed in the form of graph and so we have graph db.

For scientific data we have something called SciDB. But again the database is designed by the type of functions and not the domain. The databases are more generic and try to offer generic type of language to perform data operations and not a DSL. In a healthcare database a specific operation or query may say - Group Claim(Id) for DRG

If someone reading this blog comes across a domain specific database please post a link

Ideas from Telehealth and Hospital CIO track @ MIT Med GrandHackFest


TELEHEALTH

Data points on Telehealth - 
Mass General admission data - 1.5 million outpatient visits, 1.5k beds, 47k inpatient admissions. Potential of 30% as televisits
Video conferencing - trust is important - doc presence will help get better

Current departments - 
Telestroke - first found in 1996
Teleneurology - virtual visits 
Telecardiology - virtual visits 
Telepsychiatry - virtual visits 
Teleburns - virtual visits 

Barriers for adoption -
1. EHR implementation 
2. Providers are worried 
3. Regulations 
4. Security
5. Reporting 
6. Don't get paid to see people remotely 

Competitions for providers -
1. Minute clinic
2. Over the counter med
3. Community 

Ideas - 
Build a platform for monitoring - visualization tool
Decrease the efforts to adopt televisits
Increase integration and insight at the point of care

HOSPITAL CIO

Pain points -
1. Meaning full use issues - good in 2015 
2. Break monolithic EHR 
3. Usability in EHR 
4. Patient and family engagement tools are poor / value proposition 
5. Re-represent data  
6. ICD 10 BILLING ISSUE - put in wrong codes 
7. Privacy issues - HIPAA  

Ideas - 
Doctors are overwhelmed with data - Beth Hospital has 3 PetaBytes of data 
Record of the future - Wikipedia for patient


BI tools transformation from passive to active analysis

Microstrategy, Tableau, Spotfire, Qlik and the list goes on. BI tools offer software to understand and report data. But can you really understand data without under standing the business well, so the tools don't provide anything to do with business. In college I learned Matlab. Matlab had the set of tool boxes and it allowed to understand the subject better like DSP or others. 

So that's the difference between active and passive analysis tools. Passive analysis tools like the current popular once leaves it upto the user of how they want to use it, whereas active tools can provide you toolbox. 

The BI tools needs to have plugin ecosystem to create domain specific BI tools. Like Healthcare BI tools, why is the BI market hesitant to create that? Or why is the BI market hesitant to open up there products as platforms. From my experience I see that the BI tools with such an ecosystem will be successful especially with small-mid companies who cannot afford to have their own experts in the domain to provide classification and other basic data analysis. 

But the tools who have such an ecosystem like SAS are too expensive for small enterprises. Probably then the solution is Web BI tools. Lot of them have emerged in last few years definitely few of them might have thought to be platform for the specific domain instead of being generic BI tool. 

 Waiting for more active analysis BI tools.