Developer Guide - Application Architecture

FO Transactions as Systemroles and Profiles

The FO transactions are implemented as application system roles, which in turn are based on the platform profiles defined within the AORTA‑LSP AoF infrastructure.

The requirements for each application‑specific system role are described in the corresponding PvEs.

Each application‑specific system role is derived from, or composed of, one or more underlying AoF infrastructure GBx systemrole profiles.

For example:
The MP‑MGR transaction is implemented using the ‘MP Opvragend Systeem’ application system role. This role is composed of the ‘ZA Opvragend Systeem’ GBx systemrole profile, which itself is based on the ‘Client Systeem’ profile.

MedMij Systemroles and VZVZ components

For the legacy MP6.12 and MP-9.0.7 Information Standards, the MedMij Afsprakenstelsel supports the following Gegevensdiensten:

• Gegevensdienst #31 – Verzamelen Medicatiegegevens 9.0

• Gegevensdienst #35 – Verzamelen Medicatiegegevens 9.A

For the MP9v3 Information Standard, the MedMij Afsprakenstelsel supports the following Gegevensdienst:

• Gegevensdienst #68 – Verzamelen Medicatiegegevens 9 versie 3.0.0

Capabilities of LSP+ towards service (Gegevensdienst) #68:

• Access to legacy MP6.12 data sources, including AIS systems implementing the QURX Verstrekkingenlijst transaction. Data is exposed as MP9v3 Therapeutic Agreements (TAs) and Medication Dispense Events (MVEs). The required HL7v3-to-FHIR and MP6.12-to-MP9v3 transformations are performed by the BTD.

• Access to native MP9v3 FHIR data sources.

• Access to native MP9v3 HL7v3 data sources. The required HL7v3-to-FHIR transformations are performed by the BTD before the data is exposed through the service.

• LSP+ as as DVZA and LSP as broker implement the systemrole MP-MGB-3.0.0-FHIR for the service (Gegevensdienst) #68.

Limitations