Visit data never reaches its destination
The screen says the submission succeeded, but the data does not appear on the receiving side. Nobody can show the original error message.
Healthcare Facility System
The system already exists, the connection does not
We start from what you already have, then work on the part that genuinely does not run. Replacing the whole system is something we recommend only when there is no other way, and we say why.
Before you read further
We have not built a healthcare facility system before
Stated plainly
Our portfolio register holds no clinic or hospital project. Presenting a case study that never happened costs you more than it costs us, so this section carries the real work that sits closest to what this page is about.
- Tenant data separation at the database schema level in our own product
- A document portal that opens without an account, with a snapshot frozen at issue time
- A delivery record for every call to a third-party service, including failures and their response codes
If your institution scores healthcare sector experience as a requirement, we are not the right fit, and you deserve to know that now.
See the full portfolioWhat usually happens at facilities that already have a system
This page is written for those who already bought a system, not for those who have nothing yet.
Medical records are still on paper
Files pile up, searching an old patient history takes time, and a lost copy cannot be restored.
Staff enter the same data twice
Once in your own system, once again in the insurer portal. The mismatch surfaces when a claim is rejected.
The module you need does not exist
Your workflow has a step the off-the-shelf vendor never considered, and your request never reaches their queue.
Switching systems means losing history
The previous vendor offers no complete export, so moving feels like starting from zero.
Queues build up at peak hours
Registration, calling, and recording happen in different places, so the queue is longer than the medical cause explains.
What changes once it is sorted out
Without replacing the whole system, unless there really is no other way, and we will say so plainly.
Every submission can be traced
Each submission is logged, failures included, with the reason. Failed ones can be resent without retyping.
History from the old system comes across
Data from the previous system is migrated and reconciled before and after the move. For archives still on paper, the scanning is done by another party and we handle the indexing and the import.
One entry serves several destinations
The same data is not retyped for claims and for reporting.
Missing modules can be added
What is not available yet is built alongside the system you already use, not in place of it.
Supporting documents ready for review
Records and reports are stored complete with timestamps, so nothing has to be gathered at the last minute.
Access limited by role
Patient data opens only to those entitled to it, and every access is logged.
Scope of work
We do not start by building. We start by reading what already runs.
Review of the running system
What exists, what is worth keeping, and which part is genuinely broken.
Integration work
Connecting to the destination system, including failure handling, resubmission, and an audit trail.
Data migration
Moving data from the old system, with reconciliation before and after. Scanning paper archives is not our work, but we can index and import the scans.
Additional modules
What the current system lacks, built to match the workflow already in place.
Queue and registration
Registration, queue numbers, and calling that connect to visit records.
Access rights and audit trail
Role separation plus a record of who opened what and when.
The regulations we rely on
Every quotation below can be checked against the official document.
Hospital recording and reporting obligation
Article 74 paragraph (1) of Minister of Health Regulation Number 6 of 2026 on Hospitals states that every hospital must record and report all hospital operational activities in a Health Information System integrated with the National Health Information System.
Permenkes 6 of 2026 at JDIH KemkesTransition period
Article 83 letter a gives hospitals up to 2 years from promulgation to comply with the regulation, due 12 June 2028. Letter b gives up to 4 years for a class D pratama hospital that already holds a business licence, due 12 June 2030. Note that letter a covers the whole regulation, not the information system alone.
Permenkes 6 of 2026 at JDIH KemkesSanctions applied in stages
Article 79 paragraph (1) states a breach of Article 74 paragraph (1) draws a verbal warning, a written warning, an administrative fine, adjustment or revocation of accreditation status, and revocation of the hospital business licence. The order is graduated. A verbal warning is issued at most once and a written warning at most twice before the next stage.
Permenkes 6 of 2026 at JDIH KemkesClinics are not the subject of this regulation
Permenkes 6 of 2026 governs hospitals. The phrase in Article 83 letter b is class D pratama hospital, not pratama clinic. If your facility is a clinic, the basis for the obligation is different and we will not quote this regulation as if it applied to you. We look for the right reference together before the scope is locked.
Permenkes 6 of 2026 at JDIH KemkesWe name the National Health Information System rather than any platform brand, because that is what the regulation says. We also make no claim to be a registered electronic medical record provider at the Ministry of Health. If your procurement requires a registered provider, tell us at the start so you do not spend time on an option that cannot qualify.
Cost and duration range
Integration work is the hardest to size from outside. What we can state now is the entry point and what moves your position inside the range.
Integration, migration, or additional modules
From Rp 25 million
Delivery in 4 to 12 weeks
The entry point and duration above follow the Web App Custom package already published on our website development page. The upper bound depends on the final scope and is written into the proposal before work begins.
Check the Web App Custom package on our website development pageWhat decides your position inside the range
Documentation of the existing system
A system with interface documentation is far faster to connect than one that has to be read from its behaviour.
Volume and condition of the data
The number of medical records and how tidy they are decides how long migration and reconciliation take.
Whether the previous vendor grants access
If the data export has to be requested from another party, their timeline decides the schedule, not ours.
Number of modules added
One standalone module is not the same as several that depend on each other.
Number of service units
A single-site clinic is not the same as a hospital with many units and a different flow per unit.
Reporting requirements
Several report formats maintained side by side add testing work.
Other pages you may need
If your need sits outside healthcare, these three are closer.
Safety reporting and documentation system
For occupational safety reporting duties and safety training providers.
Transaction and operations system
For orders, invoicing, and stock figures that never reconcile.
Web application development
The general page for internal systems outside these three categories.
Questions that come up often
We are registered but our data does not arrive, why?
Three things we check first: the submission shape does not match what the receiver expects, the patient identifier is incomplete, and failures are never surfaced to staff so nobody knows to retry. All three can only be confirmed after reading the submission trail.
Does the current system have to be thrown away?
Not always, and that is not a decision we make before seeing it. If daily recording is in use and causing no trouble, replacing everything only adds risk. Usually only the part that does not run needs work.
Does CoreAsia scan paper medical records?
No. Scanning archives is not our work and we do not sell it. What we do is index and import the scans into the system, and set the rule on which source prevails while the paper archive and the new system run side by side. The order in which records move is decided by you and your clinical team.
How long does an integration take?
It depends on the availability of interface documentation and how quickly the receiving side responds. The part we control is usually not the longest part. We give a time estimate after reading the submission trail you have today.
Is CoreAsia a registered electronic medical record provider?
We make no claim to that status. If your procurement requires a registered provider, say so at the start so the scope and eligibility are clear before you spend time.
Does the new hospital regulation apply to clinics?
No. Permenkes 6 of 2026 governs hospitals. Article 83 letter b names class D pratama hospitals, not pratama clinics. For clinics the basis has to be found separately, and we will not use this regulation as an argument.
How is patient data protected?
Access is limited per role, every data access is logged, and data moves over encrypted channels. Additional rules that apply at your facility are followed and written into the agreement before work begins.
Send us one failed submission you hit
An error screenshot or the submission log is enough for us to name the likely cause and the scope of work.