[01]
Electronic Medical Records
SOAP, e-prescription, DPJP signature.
Company
PT Adievia Medika Teknologi
An Indonesia-based health-tech company (Bulukumba, South Sulawesi). We build Adievia HMS — a Hospital Information System (SIMRS) with 70 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
- Registered company — PT Adievia Medika Teknologi
- Komdigi PSE registered — TDPSE No. 023937.01/DJAI.PSE/06/2026
- DJKI Copyright — No. 001288172
- Official contact — info@adievia.co.id
Live product
Not a mockup — two live products you can click right now.
One full HMS for hospital operations, one portal for patients & the public. Both running now — no install, no waiting.
HMS — Core Hospital System
— the hospital's core operating system: doctors, nurses, pharmacy, lab, cashier, accounting (58+ modules)
Open HMS Demo
Auto-login as guest — explore modules instantly, no signup.
Patient Portal & Hospital Web
— public hospital site + patient self-service (find a doctor, book, personal records)
Open Patient Portal
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.
Six reasons hospitals choose Adievia.
[01]
58+ modules, one system
Clinical, financial, integrations, and administration — all in one platform. No separate vendors for billing, lab, or pharmacy.
[02]
Native BPJS + SATUSEHAT
VClaim, Antrean, Apotek, i-Care, PCare for BPJS. FHIR R4 for SATUSEHAT — integration is built into the core system, not bolted on.
[03]
Compliant by design
Permenkes 24/2022 EMR. Indonesia PDP Act. Tamper-evident audit trail over patient-data operations. Field-level AES-256-GCM encryption for sensitive data.
[04]
Fast deployment
Containerized stack ready to deploy. Implementation timeline is scoped to your hospital's size and data-migration needs, defined in an upfront discovery session.
[05]
Multi-branch ready
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.
[06]
Local
Based in Indonesia, Indonesian time zones, Bahasa Indonesia documentation. Direct support from the developer building the product.
[02] Engineering foundation
we ship more than software. we ship momentum.
A good system accelerates everything — from patient registration to BPJS claims. Every second saved for hospital staff is time returned to patient care.
58+
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
Clinical.
9 core clinical modules for end-to-end workflows — from registration to discharge. See the full clinical group (26 modules) on the Products page.
[02]
ICU
NEWS2, APACHE II, SOFA scoring, multi-bed live board.
[03]
Emergency (IGD)
Multi-flow triage, admit-to-ward, SBAR handover.
[04]
Outpatient & Inpatient
Queue, bed assignment, doctor visits, monitoring.
[05]
Pharmacy
Dispensing, POS, narcotics control.
[06]
Laboratory
Order, result entry, critical value notification.
[07]
Radiology
Order, scheduling, PACS/DICOM integration.
[08]
Surgery
OR scheduling, surgical site checklist.
[09]
Maternity & NICU
Antenatal, delivery, perinatology.
[06] Status & availability
production-ready, released in stages.
The system is ready to run today — what we limit is how many hospitals we take on in each phase, so every implementation gets our full attention. Trust is built on clarity, not claims.
2026 — Now
Production-ready
70 integrated modules — built, tested, and open to explore in the public demo right now. BPJS & SATUSEHAT integration is functional.
2026 H2
Founding partners — first batch
Slots deliberately limited to 1-2 hospitals — open across Indonesia — so the first implementations are guided directly by the developer: end-to-end clinical workflow validation and Kemenkes integration certification with the partner hospital.
Q1-Q2 2027
Third-party audit & certification
The system is built to Permenkes 24/2022 from the foundation; this phase formalizes external validation — the 28-criteria audit, SATUSEHAT production certification, BSrE e-signature production activation, and a security penetration test.
Q3 2027 — Target
General availability
Sales open to all Indonesian hospitals — multi-tenant onboarding, implementation playbook, commercial support tiers. Until then, access is exclusively through the founding-partner program.
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
the next client story could be yours.
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.
Onboarding first clients Limited capacity — 1-2 founding hospitals.
01
Slot open
A quote from your hospital will live here.
A short story of the real impact once the system runs in full at your hospital — 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
frequently asked questions.
Yes — the system 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. As an additional layer of verification, a formal third-party 28-criteria audit is scheduled for Q1–Q2 2027 — founding-partner hospitals run a system already aligned with regulation from day one.
The 30 July 2026 joint circular (BPJS Kesehatan, the Health Ministry, the Home Affairs Ministry, KPK, BSSN) pushes JKN claims onto SATUSEHAT-integrated EMR — pilots from August 2026, with "No RME, No Claim" targeted to take full effect in 2027 (the exact date awaits the implementing guidance). The foundation this direction demands is what Adievia builds: a structured EMR, SATUSEHAT FHIR R4 bridging, BPJS & E-Klaim integration, plus a BSrE e-signature module (the certificate is a separate subscription from the provider). The circular's technical guidance is not yet out, so we do not claim full compliance — the foundation is ready and we adapt as soon as the rules are final.
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 formalized in the third-party audit phase (Q1–Q2 2027). 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 a founding-partner hospital, you get a direct priority line to the developer — our support capacity is deliberately focused on a small number of first hospitals. Response targets are agreed together in the implementation contract.
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.