Finnish Scheduling
0.2.0-cibuild - ci-build Finland flag

Finnish Scheduling, published by HL7 Finland. This guide is not an authorized publication; it is the continuous build for version 0.2.0-cibuild built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/fhir-fi/finnish-scheduling/ and changes regularly. See the Directory of published versions

ConceptMap: Ajanvarauksen tila to Appointment status

Official URL: https://hl7.fi/fhir/finnish-scheduling/ConceptMap/ajanvarauksentila-appointmentstatus Version: 0.2.0-cibuild
Draft as of 2024-10-09 Computable Name: FiAppointmentStatusCodeMap

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

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 the Encounter resource to track any clinically relevant information (see Appointment Statuses and Encounters). In FHIR, when an encounter starts, its state is tracked with the Encounter resource, and no longer with the Appointment.

The Finnish logical model does not make such a distinction. The same value set records states for when the encounter has started (#6, Alkanut) and when the service is in progress or completed (#7, Toteutunut).

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

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.

Generated Narrative: ConceptMap ajanvarauksentila-appointmentstatus

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 Concept DetailsRelationshipTarget Concept DetailsCommentProperties
Codes from https://koodistopalvelu.kanta.fi/codeserver/pages/classification-view-page.xhtml?classificationKey=1943Codes from AppointmentStatus
1Suunniteltuis equivalent towaitlistWaitlistedIn FHIR there is no distinction between Suunniteltu and Tilattu. The distinction is that in Tilattu the service provider has been identified.
2Tilattumaps to wider conceptwaitlistWaitlistedIn FHIR there is no distinction between Suunniteltu and Tilattu. The distinction is that in Tilattu the service provider has been identified.
3Varattuis equal tobookedBooked
4Peruttuis equal tocancelledCancelled
5Siirretty(not mapped)
6Alkanutmaps loosely toarrivedArrivedThere is no status for an appointment being in process in FHIR. In FHIR this information is tracked with the status of the Encounter resource.
7Toteutunutmaps loosely tofulfilledFulfilledThere is no status for an appointment being in process in FHIR. In FHIR this information is tracked with the status of the Encounter resource.
8EhdotettunarrowerproposedProposedThe code proposed can be used to highlight that none of the participants have finalized their acceptance, or that there is still uncertainty about the time.
is equivalent topendingPendingThe code pending is a more generic match to Ehdotettu.
9Saapumattais equal tonoshowNo Show
10Ilmoittautunutis equal tochecked-inChecked In