SNARS Accreditation Guide: Essential IT Checklist for Modern Hospitals
N
Back to Blog

SNARS Accreditation Guide: Essential IT Checklist for Modern Hospitals

Regulasi & Compliance
Nugroho Setiawan · Konsultan IT & Full Stack Developer 04 May 2026 6 min baca 3,224 kata 740 views
SNARS accreditation is key to hospital quality. This article provides an in-depth guide and essential IT checklist for modern hospitals, covering SIMRS integration, data security, and standards compliance strategies. Enhance your IT readiness for accreditation.

Hospitals in Indonesia face significant challenges in maintaining service quality and regulatory compliance. One of the main pillars is the National Hospital Accreditation Standards (SNARS) Accreditation issued by the Hospital Accreditation Committee (KARS). This accreditation is not merely a formality, but a reflection of the hospital's commitment to patient safety and sustainable service quality. However, hospital IT departments often feel overwhelmed by the many SNARS requirements that implicitly or explicitly demand a robust information technology role. From electronic medical record (EMR) management, the security of sensitive patient data, to complex system integration with the national health ecosystem such as SatuSehat. Without a clear and structured IT strategy, the accreditation process can become a major obstacle. This article will guide you, hospital IT managers, clinic owners, and decision-makers, through the mandatory IT checklist to achieve SNARS accreditation, with a focus on practical implementation, current technology, and concrete examples that you can immediately apply. We will discuss basic concepts, technical implementation details, code examples, error handling case studies, best practices, and frequently asked questions (FAQs).

Basic Concepts of SNARS Accreditation and the Crucial Role of IT

The currently applicable SNARS Ed. 1.1 Accreditation is an instrument for measuring the quality of hospital services in Indonesia, based on international standards and best practices in patient safety. KARS as the accreditation body sets various standard chapters, and many of them are closely related to IT infrastructure and systems. For example, in the Medical Records and Health Information (MIRM) Chapter, IT becomes the backbone in implementing a comprehensive Electronic Medical Record (EMR), from recording patient data, integrating laboratory and radiology results, to the availability of data for clinical decision-making. Without a reliable EMR system, hospitals will not be able to meet the MIRM 1.1 standard regarding the completeness and timeliness of EMR filling, or MIRM 1.2 regarding data interoperability between units.

In addition to MIRM, other chapters such as Facility and Safety Management (MFK) also heavily depend on IT. MFK covers aspects of information security, IT risk management, and business continuity planning (BCP) for critical systems. Imagine if the SIMRS or EMR system experiences sudden downtime; the impact on patient care could be fatal. Therefore, IT must ensure a structured data backup system, a tested Disaster Recovery Plan (DRP), and strict cybersecurity protocols to protect patient data from cyber threats, in accordance with MFK 5.1 and MFK 7.1 standards. This is no longer an option, but an absolute necessity in the modern hospital landscape.

Another equally important aspect is Patient and Family Rights (HPK). HPK 1.1 and HPK 2.1 require hospitals to maintain the confidentiality of patient information. This is where IT's role in implementing Role-Based Access Control (RBAC) becomes vital. Only staff with authorization and clinical relevance may access certain patient data. An audit trail system that records every access and data change activity also becomes irrefutable evidence of compliance. Without this mechanism, the risk of data privacy violations is very high, which can lead to legal sanctions and loss of public trust.

Integration is another keyword in SNARS. Modern hospitals can no longer operate with isolated systems. Patient data must flow smoothly between the registration unit, outpatient clinics, emergency department, laboratory, radiology, pharmacy, and billing. This requires clear interoperability standards, such as HL7 v2.5.1 or FHIR R4, which we will discuss further. Compliance with SNARS is not just about having an IT system, but about how that system is integrated, secure, and supports clinical workflows effectively and efficiently. The IT team must understand these standards in depth to design and implement solutions that truly support accreditation.

Technical Implementation and Hospital Information System (SIMRS) Compliant with SNARS

To achieve SNARS compliance, the technical implementation of SIMRS must be solid and integrated. A modern SIMRS must include essential modules such as an Electronic Medical Record (EMR) that supports clinical documentation standards, a Laboratory Information System (LIS), a Radiology Information System (RIS) or PACS (Picture Archiving and Communication System), a Pharmacy Information System (PIS), as well as other supporting modules such as billing and inventory management. The main key is interoperability. For integration between internal modules or with external systems, hospitals must adopt international health data communication standards. One of the most relevant is HL7 v2.5.1 for transactional message exchange (for example, ADT for registration, ORU for lab results) and FHIR (Fast Healthcare Interoperability Resources) R4 for more modern and granular RESTful API-based data exchange.

As an example, for integration with external platforms such as SatuSehat, implementing FHIR R4 is a necessity. The Indonesian Ministry of Health explicitly requires hospitals to integrate patient data with SatuSehat using the FHIR R4 standard. This means your SIMRS must be able to produce and consume FHIR resources such as Patient, Encounter, Condition, Procedure, MedicationRequest, and Observation. For developers, this can be implemented using frameworks such as Laravel 11.x on the backend with the Guzzle HTTP client library to interact with the SatuSehat API, or Node.js 20 LTS with the node-fhir-client or fhir.js modules. The recommended database for performance and scalability is PostgreSQL 16 or MySQL 8.0, with a schema optimized for health data.

Data security is a fundamental aspect that is often overlooked. SNARS accreditation, especially in the MFK chapter, demands strict protection of patient data. This includes encryption of data in transit (using TLS 1.2 or TLS 1.3 for all API and web connections) and at rest (disk encryption or database encryption). Role-based access control (RBAC) must be implemented granularly, ensuring each user can only access data relevant to their work. A comprehensive audit trail, recording every activity of access, modification, and deletion of data, must be implemented. This system must be able to store logs for at least 5 years, in accordance with best practice recommendations. Implementing the ISO 27001 standard, although not required by SNARS, is highly recommended as a comprehensive information security management framework.

System development must follow a secure system development life cycle (Secure SDLC). This means security is considered from the planning, design, implementation, testing, to maintenance phases. Use a web framework that has strong built-in security features, such as Laravel 11.x with CSRF protection, SQL injection prevention, and XSS filtering features. Conduct penetration testing and vulnerability assessment periodically, at least once a year, by an independent third party to identify and fix security holes before they are exploited. Regularly updating the server operating system (for example Ubuntu Server 22.04 LTS), web server (Nginx 1.24 or Apache 2.4), and database is also crucial to patch known vulnerabilities.

Example Code for Data Integration and Security Implementation

Data integration with the FHIR standard is the core of modern interoperability. The following is a simple example of a GET request to retrieve patient data from a FHIR server, which could be part of your SIMRS integration with SatuSehat or another system. This example uses Node.js with the axios library to make an HTTP request.

// File: fhirClient.jsconst axios = require('axios');class FhirClient {    constructor(baseUrl, accessToken) {        this.baseUrl = baseUrl;        this.headers = {            'Content-Type': 'application/fhir+json',            'Authorization': `Bearer ${accessToken}`        };    }    async getPatientById(patientId) {        try {            const response = await axios.get(`${this.baseUrl}/Patient/${patientId}`, {                headers: this.headers            });            return response.data;        } catch (error) {            console.error(`Error fetching patient ${patientId}:`, error.message);            if (error.response) {                console.error('Response data:', error.response.data);                console.error('Response status:', error.response.status);            }            throw error;        }    }    async searchPatients(queryParameters) {        try {            const queryString = new URLSearchParams(queryParameters).toString();            const response = await axios.get(`${this.baseUrl}/Patient?${queryString}`, {                headers: this.headers            });            return response.data;        } catch (error) {            console.error('Error searching patients:', error.message);            if (error.response) {                console.error('Response data:', error.response.data);                console.error('Response status:', error.response.status);            }            throw error;        }    }}// How to use// const FHIR_BASE_URL = 'https://api-satusehat.kemkes.go.id/fhir-r4/v1'; // Example// const ACCESS_TOKEN = 'YOUR_SATUSEHAT_ACCESS_TOKEN'; // Replace with a valid token// const client = new FhirClient(FHIR_BASE_URL, ACCESS_TOKEN);// (async () => {//     try {//         const patientData = await client.getPatientById('example-patient-id');//         console.log('Fetched Patient:', JSON.stringify(patientData, null, 2));//         const searchResults = await client.searchPatients({ name: 'Budi', birthdate: '1990-01-01' });//         console.log('Search Results:', JSON.stringify(searchResults, null, 2));//     } catch (e) {//         console.error('Operation failed:', e.message);//     }//}();)

The code above shows how to create a basic FHIR client class in Node.js. The getPatientById function will retrieve a Patient resource by its ID, and searchPatients allows searching based on parameters such as name or date of birth. It is important to always include the Authorization header with a valid access token, which is generally obtained through the OAuth 2.0 authentication process. Error handling is also included to provide detailed information if there is a communication problem with the FHIR server. This implementation is highly relevant for integration with SatuSehat, where every resource sent or retrieved must comply with the FHIR R4 specification and proper authorization.

Next, for data security, password hashing is a mandatory basic step. Never store passwords in plaintext form in the database. Use a strong hashing algorithm such as bcrypt. The following is an example implementation of hashing and password verification using Node.js with the bcrypt library.

// File: passwordUtils.jsconst bcrypt = require('bcrypt');const saltRounds = 10; // Standard value, can be adjustedasync function hashPassword(password) {    try {        const salt = await bcrypt.genSalt(saltRounds);        const hashedPassword = await bcrypt.hash(password, salt);        return hashedPassword;    } catch (error) {        console.error('Error hashing password:', error);        throw error;    }}async function comparePassword(password, hashedPassword) {    try {        const match = await bcrypt.compare(password, hashedPassword);        return match;    } catch (error) {        console.error('Error comparing password:', error);        throw error;    }}// How to use// (async () => {//     const userPassword = 'mySecurePassword123!';//     const hashed = await hashPassword(userPassword);//     console.log('Hashed Password:', hashed);//     const isMatch = await comparePassword(userPassword, hashed);//     console.log('Password Match (correct):', isMatch); // Should be true//     const isMismatch = await comparePassword('wrongPassword', hashed);//     console.log('Password Match (incorrect):', isMismatch); // Should be false// })();

This code demonstrates the use of bcrypt to create a secure password hash. saltRounds determines the complexity of hashing; a value of 10 is a good standard. The hashPassword function will produce a unique hash string that cannot be reverse engineered. The comparePassword function is used to verify the password entered by the user at login against the hash stored in the database. Implementing this hashing is very important to meet information security standards in SNARS, protect user credentials from data leaks, and ensure system integrity. This is one of the initial and most fundamental steps in building a secure system.

Case Study: Handling Patient Data and Error Handling

In SIMRS operations, the exchange of accurate and real-time patient data is crucial. Let us take an example of an FHIR R4 payload for the Patient resource that will be sent to SatuSehat or another system. This payload includes basic demographic information of the patient, and compliance with this structure is very important for interoperability.

{  "resourceType": "Patient",  "id": "100000030009",  "meta": {    "profile": [      "https://profile.kemkes.go.id/fhir/r4/StructureDefinition/Patient"    ]  },  "identifier": [    {      "system": "http://terminology.kemkes.go.id/CodeSystem/nik",      "value": "3174070500000001"    },    {      "system": "http://sys-ids.kemkes.go.id/simrs/1.0/identifier",      "value": "P20230001"    }  ],  "active": true,  "name": [    {      "use": "official",      "text": "Budi Santoso",      "family": "Santoso",      "given": [        "Budi"      ]    }  ],  "telecom": [    {      "system": "phone",      "value": "081234567890",      "use": "mobile"    },    {      "system": "email",      "value": "budi.santoso@example.com",      "use": "home"    }  ],  "gender": "male",  "birthDate": "1990-05-20",  "address": [    {      "use": "home",      "line": [        "Jl. Merdeka Raya No. 10"      ],      "city": "Jakarta Pusat",      "postalCode": "10110",      "country": "ID",      "extension": [        {          "url": "https://profile.kemkes.go.id/fhir/r4/StructureDefinition/Provinsi",          "valueCode": "31"        },        {          "url": "https://profile.kemkes.go.id/fhir/r4/StructureDefinition/Kota",          "valueCode": "3174"        },        {          "url": "https://profile.kemkes.go.id/fhir/r4/StructureDefinition/Kecamatan",          "valueCode": "317407"        },        {          "url": "https://profile.kemkes.go.id/fhir/r4/StructureDefinition/Kelurahan",          "valueCode": "31740705000"        }      ]    }  ],  "maritalStatus": {    "coding": [      {        "system": "http://terminology.hl7.org/CodeSystem/v3-MaritalStatus",        "code": "M",        "display": "Married"      }    ]  },  "extension": [    {      "url": "https://profile.kemkes.go.id/fhir/r4/StructureDefinition/BloodType",      "valueCode": "A"    },    {      "url": "https://profile.kemkes.go.id/fhir/r4/StructureDefinition/Citizenship",      "valueCode": "WNI"    }  ]}

The payload above is a representation of patient data for Budi Santoso according to the FHIR R4 standard and the Ministry of Health profile. Every element, from resourceType, id, identifier (including NIK and internal SIMRS ID), name, gender, birthDate, to address with administrative area code extensions, must be filled in correctly. Failure to comply with this structure can cause data rejection by the receiving server, which has a direct impact on the smoothness of services and SNARS compliance.

An example of an error scenario that often occurs is when SIMRS tries to send patient data to SatuSehat without proper authorization or with an invalid payload. You might receive an error response like this:

HTTP/1.1 401 UnauthorizedContent-Type: application/json{  "resourceType": "OperationOutcome",  "issue": [    {      "severity": "error",      "code": "security",      "details": {        "text": "Invalid or expired access token provided in Authorization header."      },      "diagnostics": "Authentication failed. Please check your access token."    }  ]}

This 401 Unauthorized error clearly indicates a problem with the access token being used. To handle it, the IT team must have mechanisms to: (1) Monitor API error logs in real-time. (2) Implement an automatic token refresh process if the token is nearing expiration or if an authorization error occurs. (3) Provide notifications to IT administrators if authorization problems recur. (4) Ensure the credential configuration (client ID, client secret) for obtaining the initial token is correct and stored securely (for example in environment variables or a vault system). This proactive error handling is very important to ensure the continuity of patient data transmission, which is an integral part of the SNARS MIRM and ARK standards.

Best Practices for Hospital IT Teams in SNARS Accreditation

  1. Conduct Internal IT Audits and SNARS Gap Analysis Periodically: Identify gaps between current IT conditions and the requirements of SNARS Ed. 1.1 or the latest version. Use the KARS checklist and PMK related to EMR to ensure every aspect is covered, such as PMK No. 24 of 2022 concerning Medical Records.
  2. Implement a Comprehensive Information Security Policy: Develop and implement a data security policy that covers access control, encryption, security incident management, and security awareness training for all staff. Ensure this policy aligns with international standards such as ISO 27001 and personal data protection regulations.
  3. Build a Robust Backup and Disaster Recovery (DRP) System: Patient data is the most valuable asset. Ensure there is a regular data backup strategy (daily or real-time for critical data) and a DRP that is tested periodically, with clearly defined recovery time objectives (RTO) and recovery point objectives (RPO).
  4. Prioritize System Integration with Open Standards (HL7/FHIR): Avoid data silos by adopting interoperability standards such as HL7 v2.5.1 and FHIR R4. This is crucial for efficient data exchange between SIMRS modules and with the national health ecosystem such as SatuSehat.
  5. Implement Continuous System and Performance Monitoring: Use monitoring tools such as Prometheus, Grafana, or the ELK stack to monitor SIMRS performance, server resource usage, and potential security anomalies. Monitor system availability (uptime) and API response time in real-time.
  6. Document All IT Policies and Procedures: Every process, configuration, system architecture, and security policy must be documented neatly and easily accessible. This documentation is important evidence during accreditation surveys, showing that the hospital has good IT governance.
  7. Facilitate Close Collaboration between IT and Clinical Teams: IT cannot work alone. Involve doctors, nurses, and other clinical staff in system design and testing to ensure IT solutions truly support clinical workflows and improve patient safety.
  8. Invest in Training and Certification for the IT Team: Improve your IT team's competence in cybersecurity, health data interoperability (FHIR Certified Professional), and SIMRS management. A competent team is an invaluable asset in maintaining compliance and innovation.

FAQ

  1. Q: What SNARS standards are most directly related to IT?

    A: The SNARS standards most relevant to IT include Chapter MIRM (Management of Information and Medical Records), which focuses on EMR and information security, Chapter MFK (Facility and Safety Management), which covers IT risk management and system continuity, Chapter ARK (Access to Services and Continuity of Services), which discusses patient data integration, and Chapter HPK (Patient and Family Rights), which highlights data privacy and confidentiality. Compliance with the points in these chapters depends heavily on the capabilities of the hospital's IT systems.

  2. Q: How does a modern SIMRS help hospitals meet SNARS electronic medical record (EMR) standards?

    A: A modern SIMRS that complies with SNARS must provide comprehensive EMR features, from patient registration, medical history recording, laboratory results, radiology, to electronic prescriptions. This system must ensure the completeness, accuracy, and real-time availability of data, and support coding standards (for example ICD-10, SNOMED CT) to facilitate interoperability and data analysis. In addition, audit trail features and granular access control are very important to meet the security and confidentiality aspects of EMR data.

  3. Q: How important is SatuSehat integration for SNARS accreditation?

    A: Integration with the SatuSehat platform is very important and will become mandatory. Although SNARS Ed. 1.1 does not yet explicitly mention "SatuSehat", the MIRM 1.2 standard on data interoperability and PMK No. 24 of 2022 concerning EMR clearly mandates the electronic exchange of health data. Readiness for integration with SatuSehat using FHIR R4 will be strong evidence of the hospital's compliance with the spirit of interoperability and government regulations, demonstrating commitment to the national health ecosystem.

  4. Q: How can patient data security be ensured in accordance with SNARS requirements?

    A: To ensure patient data security, the IT team must implement multiple layers of protection. This includes data encryption in transit (TLS 1.2/1.3) and at rest, strict role-based access control (RBAC), implementation of firewalls and IDS/IPS, as well as regular system updates. In addition, documented information security policies, staff training, and periodic security audits (penetration testing) are crucial steps to protect data from unauthorized access and cyber threats, in line with the MFK standards.

  5. Q: What is IT's role in risk management and data security incidents according to SNARS?

    A: IT plays a central role in risk management by identifying, assessing, and mitigating data security risks. This includes conducting vulnerability assessments, implementing security controls, and developing incident response plans. When a security incident occurs, the IT team is responsible for detecting, responding to, recovering from, and analyzing the incident to prevent similar occurrences in the future, in accordance with the MFK 5.1 and MFK 7.1 standards, which emphasize risk management and security management programs.

  6. Q: How often should the IT team conduct internal audits for SNARS accreditation preparation?

    A: Ideally, the IT team should conduct internal audits and gap analyses against SNARS standards at least once a year, or more frequently if there are significant changes to systems or regulations. These audits should include a review of policies, procedures, system configurations, security logs, and compliance with interoperability standards. The audit results must be documented and followed up with a clear improvement plan, ensuring the hospital is always ready for an external accreditation survey.

Preparing for SNARS accreditation does require dedication and in-depth understanding, especially in this digital era where IT's role is increasingly central. From implementing EMR that complies with MIRM standards, maintaining patient data security in accordance with HPK and MFK, to data integration with SatuSehat using FHIR R4, every aspect of IT must be planned and executed carefully. Do not let technological complexity hinder your hospital's journey toward prime accreditation. With the right strategy, the use of the latest technology, and a competent team, you can not only meet SNARS standards but also improve operational efficiency and overall service quality. If your hospital or clinic needs further consultation regarding SIMRS, SatuSehat integration, or the development of custom IT solutions that comply with SNARS, do not hesitate to contact Nugroho Setiawan. We are ready to help you build a strong and sustainable IT foundation.

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