Indonesia's E-Prescription Regulations: A Compliance and System Implementation Guide
N
Back to Blog

Indonesia's E-Prescription Regulations: A Compliance and System Implementation Guide

Regulasi & Compliance
Nugroho Setiawan · Konsultan IT & Full Stack Developer 30 Jun 2026 15 min baca 3,309 kata 401 views
The digital transformation of healthcare services demands a thorough understanding of e-prescription regulations in Indonesia. This article will guide you through the legal framework, technical standards, and practical steps to achieve compliance, ensuring your system is ready for the era of healthc

Implementing electronic prescriptions or e-prescriptions is no longer just an innovation, but a necessity in the healthcare landscape in Indonesia. The manual paper-based prescription system often faces various problems, ranging from the risk of misreading doctors' handwriting, the potential for prescription duplication, to difficulties in tracking patient medication history. These problems directly impact the operational efficiency of healthcare facilities, increase the risk of medication errors, and hinder comprehensive data integration. The Indonesian government, through the SatuSehat initiative, is aggressively promoting the digitalization of healthcare services, and e-prescriptions are one of its main pillars. With increasingly stringent regulations, such as the latest Minister of Health Regulation (PMK), hospital IT managers, clinic owners, and decision-makers in the health sector are required to deeply understand the applicable legal framework and technical standards. This article will be your comprehensive guide. We will discuss the main legal basis, the essential FHIR R4 technical standards, present implementation code examples, payload schemas, error handling strategies, as well as best practices to ensure that your electronic prescription system not only complies with PMK 18 Tahun 2024 regulations, but also functions optimally and is fully integrated with the SatuSehat platform.

Basic Concepts of E-Prescriptions and the Regulatory Framework

E-prescriptions or electronic prescriptions are medication prescriptions that are created, sent, and stored digitally. This is an integral part of electronic medical records (EMR) which aims to improve the quality, safety, and efficiency of healthcare services. The main benefits of e-prescriptions include reducing the risk of medication errors due to misreading prescriptions, increasing the speed of the process in pharmacies, ease of tracking medication history, and support for more accurate audits. A study shows that the use of electronic prescriptions can reduce medication error rates by up to 50%, a significant figure in the context of patient safety.

The main legal basis governing electronic prescriptions in Indonesia is Minister of Health Regulation (PMK) Number 24 Tahun 2022 concerning Medical Records. This regulation explicitly requires healthcare facilities (fasyankes) to maintain medical records electronically, and electronic prescriptions are one of the crucial components within it. Then, PMK Number 18 Tahun 2024 concerning the Implementation of Medical Records further strengthens and provides more detail regarding this obligation, including the implementation of e-prescriptions as an inseparable part of EMR. This regulation confirms that every healthcare facility must have a system capable of generating, storing, and transmitting prescriptions in a standardized electronic format.

In addition, health data interoperability standards are very important, where the SatuSehat platform initiated by the Indonesian Ministry of Health acts as the backbone of data integration. All electronic medical record data, including e-prescriptions, is expected to be exchangeable through this platform using certain standards. The legality aspect of electronic prescriptions is also highly emphasized, where the use of valid and certified electronic signatures from Electronic Certification Providers (PSrE) recognized by the government becomes an obligation. This electronic signature provides legal force equivalent to a wet signature, ensuring the authenticity and integrity of the prescription.

In practice, the implementation of e-prescriptions allows doctors to write prescriptions through the hospital information system (SIMRS) or clinic information system (SIM Klinik), which is then automatically sent to the pharmacy system. This eliminates the need for paper prescriptions, speeds up the medication dispensing process, and allows pharmacies to cross-verify with the patient's allergy history or drug interactions recorded in the EMR. Thus, e-prescriptions are not only about digitalization, but also about improving the quality of service and patient safety holistically.

Technical Standards and Integration with SatuSehat

To ensure interoperability and compliance in the implementation of e-prescriptions, healthcare facilities must follow established technical standards. The main standard used for health data exchange in Indonesia, especially in the context of SatuSehat, is FHIR (Fast Healthcare Interoperability Resources) version R4. FHIR R4 provides a flexible and modern framework for health information exchange, and for e-prescriptions, the two most relevant FHIR resources are MedicationRequest and MedicationDispense. The MedicationRequest resource is used to record prescription requests from doctors, while MedicationDispense records the medication dispensing process by the pharmacy.

Integration with the SatuSehat platform requires an understanding of the specific workflow. Healthcare facilities need to register and obtain credentials (Client ID and Client Secret) for authentication. This authentication process usually involves exchanging credentials to obtain an Access Token (JSON Web Token/JWT) that is used for each API request. After successful authentication, e-prescription data that has been formatted according to the Indonesian FHIR profile for SatuSehat can be sent through the relevant API endpoint, such as /MedicationRequest. This Indonesian FHIR profile defines the mandatory elements and terminology that must be used so that the data can be received and processed correctly by SatuSehat.

In system development, various tools and libraries can be utilized. For implementing a Java-based FHIR server or client, HAPI FHIR version 6.8.0 is a popular and robust choice. For developers using JavaScript, libraries such as fhir.js can help in manipulating FHIR objects on the frontend or middleware side. On the backend side, frameworks such as Laravel 11.x (PHP) or the Node.js 20 LTS runtime are solid choices for managing local prescription data, implementing business logic, and interacting with the SatuSehat API. For secure and structured storage of prescription data, a relational database such as PostgreSQL 16 is highly recommended due to its ability to handle complex data and its strong security features.

In addition to the FHIR standard, there are several additional technical requirements that need to be considered. Data security is paramount; all communication must be encrypted using HTTPS/TLS, and stored data must be protected with encryption at rest. The system must also have comprehensive audit trail capabilities, recording every activity related to prescriptions, including who created, modified, or canceled a prescription, as well as when and why. The feature to cancel or revise a prescription must be equipped with a clear audit trail mechanism to ensure accountability and compliance with regulations.

Technical Implementation of E-Prescription: Code Example

Understanding theory and regulations is one thing, but technical implementation is the key to success. In this section, we will look at a concrete example of how a MedicationRequest object can be built and sent to the SatuSehat API. This object must contain all important information such as patient identification, doctor, drug details, dosage, route of administration, frequency, and duration. Each element must refer to another FHIR resource (for example, the patient and doctor refer to the Patient and Practitioner resources respectively) and use terminology that complies with the Indonesian FHIR profile.

The first code example below shows how you can create a MedicationRequest payload in JSON format using PHP, which is often used in the Laravel environment. This function accepts an array of data containing essential information and constructs a complete FHIR object. Note the use of Carbon for dates and times, as well as how each element such as medicationCodeableConcept, subject, and requester is filled with references and codes that comply with the FHIR standard and SatuSehat terminology. For example, medicationCode will refer to the drug terminology system used by the Ministry of Health.

<?phpnamespace App"Services;use Carbon"\Carbon;class SatuSehatFhirService{    public function generateMedicationRequestPayload(array $data): array    {        // $data harus berisi: patientId, practitionerId, medicationCode, dosage, route, frequency, duration        $payload = [            "resourceType" => "MedicationRequest",            "id" => "medreq-".uniqid(), // ID unik lokal            "identifier" => [                [                    "system" => "http://sys-rekammedis.com/identifier/medication-request",                    "value" => "MRX-".strtoupper(uniqid())                ]            ],            "status" => "active",            "intent" => "order",            "medicationCodeableConcept" => [                "coding" => [                    [                        "system" => "http://terminology.kemkes.go.id/CodeSystem/medication",                        "code" => $data['medicationCode'], // e.g., "1000001" untuk Paracetamol                        "display" => $data['medicationDisplay']                    ]                ],                "text" => $data['medicationDisplay']            ],            "subject" => [                "reference" => "Patient/".$data['patientId'], // ID pasien dari SatuSehat                "display" => $data['patientName']            ],            "authoredOn" => Carbon::now()->toIso8601String(),            "requester" => [                "reference" => "Practitioner/".$data['practitionerId'], // ID dokter dari SatuSehat                "display" => $data['practitionerName']            ],            "dosageInstruction" => [                [                    "sequence" => 1,                    "text" => $data['dosageText'], // e.g., "1 tablet 3 kali sehari setelah makan"                    "timing" => [                        "repeat" => [                            "frequency" => $data['frequency'], // e.g., 3                            "period" => 1,                            "periodUnit" => "d" // per day                        ]                    ],                    "route" => [                        "coding" => [                            [                                "system" => "http://terminology.kemkes.go.id/CodeSystem/route",                                "code" => $data['routeCode'], // e.g., "PO" untuk per oral                                "display" => $data['routeDisplay']                            ]                        ],                        "text" => $data['routeDisplay']                    ],                    "doseAndRate" => [                        [                            "type" => [                                "coding" => [                                    [                                        "system" => "http://terminology.hl7.org/CodeSystem/dose-rate-type",                                        "code" => "ordered",                                        "display" => "Ordered"                                    ]                                ]                            ],                            "doseQuantity" => [                                "value" => $data['doseValue'], // e.g., 1                                "unit" => $data['doseUnit'], // e.g., "tablet"                                "system" => "http://unitsofmeasure.org", // atau sistem unit yang relevan                                "code" => $data['doseUnitCode'] // e.g., "tab"                            ]                        ]                    ]                ]            ],            "dispenseRequest" => [                "validityPeriod" => [                    "start" => Carbon::now()->toIso8601String(),                    "end" => Carbon::now()->addDays($data['durationDays'])->toIso8601String()                ],                "numberOfRepeatsAllowed" => 0,                "quantity" => [                    "value" => $data['totalQuantity'], // Total quantity to be dispensed                    "unit" => $data['doseUnit'],                    "system" => "http://unitsofmeasure.org",                    "code" => $data['doseUnitCode']                ],                "expectedSupplyDuration" => [                    "value" => $data['durationDays'],                    "unit" => "days",                    "system" => "http://unitsofmeasure.org",                    "code" => "d"                ]            ]        ];        return $payload;    }}

After the MedicationRequest payload is successfully created, the next step is to send it to the SatuSehat API. The second code example, written in JavaScript for the Node.js environment, shows how you can use the fetch function to make a POST request to the SatuSehat /MedicationRequest endpoint. It is important to ensure the Content-Type header is set to application/fhir+json and to include an Authorization header with a valid Bearer Token. Handling the API response, whether successful or failed, must also be implemented to ensure your system can react appropriately to the data submission status.

// Example in Node.js using fetch to send MedicationRequest to SatuSehatconst fetch = require('node-fetch'); // Make sure node-fetch is installed if Node.js < 18const config = {    satuSehatUrl: "https://api-satusehat.kemkes.go.id/fhir-r4/v1", // SatuSehat FHIR URL    clientId: "YOUR_CLIENT_ID",    clientSecret: "YOUR_CLIENT_SECRET",    accessToken: "YOUR_ACCESS_TOKEN" // Get from SatuSehat OAuth API};async function sendMedicationRequestToSatuSehat(medicationRequestPayload) {    try {        const response = await fetch(`${config.satuSehatUrl}/MedicationRequest`, {            method: 'POST',            headers: {                'Content-Type': 'application/fhir+json',                'Authorization': `Bearer ${config.accessToken}`            },            body: JSON.stringify(medicationRequestPayload)        });        if (!response.ok) {            const errorData = await response.json();            console.error('Failed to send MedicationRequest:', response.status, errorData);            throw new Error(`SatuSehat API error: ${response.status} - ${JSON.stringify(errorData)}`);        }        const result = await response.json();        console.log('MedicationRequest sent successfully:', result);        return result;    } catch (error) {        console.error('Error sending MedicationRequest:', error.message);        throw error;    }}

In both examples, the focus is on the correct data structure and how to interact with the API. Developers must ensure that all reference IDs (such as patientId and practitionerId) are valid IDs that have been registered in SatuSehat, and that the terminology codes (for example, for drugs and routes) comply with the CodeSystem recommended by the Ministry of Health. Following this guidance will help ensure that the e-prescriptions you create can be exchanged and understood by other systems in the SatuSehat ecosystem.

Validation, Error Handling, and Audit

Data validation is a crucial step before sending the e-prescription payload to SatuSehat. Validation failure can cause data rejection by the API and hinder medical workflows. Validation must be performed on both the client and server sides to ensure that all entered data complies with the Indonesian FHIR profiles and the required terminology. This includes checking ID formats, the presence of mandatory elements, and the conformity of code values. For example, ensuring that the referenced patient ID actually exists and is active in the SatuSehat system.

The following is an example of a realistic JSON payload for the MedicationRequest resource, which includes important details such as prescription identification, status, intent, medication information, subject (patient), requester (doctor), dosage instructions, and dispensing request details. This payload reflects the structure expected by the SatuSehat API based on the FHIR R4 standard.

{  "resourceType": "MedicationRequest",  "id": "medreq-001-fasyankes-A",  "identifier": [    {      "system": "http://sys-rekammedis.com/identifier/medication-request",      "value": "MRX-00012345"    }  ],  "status": "active",  "intent": "order",  "medicationCodeableConcept": {    "coding": [      {        "system": "http://terminology.kemkes.go.id/CodeSystem/medication",        "code": "1000001",        "display": "Paracetamol 500 mg Tablet"      }    ],    "text": "Paracetamol 500 mg Tablet"  },  "subject": {    "reference": "Patient/100000030009",    "display": "Budi Santoso"  },  "authoredOn": "2024-07-26T10:30:00+07:00",  "requester": {    "reference": "Practitioner/100000030006",    "display": "Dr. Siti Aminah"  },  "dosageInstruction": [    {      "sequence": 1,      "text": "1 tablet 3 times a day after meals",      "timing": {        "repeat": {          "frequency": 3,          "period": 1,          "periodUnit": "d"        }      },      "route": {        "coding": [          {            "system": "http://terminology.kemkes.go.id/CodeSystem/route",            "code": "PO",            "display": "Per Oral"          }        ],        "text": "Per Oral"      },      "doseAndRate": [        {          "type": {            "coding": [              {                "system": "http://terminology.hl7.org/CodeSystem/dose-rate-type",                "code": "ordered",                "display": "Ordered"              }            ]          },          "doseQuantity": {            "value": 1,            "unit": "tablet",            "system": "http://unitsofmeasure.org",            "code": "tab"          }        }      ]    }  ],  "dispenseRequest": {    "validityPeriod": {      "start": "2024-07-26T10:30:00+07:00",      "end": "2024-08-02T10:30:00+07:00"    },    "numberOfRepeatsAllowed": 0,    "quantity": {      "value": 21,      "unit": "tablet",      "system": "http://unitsofmeasure.org",      "code": "tab"    },    "expectedSupplyDuration": {      "value": 7,      "unit": "days",      "system": "http://unitsofmeasure.org",      "code": "d"    }  }}

When an error occurs, the SatuSehat API will return an OperationOutcome response. The following is an example of an error message that may be received:

{  "resourceType": "OperationOutcome",  "issue": [    {      "severity": "error",      "code": "value",      "details": {        "text": "The 'subject' field is required and must reference a valid Patient resource."      },      "expression": [        "MedicationRequest.subject"      ]    }  ]}

Effective error handling is very important. When receiving an OperationOutcome with severity: "error", your system must be able to identify the problem from details.text and expression. In the example above, the problem is that the subject field on the MedicationRequest does not reference a valid Patient resource. Error handling strategies include: (1) Logging errors in detail with timestamp and context, (2) Implementing a retry mechanism with exponential backoff for temporary failures, (3) Automatic notification to system administrators, and (4) Providing a fallback mechanism, for example, storing prescriptions locally and flagging them for resubmission if the API is unavailable. In addition, every e-prescription transaction, including creation, modification, cancellation, and submission, must be recorded in a comprehensive audit trail. This audit trail must include information on who performed the action, when, and what changes occurred, in accordance with the requirements of PMK 18/2024 for accountability and record-keeping.

E-Prescription Implementation Best Practices

  1. Frontend and Backend Data Validation: Ensure that all entered data (patient, medication, dose, route) is strictly validated on both the client and server sides according to the Indonesian FHIR profiles and SatuSehat terminology before being sent. This validation will prevent API errors, ensure data integrity, and reduce the potential for medication errors, thereby improving patient safety.
  2. Strong Authentication and Authorization Management: Implement an OAuth 2.0 authentication mechanism for the SatuSehat API and ensure access tokens are managed securely, including a periodic token refresh mechanism. Role-based authorization must be implemented to ensure that only authorized medical personnel can create, modify, or access prescriptions, in accordance with the principles of privacy and data security.
  3. Comprehensive Audit Trail: Every action related to e-prescriptions (creation, modification, cancellation, submission) must be recorded in detail in an audit trail. These records must include a timestamp, the identity of the user performing the action, and the data changes that occurred. These audit logs are very important for accountability, issue tracking, and compliance with applicable regulations.
  4. Intuitive and Secure UI/UX Design: The user interface for creating e-prescriptions must be designed to be easy to use by doctors and medical staff, minimizing the potential for input errors and speeding up the workflow. Use auto-suggest features for medication names and standard doses, and provide visual warnings for relevant drug interactions or allergies.
  5. Robust Error Handling and Retry Mechanisms: Build a system that is resilient to API failures with detailed error logging and automatic retry mechanisms (for example, exponential backoff) for sending data to SatuSehat. Also provide a clear manual option for users to resend failed data or review submission status, ensuring no data is lost.
  6. End-to-End Prescription Data Security: Ensure that electronic prescription data is encrypted in transit (using HTTPS/TLS) and at rest (encryption at rest) in accordance with applicable health data security standards. Limit data access only to authorized parties through strict access controls, and comply with the Personal Data Protection Law (UU PDP).
  7. Extensive and Gradual Testing: Conduct thorough end-to-end testing gradually, from unit testing to integration and user acceptance testing (UAT). Use the SatuSehat staging environment to ensure that all functionality flows, integrations, and error handling work correctly before the system is deployed to the production environment.
  8. Continuous User Training: Provide regular and comprehensive training to doctors, nurses, pharmacists, and pharmacy staff regarding the use of the e-prescription system and the latest regulatory changes. Effective training will increase system adoption, reduce resistance, and ensure optimal utilization of features.
  9. Proactive System Monitoring and Maintenance: Monitor system performance regularly, including SatuSehat API responses, and perform routine maintenance to ensure the system runs optimally. This includes software updates, log monitoring, and periodic review of security policies to always align with the latest standards and regulations.

FAQ

  1. Do all prescriptions have to be electronic?
    According to PMK No. 18 of 2024, healthcare facilities are required to implement electronic medical records, including electronic prescriptions, as part of the national health digitalization effort. Although there may be a transition period, the ultimate goal is that all prescriptions must be in electronic form to support data interoperability and improve patient safety. This implementation is a fundamental component of the integrated SatuSehat ecosystem.
  2. What if there is an internet disruption when creating an e-prescription?
    A robust e-prescription system must be designed with offline mode or local caching capabilities. If the internet connection is lost, prescriptions can be temporarily stored in the local system of the healthcare facility and automatically sent to SatuSehat once the internet connection is restored. It is important to have a strong data synchronization mechanism to ensure that no data is lost or duplicated during the offline period.
  3. Is an electronic signature mandatory for e-prescriptions?
    Yes, a valid and certified electronic signature from a registered Electronic Certification Provider (PSrE) is an absolute requirement for the legality of e-prescriptions in Indonesia. This electronic signature ensures the authenticity of the prescription and the identity of the doctor who wrote it, meeting legal requirements equivalent to a wet signature on a conventional prescription. Healthcare facilities need to integrate their systems with recognized PSrE providers.
  4. What drugs can be prescribed electronically?
    In principle, all types of drugs can be prescribed electronically, from over-the-counter drugs to hard drugs, narcotics, and psychotropics. However, for drugs in special categories, the e-prescription system must meet very strict security and audit trail standards, and may require additional security features to comply with specific applicable regulations.
  5. How can patient data be kept safe in the e-prescription system?
    Patient data security is a top priority and must be implemented in layers. This involves data encryption at rest and in transit, strict role-based access control, a comprehensive audit trail for every access or change to data, as well as compliance with data protection standards such as the PDP Law (Personal Data Protection) and international information security standards such as ISO 27001.
  6. How much does it cost to implement an e-prescription system integrated with SatuSehat?
    The cost of implementing an e-prescription system varies greatly and depends on several factors, such as the scale of the healthcare facility, the complexity of the existing system, and the desired customization features. These costs generally include software licenses, custom development, hardware infrastructure, staff training, as well as integration costs with the SatuSehat API and electronic signature providers. A realistic budget should be prepared after an in-depth needs analysis.

Compliance with e-prescription regulations and integration with SatuSehat is not merely a legal obligation, but a strategic investment in operational efficiency, patient safety, and the future of digital healthcare in Indonesia. By understanding the regulatory framework, technical standards, and implementing best practices, healthcare facilities can navigate this complexity with confidence. Prescription digitalization will bring long-term benefits in accuracy, speed, and auditability. If you need a trusted partner to develop or integrate your e-prescription system so that it complies with PMK 18/2024 and is connected to SatuSehat, the Nugroho Setiawan team, with experience in SIMRS, SIM Klinik, and Bridging Integrator, is ready to help. We offer efficient and secure custom solutions, from Laravel/Node.js backend development to FHIR R4 integration. Contact us for a free consultation and realize a reliable digital health system at your facility.

This article is part of the knowledge base of Nugroho Setiawan, an IT consultant in Jogja (Yogyakarta). Related solutions: SIMRS (Hospital Information System) Clinic Management System SatuSehat Integration. Need a free consultation?

Terakhir diperbarui 18 Oct 2026

Komentar

Komentar ditinjau sebelum tampil.

Belum ada komentar. Jadilah yang pertama!

Butuh bantuan implementasi atau dashboard data?

Saya membantu konsultasi IT, pengembangan aplikasi, dan visualisasi data untuk rumah sakit, klinik, dan bisnis di Yogyakarta (DIY), Magelang, dan sekitarnya.

WhatsApp Jasa Visualisasi Data Demo VizStudio
Produk & Solusi SIMRS ERP Portfolio Konsultasi Gratis