FHIR Implementation Guide Medication Process 9 version 3.0.0-rc.1 for patient use cases

Dit is een tijdelijke pagina met wijzigingen voor issue MP-1139. De gepubliceerde versie vind je hier.

Deze versie zal worden getoetst tijdens de kickstart medicatieoverdracht. De versie is niet geschikt voor gebruik buiten deze beproeving.

1 Introduction

This is the implementation guide (IG) for the information standard Medication Process 9 (MP9) version 3.0.0-rc.1 for patient use cases (MedMij) using the HL7® FHIR® standard. The MP9 standard for MedMij is described in this functional specification and further specified here using FHIR version R4. This implementation guide assumes that the reader is familiar with both the functional specification of both MP9 and MedMij and this version of FHIR.

This document is a specification of FHIR Implementation Guide Medication Process 9, only applicable to the patient use cases. The guidelines as specified in the MedMij FHIR Implementation Guide apply. This document extends the general FHIR Implementation Guide with the specification of the 'Afsprakenstelsel'.

This IG first describes the boundaries and relationships where they differ between the MP9 and MedMij IG, after which the implementation is described per relevant transaction.

2 Boundaries and relationships

Both the MP9 Boundaries and relationships and the MedMij Overarching principles apply. The following sections highlight the points where these two documents contradict and provides guidance on which principles to follow.

2.1 'Use cases' or 'transactions'

Where MP9 uses the term 'transaction', MedMij generally uses the term 'use case'. On this page, the terms are used interchangeable.

2.2 Patient identification

Where the MP9 describes the use of patient.identifier search parameters, the MedMij use cases use the authentification method outlined by the MedMij 'Afsprakenstelsel', using Oauth2 tokens.

3 Transactions

This section describes the FHIR implementation of the Retrieve and Serve Medication Data transactions (for MedMij) listed in the functional specification. Each transaction hyperlinks to the functional definition in an ART-DECOR publication. The ART-DECOR publication details which data elements are expected to be supported (cardinality and conformance).

3.1 Medication data (Retrieve/Serve)

The retrieve medication data transaction is used by the client to retrieve medication data from a server. The client can retrieve its desired information by searching for specific medication building blocks.

Transaction group	Transaction	Actor	System role	FHIR CapabilityStatement
Medication data (PULL)	Retrieving medication data	Client	MP-MGR
	Serving medication data	Server	MP-MGB

3.1.1 Retrieve (request message)

When a patient or healthcare professional wants to obtain all medication data or specific parts matching various parameters, they issue a retrieve medication data request message. This message uses the HTTP GET method parameterized query against the server's medication FHIR endpoints. These endpoints can be one of the following:

• MedicationRequest
• MedicationDispense
• MedicationStatement
• MedicationAdministration

The search interaction is performed by an HTTP GET conform the FHIR search specification, as shown below. This URL is configurable by the client by configuring the search query. Multiple request messages may be needed to retrieve all desired information.

GET [base]/[type]{?[parameters]}

3.1.1.1 Search parameters

All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients.

MP9 search parameter	Description	FHIR search parameter	FHIR resource	Example 4 Release notes Release notes can be found here. 5 Footnotes