Generated Mon Mar 23 14:17:11 GMT 2026, FHIR version 4.0.1 for de.gematik.epa.medication#1.3.1 (canonical = https://gematik.de/fhir/epa-medication (history)). See Full QA Report & IP
| Filename | Errors | Warnings | Hints |
| Build Errors | 0 | 0 | 0 |
| /workspaces/fhir-epa-medication/fsh-generated/resources/MedicationRequest-55b8a1f8-daeb-4d1e-a0e1-36279e2d9913 | 2 | 0 | 0 |
| /workspaces/fhir-epa-medication/fsh-generated/resources/Parameters-invalid-example-history-reference-not-allowed-emp-input | 1 | 0 | 0 |
| Path | Severity | Message | Validating |
| MedicationRequest.extension[4] (l33/c6) | error | Constraint failed: epa-no-history-reference: 'Die Referenz darf keine History-Referenz enthalten ('/_history/' ist nicht erlaubt). (value.where($this is Reference).reference.exists() implies value.where($this is Reference).reference.contains('/_history/').not())' (defined in https://gematik.de/fhir/epa-medication/StructureDefinition/emp-origin-medication-extension) Editor's Comment: This example is INTENTIONALLY INVALID to demonstrate that the invariant epa-no-history-reference correctly rejects versioned history references (/_history/). The validation error is expected. https://gematik.de/fhir/epa-medication/StructureDefinition/emp-origin-medication-extension#epa-no-history-reference | eMP MedicationRequest |
| MedicationRequest.extension[5].extension[0] (l41/c10) | error | Constraint failed: epa-no-history-reference: 'Die Referenz darf keine History-Referenz enthalten ('/_history/' ist nicht erlaubt). (value.where($this is Reference).reference.exists() implies value.where($this is Reference).reference.contains('/_history/').not())' (defined in https://gematik.de/fhir/epa-medication/StructureDefinition/emp-medicationrequest-activity-extension) Editor's Comment: This example is INTENTIONALLY INVALID to demonstrate that the invariant epa-no-history-reference correctly rejects versioned history references (/_history/). The validation error is expected. https://gematik.de/fhir/epa-medication/StructureDefinition/emp-medicationrequest-activity-extension#epa-no-history-reference | eMP MedicationRequest |
| Path | Severity | Message | Validating |
| Parameters.parameter[1].part[0] (l16/c10) | error | Constraint failed: epa-no-history-reference: 'Die Referenz darf keine History-Referenz enthalten ('/_history/' ist nicht erlaubt). (value.where($this is Reference).reference.exists() implies value.where($this is Reference).reference.contains('/_history/').not())' (defined in https://gematik.de/fhir/epa-medication/StructureDefinition/epa-op-add-emp-entry-input-parameters) Editor's Comment: This example is INTENTIONALLY INVALID to demonstrate that the invariant epa-no-history-reference correctly rejects versioned history references (/_history/). The validation error is expected. https://gematik.de/fhir/epa-medication/StructureDefinition/epa-op-add-emp-entry-input-parameters#epa-no-history-reference | EPA Operation addEMPEntry Input-Parameters |
Suppressed Messages (Warnings, hints, broken links)
Bundle Example Instances
Codesystems that cannot be resolved by tx.fhir.org
Context in Extensions Causes Validation Errors in Contained Resources
Dispite the warning tests prove the FHIR path expression to be correct
Draft Reference
Ignoring Warnings: Example Instances
Ignoring Warnings: Unavailable German ValueSets and CodeSystems
Ignoring Warnings: ValueSets and CodeSystems
Ignoring Warnings: We are using a custom template of our own
No display names for de-DE
Not an Error: Profiles Correctly Set in Medication.contained
Not resolvable
Operation Definition
SnomedCT version that cannot be resolved
This example is INTENTIONALLY INVALID to demonstrate that the invariant epa-no-history-reference correctly rejects versioned history references (/_history/). The validation error is expected.
Value sets that cannot be resolved by tx.fhir.org
Warning
We are using R4 and so this is fine for now
We dont want to pin versions in Profiles
We only want to use narratives if needed
We use bracket notation for some UCUM codes
We want to allow HTML tags in
must-support
Errors sorted by type