DHEALTH — INTEROPERABLE HOSPITAL INFORMATION SYSTEM
SIMRS SatuSehat BPJS: One Interoperable, Claims-Ready System
dhealth is a hospital information system (SIMRS) built for interoperability: it connects to Indonesia's SatuSehat platform over HL7 FHIR and bridges to BPJS Kesehatan systems (V-Klaim, E-Klaim, INA-CBG) from a single workflow. Your hospital meets its Permenkes 24/2022 obligations while shortening the claims cycle — with no double data entry.
Since Ministry of Health Regulation (Permenkes) No. 24 of 2022 on Medical Records came into force, every healthcare facility in Indonesia has been required to run electronic medical records and exchange health data through the Ministry of Health's SatuSehat platform. A SIMRS ready for SatuSehat and BPJS is therefore no longer a marketing phrase — it is an operational necessity: a hospital information system is now judged not only by what it records, but by how well it exchanges standardized data with the national health ecosystem.
On the financing side, most hospital services in Indonesia are tied to the national JKN insurance program. That means the SIMRS must speak fluently with BPJS Kesehatan systems: eligibility checks and SEP issuance through the V-Klaim web service, and claim grouping and submission through the E-Klaim application using INA-CBG tariffs. When the SIMRS is not integrated, staff re-enter the same data across multiple applications — the leading source of delayed claims, pending claims, and administrative burden that eats into clinicians' time.
dhealth by PT Docotel Teknologi Informasi (DTI) was built to answer both demands at once. As a SIMRS with SatuSehat interoperability based on HL7 FHIR and BPJS bridging embedded in clinical and administrative workflows, dhealth lets hospitals meet regulatory obligations and keep claims cash flow healthy — through a phased integration approach that does not disrupt patient services.
Why a SIMRS Without Interoperability Becomes a Liability, Not an Asset
Double data entry across applications
Staff key the same patient data into the SIMRS, V-Klaim, and E-Klaim separately. Beyond the wasted time, every re-entry creates room for discrepancies that end in problematic claims.
Permenkes 24/2022 obligations on legacy systems
The regulation mandates electronic medical records interoperable with SatuSehat, yet many legacy SIMRS have no HL7 FHIR-based APIs. That gap puts hospitals at compliance risk.
Pending and disputed claims from inconsistent data
Mismatches between medical summaries, diagnosis-procedure coding, and INA-CBG claim files are a common reason claims are returned. Without a single source of data, reconciliation becomes repetitive manual work.
Health data security risks during integration
Indonesia's Personal Data Protection Law (Law No. 27 of 2022) classifies health data as specific personal data. Point-to-point integrations built ad hoc, without access controls and audit trails, widen the risk surface.
dhealth: A SIMRS Born for Interoperability
SatuSehat interoperability on HL7 FHIR
dhealth maps clinical data to the FHIR resources required by the SatuSehat platform — including Patient, Encounter, Condition, and Observation — so submissions to the Ministry of Health happen as part of the workflow, not as extra work.
BPJS V-Klaim bridging
Membership verification, SEP issuance, referrals, and visit data are processed directly inside the SIMRS through the V-Klaim web service. Registration staff work on one screen instead of hopping between applications.
E-Klaim and INA-CBG integration
Claims and coding data flow from dhealth into the E-Klaim application for INA-CBG tariff grouping, reducing re-entry and discrepancies between clinical records and claim files.
End-to-end electronic medical records
Registration, outpatient, inpatient, ancillary services, pharmacy, and billing share one database. That data consistency is the foundation of clean claims and accurate reporting.
Security and audit trails aligned with regulation
Role-based access control, encryption, and audit logging are designed in line with the principles of the Personal Data Protection Law and Government Regulation 71/2019 on Electronic Systems and Transactions — so interoperability never comes at the cost of patient confidentiality.
dhealth is used by healthcare facilities across Indonesia, from clinics to hospitals, backed by DTI's local implementation team.
Phased Integration, Step by Step with DTI
Readiness assessment and mapping
DTI's team audits your current systems, patient master data quality, care pathways, and BPJS claims flow. The result is a gap map against SatuSehat and BPJS bridging requirements, with a realistic integration plan — structure first, execution second.
Module implementation and data preparation
dhealth modules are implemented according to your hospital's priorities — often starting with registration and electronic medical records — alongside master-data cleansing and coding standardization, the prerequisites of healthy interoperability.
Bridging activation in test environments
Connections to SatuSehat and BPJS web services are first validated in each platform's development/staging environment: FHIR resource submissions, SEP creation tests, and simulated claim flows. No experiments on production systems.
Phased go-live and on-site support
Cutover happens unit by unit with on-site assistance, monitoring of data submission success, and retry queues for when connections to external platforms drop. DTI's support team stays engaged until operations are stable.
Frequently Asked Questions
Are hospitals required to connect to SatuSehat?
Permenkes 24/2022 requires healthcare facilities to run electronic medical records and exchange data through the platform operated by the Ministry of Health, namely SatuSehat. In practice, your SIMRS must be able to submit HL7 FHIR-standardized data to that platform. dhealth provides this capability as a built-in part of the system, not a bolt-on.
What is the difference between V-Klaim and E-Klaim?
V-Klaim is a web service from BPJS Kesehatan used by the SIMRS for membership and service administration processes such as SEP issuance and referrals. E-Klaim is a Ministry of Health application that groups claims under INA-CBG tariffs before submission. They serve different functions, and a capable SIMRS needs to connect to both so the claims flow runs without double entry.
Do we have to replace our legacy SIMRS all at once?
No. DTI's approach is phased: it starts with an assessment, then proceeds module by module or unit by unit according to your hospital's priorities and capacity. Data migration strategy and the transition period are planned so patient services are not disrupted.
How long does SatuSehat and BPJS bridging integration take?
The duration depends on your hospital's complexity — the number of service units, the state of existing data, and the scope of modules implemented. That is why the process always begins with an assessment, so the timeline you receive is grounded in your actual conditions rather than a generic promise.
How is patient data protected during integration?
Health data is classified as specific personal data under Law No. 27 of 2022 on Personal Data Protection, so its protection is a design principle, not an afterthought. dhealth applies role-based access control, encryption in transit, and audit trails over medical record access, consistent with electronic system operator obligations under Government Regulation 71/2019.
Does dhealth support other BPJS integration needs, such as online queuing?
dhealth's API-based architecture can be extended for other JKN ecosystem needs, such as online queuing connected to Mobile JKN or bed availability information. The integration scope is agreed during the assessment stage based on your hospital's needs and priorities.
DHEALTH — INTEROPERABLE HOSPITAL INFORMATION SYSTEM
Discuss Your Hospital's SatuSehat & BPJS Readiness
Schedule an assessment session with the DTI team. We will map your SIMRS gaps against Permenkes 24/2022, SatuSehat, and BPJS bridging — then build a realistic, phased integration plan for your facility.
