- Company sizes or stages where this product is overkill or insufficient
- Very small maternity units that do not need a full maternity EPR ecosystem and cannot justify integration/implementation overhead.
- Industries or use cases where competitors are clearly more appropriate
- Hospitals committed to a single enterprise EPR strategy where a separate maternity-focused system would create duplication or governance friction.
- Technical requirements that this product cannot meet
- If an RFP mandates specific, publicly evidenced certifications (e.g., SOC 2 Type II, ISO 27001 certificate, detailed pen test disclosures) and the vendor cannot provide them under NDA, this product may not meet procurement requirements.
- Budget constraints that make alternatives more appropriate
- If integration work and ongoing reporting/governance effort cannot be funded, lower-complexity alternatives may be preferable.
- Specific workflows or integrations where the product falls short
- If the buyer requires robust built-in scheduling/reminder capabilities that are confirmed absent in the vendor’s current offering, validate this explicitly before procurement.
- Red flags in the buying process
- If implementation resources appear constrained (employee feedback indicates potential post-acquisition resourcing pressure), treat this as a procurement risk.
- Current limitations acknowledged by the vendor
- K2’s response to the EuroKing NHS safety notice indicates a design choice: Athena does not automatically update gravidity/parity after birth; it retains antenatal values for antenatal care decisions and reporting.
- This behaviour may be appropriate for medico-legal reasons but can be unexpected to users who anticipate automatic updates; governance and training should address this.
- Features on the roadmap (not yet available)
- No consolidated public roadmap was found in reviewed materials. Buyers should request a roadmap and release cadence during procurement.
- Scale limitations (at what volume/size does it break down?)
- No public scale limits were identified. Buyers should request performance and scalability references relevant to their expected load (births/year, concurrent users, CTG storage volumes).
- Security or compliance gaps
- Security certifications and controls are not fully enumerated publicly. Procurement materials indicate alignment to ISO27001 principles and UK frameworks, but certificate evidence was not included in public listings.
- Technical debt or architectural limitations mentioned in reviews
- No consistent third-party pattern of software bugs or performance issues was found. Employee commentary suggests potential organizational constraints that could affect delivery timelines.
- API limitations or integration constraints
- K2 advertises HL7/FHIR interoperability and a specialist integration team. Integration breadth is an advantage but also adds complexity, cost, and testing requirements for each additional interface.