Funktionsaccount · BPMN Core Execution

One service address. Clear ownership of every response.

A functional account represents a service, not a person. Discover the distinction between staff-managed and automated identities, and inspect a controlled journey from request to approval and delivery evidence.

Contact types

Account type is not a user permission.

FHIR VZD Endpoint connection types identify the contact. They do not grant staff roles or authorize a message send.

tim

Individual

A personal TI-M identity. The user and device security boundary remain explicit.

tim-fa

Staff-managed functional account

An organizational endpoint with individual employee authorization and a traceable responder.

tim-bot

Automated contact / chatbot

A separately labelled automated account; bot recognition and permitted operating purpose are mandatory design concerns.

Source baseline: gemSpec_TI-M_Pro 1.2.0 (including A_25546, A_25547 and A_25553). Exact applicability depends on the approved release. Official specification ↗

Interactive process model

From a request to a controlled TI-M outcome.

Synthetic example: account ownership, approval and Matrix evidence form three distinct decisions. No TI-M account, BPMN engine, AI model or external server is contacted.

01

Request

A synthetic member request reaches the organization’s published contact identity.

02

Identity & scope

ConnectionType, healthcare purpose, staff access and account owner are checked.

03

BPMN case

A workflow revision assigns the case, required checks and responsible staff member.

04

Assistance (optional)

AI may suggest an answer but cannot access E2EE keys or publish a TI-M message.

05

Human approval

An authorized reviewer approves a recipient-bound, immutable message revision.

06

TI-M dispatch

The sender validates approval again, writes a durable intent and attempts an authorized send.

07

Evidence & recovery

A homeserver acknowledgement is not a recipient read receipt; ambiguous sends require reconciliation.

Trust & responsibility

The service identity does not erase human accountability.

01

Host & employees

Named staff role, authorization epoch and auditable review of each outgoing message.

02

BPMN Core Execution

Process revision, business case, durable approval intent and recovery without blind resending.

03

Headless module

A local module interface; any separately authorized network gateway belongs to the integrating system.

04

Data and E2EE

If a trusted service decrypts/re-encrypts between separate rooms, this is not continuous end-to-end encryption between the outside participant and an employee.

Normative gate

No cross-room forwarding is activated in this demonstration. The intended purpose and the Provider’s permitted integration and bridging boundaries must be assessed before implementation or publication.

Evaluate a controlled communication workflow.

Agree the organization, purpose, account type, access roles and admissible operating model before a pilot.

Discuss scenario →