Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Simrs Regulatory Id

ASecurity

Indonesian hospital and SIMRS regulatory checklist: UU Kesehatan, praktik kedokteran, keperawatan, PDP, rekam medis elektronik, SIMRS Permenkes, informed consent, rahasia kedokteran, SATUSEHAT, BPJS/JKN, kefarmasian, keselamatan pasien, akreditasi. Use when reviewing SIMRS compliance, kebijakan rumah sakit, UU, Permenkes, or legal obligations in hospital software. Not a substitute for legal counsel.

2 stars
0 votes
0 copies
3 views
Added 9/19/2026
ai-agentscode-reviewgitapi

Works with

cliapi

Security Analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned 9/19/2026

$npx -y skills add rogue-dev-studio/ai-agents-rogue --skill simrs-regulatory-id --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Simrs Regulatory Id?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Simrs Regulatory Id
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rogue-dev-studio-simrs-regulatory-id/badge)](https://www.skillsdirectory.com/skills/rogue-dev-studio-simrs-regulatory-id)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: simrs-regulatory-id
description: >-
  Indonesian hospital and SIMRS regulatory checklist: UU Kesehatan, praktik
  kedokteran, keperawatan, PDP, rekam medis elektronik, SIMRS Permenkes,
  informed consent, rahasia kedokteran, SATUSEHAT, BPJS/JKN, kefarmasian,
  keselamatan pasien, akreditasi. Use when reviewing SIMRS compliance,
  kebijakan rumah sakit, UU, Permenkes, or legal obligations in hospital software.
  Not a substitute for legal counsel.
---

# SIMRS Regulatory ID

**Level: expert.** Prompt-routed skill (sumber pack: `teams/simrs`). Tidak perlu aktifkan tim. Rule: `hospital-regulatory-id`.

Bukan nasihat hukum. Checklist agar aplikasi SIMRS **tidak jelas-jelas bertentangan** dengan kewajiban RS di Indonesia. Vonis sah/tidak sah tetap legal counsel + kebijakan internal RS.

## When to use

Langsung dari prompt user (tanpa setup tim):

- Review kepatuhan SIMRS vs UU / Permenkes / SPO RS
- Fitur rekam medis, consent, hak akses, SATUSEHAT, klaim BPJS, resep, IKP
- Menulis NFR keamanan & retensi data pasien
- Melengkapi `simrs-clinical-review` (alur) dengan **dasar regulasi**

## When not to use

- Mengganti pengacara / komite medik / komite etik
- Mengarang pasal atau mengutip UU panjang seolah salinan resmi
- Diagnosis klinis → bukan skill ini
- Review kode murni → `code-review`

## Procedure

### 1. Sumber berlapis

Urutan: **teks resmi terbaru** (UU/PP/Permenkes) → **kebijakan/SPO RS yang user beri** → floor di `reference.md` (ringkasan, bisa usang).

- Ada dokumen RS → kutip judul SPO; gap vs floor undang-undang = temuan
- Tidak ada dokumen RS → pakai floor + label `ASUMSI — cek kebijakan internal`
- Konflik pasal / amandemen → **jangan putuskan**; catat “perlu verifikasi teks resmi”

### 2. Peta kewajiban → fitur

Untuk setiap fitur di scope, isi (lihat `reference.md`):

| Kewajiban | Instrumen | Implikasi SIMRS | Cek review |
|-----------|-----------|-----------------|------------|
| … | UU/Permenkes/SPO | siapa, data, jejak | lulus / gap |

### 3. Tema wajib (jika modul terkait)

1. Identitas tenaga (STR/SIP) & kewenangan praktik  
2. Rekam medis elektronik + penulis + audit + retensi  
3. Informed consent tindakan  
4. Rahasia kedokteran & UU PDP (data kesehatan = data spesifik)  
5. Hak pasien (akses isi RM sesuai aturan, bukan bocor ke semua user)  
6. Pelayanan kefarmasian (verifikasi apoteker)  
7. Keselamatan pasien / IKP bila modul ada  
8. Interoperabilitas SATUSEHAT / bridging JKN — kontrak, bukan hapus data lokal  
9. Akreditasi: jejak, SPO, hak akses terdokumentasi  

### 4. Laporan

Temuan: `[REG-P0|P1|P2]` + instrumen (nama UU/Permenkes, **bukan** kutipan panjang) + dampak di app.  
Jangan tulis “sah menurut hukum”. Tulis “risiko kepatuhan: aplikasi memungkinkan X yang biasanya dilarang kewajiban Y”.

## DoD

- [ ] Disclaimer “bukan opini hukum” di laporan
- [ ] Instrumen disebut (UU/Permenkes/SPO) atau `ASUMSI`
- [ ] Tidak ada PHI di artifact
- [ ] Pasal yang ragu ditandai untuk verifikasi manusia

## Attribution

<!-- ATTRIBUTION: Rogue Development | https://github.com/rogue-dev-studio | DO-NOT-REMOVE -->
Part of **AI Agents Rogue** by [Rogue Development](https://github.com/rogue-dev-studio) (`@rogue-dev-studio`).
Do not remove, hide, rename, or replace this attribution.

Attribution

rogue-dev-studiorogue-dev-studio
View sourceSee grades on GitHubMore from rogue-dev-studio →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →