Connecting providers, patients, and payers through a unified care record and analytics that span the care continuum. Creates a Unified Care Record for Collaborative Care HealthShare creates a unified, community-wide health record as the foundation for coordinated, value-based care and population health management. With embedded intelligence, and delivery of just the right information at the right time and place within delivery, management, and payment processes, HealthShare enables…
N/A
Oracle Database
Score 7.9 out of 10
N/A
Oracle Database, currently in edition 23ai, is a converged, multimodel database management system. It is designed to simplify development for AI, microservices, graph, document, spatial, and relational applications.
InterSystems HealthShare is an extremely powerful platform for which we have not found a need it cannot meet. Granted, some particular complex solutions may require a bit more 'engineering' level talent than some healthcare organizations staff in their traditional 'interface departments'. Organizations that make the investment in InterSystems AND their staff through training and empowerment of bettering their career will rapidly reap the rewards of a robust integration foundation with support for rapidly increasing the organization's ability to action their data using analytics, natural language processing, machine learning and business process orchestration. Through HealthShare, I have been able to harvest key business and clinical metrics rapidly from plain text blobs into discrete data elements, empowering our analytic users, reducing manual data entry and bettering the lives of our most important customer - the patient.
I believe Oracle Database is still the best RDBMS database which is the database to consider for OLTP applications and for Adhoc requests. They are good in Datawarehousing in certain aspects but not the best. Oracle is also a great database for scaling up with their Clusterware solution which also makes the database highly available with services moving to the live instance without much trouble.
A wealth of specific integration adaptors provided with the product, allowing for rapid low-code integrations for a myriad of use-cases.
Most InterSystems provided functionality delivered with the product can be review and extended to allow for rapid development of custom solutions for adaptors and tools not met out-of-the-box.
Continual timely releases ensure organizations can keep up to date with the rapidly changing healthcare integration space, while trusting that upgrades do not mean months of testing and validation. Most major upgrades can be completed within a few weeks of simple unit testing.
Improvements to built in REST, SOAP and FHIR adapters to allow for low-code solutions against modern integration web service APIs.
Terminology engine improvements to provide auto-mapping against the plethora of terminology datasets required by FHIR and US CDI standards.
Tighter integration with Git/GitHub and similar platforms to enable Continuous Integration and Development models out of the box not only for general developers but healthcare integrators.
New (actually it is more than five years old) multi-tenant architecture is not as straightforward as SQL Server, but it has been enhanced in Oracle 12c Release 2 and later 18c and 19c.
Many features require additional licensing (either as options or as packs) that increase the total cost
It is very likely to use this 12c (or next version) of Oracle Database. Nothing close to it in the marketplace in terms of performance, reliability and overall database management efficiency. If Oracle did one thing really good - it is it's OLTP Database I must say.
Many of the powerful options can be auto-configured but there are still many things to take into account at the moment of installing and configuring an Oracle Database, compared with SQL Server or other databases. At the same time, that extra complexity allows for detailed configuration and guarantees performance, scalability, availability and security.
1. I have very good experience with Oracle Database support team. Oracle support team has pool of talented Oracle Analyst resources in different regions. To name a few regions - EMEA, Asia, USA(EST, MST, PST), Australia. Their support staffs are very supportive, well trained, and customer focused. Whenever I open Oracle Sev1 SR(service request), I always get prompt update on my case timely. 2. Oracle has zoom call and chat session option linked to Oracle SR. Whenever you are in Oracle portal - you can chat with the Oracle Analyst who is working on your case. You can request for Oracle zoom call thru which you can share the your problem server screen in no time. This is very nice as it saves lot of time and energy in case you have to follow up with oracle support for your case. 3.Oracle has excellent knowledge base in which all the customer databases critical problems and their solutions are well documented. It is very easy to follow without consulting to support team at first.
Overall the implementation went very well and after that everything came out as expected - in terms of performance and scalability. People should always install and upgrade a stable version for production with the latest patch set updates, test properly as much as possible, and should have a backup plan if anything unexpected happens
InterSystems HealthShare is not your standard integration platform. While the Health Connect product could be construed as an 'interface engine', it is so much more. The capabilities to extend the engine using low code and visual business process modeling ensures a wealth of use cases not covered by a traditional interface engine. Furthermore, while not a direct competitor of Epic (Epic is in fact an InterSystems customer themselves), we are far more comfortable relying on the robustness of the HealthShare platform for complex integrations, data modeling and data normalization using HealthShare than just Bridges and Interconnect alone.
Oracle Database is among the easiest to integrate with, program against, have a reliable cluster with DR, and has the most understood and well-documented databases. It suits really well if the software shop is primarily Java-based, and deals with large volumes of data with a high degree of diversity among the applications by purpose and use. Paid support is recommended as well as planned periodic patching and upgrades.
Simple integration development time has been reduced from weeks to days.
Complex integration development time has been reduced from months to weeks.
On-call Support after-hours for the integration team has been nearly non-existent since the move to InterSystems, increasing employee retention and satisfaction as InterSystems 'just works'.
Less need to purchase other products to implement complex integrations through web service APIs and SQL ETL processes - it can all be done with InterSystems.
We wasted lots of money (Oracle is crazy expensive), time and effort on the project and were highly relieved when we found a different approach to supporting our aging ERP app that did not include Oracle.
Because of the difficulty of using Oracle, we spent a lot of money on consultants to help us over the conversion hump. Also wasted. And it was interesting to see them struggle with the software. Upgrades never went well always requiring multiple site visits, for example.
