LTT Implementation Guide, published by Kommunernes Landsforening. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7dk/kl-ltt/ and changes regularly. See the Directory of published versions

Home

Official URL: http://fhir.kl.dk/ltt/ImplementationGuide/kl.dk.fhir.ltt				Version: 1.0.0
Active as of 2025-08-31				Computable Name: LTT

LTT - KL Lettilgængeligt tilbud

This implementation guide describes the delivery of LTT data to KL Gateway. The data originates from the documentation on the activity in LTT in the Danish municipalities. The reporting aims for compliance with the Danish core profiles.

The profiles for the reporting are restricted to allow only the information that is required to report to KL Gateway.

Overview

The data is reported as a collection of instances. A report contain instances that conforms to the profiles defined in this implementation guide. See figure below.

In addition to being structured as a report, relationships exist between the profiles. These are illustrated in the UML Class Diagram in the figure below.

The Class diagram shows that CarePlan, Encounter and Referral are all associated with Citizen i.e. these profiles know which Citizen they hold information about. The Encounter and Referral are also associated with the CarePlan.

The Citizen profile inherit from dk-core, even though it is not illustrated specifically in the Class Diagram.

Special constraints, and resulting reporting practises

Whereas the report may seem unconstrained, each profile define constraints on attributes, datatypes and cardinalities. See descriptions below.

Citizen

Information about the citizens that are the subjects of the report. This resource is used to get a reference to the child or youth.

Attributes

• civil registration number (CPR-nr).
• identification of the municipality holding and reporting the data.
• a FHIR status attribute used to report errors.

Validation

• One and only one civil registration number exists, and is a syntactically valid CPR-nr.
• One and only one managing organization exists, and is a syntactically valid SOR code (only code length is currently validated in the profile, but the authorization validates the actual SOR code).
• One FHIR status may exist, and should be selected from the standard ValueSet.

CarePlan

This model contains information about the treatment pathway from the child’s or youths first encounter with the municipality concerning LTT.

Attributes

• A start time.
• An end time.
• A code that decribes which care plan it is.
• A reference to the Citizen instance that holds the child or youth's information.
• A reasonCode that describe the focus area which is the reason for the care plan and encounters.
• Three FHIR status attributes (status, intent, activity.detail.status).

Validation

• One and only one code exists and should be selected from a specific ValueSet.
• One and only one start time.
• One and only one reference to the Citizen exists.
• The reasonCode is optional. If present, it should be selected from a specific ValueSet. It is allowed to have more than one reasonCode.
• The FHIR status attributes are mandatory, and should be selected from the standard FHIR ValueSet.

Encounter

Information about when a child or youth have an encounter such as screenings, prelimerary interviews, treatments, etc. in a Danish municipality context.

Attributes

• Type of encounter. The attribute describe which encounter is delivered using a code.
• Encounter class. The attribute holds a code which describe the place of delivery.
• The encounter start time.
• A reference to the Citizen instance that holds the child or youth's information.
• A FHIR status attribute.
• The participant of the encounter. It can be the child or youth itself or its parents.
• A delivery type code that express whether the encounter is delivered in a group or individually.
• A reference to the CarePlan instance the Encounter is a part of.

Validation

• One and only one encounter type exists, and should be selected from a specific ValueSet, no other codes may be reported.
• One and only one encounter class exists, and should be selected from a specific ValueSet.
• One and only one encounter start time exists.
• One and only one reference to the Citizen exists.
• One and only one reference to the CarePlan exists.
• One and only one FHIR status exists, and should be selected from the standard FHIR ValueSet.
• One delivery type code, which should be selected from a specific ValueSet, may exist.
• One participant code, which should be selected from a specific ValueSet, may exist.

Referral

Referrals in this context are informal recommendations to other parties, such as the child’s or youth’s general practitioner, a §126a service in another municipality, and similar instances.

Attributes

• A code indicating which service the citizen is being referred to.
• A start time.
• A reference to the Citizen instance that holds the child or youth's information.
• A reference to the CarePlan instance that this referral is a part of.
• Three FHIR status attributes (status, intent, activity.detail.status).

Validation

• One and only one code is mandatory and should be selected from the specified ValueSet.
• One and only one start time.
• One and only one reference to the Citizen exists.
• One and only one reference to the CarePlan exists.
• The FHIR status attributes are mandatory, and should be selected from the standard FHIR ValueSet. activity.detail.status must be set to 'completed'.

Dependencies

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.1.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, Apr 27, 2024 18:39+1000+10:00)

Package hl7.fhir.uv.pocd#0.3.0 ImplementationGuide for Point-of-Care Devices (PoCD), such as those typically found in a hospital care setting (e.g., physiological monitors, infusion pumps, ventilators, pulse-oximeters, etc.). (built Sat, Aug 14, 2021 20:37+0000+00:00)

Package hl7.fhir.uv.phd#1.1.0 ImplementationGuide for Personal Health Devices (PHD), used in remote patient monitoring (e.g., weight scales, blood pressure cuffs, glucose monitors, pulse-oximeters, etc.). (built Fri, Oct 18, 2024 13:22+0000+00:00)

Package hl7.fhir.uv.ipa#1.0.0 This IG describes how an application acting on behalf of a patient can access information about the patient from an clinical records system using a FHIR based API. The clinical records system may be supporting a clinical care provider (e.g. a hospital, or a general practitioner), or a health data exchange, including a national health record system. (built Sun, Mar 26, 2023 20:50+0000+00:00)

Package hl7.fhir.dk.core#3.4.0 A FHIR Implementation Guide for the Danish common needs across healthcare sectors (built Sat, Feb 1, 2025 19:18+0100+01: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)

Cross Version Analysis

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 (kl.dk.fhir.ltt.r4) and R4B (kl.dk.fhir.ltt.r4b) are available.

Global Profiles

There are no Global profiles defined

IP Statements

This publication includes IP covered under the following statements.

• This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
  Show Usage
  • ActCode: Bundle/DeliveryReport-Josefine-2, Bundle/DeliveryReport-Josefine-3... Show 7 more, Bundle/DeliveryReport-Josefine-4, Bundle/DeliveryReport-Josefine-5-6-7, Bundle/DeliveryReport-Josefine-8, Bundle/RapportOmJosefine, Encounter/Behandlingskontakt, EncounterClassCodes and KLGatewayLTTEncounter