Product Updates

What Micromeet’s Regulatory Sandbox Milestone Means for MCU and Continuous Care

What Micromeet’s Regulatory Sandbox milestone means for our product direction across individual, occupational and premium MCU, Care Workspace and Care Loop.

Published December 3, 2025Updated September 25, 20266 min readMicromeet Editorial
Share
TopicsMicromeetIndonesia Regulatory SandboxKemenkes healthcare innovationMCU continuous care IndonesiaCare WorkspaceCare Loop
What Micromeet’s Regulatory Sandbox Milestone Means for MCU and Continuous Care

Micromeet has passed Indonesia’s Ministry of Health Regulatory Sandbox for 2025–2026. The Ministry announced the official results on 11 September 2026, listing Micromeet among the successful participants in the Regulatory Sandbox category.

The results recognise 21 innovations that completed all testing stages and met the programme’s criteria. Those innovations were recommended for Tanda Daftar Inovasi Teknologi Kesehatan (ITK), the health technology innovation registration document. The programme brought testing, evaluation, mentoring and guidance into a structured process. The Ministry team also shared the result in its LinkedIn announcement.

Micromeet thanks the Ministry programme team and everyone who contributed to the evaluation and guidance process. This is a company milestone in Indonesia and part of Micromeet’s work on healthcare AI infrastructure that connects medical check-ups with continuous care. Read our official milestone announcement for the source links and our next steps.

From medical check-ups to continuous care

A medical check-up (MCU) creates a starting point for care: findings to understand, decisions to discuss and a plan to carry forward. Micromeet connects that work through Micromeet Care Workspace, bringing the report, doctor explanation, care plan, follow-up and next appointment into a connected journey.

This is the product direction behind Micromeet’s MCU work. It covers individual, occupational and premium medical check-ups, as well as follow-up that begins with a care plan already approved by a doctor. The question guiding that work is practical: how does the care agreed during one encounter continue into the next?

From an MCU report to the next step in care

The report brings findings together. The doctor explains what they mean for the person receiving care and decides which next steps are appropriate. Those steps may include a repeat examination, a referral, a follow-up conversation or another appointment. Each has a different purpose, and each needs someone to carry it forward.

A completed report therefore leaves further work for the healthcare team. The person receiving it needs to understand the plan. The team continuing care needs the relevant information and a clear next action. When the next visit takes place, the earlier findings and decisions provide context for the conversation.

That relationship between a report and the care that follows shapes Micromeet’s approach. The MCU build story explains the thinking behind the product, while the article on clinical review of MCU reports looks at why producing a useful report requires clinical judgment. Continuous care carries that work into the next stage.

Put the evidence in context

Review the intended task, source information, human checkpoints and observed results together. A benchmark or sandbox result has a defined scope; it does not establish suitability, approval or performance for every institution.

Read the full explanation
Discuss this step for your team

Individual, occupational and premium MCU

People reach medical check-ups through different services. An individual may seek a clearer understanding of their health. An occupational MCU operates within a work-related service context. A premium programme may place particular emphasis on explanation and ongoing service. These settings bring different expectations and responsibilities.

Micromeet’s MCU scope includes all three. Occupational and premium MCU are entry points for applying the product to distinct service needs. Across those settings, the shared purpose is to connect the medical check-up with the next appropriate step in care.

The service context remains important when an institution defines its workflow: who receives an explanation, who coordinates follow-up and how the next appointment is arranged. A connected journey follows those responsibilities. Doctors retain clinical decisions and approval, while the institution defines the roles and services involved in delivering care.

Care Workspace connects the journey

Micromeet Care Workspace is the daily working environment for healthcare teams. Within it, MCU CoPilot supports the MCU workflow, and Care Loop supports the work that continues after the initial visit. Together, these workflows connect the report and doctor explanation with a clinician-approved plan, follow-up and the next appointment.

The value lies in how the work connects. A report informs a conversation. The conversation leads to an agreed plan. Follow-up carries that plan forward, with a recheck, referral or appointment when appropriate. The next encounter becomes part of the same care journey.

Care Loop can also begin with an existing clinician-approved care plan, without requiring a new MCU report. For a person who already has a plan, the useful starting point is the action that needs follow-up. This allows the discussion with an institution to begin from the care it is already delivering.

The workflows, integrations and services enabled are agreed with each institution. Clinical judgment and approval remain with doctors; the product supports the team’s work around those decisions. AI prepares; people decide. That is how Micromeet approaches continuity across the report, plan and subsequent care.

Frequently asked questions

Which medical check-ups does Micromeet support?

Micromeet’s MCU scope includes individual, occupational and premium medical check-ups. Care Workspace connects reporting and doctor explanation with clinician-approved plans, follow-up and the next appointment. Enabled workflows are agreed with each institution.

Can Care Loop start from an existing care plan?

Yes. Care Loop can begin with an existing clinician-approved care plan without requiring a new MCU report. Doctors retain clinical decisions and approval, and the team coordinates the follow-up work.

What is Micromeet’s Regulatory Sandbox milestone?

Indonesia’s Ministry of Health lists Micromeet in the Regulatory Sandbox category among 21 innovations that completed all testing stages, met programme criteria and were recommended for Tanda Daftar Inovasi Teknologi Kesehatan (ITK) in the 2025–2026 results.

Micromeet. Explore the evidence, review steps and product scope relevant to your team.

Explore the workflow

ME

Micromeet Editorial

Micromeet Team

Micromeet builds healthcare AI infrastructure for continuous care. MCU CoPilot, AI Scribe, Patient Access & Appointments and Care Loop support focused workflows; Micromeet Care Workspace connects approved context and next steps.

About Micromeet

Connect your MCU service with continuous care

Explore how reports, care plans, follow-up and the next appointment fit together in your institution.