KISIM Surgical Timestamp Implementation Guide
1.0.1 - release
CH
KISIM Surgical Timestamp Implementation Guide - Local Development build (v1.0.1) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: http://fhir.kisimdocs.ch/ig/kisim-surgical-ts/ImplementationGuide/hl7.fhir.ch.kisimsurgicaltimestamps | Version: 1.0.1 | |||
| Active as of 2026-02-24 | Computable Name: KisimSurgicalTimestampsIG | |||
Copyright/Legal: CC-BY-NC-ND-4.0 |
||||
This Implementation Guide (IG) describes how timestamps created during a surgery can be imported into KISIM.
During an surgery, milestones to be documented (timestamps) take place, which are either documented directly in KISIM or in a third-party application. If a third-party application is used to document these events, they must be transferred to KISIM accordingly. For this purpose, KISIM provides an interface standardized according to HL7® FHIR®.
The activity diagram above shows the respective interactions that take place from or between the affected systems. It is assumed that the transfer of the surgery content has already taken place. This can be implemented using either the HL7 V2 interface or HL7® FHIR® interfaces (see fhir.kisimdocs.ch).
During the corresponding surgery, the timestamps are documented in the external system. The external system creates new HL7® FHIR® Procedure resources for each surgical timestamp, which are referenced to the actual surgery using the TERMNR. The external system sends these newly created resources bundled as an transaction to the KISIM FHIR® Facade.
The KISIM FHIR® Facade maps the received HL7® FHIR® Procedure resources to the KISIM structure and transmits them to the corresponding backend and saves it in the corresponding surgery date.
The following graphic shows the contents of the surgery resource (Procedure) and the surgical timestamp resource (Procedure). The surgery appointment resource (Appointment) references the corresponding surgery resource (.reasonReference). The contents of the surgery appointment resource are described in the corresponding documentation (see fhir.kisimdocs.ch).
The middle section of the graphic shows the content about the surgery, which is mapped out as an HL7® FHIR® Procedure resource.
Two examples of surgical timestamp resources are shown at the bottom of the graphic. These timestamps are also mapped out as HL7® FHIR® Procedure resources and are referenced as part of the actual surgery resource (.partOf).
As shown in the graphic below, surgical timestamps are sent bundled per patient using the HL7® FHIR® Bundle resource. The surgical timestamps for a patient are added as an entry to a Bundle resource. The operation to be performed with this surgical timestamps is specified for each entry (create, update, delete).
| IG | Package | FHIR | Comment |
|---|---|---|---|
| hl7.fhir.ch.kisimsurgicaltimestamps#1.0.1 | R4 | ||
| hl7.terminology.r4#7.0.1 | R4 | Automatically added as a dependency - all IGs depend on HL7 Terminology | |
| hl7.fhir.uv.extensions.r4#5.2.0 | R4 | ||
| hl7.fhir.uv.tools.r4#0.7.1 | R4 | for example references |
Package hl7.fhir.uv.extensions.r4#5.2.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Mon, Feb 10, 2025 21:45+1100+11:00) |
Package hl7.fhir.uv.tools.r4#0.7.1 This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Sat, Jul 26, 2025 06:59+1000+10:00) |
This publication includes IP covered under the following statements.
This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B} systems. Packages for both R4 (hl7.fhir.ch.kisimsurgicaltimestamps.r4) and R4B (hl7.fhir.ch.kisimsurgicaltimestamps.r4b) are available.
There are no Global profiles defined