> In New Zealand, the market is different at this point, but how long can they resist the network effects of the big vendors?
Good point, here all hospitals use software from Orion Health, which is an NZ company - They have a really good hold on the market and I don't see that changing.
> You have mentioned in another post that you are concentrating just on records, … With all due respect, I think you are being naïve.
That thought has definitely crossed my mind. It's a tricky puzzle - part of the reason I think healthcare software is so hard, is that current systems are so monolithic - they do it all. To compete, you need to do it all as well. This impedes improvement, if you know how to build a fantastic appointment system, why should you have to also build invoicing systems? You have to bite off more than you can chew.
I don't really have an answer to this problem, but my approach is to break up the problem as much as possible into smaller parts.
It's kind of funny cause I'm in the imaging side and there's a buzz now about "deconstructed PACS" where centers will mix and match different vendors to provide radiologist workflow, image storage, DMWL worklist, Diagnostics Viewer, VR, distribution and analytics.
Right now, that's quite niche and arguably the DICOM space is the most open part of Health IT, but perhaps that will eventually percolate up to EMRs. Maybe once FHIR catches on or whatever will replace FHIR. I'm frankly still using HL7 2.x and mostly 2.2/2.3 level features.
Good point, here all hospitals use software from Orion Health, which is an NZ company - They have a really good hold on the market and I don't see that changing.
> You have mentioned in another post that you are concentrating just on records, … With all due respect, I think you are being naïve.
That thought has definitely crossed my mind. It's a tricky puzzle - part of the reason I think healthcare software is so hard, is that current systems are so monolithic - they do it all. To compete, you need to do it all as well. This impedes improvement, if you know how to build a fantastic appointment system, why should you have to also build invoicing systems? You have to bite off more than you can chew.
I don't really have an answer to this problem, but my approach is to break up the problem as much as possible into smaller parts.