Requestor not authorized (no user session with valid ID-Token available)
Requestor role is not in the list of allowed user groups
Device registration does not exist (if requestor role is oid_versicherter only)
Health record is in state UNKNOWN or INITIALIZED
Request conflicts with the current state of the health record
If the insurant objected to the medication process or objected to the submission of prescription and dispensation data into the ePA system, the Medication Service is locked.
EPA Capability Statement für Clients des ePA Medication Service
Dieses Capability Statement legt die Anforderungen an ePA Clients fest, die den Medication Service der verwenden. Es definiert die unterstützten Interaktionen, erforderliche HTTP Header sowie erwartete Status Codes.
gematik GmbH / Dieser Implementation Guide ist lizenziert unter [Apache License](./license.html), Version 2.0.
Return resources linked to by the given target
Medication.ingredient.item as CodeableConcept
MedicationRequest.medication as Reference
MedicationDispense.medication as Reference
MedicationStatement.medication as Reference
MedicationStatement.derivedFrom as Reference
MedicationStatement.basedOn mit Extension:is-emp = true
Base64 encoded FHIR Organization resource in JSON format used to identify the originator of the request
Requesting Organization Header exceeds maximum size
Invalid Data Structure in Medication Service
Operation %s not allowed for resource %s
MedicationStatement could not be linked to an eMP-Entry successfully
Mismatch between acknowledged and current eMP chronology ID
MedicationStatement could not be unlinked from an eMP-Entry successfully
Target References - usually version specific
When the activity was recorded / updated
Update Conflict (server current version = %s, client version referenced = %s)
The operation can only be executed within a batch context