Frenda Wof-Connect FLC
0.1.2 - ci-build [WIP]

Frenda Wof-Connect FLC, published by Service Well AB. This guide is not an authorized publication; it is the continuous build for version 0.1.2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/servicewell/servicewell.fhir.se.frenda-wof-connect-flc/ and changes regularly. See the Directory of published versions

Artifacts Summary

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Operation Definitions

These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide.

Find appointment operation for Frenda

For input parameters that are codes, the simple FHIR token search parameter type is used instead of the complex Coding datatype. This allows either the 'GET' or the 'POST' syntax to be used to initiate the interaction in many cases. The Reference datatype is used for resources references, which allows the requester to use either a reference to existing resource, or an identifier (logical reference). Examples of both are shown below.

  • If multiple patients are provided as parameters, this conveys the need for a group appointment.
  • If more than one non-patient participant type of parameter is present (e.g. a Provider and a Location), the response SHOULD contain appointments with all of these participants (i.e, this is a logical 'AND'). If a particular participant type is repeated, the response SHOULD contain appointments with any of these participants and SHOULD be interpreted as the order of preference (i.e. this is a logical 'OR' and does not drive a joint appointment with multiple practitioners. locations or organizations). Ultimately the server is responsible for determining the first/best available appointment options to return.
  • References can be to an absolute URL, but the Scheduling Server can create or modify resources only on the resources on the server or a defined domain.
  • To set the upper limit on the total number of available appointment options to return use the standard _count search parameter. See the examples below for how this is implemented.
  • The Scheduling Server SHALL NOT include any held appointments (i.e. appointments that were reserved as a result of a previous $hold operation, and for which the holding period had not expired) in the list of potential appointments.

Knowledge Artifacts: Libraries

These define logic, asset collections and other libraries as part of content in this implementation guide.

FLC Liquid Templates

This library includes the LIQUID-templates and source sampledata used in this FLC-IG

Structures: Logical Models

These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.

BookAppointmentResponse (Extract Model)

Extract model for retrieving Frenda's booking response.
Extraction Base (Extract Model)

Standard base data (meta and data wrapper) captured with each extraction.
Frenda Appointment (Logical Model)

Logisk modell av Frenda Get Appointment, inkl. klinik, behandlare och behandling.
Frenda Available Slot (Logical Model)
Frenda Booking Response (Logical Model)
Frenda Clinic (Logical Model)

Logical Model for a Frenda clinic, including cost locations.
Frenda Clinic Treatments (Logical Model)

Summary per clinic with treaters and treatments that can be offered, which can be used as source for schedule.
Frenda Cost Location (Logical Model)

Logical Model representing a cost location within a Frenda clinic.
Frenda New Booking Request (Logical Model)

Logical model of Frenda NewBookingExternalRequest.
Frenda Patient Details (Logical Model)

Logical model of Frenda Details.
Frenda Patient Request (Logical Model)

Logical model of Frenda Patient Request.
Frenda Treater (Logical Model)

Person performing treatments (maps to Practitioner/PractitionerRole).
Frenda Treatment (Logical Model)

Bookable treatment/service as exposed by Frenda.
GetAppointmentById (Extract Model)

Extract model for retrieving a single booking from /api/appointment/booking.
GetAppointmentsByPatient (Extract Model)

Extract model for retrieving patient bookings from /api/patient/appointments (optionally filtered by period or clinic).
GetClinicTreatments (Extract Model)

Extract model for retrieving clinic treatments.
GetPatientDetails (Extract Model)

Extract model for retrieving patient details from /api/patient/details.
GetSlots (Extract Model)

Extract model for retrieving available booking slots.
Post Create Appointment (Extract Model)

Extract model for creating an appointment

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

Frenda Appointment

Frenda Appiontment derived from IHE_ITI_Appointment_Profile

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

WOF Portal Identifier types

Code system for the identifiertypes usen i WOF Portal

Terminology: Structure Maps

These define transformations to convert between data structures used by systems conforming to this implementation guide.

FLC BookAppointmentResponse

Structure Map for transforming Frenda BookAppointmentResponse to the IHE Scheduled Appointment Bundle.
FLC FindAppointments

Structure Map for transforming FindAppointments to FHIR
FLC GetAppointmentById

StructureMap for transforming FrendaBookingResponse from /api/appointment/booking to IHE Appointment.
FLC GetScheduleContext

StructureMap for transforming GetScheduleContext to a context Bundle.
FLC GetSchedules

Structure Map for transforming GetSchedules to FHIR
FLC Patient Details

StructureMap for transforming PatientDetailsResponse from /api/patient/details to WofConnectPatient.
FLC appointmentsbypatient

StructureMap for transforming FrendaBookingResponse from /api/patient/appointments to IHE Appointments.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

AppointmentBundleExample
CreateAppointmentResponseExample
GetAppointmentByIdResultExample

Akut
GetAppointmentByPatientResultExample
GetPatientDetailsResultExample
GetScheduleContextOperationResult
GetScheduleExample1

An FLC output example Schedule resource for getting schedules from Frenda WOF Connect