5 ms·

I think that would be a good idea and the only way it would work. Unless this is way, way, way more polished you won't see a Mayo Clinic or Cedars-Sinai using

I think that would be a good idea and the only way it would work. Unless this is way, way, way more polished you won't see a Mayo Clinic or Cedars-Sinai using something like this. They tried that 20 years ago and it was scrapped for Epic. If it targeted smaller rural access hospitals or smaller practices and sold consulting and hosting services it might work if it way undercut the current bigger players... But this market is already way more crowded than the massive enterprise systems like Cerner-Oracle and Epic.

nativeit 2y ago
I work with a lot of smaller healthcare offices, and there are plenty of field-specific solutions like MedicFusion, ChiroTouch, et al.. Despite the relative small sizes and simpler needs for these offices, you'll still find unique complexities, business logic, and bespoke integrations. The process of migrating from one solution to another is so involved and time-consuming that I wouldn't expect it to happen more than once in a decade, and only then if the current solution is somehow critically deficient, or their practice is changing in a way that demands expanded options. The only potential advantage I can think of is the relatively higher frequency of new practices being opened, which creates a wider target audience of potential customers, and that's probably why there's more field-specific solutions, rather than general ePHI that supports multiple fields of practice.
- FireBeyond 2y ago
  One of the more interesting ones is ESO's ESOsuite, for pre-hospital providers. It has to deal with rough and spotty connectivity even during record creation, it has to handle sync between different providers (FD arrives first, starts gathering information, EMS arrives after to transport. How do you reconcile field values? It's one thing to coalesce provider interventions, but what about demographic discrepancies? "Just give the provider a choice between options" you think - not the biggest priority when approaching the hospital and stabilizing your patient, and not when you need to contact the hospital and give them said demographics and CC/HX/VS before you arrive).
Taikonerd 2y ago
> They tried that 20 years ago and it was scrapped for Epic. Did the Mayo Clinic use to use something open-source? They switched from Cerner to Epic 6 years ago [0], but that's just switching one closed-source vendor to another. [0] https://www.healthcareitnews.com/news/mayo-clinic-cio-christopher-ross-breaking-1-billion-ehr-and-it-modernization-rollout-barrier https://www.healthcareitnews.com/news/mayo-clinic-cio-christ...

nativeit 2y ago

I work with a lot of smaller healthcare offices, and there are plenty of field-specific solutions like MedicFusion, ChiroTouch, et al.. Despite the relative small sizes and simpler needs for these offices, you'll still find unique complexities, business logic, and bespoke integrations. The process of migrating from one solution to another is so involved and time-consuming that I wouldn't expect it to happen more than once in a decade, and only then if the current solution is somehow critically deficient, or their practice is changing in a way that demands expanded options. The only potential advantage I can think of is the relatively higher frequency of new practices being opened, which creates a wider target audience of potential customers, and that's probably why there's more field-specific solutions, rather than general ePHI that supports multiple fields of practice.

FireBeyond 2y ago
One of the more interesting ones is ESO's ESOsuite, for pre-hospital providers. It has to deal with rough and spotty connectivity even during record creation, it has to handle sync between different providers (FD arrives first, starts gathering information, EMS arrives after to transport. How do you reconcile field values? It's one thing to coalesce provider interventions, but what about demographic discrepancies? "Just give the provider a choice between options" you think - not the biggest priority when approaching the hospital and stabilizing your patient, and not when you need to contact the hospital and give them said demographics and CC/HX/VS before you arrive).

Taikonerd 2y ago

> They tried that 20 years ago and it was scrapped for Epic. Did the Mayo Clinic use to use something open-source? They switched from Cerner to Epic 6 years ago [0], but that's just switching one closed-source vendor to another. [0] https://www.healthcareitnews.com/news/mayo-clinic-cio-christopher-ross-breaking-1-billion-ehr-and-it-modernization-rollout-barrier https://www.healthcareitnews.com/news/mayo-clinic-cio-christ...