About
An HMS built from the code by a practitioner who understands compliance — not retrofitted after an audit. Started on one conviction: every hospital deserves a system that's compliant, integrated, and truly its own.
Vision
One quality standard for every hospital, whatever its size or location — compliant from the first line of code, natively integrated with the Ministry of Health ecosystem, and your data stays fully yours.
Mission
Intellectual property
Copyright of the "SIMRS Adievia" computer program is officially registered with the Directorate General of Intellectual Property (DGIP), Ministry of Law of the Republic of Indonesia, under Registration No. 001288172, in accordance with Law 28/2014 on Copyright.
Copyright holder: PT ADIEVIA MEDIKA TEKNOLOGI. Moral rights remain attached to the Author in accordance with Article 5 of Law 28/2014.
10 standards
Compliance built into the architecture from the foundation — most controls already live; the rest are formalized in the third-party audit phase (Q1–Q2 2027). Each card states its status as it is.
Electronic Medical Records — designed to its provisions from the architecture up.
Consent, access, deletion, portability rights.
Tamper-evident audit trail (SHA-256 hash chain) over medical-record operations; retention policy follows Permenkes 24/2022 (5 yrs / 25 yrs for minors).
Field-level AES-256-GCM for sensitive data at rest, TLS 1.2/1.3 in transit.
TOTP (RFC 6238) + passkey/WebAuthn + single-use backup codes; accounts can be required to use MFA.
Deterministic (searchable) for NIK, BPJS, and passport number; other sensitive data uses a random IV.
Scalable permission system per role and module, synced between application and database.
Medical resumes, doctor certificates, and clinical consent are signed straight from the EMR flow — today as an uncertified electronic signature. Certified e-signature integration (BSrE for government hospitals, a non-agency PSrE for private hospitals) is being prepared with the first partner hospital; certificates are issued by the provider, separate from the Adievia license.
Data freeze mechanism for litigation support — scheduled for the third-party audit phase (Q1–Q2 2027).
Periodic restore tests in sandbox — procedures verified and formalized in the third-party audit phase.
Trust
Separate environment with sandboxed BPJS/SATUSEHAT/E-Klaim. Zero spam or data leak risk.
Adievia hosted on infrastructure of your choice — on-premise, GCP, AWS, or Azure. Hospital data is not locked to a single provider.
Bahasa Indonesia operational tutorials per module. API docs for third-party integrations.
All hospital data can be exported in standard formats (CSV, FHIR R4 JSON, SQL dump) at any time. No vendor trap when you want to migrate.
Based in Indonesia, hospital-preferred servers, Indonesian time zones, direct support from the developer.
Team
Adievia was founded by healthcare-tech practitioners who understand Permenkes 24/2022 compliance from the code level — not just a sales checklist.
Founder & Software Architect
Leads the architecture of Adievia HMS — 58+ Go backend modules + a React/TypeScript frontend, building integrations for SATUSEHAT FHIR R4, BPJS PCare + V-Claim, SISRUTE, e-Klaim INA-CBG, BSrE, DICOM PACS, and HL7 v2 LIS.
Focused on an HMS designed to meet Permenkes 24/2022 + UU 27/2022 PDP from the ground up — compliance built into the architecture, not retrofitted. Based in Bulukumba, South Sulawesi.
Verified profile on LinkedInConsultative — not yet permanent staff
Adievia is currently developed directly by its founder. Clinical workflows are validated with consultative support from doctors, nurses, and medical records staff, plus contributors from Indonesia's open-source healthcare community. A permanent team will be built gradually alongside the first hospital to join — your hospital could become our first reference site.