- Company sizes or stages where this product is overkill or insufficient
- Overkill for small clinics that do not require ERP-grade back office functionality.
- Industries or use cases where competitors are clearly superior
- Multinational health systems that require a single global-standard EHR platform across multiple countries may prefer large global vendors such as Oracle Health or InterSystems.
- Technical requirements that this product cannot meet (based on public information)
- If procurement requires public evidence of SOC 2 Type II or ISO 27001 certification, the vendor’s public materials (as reviewed) do not show these attestations.
- Budget constraints that make alternatives more appropriate
- Organizations unable to sustain ongoing maintenance/support contracts may face operational risk, as indicated by third-party documentation describing issues when maintenance was not in place.
- Specific workflows or integrations where the product falls short
- Not clearly documented publicly; formal technical evaluation is recommended to validate DG’s APIs, HL7/DICOM capabilities, and integration tooling for specific projects.
- Red flags in the buying process
- Lack of transparent public pricing, limited independent review footprint, and absence of publicly documented security attestations. Buyers should require detailed statements of work, SLAs, upgrade policy and roadmap commitments, and security documentation during procurement.
- Current limitations acknowledged by the vendor
- Vendor materials note an ongoing migration of key modules to a web-based architecture and other modernization efforts.
- Features on the roadmap (not yet available) - note estimated dates if available
- Bulletins in 2024–2025 reference migration work (including preparation for .NET 8) and progressive webification of modules. Public timelines are directional and do not constitute guaranteed release dates.
- Scale limitations (at what volume/size does it break down?)
- Not publicly documented in accessible sources.
- Security or compliance gaps
- Security controls are described in vendor materials, but public documentation does not include major international security certifications (e.g., SOC 2, ISO 27001).
- Technical debt or architectural limitations mentioned in reviews
- Not documented due to limited independent review coverage.
- API limitations or integration constraints
- Public materials do not include comprehensive official API documentation. A third-party post referenced integration with DG’s database, but formal API specifications were not found in public materials.