DHEALTH HIS — SATUSEHAT INTEROPERABILITY
SatuSehat Hospital Integration through a FHIR-Ready HIS
dhealth connects your hospital to Indonesia's SatuSehat platform through a hospital information system built on HL7 FHIR R4, with standardized terminology mapping and phased guidance from sandbox to production. Meet the requirements of Permenkes 24/2022 without overloading your internal IT team.
SatuSehat integration has become an unavoidable agenda for Indonesian hospitals. Through Ministry of Health Regulation No. 24 of 2022 on Medical Records, healthcare facilities are required to run electronic medical records and prepare for health data interoperability. The SatuSehat platform is the backbone of that exchange: hospitals are directed to submit service data — encounters, diagnoses, prescriptions, and more — to the national health platform in a standardized format.
In practice, this obligation demands more than simply 'having a hospital information system'. SatuSehat uses the international HL7 FHIR R4 standard with OAuth 2.0 authentication, along with standard terminologies such as ICD-10 for diagnoses, ICD-9-CM for procedures, LOINC for laboratory tests, and KFA for pharmaceutical data. Systems built before the interoperability era typically store data in proprietary internal structures, so data mapping, code standardization, and reliable submission mechanisms are required — substantial technical work for any hospital IT team.
dhealth by DTI is designed to answer this need end to end. As a hospital information system with built-in SatuSehat integration, dhealth handles data transformation into FHIR resources, terminology mapping, synchronization of patient and practitioner master data, and monitoring of submission status. The process runs in measured stages — from assessment and sandbox testing to production go-live — so your hospital can meet its interoperability obligations with operational risk kept firmly under control.
Why SatuSehat Integration Stalls in Many Hospitals
Legacy systems don't speak FHIR
Many hospital systems store data in internal schemas incompatible with HL7 FHIR R4 resources, so patient, encounter, and diagnosis data cannot be sent to SatuSehat without thorough transformation.
Terminology is not standardized
SatuSehat submissions require standard codes such as ICD-10, ICD-9-CM, LOINC, and KFA, while historical hospital data often relies on local codes or free text that must be mapped item by item.
Heavy technical burden on lean IT teams
Managing OAuth 2.0 credentials, sandbox and production environments, failed-submission handling, and evolving Ministry of Health specifications demands technical capacity rarely available in full within a hospital.
Data protection compliance risk
Medical records qualify as specific personal data under Law No. 27 of 2022 on Personal Data Protection, so an integration built without proper security governance creates new legal exposure instead of resolving it.
How dhealth Connects Your Hospital to SatuSehat
Built-in SatuSehat integration module
dhealth ships with a SatuSehat connector that handles OAuth 2.0 authentication and generates HL7 FHIR R4 resources — such as Patient, Encounter, Condition, Observation, and Medication — directly from clinical workflows.
Standard terminology mapping
Diagnoses, procedures, laboratory results, and medication data are mapped to ICD-10, ICD-9-CM, LOINC, and KFA, so the data reaching the national platform is valid and consistent at the source.
Master data synchronization
NIK-based patient data, facility data, and practitioner data are synchronized with IHS numbers in SatuSehat, so every data transaction references the same national identity registry.
Submission monitoring and failure handling
Every submission is recorded with an auditable status and log; failed transactions can be identified and resubmitted without disrupting day-to-day patient care.
Security and privacy governance
Role-based access control, encryption, and audit trails are applied in line with the principles of Government Regulation 71/2019 on Electronic Systems and Transactions and the Personal Data Protection Law, so interoperability never comes at the expense of patient data protection.
dhealth is developed by DTI, a technology provider experienced in supporting institutions across Indonesia's regulated sectors, including healthcare facilities undergoing medical record digitalization and integration with the national health platform.
A Phased Integration Path to Go-Live
Assessment and registration
The DTI team maps the state of your existing system and data, then guides organizational registration with SatuSehat until sandbox access credentials are obtained. The assessment results become the basis of an integration plan that is realistic about your internal readiness.
Data and terminology mapping
Patient, encounter, diagnosis, procedure, laboratory, and pharmacy data structures are mapped to FHIR R4 resources along with their standard terminology codes. Patient and practitioner master data are aligned with national references so every submission is correctly identified.
Testing in the sandbox environment
Real-world scenarios — outpatient, inpatient, and ancillary services — are tested in the SatuSehat sandbox to validate data completeness and validity. Findings are fixed iteratively before the system is declared production-ready.
Production go-live and monitoring
Data submission to the SatuSehat production environment is activated in a controlled manner, supported by a submission-status monitoring dashboard, failure-handling procedures, and ongoing support as the national platform's specifications evolve.
Frequently Asked Questions about SatuSehat Integration
Are hospitals required to integrate with SatuSehat?
Permenkes 24/2022 requires healthcare facilities to run electronic medical records and governs health data interoperability through the platform designated by the Ministry of Health, namely SatuSehat. Integration readiness is therefore part of a hospital's regulatory obligations, not merely a technology initiative.
Our hospital system has been running for years. Do we have to replace it entirely?
Not necessarily. There are two options: building an integration bridge from your existing system to SatuSehat, or migrating to a FHIR-ready system such as dhealth. An initial assessment will show which path is more efficient given your data condition, system architecture, and long-term plans.
Which technical standards does SatuSehat use?
SatuSehat uses the HL7 FHIR R4 data exchange standard with OAuth 2.0 authentication, together with standard terminologies such as ICD-10 for diagnoses, ICD-9-CM for procedures, LOINC for laboratory tests, and KFA for pharmaceuticals. dhealth generates these resources and code mappings automatically from clinical workflows.
How long does the integration process usually take?
The duration depends on master data readiness, terminology code quality, and the scope of modules being integrated, so promising a uniform figure would be dishonest. dhealth's phased approach — assessment, mapping, sandbox, then production — keeps progress measurable at every stage, and a realistic timeline can be drawn up from the initial assessment.
How is patient data secured during integration?
Medical records are specific personal data under the Personal Data Protection Law, so the entire integration applies role-based access control, encryption in transit, and audit trails. The electronic system security principles of GR 71/2019 serve as the governance reference, and data is only sent to SatuSehat in accordance with applicable provisions.
What data does a hospital send to SatuSehat?
The data scope follows the use-case stages defined by the Ministry of Health, generally covering encounters, diagnoses, procedures, observations or vital signs, diagnostic results, and medication data. dhealth lets you activate this scope in stages, following your hospital's readiness and the platform's evolving requirements.
DHEALTH HIS — SATUSEHAT INTEROPERABILITY
Start Your Hospital's SatuSehat Integration Now
Discuss your hospital system's condition and data readiness with the DTI team. We will help you build a phased, measurable, and compliant SatuSehat integration roadmap — from initial assessment to data flowing in production.
