Finnish Scheduling
2.0.0-rc3 - ballot

Publication Build: This will be filled in by the publication tooling

## ConceptMap: Ajanvarauksen tila to Appointment status

Official URL: https://hl7.fi/fhir/finnish-scheduling/ConceptMap/ajanvarauksentila-appointmentstatus | Version: 2.0.0-rc3
Draft as of 2025-08-27 | Computable Name: FiAppointmentStatusCodeMap

Mapping between the Finnish logical model Ajanvaraus - Ajanvarauksen tila (oid `1.2.246.537.6.881`) and FHIR Appointment status codes.

Note: the codes are ordered according to the sequence (järjestys) indicated in the Finnish logical model. This ordering is different from the numeric order of the codes.

Mapping from https://koodistopalvelu.kanta.fi/codeserver/pages/classification-view-page.xhtml?classificationKey=1943 to AppointmentStatus

Group 1 Mapping from `https://koodistopalvelu.kanta.fi/codeserver/pages/classification-view-page.xhtml?classificationKey=1943` to AppointmentStatus

Source Code | Relationship | Target Code | Comment
1 (Suunniteltu) | is equivalent to | waitlist (Waitlisted) | Patient and need have been identified, the service provider and time have not.
2 (Tilattu) | is equivalent to | proposed | Differs from Suunniteltu in that in Tilattu the service provider has been identified.
8 (Ehdotettu) | is equal to | pending |
3 (Varattu) | is equal to | booked |
4 (Peruttu) | is equal to | cancelled |
5 (Siirretty) | maps to wider concept | cancelled | There is no separate status code in FHIR for rescheduled appointments. Note that this code is deprecated.
10 (Ilmoittautunut) | is equal to | checked-in |
6 (Alkanut) | maps to wider concept | fulfilled | Alkanut means that the encounter has begun and is ongoing. Most FHIR systems track this with the Encounter resource. There is no such state in Appointment.
7 (Toteutunut) | maps to wider concept | fulfilled | Toteutunut means that the service the appointment is for has started or is complete. Most FHIR systems track this with the Encounter resource. There is no such state in Appointment.
9 (Saapumatta) | is equal to | noshow |

### Notes:

The Finnish logical model for appointments includes a code set for appointment statuses that differs from the FHIR Appointment.status values.

The Finnish logical model is more detailed when the service is being planned, and separates between states where the need fo a service has been identified but no service provider has yet been identified (#1, Suunniteltu), and when the service provider has been selected (#2, Tilattu).

The FHIR specification uses the Appoinment resource to track information on scheduling and for administrative purposes, and in general for prepapring for the encounter. In FHIR, the Encounter resource is used to track the encounter, and any clinically relevant information (see Appointment Statuses and Encounters). In FHIR, when an encounter starts, its status is tracked with the Encounter resource, and no longer with the Appointment. The Finnish logical model does not make such a distinction between the appointment and the encounter.

The Finnish logical model does not have a separate status for when the patient has arrived (FHIR status arrived). It does have a code #10, Ilmoittautunut that matches the FHIR code checked-in.

On the other hand, the Finnish logical model separates between when an encounter has started (#6, Alkanut) and when the service is in progress or completed (#7, Toteutunut).

The Finnish logical model used to have a separate code for an appointment that has been rescheduled (#5, Siirretty), but that code is now deprecated.

The Finnish logical model does not have any code for appointments that have been entered in error.

The Ajanvarauksen tila codes can be added using the Ajanvarauksen tila extension to `Appoinment.status`.