Startups

The Omi Health Tech Experience: Transitioning from Services to Software Products in the Healthcare Sector

Vietnam-based Omi Health Tech reviews its experience in building a national health data platform and how development tools contributed to accelerating regulatory compliance and software transformation.

2026-11-05
2 min read
1 views
certi.news Editorial Team
The Omi Health Tech Experience: Transitioning from Services to Software Products in the Healthcare Sector

Omi Health Tech, based in Vietnam, is a model for startups seeking to drive change in national digital infrastructure. The company, which emerged from the OmiGroup, transitioned from a business model based on providing technical services to clients in Japan to developing proprietary software products for the local market, specifically in the healthcare sector.

Building a National Health Data Platform

The company focuses on developing two main platforms: Omi Health Platform, which works to unify clinical data from hospitals and laboratories and connect it to the Vietnamese Ministry of Health, and the Omi LGSP platform, which connects this data to the national data exchange platform. This transition from providing services to building products requires a robust and scalable software infrastructure.

Regulatory and Technical Challenges

The team faced significant challenges in adapting to new data protection laws and artificial intelligence regulations issued in Vietnam within a short period. This required updating data access layers, audit trails, and approval processes across multiple software repositories. According to the company's CEO, Van Manh Hung, relying on advanced development tools such as IntelliJ IDEA Ultimate was a decisive factor in accelerating these processes.

What Changed Practically in the Workflow?

The team noted that using an Integrated Development Environment (IDE) specialized in Java contributed to tangibly improving work efficiency:

  • Refactoring: Making software changes across multiple files became a routine part of development cycles (Sprints), reducing the risk of errors.
  • Regulatory Compliance: Engineers were able to implement updates related to patient data privacy in days instead of weeks.
  • Review Speed: The tools helped automate the detection of mechanical errors, allowing reviewers to focus on the quality of the architectural design rather than correcting simple coding errors.
  • Employee Onboarding: New developers were able to reach their first effective Pull Request within just one or two days.

The company plans to double its engineering team by the end of 2026, with a continuous focus on developing FHIR (Health Level Seven Fast Healthcare Interoperability Resources) resource processors and expanding the scope of technical compliance, considering that development tools will remain the primary engine for reviewing and refactoring code, especially with the increasing reliance on AI-generated code.

News source
JetBrains Blog
Open original source ↗
c
Author

certi.news Editorial Team

In the same category

You may also like

View all news