Electronic Medical Records
SOAP, e-prescription, DPJP signature.
Company
An Indonesia-based health-tech company (Bulukumba, South Sulawesi). We build Adievia HMS — a Hospital Information System (SIMRS) with 49 integrated modules across clinical, financial, and BPJS & SATUSEHAT (FHIR R4) integration, built to Indonesia's Permenkes 24/2022 EMR standard. Official site: adievia.co.id.
Verified credentials
Live product
One full HMS for hospital operations, one portal for patients & the public. Both running now — no install, no waiting.
Auto-login as guest — explore modules instantly, no signup.
Public — no login to explore.
Built to integrate with







Integrations are built at the code level per each authority's official specs; production activation follows the issuance of credentials & certification for your hospital.
Clinical, financial, integrations, and administration — all in one platform. No separate vendors for billing, lab, or pharmacy.
VClaim, Antrean, Apotek, i-Care, PCare for BPJS. FHIR R4 for SATUSEHAT — integration is built into the core system, not bolted on.
Permenkes 24/2022 EMR. Indonesia PDP Act. Tamper-evident audit trail over patient-data operations. Field-level AES-256-GCM encryption for sensitive data.
Containerized stack ready to deploy. Implementation timeline is scoped to your hospital's size and data-migration needs, defined in an upfront discovery session.
Single hospital today, hospital group tomorrow. The multi-tenant backend foundation is in place — multi-branch activation as you grow into a group, no rewrite.
Based in Indonesia, Indonesian time zones, Bahasa Indonesia documentation. Direct support from the developer building the product.
[02] Engineering foundation
A good system accelerates everything — from patient registration to BPJS claims. Every second saved for hospital staff is time returned to patient care.
Integrated modules — clinical, financial, administrative, integrations.
AES-256
Field-level AES-256-GCM encryption at rest for sensitive patient data — identifiers (NIK, BPJS, passport, phone, email) plus select sensitive medical data — with NIK/BPJS/passport using a deterministic mode so they stay searchable. TLS 1.2/1.3 in transit.
ACID
Clinical transactions with full integrity — no medical record is lost to mid-write failure or race conditions when multiple staff input concurrently.
Highlighted modules
9 core clinical modules for end-to-end workflows — from registration to discharge. See all 15 clinical modules on the Products page.
SOAP, e-prescription, DPJP signature.
NEWS2, APACHE II, SOFA scoring, multi-bed live board.
Multi-flow triage, admit-to-ward, SBAR handover.
Queue, bed assignment, doctor visits, monitoring.
Dispensing, POS, narcotics control.
Order, result entry, critical value notification.
Order, scheduling, PACS/DICOM integration.
OR scheduling, surgical site checklist.
Antenatal, delivery, perinatology.
[06] Development stage
Transparent about where we are and where we're headed. Trust is built on clarity, not claims.
2026 — Now
49 integrated modules already running in a staging + public demo environment. BPJS & SATUSEHAT integration is functional.
2026 H2
Opening our first hospital pilot program — Eastern Indonesia priority, limited first-batch slots. End-to-end clinical workflow validation + Kemenkes integration certification with the first partner hospital.
Q1-Q2 2027
Permenkes 24/2022 audit (28 criteria), SATUSEHAT production certification, BSrE e-signature production activation, security penetration test.
Q3 2027 — Target
General availability for Indonesian hospitals. Multi-tenant onboarding, implementation playbook, commercial support tiers.
Want to be a founding-partner hospital? Limited founding-partner slots — with special founder pricing and a direct priority line to the founder (business hours). Your data stays fully yours.
Discuss Pilot[07] Pilot Program
We're opening registration for our first cohort of hospitals. The testimonial slots below are waiting for an HIS partner ready to begin their digital transformation with us.
01
Slot open
A quote from your hospital will live here.
A short story of the real impact after Adievia goes live — queue times, BPJS claims, admin load.
02
Slot open
A story from the CEO or IT Lead.
How an HIS decision reshaped the way your hospital operates every single day.
03
Slot open
Testimony from a DPJP or clinical staff.
The end-user perspective — whether the system truly frees up time to focus on patients.
First clients receive a priority implementation lane, founder pricing, and direct access to the developer.
Become our first client[08] FAQ
Adievia is built to the Permenkes 24/2022 EMR standard from the architectural foundation — SOAP structure, DPJP-signed e-prescriptions, a tamper-evident audit trail over patient-data operations, and a regulation-aligned retention policy. The formal 28-criteria compliance audit is scheduled for the pre-go-live hardening phase (Q1–Q2 2027), so the first partner hospitals receive a system already aligned with regulation.
Native integration for BPJS: VClaim, Antrean, Apotek, i-Care, PCare. For SATUSEHAT: FHIR R4 with full bundle resource support (Patient, Encounter, Observation, Condition, Procedure, MedicationRequest, etc.). Activation once facility credentials are issued.
Implementation timeline depends on hospital scale and migration scope — covering module configuration, legacy data migration, staff training, and UAT. We define the estimate together in an initial discovery session so it fits your hospital.
Field-level AES-256-GCM encryption at rest for sensitive patient data — identifiers (NIK, BPJS, passport, phone, email) plus select sensitive medical data. TLS 1.2/1.3 in transit, with legacy protocols (TLS 1.0/1.1) disabled. Daily backups are managed at the infrastructure level (30-day retention target); verification and restore-testing procedures are finalized in the pre-go-live hardening phase. Google Cloud servers (Jakarta region) — hospital data never leaves Indonesia, per Indonesia's PDP Act.
Yes. Adievia provides legacy data migration services (from old databases, Excel files, or exports from other vendors). Mapping is done directly by the developer alongside the hospital's clinical lead to ensure clinical data integrity.
No. All your data — including master data configuration and clinical logs — can be exported in standard formats (CSV, FHIR R4 JSON, or SQL dump) at any time. Adievia can also be hosted on-premise on your hospital servers — data never leaves your infrastructure if you prefer.
Tier-1 support via WhatsApp Business and email. As an early pilot client, you get a direct priority line to the developer. Response targets are agreed together in the implementation contract, in line with our early-stage capacity.
The architecture is multi-branch by design — the multi-tenant backend foundation is in place. As your hospital grows into a group, one Adievia instance can serve multiple hospitals with per-tenant data isolation, centralized master data (formulary, ICD-10, procedure codes), and aggregate group dashboards — activated with no rewrite.