-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Anlage Profil und Datenobjekt-Seite für QuestionnaireResponse
- Loading branch information
1 parent
00ea90a
commit 5f407da
Showing
19 changed files
with
175 additions
and
74 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
70 changes: 70 additions & 0 deletions
70
ImplementationGuide/markdown/Datenobjekte/ISiKFormulardaten.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,70 @@ | ||
--- | ||
canonical: https://gematik.de/fhir/isik/v3/Terminplanung/StructureDefinition/ISiKFormulardaten | ||
expand: 2 | ||
--- | ||
|
||
## ISiKFormulardaten [(QuestionnaireResponse)](https://hl7.org/fhir/R4/questionnaireresponse.html) | ||
|
||
### Motivation | ||
ISiKQuestionnaireResponse dient im Kontext der Terminplanung dazu strukturierte, formularbasierte Zusatzinformationen vom Termin-Requestor an das Termin-Repository zu übermitteln (vgl. {{pagelink:ImplementationGuide/markdown/Datenobjekte/ISiKNachrichtCommunication.md, text:'ISiKCommunication.payload.contentAttachment'}}). | ||
|
||
Konkret kann die QuestionnaireResponse dazu genutzt werden, vom Patienten bzw. dem Benutzer eines Terminbuchunsportals erhobene Informationen zu übermitteln, die für die Terminplanung von Relevanz sind, z.B. Fragen zu Symptomen, Anamnese, benötigten Mobilitätshilfen usw. | ||
|
||
Die Questonnaire-Ressource dient in FHIR dazu, solche Fragen im Sinne eines Formulars zu spezifizieren, Antwortmöglichkeiten vorzugeben, gegebene Antworten zu Validieren, und diese Formulare in standardisierter Form zwischen verschiedenen Systemen austauschbar zu machen. | ||
|
||
In dieser Ausbaustufe ist die Frage nach der Festelegung und dem Austausch der Formulardefinitionen jedoch noch außen vor. Zunächst geht es nur um die Frage, wie die Informationen, die über Formulare erfasst wurden, strukturiert kommuniziert und in den empfangenden Systemen (ohne Kenntnis der Formulardefinition) zur Anzeige gebracht werden können. | ||
|
||
In künftigen Ausbaustufen, kann dieses Szenario erweitert werden um z.B. | ||
* Formulardefinitionen zwischen Termin-Repository und Termin-Requester auszutauschen ("KIS gibt vor, welche Informationen im Portal vom Patienten abgefragt werden sollen") | ||
* Formulardefinitionen an bestimmte Terminarten (Appointment.serviceType) zu binden ("Bei Impfterminen müssen andere Informationen vom Patienten erhoben werden als bei Check-Ups") | ||
* Weiternutzbare und -verarbeitbare FHIR-Ressourcen aus den QuestionnaireResponses zu extrahieren ("Aus den Angaben des Patienten zu seinen Allergien werden AllergyIntolerance-Ressourcen erstellt und in die Patientenakte übernommen") | ||
* Formularfelder mittels der über einen FHIR-Endpunkt verfügbaren Daten automatisch vorbelegen um redundante Datenerfassung zu minimieren ("Wenn der Patient bereits im Haus war, muss er seine benötigten Mobilitätshilfen nicht erneut eingegben, er muss lediglich bestätigen, dass die zuvor erfassten Daten weiterhin aktuell sind.") | ||
|
||
Um in der ersten Ausbaustufe des formularbasieren Datenaustauschs die Komplexität bei der Darstellung der erhobenen Informationen möglichst gering zu halten, | ||
müssen die Systeme, die formularbasierte Daten erfasen, die Einschränkungen des folgenden QuestionnaireResponse-Profils berücksichtigen: | ||
|
||
--- | ||
### Kompatibilität | ||
Das QuestionnaireResponse-Profil ist kompatibel zu | ||
* https://demis.rki.de/fhir/StructureDefinition/StatisticInformationBedOccupancy | ||
|
||
|
||
### FHIR-Profil | ||
|
||
|
||
<fql> | ||
from | ||
StructureDefinition | ||
where | ||
url = %canonical | ||
select | ||
Name: name, Canonical: url, Basis: baseDefinition | ||
</fql> | ||
<fql output="inline" headers="false"> | ||
from | ||
StructureDefinition | ||
where | ||
url = %canonical | ||
select | ||
Beschreibung: description | ||
with | ||
no header | ||
</fql> | ||
{{tree, buttons}} | ||
|
||
--- | ||
|
||
### Anmerkungen zu Must-Support-Feldern | ||
|
||
<fql output = "table" headers="true"> | ||
|
||
from | ||
StructureDefinition | ||
where | ||
url = %canonical | ||
for | ||
differential.element | ||
where | ||
mustSupport = true | ||
select Feldname: id, Kurzbeschreibung: short, Hinweise: comment | ||
</fql> |
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
2 changes: 1 addition & 1 deletion
2
...urces/fsh-generated/resources/StructureDefinition-ISiKMedizinischeBehandlungseinheit.json
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
2 changes: 1 addition & 1 deletion
2
Resources/fsh-generated/resources/StructureDefinition-ISiKNachricht.json
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
48 changes: 0 additions & 48 deletions
48
...h-generated/resources/StructureDefinition-ISiKTerminKontaktMitGesundheitseinrichtung.json
This file was deleted.
Oops, something went wrong.
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
Oops, something went wrong.