Home » Readers Write » Currently Reading:

Readers Write: Our Experience with Epic’s App Orchard

November 19, 2018 Readers Write 2 Comments

Our Experience with Epic’s App Orchard
By Chinmay Singh

Chinmay Singh, MBA, MSE is co-founder and CEO of SimplifiMed of San Francisco, CA.

image

SimplifiMed went live last month on App Orchard after several months of work. I believe other startups can benefit from our experience as they pursue integration with Epic.

We integrated with many other EHRs before Epic, including Athenahealth, Centricity, and Drchrono. As I review my experience, there may be a whiff of unavoidable comparison.

1. Epic is the most customer-focused EHR vendor

This became clear to me in my first call with Epic’s App Orchard team. I could vividly imagine a customer in the center of anything App Orchard team discussed — workflow, security, or marketing message. For this reason, I would recommend that startups first integrate with other EHRs, learn from that, and then approach Epic.

2. The App Orchard team knows the customer

Your contact at App Orchard is unlikely to be a mere project manager. He or she will be an active participant and will gently prod and challenge you on your workflows and the selection of APIs. If you don’t have an active Epic customer, this is one of the best resources you have to compensate for the lack of information. Use it.

3. Epic listens to App Orchard members

We all have heard about a certain recalcitrant Midwest company. I was surprised at how receptive the App Orchard team was to my suggestions on the program, pricing, and terms. They listened to my concerns and responded to them in a timely fashion, and I assume that the new program terms were partially influenced by the feedback I provided to them. Reach out to them with your feedback.

4. App Orchard documentation is lacking

The API documentation is very basic, and in some cases, unusable. For example, there is no explanation of the different versions of the same APIs. Or that two different APIs appear to be doing the same thing (they are not) without a good explanation. The advice in #1 and #2 above partially compensates for this. If Epic team needs some inspiration, they should look at Athenahealth’s developer suite. Not only does Athenahealth have more robust documentation, all of their APIs can be tried in the sandbox.

5. No Hyperspace

This is the biggest issue with App Orchard. Without access to Hyperspace, it is difficult to test the product. Moreover, Epic periodically resets the back end, forcing you to re-create your test cases. This is a huge time sink. As we are experiencing now, prospects want to see a demo of SimplifiMed working with Epic. But without access to an Epic instance, we are unable to do so. I would love to hear from other App Orchard partners on how they are overcoming this problem.

View/Print Text Only View/Print Text Only


HIStalk Featured Sponsors

     

Currently there are "2 comments" on this Article:

    • You may want to check the revised fee structure for AppOrchard. It’s not perfect but much more friendly than the original one. At the end of the day, I would like to see EHR vendors take a long-term view of their ecosystem, identify what is core for them and enable partners to develop around that core.







Subscribe to Updates

Search


Loading

Text Ads


Report News and Rumors

No title

Anonymous online form
E-mail
Rumor line: 801.HIT.NEWS

Tweets

Archives

Vince Ciotti’s HIS-tory of Healthcare IT

Founding Sponsors


 

Platinum Sponsors


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Gold Sponsors


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Reader Comments

  • Woodstock Generation: What a nice way to start a Monday morning with the above posts!...
  • Luis Saldana: A really good area to raise for discussion. From my own experience, the informatics team needs to have a focus on the 5...
  • Lady Pharmacist: A decade or so ago, I worked in a health system in which the Risk Management Dept weighed into the decisions around aler...
  • 40 lashes with a wet noodle: Or, just raise prices the tiny amount required to cover that $109,500 per year....
  • AC: "...he probably grabbed their logins to Gmail or other..." A good reminder for people to turn on two factor authenticat...
  • MoMoney MoProblems: Seeing that the fine for not being transparent with data is $300 per day, or $109,500 per year. I suspect most organiza...
  • AthenaShouldAcquireMeditech: I don't think webOMR ever made it anywhere. The product that these hospitals are using is basically the ambulatory produ...
  • toothless: Important to note the proposed penalty for hospitals failing to publish pricing is THREE HUNDRED DOLLARS PER DAY. A t...
  • Lazlo Hollyfeld: There are plenty of valid reasons on why I can see an individual would not trust Google or Facebook. When an individ...
  • Andy Spooner: Read the Mayo Clinic article on usability. Saw that microwave ovens were better, so decided to try it in clinic. It took...

RSS Industry Events

  • An error has occurred, which probably means the feed is down. Try again later.

Sponsor Quick Links