CH ALIS Connect (R4), published by ALIS-Connect. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7ch/ch-alis-connect/ and changes regularly. See the Directory of published versions
| Official URL: http://fhir.ch/ig/ch-alis-connect/ImplementationGuide/ch.fhir.ig.ch-alis-connect | Version: 1.0.0-ballot | ||||
| Active as of 2026-06-12 | Computable Name: CH_ALIS_CONNECT | ||||
Copyright/Legal: CC0-1.0 |
|||||
This Implementation Guide is provided to define a Mapping between the HL7 FHIR®© standard and the ALIS XML 5.1 standard provided by ALIS Connect. For over 20 years, ALIS-Connect has represented for a reliable and standardized exchange of medical service data. The established interface standard ensures interoperability, security and efficiency in digital healthcare. Supported by a committed network of experts, ALIS-Connect stands for binding standardization and certified quality. The certification ensures that software solutions are correctly integrated and continuously developed further.
ALIS is an XML-based standard interface for the electronic transmission of services between IT systems in the hospital and healthcare sector. It supports in particular the data exchange between service-recording, clinical, radiology and other specialist systems on one side and billing systems on the other. In addition, ALIS enables the structured transmission of coding data according to the differing requirements of service providers, insurers and public authorities. In a file-based exchange, one or more Visits are documented, each grouping the patient case together with its individual services.
ALIS 5.1 supports TARDOC and outpatient flat rates (ambulante Pauschalen), the national outpatient tariffs managed by OAAT-OTMA AG (Organisation ambulante Arzttarife / Organisation des tarifs médicaux ambulatoires), the organization responsible for maintaining and further developing these tariffs. The version enables the transmission of additional information required for the correct tariff representation and billing. This includes diagnosis information at the level of the individual service, session information according to Annex B of the tariff, and the assignment of laboratory, pathology or report services in line with the tariff agreement. ALIS 5.1 thereby establishes the basis for representing the extended requirements of TARDOC and outpatient flat rates in a standardized, traceable and interoperable way between the participating systems.
HL7 FHIR provides a dedicated set of financial and administrative resources for representing billing and accounting information, such as Account, Invoice, Claim and ChargeItem. Among these, the ChargeItem resource fits closest to the information contained in a service within an ALIS Visit: it describes a single billable item — the service that was performed, the products and codes involved, the quantity and the context (patient, encounter and performer) — and is intended to be aggregated for subsequent billing. For this reason the mapping in this guide centers on ChargeItem, where each ALIS service of a Visit is represented as one ChargeItem, transmitted together within a single transaction Bundle (see Mapping).
This implementation guide is under informative ballot by HL7 Switzerland until September 30th, 2026 midnight. Please add your feedback via the ‘Propose a change’-link in the footer on the page where you have comments.
Download: You can download this implementation guide in npm format from here.
This document presents ALIS-connect use concepts defined via FHIR processable artefacts:
This implementation guide is managed by ALIS-Connect.
This guide is the product of collaborative work undertaken with participants from:
This document is licensed under Creative Commons "No Rights Reserved" (CC0).
HL7®, HEALTH LEVEL SEVEN®, FHIR® and the FHIR
® are trademarks owned by Health Level Seven International, registered with the United States Patent and Trademark Office.
This implementation guide contains and references intellectual property owned by third parties ("Third Party IP"). Acceptance of these License Terms does not grant any rights with respect to Third Party IP. The licensee alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize Third Party IP in connection with the specification or otherwise.
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 (ch.fhir.ig.ch-alis-connect.r4) and R4B (ch.fhir.ig.ch-alis-connect.r4b) are available.
| IG | Package | FHIR | Comment |
|---|---|---|---|
| ch.fhir.ig.ch-alis-connect#1.0.0-ballot | R4 | ||
| hl7.terminology.r4#7.4.0 | R4 | Automatically added as a dependency - all IGs depend on HL7 Terminology | |
| hl7.fhir.uv.extensions.r4#5.3.0 | R4 | Automatically added as a dependency - all IGs depend on the HL7 Extension Pack | |
| hl7.terminology.r4#7.1.0 | R4 | ||
| hl7.fhir.uv.extensions.r4#5.2.0 | R4 | ||
| ch.fhir.ig.ch-core#7.0.0-ballot | R4 | ||
| hl7.fhir.uv.xver-r5.r4#0.1.0 | R4 | ||
| hl7.fhir.uv.tools.r4#1.3.0 | 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.extensions.r4#5.3.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, May 16, 2026 18:32+1000+10:00) |
Package hl7.fhir.uv.xver-r5.r4#0.1.0 Extensions for Using Data Elements from FHIR R5 in FHIR R4 (built Fri, Mar 20, 2026 15:40+1100+11:00) |
Package ch.fhir.ig.ch-core#7.0.0-ballot FHIR implementation guide CH Core (built Wed, Jun 10, 2026 14:59+0000+00:00) |
Package hl7.fhir.uv.tools.r4#1.3.0 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 Tue, Oct 6, 2026 15:55+1100+11:00) |