Sold by: Netsmart
Deployed on AWS
Cloud - Managed by Vendor (Annual or Multi-Year Subscription)
4
Overview
Annual SaaS Health Record subscription. Health Record can support Human Services, Post Acute and other Healthcare programs and services. Does not include implementation and may not include all possible optional modules. For private pricing, please contact mjohnson@ntst.com .
Highlights
- Supports clinical, financial and operational workflows.
Details
New
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing
Pricing is based on the duration and terms of your contract with the vendor. This entitles you to a specified quantity of use for the contract duration. If you choose not to renew or replace your contract before it ends, access to these entitlements will expire.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
Dimension | Description | Cost/36 months |
|---|---|---|
EHR - Small | Cloud - Managed by Vendor (Annual or Multi-Year Subscription) | $3,676,910.00 |
EHR - Med | Cloud - Managed by Vendor (Annual or Multi-Year Subscription) | $13,103,160.00 |
EHR - Lg | Cloud - Managed by Vendor (Annual or Multi-Year Subscription) | $28,746,730.00 |
Dimensions summary
This listing sells the Electronic Health Record through a private offer, billed as a contract subscription. You choose one of three tiers based on your number of users: Small, Medium, or Large. Each tier is cloud-based and managed by the vendor. Pricing scales by the size of your user base, so you pick the tier that matches your organization. You commit for an annual or multi-year term. The tiers differ only by user capacity, not by billing method. Actual pricing is set through the private offer.
Top-of-mind questions for buyers
A user is an individual staff account that logs into the electronic health record. Clinical, administrative, and financial team members each count as one user. Your total user count determines which tier fits: Small, Medium, or Large. The pricing table sizes each tier by user volume.
The vendor hosts and manages your electronic health record in the cloud. This covers operating systems, databases, and application software updates, plus system monitoring and vulnerability management. Data is encrypted in transit and at rest. The environment meets HIPAA requirements. You do not manage servers yourself under any tier.
The three tiers differ only by user capacity. If your staff grows past your tier's range, you would move to the tier matching your new user count. Because this is sold through a private offer with an annual or multi-year term, contact the vendor to arrange the change.
www.ntst.com+1
Helpful?
Vendor refund policy
NA
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Vendor resources
Support
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Updated weekly
By Netsmart
By Cognosante
By Pieces Tech
AI generated from product descriptions
Clinical Workflow Support
Supports clinical workflows for healthcare operations
Financial Workflow Support
Supports financial workflows for healthcare operations
Operational Workflow Support
Supports operational workflows for healthcare operations
Multi-Program Support
Supports Human Services, Post Acute and other Healthcare programs and services
Cloud-Based Deployment
Cloud-managed deployment model with vendor management
Secure Clinical Data Storage
Utilizes Amazon HealthLake HIPAA-eligible service for secure storage, transformation, and query of clinical and claims data
Health Interoperability Standards
Implements modern health interoperability standards for seamless integration and exchange of medical information
Clinical Data Analytics
Provides analysis and inference capabilities for documents, diagnoses, medications, and vital sign data tracking over time
Chronological Medical Records Management
Displays chronological medical records including prescriptions, procedures, and diagnoses in organized format
Scalable Healthcare Architecture
Built on AWS infrastructure providing scalable architecture for handling increasing healthcare data volume and complexity
Generative AI-Powered Clinical Summarization
Leverages generative AI technologies to distill extensive EHR information, both structured and unstructured, into actionable clinical insights and real-time patient summaries.
Predicted Discharge Date and Barrier Analysis
Provides real-time analysis to predict discharge dates, identify potential discharge barriers, detect readmission risks, and generate auto-resolution recommendations for multidisciplinary care teams.
EHR-Integrated Clinical Decision Support
Integrates seamlessly within existing EHR systems at the point of care, providing physicians, nurses, case managers, and social workers with accessible clinical insights within patient lists and documentation workflows.
Customizable Clinical Summary Generation
Converts extensive patient chart data into concise, editable summaries that refresh upon clinically relevant updates, enabling use for patient sign-out and progress note documentation.
Organization-Specific Model Integration
Supports integration of organization-specific derived models within the platform summary or comparison with standard Pieces models to accommodate varied health system use cases.
Standard contract
No
Customer reviews
Mohammad Shahabuddin Anwar
Integration has simplified patient data exchange and supports faster go-live using sandbox testing
Reviewed on Sep 26, 2026
Review provided by PeerSpot
What is our primary use case?
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.
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.