KISIM Administrative Implementation Guide
1.0.0 - release CH

KISIM Administrative Implementation Guide - Local Development build (v1.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

KISIM CareTeam

KISIM CareTeam representing external and internal hospital care teams.

KISIM Practitioner

KISIM-adapted practitioner profile with GLN/ZSR support and DispatchType extension.

Structures: Data Type Profiles

These define constraints on FHIR data types for systems conforming to this implementation guide.

Gepart Identifier

Identifier holding the GEPART - Geschaeftspartner - Number

KISIM Loginame Identifier

Identifier holding the KISIM login name

Personal number Identifier

Identifier holding the KISIM user person number as hospital employee

Visum Identifier

Identifier holding the KISIM user visum

Structures: Extension Definitions

These define constraints on FHIR data types for systems conforming to this implementation guide.

Practitioner dispatch type

Prefered channel for communication with the practitioner.

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

CareTeam category

ValueSet for CareTeam.category: internal or external.

CareTeam participant roles

Combined ValueSet of internal and external roles. Open to additional customer roles.

Practitioner dispatch type

Values for dispatch type.

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

CareTeam category

Category of the CareTeam: internal or external.

CareTeam external roles

External roles, as fragments. Can get extented; Codes can also occur in resources without a code system.

CareTeam internal roles

Internal roles (KIS/customers), fragmentary. Can be expanded; codes may also occur in resources without a code system.

Practitioner dispatch type

Represents prefered channels for contacting a practitioner: POST, FAX, EMAIL.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

External CareTeam example

External CareTeam with referring and follow-up physicians.

External CareTeam with custom roles

External CareTeam with two customer-specific participant roles not in the code system.

Internal CareTeam example

Internal CareTeam with two internal physicians.

Internal CareTeam with custom role

Internal CareTeam with a custom participant role not included in the code system.

Practitioner-GEPART-F5803C94
Practitioner-USER-CISDRICH