Why ROCOM Security & Safety
The Standard — Parts
Part 1 — Overview & Scope Part 1 — Architecture Reference Model Part 2 — Conformance Part 2 — Service Levels L0–L3 Part 5 — Transport Profile
Supplements
All Supplements Sup-001 — Orchestrator API Annex A — Engineering Practice Sup-003 — BMS Infrastructure
Reference
Principles & Architecture Specification Modules (YAML) Changes
About
Governance Contribution Process
Action
Get Started

Rocom Governance

Contents

Rocom Governance

Ownership

The Rocom specification is owned by ROCOM (CVR 46774043), an independent Danish non-profit association established September 2026. ROCOM holds the specification, domain (rocom.org), and word mark in the interest of the standard and its users.

Tech Happens Europe ApS (Odense, Denmark) participates as an organizational member and provides secretariat services. Tech Happens is not the owner — ROCOM is.

Board of Directors

ROCOM is governed by a Board of Directors. The Board:

Board membership is public. Nomination and selection criteria are published as a Supplement.

Secretariat

Day-to-day specification maintenance is handled by the secretariat (Tech Happens Europe ApS) under Board oversight. The secretariat is responsible for:

The secretariat does not make certification decisions.

Certification Program

The Certification Program verifies that an implementation conforms to the declared conformance level. Certification is:

Independent certification. Formal certification is performed by independent ICT providers with ISO 27001 competence, selected under Board oversight per Sup-005 (Certification Provider Requirements). The secretariat and its members do not certify their own implementations.

Transition period. Until the Board has appointed independent Certification Providers, the secretariat maintains the test suite and conformance infrastructure. Self-declaration of conformance remains available during this period.

Stewardship Principles

  1. Owned by ROCOM. The specification, domain, and word mark are owned by the ROCOM association. The certification program is overseen by the Board.

  2. Vendor neutrality. The specification MUST NOT contain language that advantages or disadvantages any specific vendor, product, or national scheme. Implementations are examples, not requirements.

  3. Transparent process. All changes to normative text follow the Edition / Supplement / Correction Proposal process defined in CONTRIBUTING.md. No changes are made outside this process.

  4. Open participation. Any organization or individual may propose changes via the CONTRIBUTING process. Proposals are reviewed on technical merit, not on the proposer’s relationship to the steward.

  5. Dual licensing. Specifications are licensed CC-BY 4.0. Code and reference implementations are licensed Apache 2.0. See LICENSE-SPEC and LICENSE-CODE.

Advisory Board

An Advisory Board of independent experts from healthcare IT, robotics, and standards organizations provides input on:

Advisory Board membership will be public. The Board is not yet constituted (Edition 2026a draft).

Funding

The secretariat seeks foundation and public grant support for the development of the specification; no external funding has been received to date. Funding sources will not influence specification content.

Contact

ROCOM · c/o Tech Happens Europe ApS Aarestrupsvej 22, 5230 Odense M, Denmark Phone: +45 22 54 01 30

For conformance inquiries, certification applications, or governance questions: specs@techhappens.eu

Rocom Specification © 2026 ROCOM (CVR 46774043) · Licensed under CC-BY 4.0