My main use case for Netsmart Electronic Health Record is that some of our customers are using it as an EHR, so we are trying to build a bridge between our system. Basically, we are integrating their FHIR APIs into our system so that we can pull any record or any patient data if our customer is having a service with Netsmart.
Integration has simplified patient data exchange and supports faster go-live using sandbox testing
What is our primary use case?
What is most valuable?
The best features that Netsmart Electronic Health Record offers include the sandbox first of all. If we want to create a bridge without paying anything, we can do that using the sandbox, so that we can show our customers that we are integrating with Netsmart. When a customer comes with Netsmart as an EHR, we can work on getting production-level data.
What I appreciate about the features of Netsmart Electronic Health Record is that the documentation is well-maintained. There is substantial documentation available, and using that, I have created the integration. The documentation is very helpful. They are also using the latest OAuth 2.0 authentication, which is excellent.
Netsmart Electronic Health Record has positively impacted my organization because some of our customers are using it. We have integrated everything with Netsmart ahead of time, and we are ready for production or go-live. Having a sandbox and a feature that can be used before going live helps with the entire testing process.
This integration with Netsmart Electronic Health Record helped us reduce the time to go live. We had everything ready in place and just needed to change the base URL from the sandbox URL to the production URL. This integration has improved customer satisfaction.
What needs improvement?
The most challenging part of the integration process with Netsmart Electronic Health Record is that they do not have much test data on the sandbox. The sandbox is available, which is significant, but there are not many examples. Epic, for instance, has many APIs or resources available for testing, so that was the challenging part.
I believe that Netsmart Electronic Health Record should provide more test patients on the sandbox so that any integration engineer building a bridge or trying to integrate with Netsmart will have more scope and resources to test all the FHIR resources that are available.
Other than this, everything about Netsmart Electronic Health Record is good. The documentation is thorough, and the user experience is strong. It is not lagging, and there is a rate limit for APIs, but in my integration, everything was good other than not having enough test patients for the different resources, such as document reference. Only a couple of resources were available for testing.
For how long have I used the solution?
I have used Netsmart Electronic Health Record in my last organization, where I was responsible for building a connection or bridge from our system to a Netsmart myAvatar system, which is public. They have a sandbox. I have been using this for about two years.
What do I think about the stability of the solution?
Netsmart Electronic Health Record is stable in my experience. It was stable, but I saw a few downtimes when hitting an API, but later on, it started working.
What do I think about the scalability of the solution?
In my experience, Netsmart Electronic Health Record's scalability is limited. I feel there are not many customers who are using it on a large scale, but I would say that for starter companies or whoever wants to hold some data, such as a hospital, it will be a good option to choose Netsmart. However, it is not that scalable.
How are customer service and support?
As for customer support for Netsmart Electronic Health Record, there was not much customer demand, and we did not have any issues that required us to contact customer support.
Which solution did I use previously and why did I switch?
I have previously worked with different solutions before Netsmart Electronic Health Record, including different integration engines such as Epic and Cerner, depending on what the hospital has opted for.
Which other solutions did I evaluate?
I evaluated other options before choosing Netsmart Electronic Health Record, but it is not about choosing based on requirements. As I mentioned, we are not an EHR company; I am an integration engineer and I do integration across various EHR systems. Not only Netsmart, but also Epic, Cerner, Athena, and Greenway. Compared to other EHRs, I feel Netsmart is quite good.
What other advice do I have?
My advice for others looking into using Netsmart Electronic Health Record is that it is a new company which offers features similar to those of Epic and Cerner. Anyone can use it, and it will be a good start. If you are a small company or a hospital, you can choose Netsmart for integration.
Netsmart Electronic Health Record is a strong electronic health record system where all the necessary things are available. I would rate this review an 8 out of 10.
Which deployment model are you using for this solution?
Private Cloud
