Required Systemroles
For a legacy MP6.12 AIS
-
INF.BAS.2025
-
GBZ.BES.2022
-
DVZA.BES.2020
-
BES.MG.HL7m.68.1
-
ATT.JWT.3
-
MP.MVSb.2011
Routing
-
MedMij routing is steered across AoF route through Systemrol > ATT.JWT.3.
-
This routing is also required for legacy MP6.12 QURX sources which need to be addressed through the AoF route of the VnC and BTD.
Building blocks
These are the building blocks which are relevant for the MP6.12 data sources.
These are the building blocks which are queriable via a LatestStop query.
MP6.12 data sources will give no results for the LatestStop query.
|
Building block (EN) |
Building block (NL) |
FHIR resource |
FHIR profile |
MP6.12 via QURX |
LatestStop Query |
|---|---|---|---|---|---|
|
MedicationAgreement |
Medicatieafspraak |
MedicationRequest |
http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement |
- |
Ja |
|
VariableDosingRegimen |
WisselendDoseerschema |
MedicationRequest |
http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen |
- |
Ja |
|
DispenseRequest |
Verstrekkingsverzoek |
MedicationRequest |
http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest |
- |
|
|
AdministrationAgreement |
Toedieningsafspraak |
MedicationDispense |
http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement |
Ja |
Ja
|
|
MedicationDispense |
Medicatieverstrekking |
MedicationDispense |
http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense |
Ja |
|
|
MedicationUse2 |
Medicatiegebruik2 |
MedicationStatement |
- |
|
|
|
MedicationAdministration2 |
Medicatietoediening2 |
MedicationAdministration |
http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2 |
- |
|
Error handling
LSP+ in its role as DVZA supports only the Late Availability Check (mandatory) and does not implement the Early Availability Check (optional) as defined by the MedMij Afsprakenstelsel.
See Functies en gegevens, Core | MedMij Afsprakenstelsels - De vroege beschikbaarheidstoets (optioneel)
The MedMij requirement states:
"De beschikbaarheidstoets omvat de controle op de aanwezigheid van een behandelrelatie (kent de Aanbieder de Persoon). Daarnaast wordt de leeftijd van de Persoon gecontroleerd en wordt getoetst of de Aanbieder de gewenste gegevens beschikbaar heeft."
Within the LSP+ DVZA implementation, this requirement is interpreted as follows:
-
When no active treatment relationship exists, but patient data is available, the available data must still be returned.
-
The existence of a current or historical treatment relationship is considered sufficient to meet the treatment relationship criterion.
-
A patient record that is actively shielded and a patient for whom no record exists should result in the same outcome.
Consequently, the requirement is interpreted as:
"De beschikbaarheidstoets omvat de controle op de aanwezigheid van een behandelrelatie of eerdere behandelrelatie (kent de Aanbieder de Persoon). Daarnaast wordt de leeftijd van de Persoon gecontroleerd en wordt getoetst of de Aanbieder de gewenste gegevens beschikbaar heeft."
The following HL7v3 error situations are expected from the XIS:
-
PATLFT: the patient does not meet the minimum age requirement.
-
KEY204: no patient record exists because no treatment relationship has ever existed.
-
KEY204: the patient record is actively shielded by the XIS.
-
NF: the patient is known but no matching data is available for the requested query.
The MedMij specification associates these situations with the Early Availability Check (optional) performed in Resource Interface 5, where the Resource Server determines that the availability condition cannot be met.
See Resource interface | MedMij Afsprakenstelsels
In the cases PATLFT and KEY204, a HTTP 403 Forbidden response with error value access_denied is returned by LSP+.
In the case NF, a HTTP 200 response with an empty result set is returned by LSP+.