- Review sources and summary observations
- G2 (sample reviews)
- One reviewer characterized pricing as cost-effective for small offices and described the software as straightforward to learn and implement in smaller settings; the same reviewer also reported additional fees for third-party integrations and frequent stability issues.
- Other reviewers reported occasional bugs and inconvenience related to software updates.
- Capterra (broader set of reviews)
- Some reviewers reported slow performance and freezing in virtual/hosted environments and expressed dissatisfaction with support in certain cases.
- Reddit / community discussions
- Clinicians in forum threads have described Amazing Charts as learnable without formal training in some cases, and as a potential trade-off between cost and features compared with other options.
- Gartner Peer Insights / HackerNews
- Direct, product-specific listings or substantive discussions were not reliably retrievable during this research session.
- Balanced examples (paraphrased for neutral presentation)
- Positive sentiment examples:
- Several reviewers described the product as easier to learn than some alternatives and reported that scheduling and basic charting meet their workflow needs.
- Negative sentiment examples:
- Multiple reviewers described performance and stability problems (crashes, freezing, slow response), and some expressed dissatisfaction with support response or feature limitations.
- Common criticisms and complaints (support issues, bugs, missing features)
- Performance/stability: recurring theme across review platforms: crashes, freezing, and slow performance in some hosted or virtualized setups.
- Support quality: mixed reports, with some reviewers noting unsatisfactory support experiences.
- Integration/add-on costs: reviewers cited additional fees for third-party integrations and add-ons as a concern.
- Feature gap versus newer entrants: some reviewers and community discussions indicated that newer EHRs may offer more modern feature sets.
- Why customers chose or left the product
- Chosen for: lower headline price relative to some alternatives, perceived ease of learning and basic usability, on-prem deployment option for customers requiring local control.
- Left for: perceived lack of advanced functionality, stability issues, and desire for a more modern UX or deeper integrations in some cases.
- Specific outcomes reported
- Limited quantitative outcomes were available; one user review reported a small self-reported improvement in business performance without a formal methodology.
- Customer pain points and deal-breakers
- Recurrent pain points: application stability, update disruption, incremental integration fees.
- Potential deal-breakers for procurement teams: lack of publicly available enterprise security attestations and reliability concerns in high-throughput clinics.