Versie van 27 aug 2020 14:19

1 Introduction

This page describes how a patient can manage his health care related appointments in a MedMij context using the HL7 FHIR Standard. Initially, this guide will contain information on how to request existing appointment information. Guidance on how to create, update, or cancel appointments will be available here as well at a later stage. The functional requirements for this use case can be found in the functional design.

Note: This implementation guide builds on the general guidelines described in the use case overarching principles.

2 Use case: retrieve appointments

This FHIR implementation guide assumes that the PHR system is able to make a connection to the right XIS that contains the patient's information. It does not provide information on finding the right XIS nor does it provide information about security. Moreover, each transaction is performed in the context of a specific authenticated patient, for whose context (token) has been established using the authentication mechanisms described in the 'Afsprakenstelsel'. Each XIS Gateway is required to perform filtering based on the patient associated with the context for the request, so only the records associated with the authenticated patient are returned. For this reason, search parameters should not be included for patient identification.

2.1 Introduction

The goal of this use case is to give patients an overview of their appointments with all healthcare providers. The appointment information that is shared with the patient will contain start and end date/time, location, type of appointment, patient instructions, health care professionals present. Below is described how a PHR can retrieve this information and how a XIS should make this information available.

2.2 Actors

Actor	Role
Patient (using a PHR)	Request appointments from the XIS
Healthcare professional (using a XIS)	Serves appointments to the PHR

2.3 Invocations

2.3.1 Client - PHR

2.3.1.1 Search for appointments

The PHR executes an HTTP GET conform to the FHIR RESTful and search specification against the XIS's Appointment endpoint. This search query URL is configurable by the PHR and has the following format:

GET [base]/Appointment?date=[date]

The PHR may use, and the XIS shall be capable of processing, the following parameters to configure the search query:

Observation
Name	Type	Description	Example
`date`	date	Appointment date/time based on start date/time.	Retrieve appointments with a start date/time from 01-01-2018 onwards: GET [base]/Appointment?date=gt2017-12-31 Retrieve appointments with start date/time from 01-01-2018 until 01-03-2018: GET [base]/Appointment?date=ge2018-01-01&date=lt2018-03-01

2.3.2 Server - XIS

The returned data to the PHR should conform to the HCIMS and their associate profiles listed in the table below.

Name NL	Name EN	FHIR Resource	URL profile
Patient	Patient	Patient	http://fhir.nl/fhir/StructureDefinition/nl-core-patient
Zorgverlener	HealthProfessional	Practitioner	http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner
Zorgaanbieder	HealthcareProvider	Organization	http://fhir.nl/fhir/StructureDefinition/nl-core-organization
Afspraak	Appointment	Appointment	http://nictiz.nl/fhir/StructureDefinition/eAfspraak-Appointment

Example instances of FHIR resources can be found on Simplifier. Please note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of any information standard.

3 Use case: book an appointment

4 Use case: cancel/reschedule an appointment

5 Terminology, NamingSystems, Mappings

5.1 Terminology

Relevant ValueSets can be found through the ValueSet bindings in the listed StructureDefinitions. All ValueSets can be found here here and can be downloaded as a .zip in XML or JSON format.

5.2 NamingSystems

Relevant NamingSystems can be found here.

5.3 Mappings

A FHIR ConceptMap resource is provided when a FHIR value set is used instead of a HCIM value set. A ConceptMap maps the values between the two value sets. These ConceptMaps can be found here.

An explanation about mappings can be found at Mapping of coded concepts.

6 Release notes

Release notes can be found on the functional design page.

@@ Regel 1: / Regel 1: @@
 __NUMBEREDHEADINGS__
 {{DISPLAYTITLE:MedMij FHIR Implementation Guide - eAfspraak {{VersieInfo|eAfspraak}}}}
-{{MedMij:V2020.01/Issuebox_FHIR_IG}}
+{{MedMij:Vprepub/Issuebox_FHIR_IG}}
 [[Bestand:EAfspraak_icoon_zonder_tekst.png |link=|links |87px|eAfspraak]]
@@ Regel 7: / Regel 7: @@
 <imagemap>Bestand:Leeswijzer-technisch-banner 03 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
 circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
-circle 1013 224 212 [[MedMij:V2020.01/OntwerpeAfspraken|Functioneel]]
+circle 1013 224 212 [[MedMij:Vprepub/OntwerpeAfspraken|Functioneel]]
-circle 1787 230 212 [[MedMij:V2020.01/FHIR_IG|Technisch]]
+circle 1787 230 212 [[MedMij:Vprepub/FHIR_IG|Technisch]]
 desc none
 </imagemap>
@@ Regel 16: / Regel 16: @@
 =Introduction=
 This page describes how a patient can manage his health care related appointments in a MedMij context using the HL7 FHIR Standard. Initially, this guide will contain information on how to request existing appointment information. Guidance on how to create, update, or cancel appointments will be available here as well at a later stage.
-The functional requirements for this use case can be found in the [[MedMij:V2020.01/Ontwerpen|functional design]].
+The functional requirements for this use case can be found in the [[MedMij:Vprepub/Ontwerpen|functional design]].
-'''Note''': This implementation guide builds on the general guidelines described in the [[MedMij:V2020.01/FHIR_IG#Use case overarching principles|use case overarching principles]].
+'''Note''': This implementation guide builds on the general guidelines described in the [[MedMij:Vprepub/FHIR_IG#Use case overarching principles|use case overarching principles]].
 =Use case: retrieve appointments=
@@ Regel 116: / Regel 116: @@
 A FHIR ConceptMap resource is provided when a FHIR value set is used instead of a HCIM value set. A ConceptMap maps the values between the two value sets. These ConceptMaps can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ConceptMap here].
-An explanation about mappings can be found at [[MedMij:V2020.01/FHIR_IG#Mapping_of_coded_concepts|Mapping of coded concepts]].
+An explanation about mappings can be found at [[MedMij:Vprepub/FHIR_IG#Mapping_of_coded_concepts|Mapping of coded concepts]].
 =Release notes=
-Release notes can be found on the [[MedMij:V2020.01/OntwerpeAfspraak#Release_notes| functional design page]].
+Release notes can be found on the [[MedMij:Vprepub/OntwerpeAfspraak#Release_notes| functional design page]].

MedMij:V2020.01/FHIR eAfspraak: verschil tussen versies