-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'origin/rc/main-stufe-4' into feat/pat-m…
…erge # Conflicts: # Resources/input/fsh/aliases.fsh
- Loading branch information
Showing
27 changed files
with
887 additions
and
204 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
12 changes: 12 additions & 0 deletions
12
...rtraeglichkeit/AllergieUnvertraeglichkeit_AnmerkungenZuDenMustSupportFeldern.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
### Anmerkungen zu den Must-Support-Feldern | ||
|
||
@```from | ||
StructureDefinition | ||
where | ||
url = 'https://gematik.de/fhir/isik/StructureDefinition/ISiKAllergieUnvertraeglichkeit' | ||
for differential.element | ||
where mustSupport = true | ||
and short.exists() | ||
select | ||
Feldname: id, Kurzbeschreibung: short, Hinweise: comment | ||
``` |
5 changes: 5 additions & 0 deletions
5
...ide/markdown/AllergieUnvertraeglichkeit/AllergieUnvertraeglichkeit_Beispiele.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
### Beispiel | ||
|
||
Valides Beispiel Allergie/Unverträglichkeit: | ||
|
||
{{json:ISiKAllergieUnvertraeglichkeitBeispiel1}} |
62 changes: 62 additions & 0 deletions
62
...markdown/AllergieUnvertraeglichkeit/AllergieUnvertraeglichkeit_Interaktionen.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,62 @@ | ||
### Interaktionen | ||
|
||
Für die Ressource AllergyIntolerance MUSS die REST-Interaktion "READ" implementiert werden. | ||
|
||
Folgende Suchparameter sind für das Bestätigungsverfahren relevant, auch in Kombination: | ||
|
||
1. Der Suchparameter "_id" MUSS unterstützt werden: | ||
|
||
Beispiele: | ||
|
||
```GET [base]/AllergyIntolerance?_id=test``` | ||
|
||
Anwendungshinweise: Weitere Informationen zur Suche nach "_id" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Parameters for all resources"](https://hl7.org/fhir/R4/search.html#all). | ||
|
||
1. Der Suchparameter "clinical-status" MUSS unterstützt werden: | ||
|
||
Beispiele: | ||
|
||
```GET [base]/AllergyIntolerance?clinical-status=active``` | ||
|
||
Anwendungshinweise: Weitere Informationen zur Suche nach "AllergyIntolerance.clinicalStatus" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Token Search"](https://hl7.org/fhir/R4/search.html#token). | ||
|
||
Dieser Suchparameter ist für die Umsetzung des IHE QEDm Profils verpflichtend. | ||
|
||
1. Der Suchparameter "patient" MUSS unterstützt werden: | ||
|
||
Beispiele: | ||
|
||
```GET [base]/AllergyIntolerance?patient=Patient/123``` | ||
|
||
Anwendungshinweise: Weitere Informationen zur Suche nach "AllergyIntolerance.subject" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Reference Search"](https://www.hl7.org/fhir/R4/search.html#reference). | ||
|
||
1. Der Suchparameter "onset" MUSS unterstützt werden: | ||
|
||
Beispiele: | ||
|
||
```GET [base]/AllergyIntolerance?onset=2015-01-01T12:00:23Z+02:00``` | ||
|
||
Anwendungshinweise: Weitere Informationen zur Suche nach "AllergyIntolerance.onset[x]" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Date Search"](https://hl7.org/fhir/R4/search.html#date). | ||
|
||
1. Der Suchparameter "date" MUSS unterstützt werden: | ||
|
||
Beispiele: | ||
|
||
```GET [base]/AllergyIntolerance?date=2015-01-01T12:00:23Z+02:00``` | ||
|
||
Anwendungshinweise: Weitere Informationen zur Suche nach "AllergyIntolerance.recordedDate" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Date Search"](https://hl7.org/fhir/R4/search.html#date). | ||
|
||
1. Der Suchparameter "category" KANN unterstützt werden: | ||
|
||
Beispiele: | ||
|
||
```GET [base]/AllergyIntolerance?category=environment``` | ||
|
||
1. Der Suchparameter "type" KANN unterstützt werden: | ||
|
||
Beispiele: | ||
|
||
```GET [base]/AllergyIntolerance?type=allergy``` | ||
|
||
|
||
--- |
10 changes: 10 additions & 0 deletions
10
...rkdown/AllergieUnvertraeglichkeit/AllergieUnvertraeglichkeit_Kompatibilitaet.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
### Kompatibilität | ||
|
||
|
||
Für das Profil ISiKAllergieUnvertraeglichkeit wird eine Kompatibilität mit folgenden Profilen angestrebt; allerdings kann nicht sichergestellt werden, dass Instanzen, die gegen ISiKAllergieUnvertraeglichkeit valide sind, auch valide sind gegen: | ||
* [das Profil KBV_PR_Base_AllergyIntolerance der KBV](https://fhir.kbv.de/StructureDefinition/KBV_PR_Base_AllergyIntolerance) | ||
* [das Profil EMDAF_PR_AllergyIntolerance der GEVKO](https://fhir.gevko.de/StructureDefinition/EMDAF_PR_AllergyIntolerance) | ||
* [das Profil AllergyIntolerance-uv-ips der International Patient Summary](http://hl7.org/fhir/uv/ips/StructureDefinition/AllergyIntolerance-uv-ips) | ||
|
||
Hinweise zu Inkompatibilitäten können über die [Portalseite](https://service.gematik.de/servicedesk/customer/portal/16) gemeldet werden. | ||
--- |
7 changes: 7 additions & 0 deletions
7
...de/markdown/AllergieUnvertraeglichkeit/AllergieUnvertraeglichkeit_Motivation.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
### Motivation | ||
|
||
Die Möglichkeit, auf eine Übersicht der Allergien und Unverträglichkeiten eines Patienten zuzugreifen, ist eine wichtige Funktionen im klinischen Behandlungsablauf. Dies gilt insbesondere, aber nicht ausschließlich, im Bereich der Arzneimitteltherapiesicherheit. | ||
|
||
In FHIR werden Allergien und Unverträglichkeiten mit der [AllergyIntolerance](https://hl7.org/fhir/R4/allergyintolerance.html)-Ressource repräsentiert. | ||
|
||
--- |
27 changes: 27 additions & 0 deletions
27
...nGuide/markdown/AllergieUnvertraeglichkeit/AllergieUnvertraeglichkeit_Profil.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
### Profil | ||
|
||
@``` | ||
from StructureDefinition where url = 'https://gematik.de/fhir/isik/StructureDefinition/ISiKAllergieUnvertraeglichkeit' select Name: name, Canonical: url | ||
``` | ||
{{tree:https://gematik.de/fhir/isik/StructureDefinition/ISiKAllergieUnvertraeglichkeit, hybrid}} | ||
--- | ||
**Terminology Bindings** | ||
@``` | ||
from StructureDefinition | ||
where url in ('https://gematik.de/fhir/isik/StructureDefinition/ISiKAllergieUnvertraeglichkeit' ) | ||
for differential.element | ||
select | ||
Path: path, | ||
join binding.where(valueSet.exists()) | ||
{ | ||
Name: valueSet.substring((9 + valueSet.indexOf('ValueSet/'))), | ||
Strength: strength, | ||
URL: valueSet | ||
} | ||
``` | ||
|
||
--- |
3 changes: 3 additions & 0 deletions
3
...mentationGuide/markdown/Datenobjekte/Datenobjekte_AllergieUnvertraeglichkeit.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
## Allergie/Unverträglichkeit [(AllergyIntolerance)](https://hl7.org/fhir/R4/allergyintolerance.html) | ||
|
||
--- |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
32 changes: 32 additions & 0 deletions
32
ImplementationGuide/markdown/KontaktGesundheitseinrichtung/Kontakt_Includes.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
### Verkettete Suchparameter (Chaining und Reverse Chaining) | ||
|
||
Für Suchparameter vom Typ 'Reference' MÜSSEN die Festlegungen für [Chaining](https://hl7.org/fhir/R4/search.html#chaining) und [Reverse Chaining](https://hl7.org/fhir/R4/search.html#has) verpflichtend implementiert werden. Chaining und Reverse Chaining MUSS für alle Suchparameter über alle Ebenen und Datenobjekte hinweg (potentiell in Kombination) unterstützt werden. | ||
|
||
Alle zu unterstützenden verketteten Suchparameter auf den entsprechenden Referenzen sind im CapabilityStatement unter ```CapabilityStatement.rest.resource.searchInclude``` bzw. ```CapabilityStatement.rest.resource.searchRevInclude``` angegeben. Siehe {{pagelink:ImplementationGuide/markdown/CapabilityStatement.md}} | ||
|
||
Weitere Informationen und Beispiele zur Suche nach verketteten Parametern finden sich in {{pagelink:ImplementationGuide/markdown/UebergreifendeFestlegungen/UebergreifendeFestlegungen_Suchparameter.md, text:diesem IG unter Suchparameter}} und in der FHIR-Basisspezifikation im [Abschnitt "Chained Parameters"](https://hl7.org/fhir/R4/search.html#chaining) und im [Abschnitt "Reverse Chaining"](https://hl7.org/fhir/R4/search.html#has). | ||
|
||
Die verketteten Suchparameter des Profils ```Encounter``` hängen wie folgt mit den festgelegten {{pagelink:ImplementationGuide/markdown/Zusammenfassung/UseCases.md, text:Anwendungsfällen (Use Cases)}} zusammen: | ||
|
||
|
||
1. Der verkette Suchparameter ```Encounter:patient``` unterstüzt den Anwendungsfall: | ||
|
||
Um für einen Patienten {{pagelink:ImplementationGuide/markdown/Zusammenfassung/UseCases.md, text:eindeutig}} zu den aktuell vorliegenden {{pagelink:ImplementationGuide/markdown/Zusammenfassung/UseCases.md, text:Fall}} identifizieren zu können {{pagelink:ImplementationGuide/markdown/Zusammenfassung/UseCases.md, text:Verwechslung}} auszuschließen. | ||
|
||
1. Der verkette Suchparameter ```Encounter:subject``` unterstüzt den Anwendungsfall: | ||
|
||
Um für eine Person {{pagelink:ImplementationGuide/markdown/Zusammenfassung/UseCases.md, text:eindeutig}} den aktuell zugehörigen Kontakt identifizieren zu können auszuschließen. | ||
|
||
1. Der verkette Suchparameter ```Encounter:part-of``` unterstüzt den Anwendungsfall: | ||
|
||
Um einem Kontakt eindeutig als Teil einer {{pagelink:ImplementationGuide/markdown/Zusammenfassung/UseCases.md, text:Behandlugsjourney}} identifizieren zu können. | ||
|
||
1. Der verkette Suchparameter ```Encounter:diagnosis``` unterstüzt den Anwendungsfall: | ||
|
||
Um bei einem vorliegenden Fall {{pagelink:ImplementationGuide/markdown/Zusammenfassung/UseCases.md, text:eindeutig}} zu all die zugehörigen {{pagelink:ImplementationGuide/markdown/Zusammenfassung/UseCases.md, text:Diagnosen}} zu finden. | ||
|
||
1. Der verkette Suchparameter ```Encounter:account``` unterstüzt den Anwendungsfall: | ||
|
||
Um bei einem vorliegenden Fall die korrekte {{pagelink:ImplementationGuide/markdown/Zusammenfassung/UseCases.md, text:eindAbrechnungeutig}} mit all den erbrachten {{pagelink:ImplementationGuide/markdown/Zusammenfassung/UseCases.md, text:Leistungen}} zuordnen zu können. | ||
|
||
--- |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.